I have a rooted s-on China Unicom m8sw which I was using on kitkat. Finally got around to upgrading to lollipop by flashing back to stock using the RUU and letting the OTA update run, then flashing TWRP and rooting.
Instead of leaving well alone I restored an old kitkat TWRP backup, then decided I would get back to lollipop again by the same process of relocking the bootloader and letting the RUU run in hboot. Unfortunately, I got an error that the hboot version was too old. I hadn't realised the hboot must have been upgraded when I'd previously upgraded to lollipop. So the RUU wouldn't flash.
Now I seem to have lost my system altogether and my bootloader is relocked, and I am stuck on the white screen with the options to hboot, reboot, reboot fastboot or power down. Nothing works since I can't get into recovery and the phone can't boot into the system.
Have I bricked the phone for good? Feeling very desperate and would really appreciate any advice please.
Can you flash twrp and restore a clean backup
Gesendet von meinem HTC One_E8 mit Tapatalk
Thanks for that. I am such an idiot. I worked myself up into such a blind panic I completely forgot I can still use adb to manage my phone, unlock the bootloader and flash as you said. Thank you so very much for that mate!
Related
Hello
I was on dirby-H beta - Gingerbread 2.3.5 rom and wanted go back to stock rom. I did everything like in this guide (last time i had no problems to restore stock and s-on) and now im stuck on bootloader. Phone boots to bootloader only (im s-on now, hboot version 0.98.000, recovery is gone). When i run RUU it says update from version 10.47.401.4 to 1.28.401.1, reboots to bootloader. Everything goes fine until i get this. Adb gives me error: device not found. One thing that i forgot to do before downgrading hboot, i did no wipe.
So, does this means my phone is "bricked"? I have warranty for 2 years and im s-on, so my warranty isn't gone, right?.
I will be grateful for any help
Hi all, im looking for a bit of help in recovering my orange uk one s. I had unlocked the bootloader, rooted and installed cwm mod recovery without any problems.
I decided i wanted to do the ota 4.04 update which is where my problems started. I read that you needed to restore stock recovery and relock the bootloader to do this, which i did and now the phone wont boot
I can access the bootloader and recovery ok and can unlock and relock the bootloader ok. I still have the original cwm back up i made when i first rooted the phone, have tried to restore this without any joy.
There doesent seem to be a an orange uk ruu out there which would be the easiest way to recover the phone and im presuming i need the phone up and running properly to change to super cid to install a general ruu.
Does anyone out there have any ideas or suggestions to help me restore my phone ?
I know this has been posted before but i have spent the last two days going round in circles trying to fix this, any help greatly appreciated
norniron said:
Hi all, im looking for a bit of help in recovering my orange uk one s. I had unlocked the bootloader, rooted and installed cwm mod recovery without any problems.
I decided i wanted to do the ota 4.04 update which is where my problems started. I read that you needed to restore stock recovery and relock the bootloader to do this, which i did and now the phone wont boot
I can access the bootloader and recovery ok and can unlock and relock the bootloader ok. I still have the original cwm back up i made when i first rooted the phone, have tried to restore this without any joy.
There doesent seem to be a an orange uk ruu out there which would be the easiest way to recover the phone and im presuming i need the phone up and running properly to change to super cid to install a general ruu.
Does anyone out there have any ideas or suggestions to help me restore my phone ?
I know this has been posted before but i have spent the last two days going round in circles trying to fix this, any help greatly appreciated
Click to expand...
Click to collapse
you get stuck at HTC logo? or you get a bootloop?
McGiver93 said:
you get stuck at HTC logo? or you get a bootloop?
Click to expand...
Click to collapse
Hi and thanks for the reply.
I get bootloop, htc logo then green circle then red triangle
norniron said:
Hi and thanks for the reply.
I get bootloop, htc logo then green circle then red triangle
Click to expand...
Click to collapse
boot into bootloader
unlock bootloader if you haven't alredy unlocked it
install twrp recovery (because its better than CWM with S-ON)
change your CID to Super CID or a Generic one like "HTC_001"
install stock recovery
relock bootloader
Install European RUU.
It's not bricked if you can get into the bootloader or if the screen turns on.
A brick is what it says, the screen doesn't turn on, nothing works, not the bootloader, not recovery, nothing.
McGiver93 said:
boot into bootloader
unlock bootloader if you haven't alredy unlocked it
install twrp recovery (because its better than CWM with S-ON)
change your CID to Super CID or a Generic one like "HTC_001"
install stock recovery
relock bootloader
Install European RUU.
Click to expand...
Click to collapse
Thanks for taking the time to reply. I got sorted this afternoon (I posted this in another thread) using that method. for some reason i couldnt get into adb shell before installing twrp. Wverything all up and running again.
Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
mrminor13 said:
Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
That's what I thought. I'm excited that I get to see it on my wife's phone.
Sent from my One S using xda app-developers app
fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
SoTacMatt said:
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
That's been my experience. Try it without if you would like. Can't hurt anything.
i am currently S-off and running viper rom. If I change my cid back to the TMo version and reflash the ruu so I return to stock, would I get the update? DO i need to lock the bootloader and S-ON?
I hav relocked the bootloader bt cn some one provide me stock recovery for cid 044 jelly bean
Sent from my HTC One S using xda app-developers app
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
aegentirony said:
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
Click to expand...
Click to collapse
You should not use supercid for an ota there are many reports of bricked phones that way! change your cid to original also stock recovery is a must!
fbihawk said:
That's been my experience. Try it without if you would like. Can't hurt anything.
Click to expand...
Click to collapse
Re-locked bootloader and the RUU is working. Thanks!!!
Have you guys updated your phone yet, and if so were you able to unlock and root again? I just finished restoring the gf's phone back to stock but all her apps were backed up via Titanium and from Viper 2.0, which is JB based. I can't restore her apps and data unless she's on a JB rom, if I remember correctly.
Sent from the other One.
Could someone please point me in the right direction to where I can get my wife's T-MobileUS One S (S4) back to where she can OTA update it to JB? I've been around quite awhile, but am personally a Nexus user and am not very familiar with Sense roms yet. I've done a lot of reading up on it but am getting a little confused. I keep reading about the HBOOT version possibly causing problems? Here is her setup.
Stock 4.0.4/rooted
CWM recovery
CID-T-MOB010
***TAMPERED ***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012,18:01:48
I'm not sure what ROM my gf was on. First I backed up with Titanium Backup. I flashed the stock recovery with fastboot, locked the bootloader, ran the 2.35 Tmobile RUU (to get her to completely stock), ran the Software Update from the About Menu to get JB, unlocked the bootloader, flashed TWRP recovery with fastboot, and flashed the supersu.zip in TWRP. All is good, I have working root and was able to restore using Titanium. She'll be happy when she wakes up.
Is a locked bootloader necessary?
SoTacMatt said:
Re-locked bootloader and the RUU is working. Thanks!!!
Click to expand...
Click to collapse
Did you try updating without re-locking the bootloader? I was able to update the last time (the security fix they pushed out) without re-locking the bootloader. I'd like to avoid re-locking if possible. I know I need to revert to the stock recovery (that's fine).
--------------
ROM: T-Mobile Stock 4.0.4
HBOOT: 1.14.0005
Recovery: CWM 5.8.3.1
Rooted: Yes
I did try to use the RUU without locking the bootloader. It failed. That is when I did 'fastboot oem lock' and everything else went smoothly!!!
Not necessary to re-lock bootloader for OTA
I can confirm that it is not necessary to re-lock the bootloader to receive the OTA update to JB. I am on Stock TMOUS, rooted and with an unlocked bootloader. I suspect that one needs to re-lock the bootloader only if one is restoring the device to factory settings using an RUU. It certainly isn't required for a successful OTA update.
Here are the steps I followed (assuming you have the android SDK configured and the phone plugged in via USB into a PC):
1. Installed the stock recovery (fastboot flash recovery <name_of_recovery_file.img>)
2. Un-installed Superuser.apk to remove root. ( rm /system/app/Superuser.apk )
3. Rebooted the phone.
4. Checked for system update (Settings - About - Software updates - Check now...)
5. Chose to download the update. It took a while to download even on WiFi.
6. Chose to install the update.
7. Let the phone settle for about 30 minutes. It will not be as responsive during this time.
8. Re-install custom recovery (I use ClockworkMod).
9. Re-install root.
Once the update was complete (step 6 above), I did have a minor issue where the keypad was not showing up for me to enter the PIN to unlock the phone. I rebooted (hold down the Power button for about 10 seconds) and then I was able to get past that just fine.
------------
ROM: T-Mobile US Stock 4.1.1
HBOOT: 2.15.0000
Radio: 1.13.50.05.31
Recovery: CWM 5.8.3.1
Rooted: Yes
ok, I was super cid and hboot was moonshine i was running the unknown rom and went to install a bulletproof kernel. it booted and soon after rebooted, I went into cwm and it came up with a whole bunch of errors about storage and started soft resetting again. I reset with an ruu from tmobile and it still wont boot properly. my hboot was reset and now im bootloader locked again and i cant flash a recovery it resets into the ruu image thats installed an trys to scan phone storage and then just resets. am I screwed?
davwman said:
ok, I was super cid and hboot was moonshine i was running the unknown rom and went to install a bulletproof kernel. it booted and soon after rebooted, I went into cwm and it came up with a whole bunch of errors about storage and started soft resetting again. I reset with an ruu from tmobile and it still wont boot properly. my hboot was reset and now im bootloader locked again and i cant flash a recovery it resets into the ruu image thats installed an trys to scan phone storage and then just resets. am I screwed?
Click to expand...
Click to collapse
Why not just Unlock bootloader again and flash recovery anew, flash ROM.
Boot to bootloader and select clear storage. Then boot to bootloader and do a factory reset. Hopefully that will do it. Then you can unlock bootloader again and flash a custom recovery.
Sent from my One S using Tapatalk 4
El_Svanto said:
Boot to bootloader and select clear storage. Then boot to bootloader and do a factory reset. Hopefully that will do it. Then you can unlock bootloader again and flash a custom recovery.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
how do I unlock boot loader from bootloader. I tried fastboot oem unlock, and nothing. I cant use adb because i cant boot into android
Did the RUU install correctly? So you are now on a stock ROM? If so, did you try the first two steps i wrote?
Sent from my One S using Tapatalk 4
tried that too. still just bootloops. it will boot up show the internal storage than just bootloops.
I would try to enter fastboot and run the RUU again to be sure it flashed correctly. Then try clear storage one more time to fix your SD-card. If that doesn't work i think there is a manual way to format the sd-card. Maybe someone can provide a link?
BTW, going to sleep now.
Sent from my One S using Tapatalk 4
El_Svanto said:
I would try to enter fastboot and run the RUU again to be sure it flashed correctly. Then try clear storage one more time to fix your SD-card. If that doesn't work i think there is a manual way to format the sd-card. Maybe someone can provide a link?
BTW, going to sleep now.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
ok im unlocked on hboot 2.15.0000 again due in part to the ruu and s-off. im getting errors in fastboot trying to install a recovery
davwman said:
ok im unlocked on hboot 2.15.0000 again due in part to the ruu and s-off. im getting errors in fastboot trying to install a recovery
Click to expand...
Click to collapse
factory recovery is now accessible
davwman said:
ok im unlocked on hboot 2.15.0000 again due in part to the ruu and s-off. im getting errors in fastboot trying to install a recovery
Click to expand...
Click to collapse
Usual errors while installing a recovery are because the boot loader is locked (relocked).
You sure you unlocked the boot loader after you ran the RUU?
Def. Was unlocked. I am running completely stock rooted right now, only because I need the phone reliably for a few days. Cell service took forever to connect after the restore to stock and speeds are really bad on data now. Have to figure that one out. After 12 hours getting this thing to finally resemble its former self, I have files all over my laptop and am going to completely flush everything pertaining to this phone and start from scratch to get back to s off and moonshine hboot. This phone is a pita, though.
I was helping my friend switch to a custom rom and I messed up. His One XL was on 4.1.1 with 3.18 software. I managed to temporarily change the CID by followin guides and unlock the bootloader using htcdev.com. The problem began after I tried to flash boot.img, from an One X rom because I thought this is a One X(ATT's naming). Now the device is stuck in a recovery boot loop. Once in a while I can get out of it and get to the bootloader. From there I'd erase cache, flash new recovery (TWRP for One XL), flash correct boot.img, go into recovery and flash rom. However, upon finishing install the reboot will start the recovery boot loop again. The phone keeps trying to boot recovery instead of normal boot on restart and gets stuck. I've tried both CWM and TWRP, wiped many times, but it refuses to boot normally. Every time after the logos for the rom plays the phone reboots. Unlocked bootloader but no root or S-off. What can I do?
Thanks
What ROM are you tying to flash? And are you sure you're flashing the boot.img from that ROM zip?
Out of interest, is there a reason your friend isn't doing this himself? Handing an unlocked phone to someone who hasn't undergone the learning experience of actually unlocking the device and researching the ins and outs of a modified phone is a pretty terrible idea.
Sent from my Evita
Wouldn't it be advisable if he formatted and ran a ruu? Sounds like he messded up his bootloader with a incompatible ROM.
Sent from my Desire HD using Tapatalk
He can't run an RUU. The fact that he flashed a boot.img would suggest that he's s-on, he mentioned changing the CID which suggests that he has SuperCID. S-on + SuperCID + jb RUU = brick.
Sent from my Evita
Uh oh. Nothing can be done....?
?
Sent from my Desire HD using Tapatalk