Jump to content
Reliance Jio & Reliance Mobile Discussion Forums

kapil_k

Members
  • Content count

    12
  • Joined

  • Last visited

Everything posted by kapil_k

  1. Fixing Pre "phone Error"

    This solution is *only* for people who have a semi-bricked Pre. For e.g. If even after reflashing with webosdoctor you get a "Phone Error" after you reboot, then thats because the radio wasn't programmed correctly. You have to now basically bypass the first-use / activation to get the phone to boot. Keep in mind that even after bypassing the first-use app you will still get the "Phone Offline" error when you boot up. But now its easy to fix because you can put the phone in diagnostic mode and use QPST/QXDM, etc. Note that you can easily create a webosdoctor version that bypasses the firstuse app using meta-doctor but that only works for versions > 1.2.1. For versions like 1.0.3 you have to manually unpack the .jar file and change a few files to get it to work. So I've taken the qinray - 1.0.3 v1 ROM and disabled first-use-app and enabled-developer mode. Most people know why the 1.0.3 version is important (There are other bypass roms like xxrake but they always crashed after 80% for me and didn't work) http://rapidshare.com/files/396531423/webos1.0.3qinray_bypass.jar.html
  2. Fixing Pre "phone Error"

    Hey, I'm not really an expert at this. I am learning too. After much trial and error I finally managed to learn a few things, and I almost bricked my pre in the process when I accidentally flashed an incorrect AMSS firmware. I don't want to make a mistake and damage your phone permanently ! You should ask mufaddal, hes quite experienced with the pre.
  3. I can get into the test mode menu using *#123580# or 47*869#123580. What is the command to enable SIO mode for SCH-B519?
  4. Fixing Pre "phone Error"

    Yes, but xxrake always crashes for me after 80% . Anyway after spending many hours I have created a QXDM script that works 100% of the time on 1.0.3 - qinray. The trick in my case was to set both esn and meid to 0 and then *reboot* and then repair meid. If I try that before rebooting it doesn't work for me and the NV write always fails. depends, in my case it used to get **** at the palm logo (before it starts flashing). hmm, I thought all you needed to do was to reblash to 1.0.3 bypass and repair meid again. Maybe I've just been lucky
×