Related
Hey,
I have a Telus Amaze 4G and I have lost my radio. Phone says it has an unknown Baseband/IMEI. Not sure where I went wrong/ lost my radio but this is a run down of what I've done to my handset so far:
- Rooted
- Flashed CWM recovery.
- Flashed EnergyRom.
- Sent phone to HTC because of suspected warranty issue. (Wouldn't Charge)
- Phone returned un-repaired from HTC.
- Charged battery externally, phone finally booted.
- Replaced CWM with 4EXT.
- Ran the Telus GB RUU exe from windows.
- Did the OTA ICS from the phone.
- Attempted upgrade to SpeedRom, failed because the OTA had failed, didn't realize this until the next around, this is where I think it went wrong. Had done a full wipe of all partitions, except SD from 4EXT in the process.
- Re-applied original Telus GB RUU.
- Re-applied Telus ICS OTA. this is when I realized I had no radio. I had not put in my SIM-Card since the phone was returned from HTC so not exactly sure when it stopped working but the OTA had installed correctly this time.
- Re-rooted.
- Did the wire-trick and obtained S-OFF.
- Flashed the latests JP hboot.
- Used fastboot to flash several radio.img files from various TMO and Telus RUUs, nada.
- Flashed the T-Mobile ICS RUU via hboot, still no radio.
- Extracted the rom from the Telus GB RUU and applied that via hboot, still no radio.
The only thread I could find where someone had mentioned the missing baseband on an amaze 4g, the only suggested fix was to reflash a stock, GB rom but that didn't work. Now I am at a loss at to what I could try next.
Any suggestions would be greatly appreciated.
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Jay_Rulen said:
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Click to expand...
Click to collapse
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Dark Nightmare said:
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Click to expand...
Click to collapse
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
inluck said:
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
Click to expand...
Click to collapse
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
inluck said:
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
Click to expand...
Click to collapse
I can't say, just keep your fingers crossed that it doesn't.
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
inluck said:
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
Click to expand...
Click to collapse
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
inluck said:
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
Click to expand...
Click to collapse
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
inluck said:
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
Click to expand...
Click to collapse
It's not the hboot. I gotta find the s-on thread, since you have to be on a stock bootloader before you s-on. I probably missed something.
Sent from an Amaaaaaazing place :-D
http://forum.xda-developers.com/showthread.php?t=1647728
I just remembered another trick as well, when you s-off the device, it relock your bootloader but it says "locked" not relocked, therefore when you s-off, do not flash the jb hboot when they ask you if you wanna flash it, then simply s-on via the fastboot command, voila!
Sent from an Amaaaaaazing place :-D
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
I was using Evolver 3D 2.5 ICS ROM when I noticed BiParanoid JB rom out there, so I tried the ROM...
Then I find the ROM not fully working for me so I tried to get back to KingCobra3D ICS ROM, and the problem was, every HTC rom didn't boot up although I flashed the boot.img via fastboot. I tried at least 5 ROMs doing that but all I get is stuck at boot. Then I try flashing any other rom like AOKP and BiParanoid and they all boot up. I am running EVO 3D GSM S-ON. Any help would be appriciated and sorry for my bad english.
Seems like there's a problem with AOKP rom's when you try to flash htc rom
wayphaax said:
I was using Evolver 3D 2.5 ICS ROM when I noticed BiParanoid JB rom out there, so I tried the ROM...
Then I find the ROM not fully working for me so I tried to get back to KingCobra3D ICS ROM, and the problem was, every HTC rom didn't boot up although I flashed the boot.img via fastboot. I tried at least 5 ROMs doing that but all I get is stuck at boot. Then I try flashing any other rom like AOKP and BiParanoid and they all boot up. I am running EVO 3D GSM S-ON. Any help would be appriciated and sorry for my bad english.
Seems like there's a problem with AOKP rom's when you try to flash htc rom
Click to expand...
Click to collapse
I would recommend relocking the phone "fastboot oem lock" and running the appropriate ruu off the computer. This will get you back to a completely stock htc android. From there you can re do the unlock on htcdev and flash any rom you like.
dessolator666 said:
I would recommend relocking the phone "fastboot oem lock" and running the appropriate ruu off the computer. This will get you back to a completely stock htc android. From there you can re do the unlock on htcdev and flash any rom you like.
Click to expand...
Click to collapse
I already put the PG86IMG.zip to my SD card, got in to bootloader, but it said this zip is wrong, although its for my region...
I tried running ruu too, but got stuck on instal...
So if I relock the phone its possible to get to stock?
Thank you for the reply
wayphaax said:
I already put the PG86IMG.zip to my SD card, got in to bootloader, but it said this zip is wrong, although its for my region...
I tried running ruu too, but got stuck on instal...
So if I relock the phone its possible to get to stock?
Thank you for the reply
Click to expand...
Click to collapse
yes, if you're not S-off you have to relock your bootloader for the RUU to flash
Thank you, will try that out
Sent from my Evo 3D GSM using xda app-developers app
Another thing, im little of newbie, so I just use "fastboot oem lock" and bootloader will relock or i have to do full project? I unlocked bootloader on htcdev
Sent from my Evo 3D GSM using xda app-developers app
wayphaax said:
Another thing, im little of newbie, so I just use "fastboot oem lock" and bootloader will relock or i have to do full project? I unlocked bootloader on htcdev
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Ok, so, connect your phone to the PC.
go into settings find "Enable USB Debugging" and turn it on.
On your computer, start command prompt(cmd) and navigate to the directory where your adb and fastboot are.
type "adb reboot bootloader" and wait for the phone to get into the bootloader
it should now say "fastboot USB"
in cmd type "fastboot oem lock"
your phone bootloader is now locked.
go to : http://forum.xda-developers.com/showthread.php?t=1208485 and find the RUU you need
with the phone in fastboot run the RUU.
assuming you have the right RUU it should have worked and your phone should now be fully stock HTC
to do any other flashing you're going to need to re unlock you bootloader using the htcdev method (or at least your old Unlock_Token though you might need a new one)
dessolator666 said:
Ok, so, connect your phone to the PC.
go into settings find "Enable USB Debugging" and turn it on.
On your computer, start command prompt(cmd) and navigate to the directory where your adb and fastboot are.
type "adb reboot bootloader" and wait for the phone to get into the bootloader
it should now say "fastboot USB"
in cmd type "fastboot oem lock"
your phone bootloader is now locked.
go to : http://forum.xda-developers.com/showthread.php?t=1208485 and find the RUU you need
with the phone in fastboot run the RUU.
assuming you have the right RUU it should have worked and your phone should now be fully stock HTC
to do any other flashing you're going to need to re unlock you bootloader using the htcdev method (or at least your old Unlock_Token though you might need a new one)
Click to expand...
Click to collapse
THANKS FOR THE HELP, it worked!! apriciate the help really!
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
I am S-ON and was on the JB OTA and was going to relock and run the RUU and get back to stock and take the latest update. I know i should have been S-OFF but was uncomfortable. OK now I am stuck on the white bootloader screen and I cant get into recovery or restart or even power down the phone just restarts. All i did was relocked and now im stuck like this. What do I do next? Run the RUU? I downloaded the RUU 3.15.651.16 - HBOOT 2.09 zip off the DirtyRacun site but it keeps telling me windowns cannot open the folder to let me run it as administrator. Any help would be much appreciated I have done this before and didnt have this problem.
xbmoyx said:
I am S-ON and was on the JB OTA and was going to relock and run the RUU and get back to stock and take the latest update. I know i should have been S-OFF but was uncomfortable. OK now I am stuck on the white bootloader screen and I cant get into recovery or restart or even power down the phone just restarts. All i did was relocked and now im stuck like this. What do I do next? Run the RUU? I downloaded the RUU 3.15.651.16 - HBOOT 2.09 zip off the DirtyRacun site but it keeps telling me windowns cannot open the folder to let me run it as administrator. Any help would be much appreciated I have done this before and didnt have this problem.
Click to expand...
Click to collapse
I am currently downloading the 3.15 RUU and am watching QBKing77's video on unrooting. He runs the RUU with the phone turned on. I cannot turn my phone on can I run this RUU with the phone in bootloader/Fastboot USB?
Steps 6, 7, 8, and 9 on the unlimited Io website have you relock and RUU from fastboot. You can stop there if you don't feel confident going for full s-off. Their Dirty racoon zip for windows has adb and fastboot in it. Just put the RUU.zip in there and run the commands from that directory.
Or wait for someone who knows more than me and be completely sure.
tilltheend714 said:
Steps 6, 7, 8, and 9 on the unlimited Io website have you relock and RUU from fastboot. You can stop there if you don't feel confident going for full s-off. Their Dirty racoon zip for windows has adb and fastboot in it. Just put the RUU.zip in there and run the commands from that directory.
Or wait for someone who knows more than me and be completely sure.
Click to expand...
Click to collapse
OK so I am currently downloading the RUU_PLUS_ROOT.zip from BigDaddy619's sig. Do I open a command prompt in the location of the download and type...
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU.zip
???? Sorry kinda noob at this and havent had this problem before. I am not trying to S-OFF just get back to Jellybean stock to take the latest OTA.
I'm not sure what that zip contains so I can't help with that.
On your first post you said you downloaded the RUU from the dirty racun site. It should be called "RUU.zip". That can be flashed through fastboot with those commands. Do you still have that file?
Edit: And steps 1-9 of the S-off procedure are to get you locked and RUU so you can be completely stock for the procedure. So you can stop there if you don't want to attempt s-off.
tilltheend714 said:
I'm not sure what that zip contains so I can't help with that.
On your first post you said you downloaded the RUU from the dirty racun site. It should be called "RUU.zip". That can be flashed through fastboot with those commands. Do you still have that file?
Edit: And steps 1-9 of the S-off procedure are to get you locked and RUU so you can be completely stock for the procedure. So you can stop there if you don't want to attempt s-off.
Click to expand...
Click to collapse
Yes I still have it on my desktop. It wont let me open it or extract it its a Zip file.
Ok. Leave it as a zip file, confirm that the md5 matches, and put it in your adb, fastboot directory. Since you said you relocked, I think you know where that is. Make sure you're locked, then run those commands one by one. And pay special attention to step 9:
"If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Especially this part
"you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
tilltheend714 said:
Ok. Leave it as a zip file, confirm that the md5 matches, and put it in your adb, fastboot directory. Since you said you relocked, I think you know where that is. Make sure you're locked, then run those commands one by one. And pay special attention to step 9:
"If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Especially this part
"you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Click to expand...
Click to collapse
Got it! Thanks for all your help man.
Sent from my EVO using xda premium
No problem.
Are you back up and running?
tilltheend714 said:
No problem.
Are you back up and running?
Click to expand...
Click to collapse
Yup! I'll stay unrooted until the new update for Viper rolls out, hopefully soon!
Sent from my EVO using xda premium
Can't wait for that update.
If you ever want to s-off and have questions send a pm. It's not as scary as it sounds.
tilltheend714 said:
Can't wait for that update.
If you ever want to s-off and have questions send a pm. It's not as scary as it sounds.
Click to expand...
Click to collapse
It just sucks that the only computer I have is a 64bit windows laptop. All that ubuntu talk confuses the hell outta me. I appreciate it though man ill keep that in mind if I ever want to s-off. :thumbup:
Sent from my EVO using xda premium
I'm still getting data disconnected even on the latest OTA man I was hoping it got fixed. Having to cycle airplane mode to get data to turn back on
I only have 64bit windows. I just used a live disc. Easy as downloading an iso from ubuntus website and burning it to a disc. 10 minutes to get familiar with ubuntu and download the files, and a couple fastboot commands. You were pretty much done with the procedure today . Then just eject the disc and store it for next time you need ubuntu.
Did you try updating prl and profile?
Nope but just did and am on a new PRL. Hopefully this helps.
Sent from my EVO using xda premium
Doesn't matter that the system is 64 bit, just download a 32 bit iso of Ubuntu. It's really not as hard as it seems. I would say it's actually more reliable on Ubuntu then windows
om4 said:
Doesn't matter that the system is 64 bit, just download a 32 bit iso of Ubuntu. It's really not as hard as it seems. I would say it's actually more reliable on Ubuntu then windows
Click to expand...
Click to collapse
Well seeing how long it takes for an update on this phone I may not need to S-OFF. I just flashed the latest OTA so I'm 100% up to date. As long as the S-ON support continues regarding ROMs I should be good. Maybe the next phone ill look into getting S-OFF out the gate.
Sent from my EVO using xda premium
Well its getting to be more of a hassle with each update. The first update disabled flashing kernels and radios, the next update blocked you from writing to the system, this one has an update to the touch panel which breaks more then a few roms. Add to that the hassle of having to flash stock rom/recovery to update firmware or flashing a ruu which can cause more problems then it solves.
om4 said:
Well its getting to be more of a hassle with each update. The first update disabled flashing kernels and radios, the next update blocked you from writing to the system, this one has an update to the touch panel which breaks more then a few roms. Add to that the hassle of having to flash stock rom/recovery to update firmware or flashing a ruu which can cause more problems then it solves.
Click to expand...
Click to collapse
Wow jeez didn't hear about any cons with the latest update. I pray Viper is still going to be OK.
Sent from my EVO using xda premium
I think so far only aosp roms and mean bean (and twrp of course) are affected by the touch panel update