i need to go back to stock but i cant use the ruu because of bootloader error i originally had the 2.31.651.7 stock which i rooted now i cant get back to stock so i can get my phone fixed or a new one.
Have a look at this thread by Il Duce.....There is an unroot tutorial, 3 different RUU methods and 2 threads to fix RUU errors.
http://forum.xda-developers.com/showthread.php?t=1063843
When i had an error with my hero i used this.....adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again....When my hero was having problems with RUU's and it worked obliviously.
Related
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Hi I was trying to make a rom and ended up in a bootloop, so i made a mistake and flashed the boot.img from the android sdk folder to my raider and now I can't get into hboot, but with adb can get into cwm. i did have a backup and can restore the backup.
now when the restore is complete i try to restart and the phone hangs at the htc logo, then the screen turns black. phone never boots.
any ideas on what might fix this?
Thanks
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Can you get back into HBOOT now that you did the restore?
I'm by far no expert but I'm curious if you can get back to HBOOT if you can put it into fastboot, re-lock the bootloader (fastboot oem lock) and then use the RUU to restore back to stock. That should fix the boot image and I you then can start the process over again by unlocking and playing.
That's what I did and I'm back to a non-bricked phone. You can get the Holiday (aka Raider) RUUs by searching these forums. Just download the one for your carrier.
Good luck
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Where did you find an RUU for the HTC Raider?
I need RUU. I am in japan,but there is some thing wrong with my vivid, factory reset did not work....I can just see htc logo and then att logo, and then...though there is a setup but when i click that it shut down directly.....can any one help me ?
http://forum.xda-developers.com/showthread.php?t=1416836
2nd post has the links for stock ruu for all carriers
Sent from my HTC PH39100 using XDA App
thank you sooooo much.
Sent from my HTC PH39100 using XDA App
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Many thanks! I thought that mine Raider was completly dead. Didn't want get into CWM only 2 lines for less than 0.25sec with messsage that is unable to get acces to cache then reboot and stuck with htc logo forever. Then i read this post and my Raider is get back to live.
Many thanks once again.
Thank you so much!
Hi, I tried to update the system on my phone and when it did a reboot after updating and installing, it is freezing on the white/logo startup screen. how can i proceed...?
Remove the battery to turn the phone off, and when turning back on, hold down the power+volume up buttons. This will put your phone in hboot mode and allow you to reflash your ROM from there.
Good luck.
Sent from my Incredible S using xda premium
thanks. Yes i did make it to that step. now i need to flash the official rom for my model which is S710e, but i found so many links that i'm confused which one is the official...can i have some indication...
thanks in advance
If you flashed a custom rom and it is stuck in white screen with logo, your boot partition is messed up. But no worries you can fix it.
Extract the boot.img file out of your custom rom (zip-file).
download the SDK files
put the boot.img in the same folder as the files
Boot phone in fast boot
connect phone through usb with a computer
open command prompt on the pc an go to folder
use command fastboot flash boot boot.img
wait 2 secs
reboot
whole proces takes maybe 10 min, very easy to do.
no i did not flash a custom rom. i just did a system update which was prompted to me on the phone itself; when i did this it got stuck on reboot. then i did a factory reset but it was in vain.
at this point what i want is to have my phone back as it was in the beginning...so I wish to know how i can flash a stock rom so that it will become like brand new. thanks.
atlam83 said:
... I wish to know how i can flash a stock rom so that it will become like brand new. thanks.
Click to expand...
Click to collapse
First, you have to know what your mainver is:
Boot into fastboot, open a cmd window in windows and type this:
Code:
fastboot getvar mainver
This will give you your mainver (e.g. 2.12.708.4)
And go here: http://www.filefactory.com/f/e45d6fe3dcf51228/
You'll find shipped rom list. The filenames are in format like this: RUU_[name][mainver][radio_version]_signed.exe You must select ones with WWE prefixes (for multi-language support) and higher mainvers than yours! For example, if your mainver is 2.12.708.4, then you can select RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed (this one's mainver is 2.33.669.2) in the shipped rom list.
Once you've downloaded, you'll face another problem: Flashing.
Flashing is not a real problem but needs some trickies.
The question: Have you rooted your phone?
If yes, this thread is your flashlight to enlighten your way..
If no, you have to obtain a goldcard. A goldcard is a special microSD which prevents the phone to check cid (Customer ID) while trying to flash an original rom. If you haven't created a goldcard yet and cannot boot your phone properly, find another Android based phone and insert your microSD card into it. Then read this thread to create your gold card. Once you've created your goldcard, then it's so easy for you to flash your original rom. Follow the steps in the link above (explaining how to flash).
hth.
-R
i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.
atlam83 said:
i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.
Click to expand...
Click to collapse
Did you previously use Revolutionary to gain S-Off on your phone. If so by trying to install the OTA update, you now have a HBOOT ROM mismatch. The OTA update requires that the HTC HBOOT 2.00.0000 be installed, but the Revolutionary S-Off HBOOT prevented the OTA from overwriting the hboot, thus creating the situation you are in.
Follow steps 1 - 2c on this thread.
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
The find the OTA file on your SD card and extract the file firmware.zip.
Copy this to the root of your SD card and rename it PG32IMG.zip and then reboot into bootloader and it should reflash the correct HBOOT and you should be good to go.
Thanks very much tpbklake, I managed to solve my issue following the thread you indicated. its been 3 weeks since last i used my mobile. Send it to various ppl including HTC (which did not want to fix my mobile) and no one fixed it. have tried that thread and now its fine working again )
HTC freezing on thie logo startup screen
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(
Aniok said:
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(
Click to expand...
Click to collapse
All you need to do is go to the Development section and upgrade from Revolutionary HBOOT 6.13.1002 to BlackRose 2.02.0002. That will allow your phone to boot.
http://forum.xda-developers.com/showthread.php?t=1509236
Thanx
..
Sent from my GT-I9300 using xda premium
Hi!
I have had some serious issues with my USB-port and am looking to send the phone back for warranty. Since the problem is the USB isn't working that well I have some issues regarding unrooting..
I found my RUU and extracted the rom.zip which I renamed to PG32IMG.zip and placed on my phone. Fastboot foudn it and started flashing and everything. But I've read that since I can't upgrade Hboot (I used Revolutionary to gain S-off) the phone won't start.
My question is: What should I do to get that working? The only thing I can do as far as I can see, is placing files on the SD-card named for auto-flashing in fastboot..
Any advice? Am I screwed? Profit?
BloomTwig said:
Hi!
I have had some serious issues with my USB-port and am looking to send the phone back for warranty. Since the problem is the USB isn't working that well I have some issues regarding unrooting..
I found my RUU and extracted the rom.zip which I renamed to PG32IMG.zip and placed on my phone. Fastboot foudn it and started flashing and everything. But I've read that since I can't upgrade Hboot (I used Revolutionary to gain S-off) the phone won't start.
My question is: What should I do to get that working? The only thing I can do as far as I can see, is placing files on the SD-card named for auto-flashing in fastboot..
Any advice? Am I screwed? Profit?
Click to expand...
Click to collapse
Which RUU did you use? Is there a comparable Android 2.3.3/Sense 2.1 that you could use instead?
Ok, I can't help meddling in this. I have managed to re-flash CWR and restore my old backup of my old 2.3.3/2.1 stock rom. I have also gotten the ADB set-up and if only I could get that rom.zip file from my RUU I will flash stock HBoot..
I used RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed since that was the one that my phone tried to download and install by it self. But when I run it, and enter my temp folder to get the rom.zip it isn't there (only an older version that isn't posible to open..)
advice?
EDIT: would this work instead? RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed
BloomTwig said:
Ok, I can't help meddling in this. I have managed to re-flash CWR and restore my old backup of my old 2.3.3/2.1 stock rom. I have also gotten the ADB set-up and if only I could get that rom.zip file from my RUU I will flash stock HBoot..
I used RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed since that was the one that my phone tried to download and install by it self. But when I run it, and enter my temp folder to get the rom.zip it isn't there (only an older version that isn't posible to open..)
advice?
EDIT: would this work instead? RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed
Click to expand...
Click to collapse
Copy the rom.zip file out of your temp dir and then open it with a 3rd party zip program (not default windows zip program)
The ruu in your edit will not have boot 2.0 although I'm not understnding why you don't just run the sense 3 ruu, after using the downgrade method in the s-on thread.
Yeah, that was the problem. Was trying to open the zip-files with windows zip-program. with that I also realized that using the first RUU would be better... I have, however, some trouble getting the downgrade thingie to work. It asks for root, it asks for gold card and it reboots in to recovery. But when it's at "checking version - main" it just gets stuck at "waiting for device"..
EDIT: sorry, I completly missed the fact that I need to create a gold card... sorryf or being a noob... will get back soon..
Communication breakdown. I was referring to the revert to s-on thread http://forum.xda-developers.com/showthread.php?t=1359555
Hi guys i decided i wanted to try the google play edition. So i got root, installed custom recovery and took a nandroid backup.
I then installed the latest play 4.3 rom. Didnt like it so went back into my cmw and restored the nandroid. Cool phone running fine again.
But i keep getting updates and when rebooting to install it would fire it into cmw and said couldnt mount. So i thought id reset the phone, and it rebooted to cmw again.
Read online it might be because the bootloader was unlocked. So i used the command fastboot oem lock in command prompt and relocked it. Now every time i try to reset the phone or update it im dropped to the bootloader
i thought an rru would fix it but i couldnt find one for my phone.
Its the htc one m7, was on o2 but i had it unlocked. It has hboot 1.54 so i couldnt get s-ff, baseband 41.17.3250.14. With the bootloader in tampered but relocked mode.
Any help would be appreciated. Just want my phone working again.
Ps i tried the guides to go back to stock. I dont have a 401 so i tried the rru, which i couldnt find for my phone and i cant seem to find the stock recovery for my device to reflash that see if its the problem, i tried a guide to extract from the nandroid, but altho i had root i couldnt see the folders. Tried the rom manager method as well and it says there is no backups altho there is one showing in cmw which i now cannot get into since relocking the bootloader
It is solved! For the answer look at my post below
Hello guys,
phone HTC one M8 Harman Kardon Edition
Happens that in my urge to unlock my phone sim lock I firstly changed the MID to unlocked SIM Dev edition MID and CID to SuperCID, well that went great until I was dumb enough to try to flash a Dev edition RUU to the phone and then i lost my TWRP recovery and everything went haywire. cause now i try to flash Recovery through fastboot and it suceeds but the phone gets stuck in entering recovery, Im not able to flash a Sprint RUU for HK because 1. i havent found one and 2. it probably wont load because of the MID which is 0P6B1200 if im correct.
please help me either load the Custom recovery so i can have access to adb, or any other way to fix it.
thank you!!
if someone could please give me any ideas, or contact anyone who could help me, it would be greatly apreciated, i can pay up to 20 usd through paypal if anyone can help me!!!
Change your MID back to Sprint and run the Sprint HK RUU...should be good to go.
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
thank you but no
Sarvesh.huddedar said:
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
Click to expand...
Click to collapse
I dont know what is going on but i did that already, even trying the new recovery image, and it gets stuck in the Entering Recovery... step
"Fastboot erase cache" and make sure you are flashing the correct version of twrp(change the MID back to the original one, this is dangerous if there is hardware difference across the 2 MIDs)
Guys all off your help was greatly apreciated but there was something wrong
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Hey
jseb14 said:
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Click to expand...
Click to collapse
Where do you type the "su ...." command into?