Related
Hi everybody,
I unlocked the bootloader of my One S successfully with htcdev.com and next I wanted to flash a recovery image via fastboot, what succeeded. I used this thread:
http://forum.xda-developers.com/showthread.php?t=1583427
But when try to start the recovery, the phone hangs in the boot screen with the red text "This build is for development..." and does not start recovery.
I tried several recovery images for the ville but none could be started.
What i recognized is, that in the Video "How to Install Recovery in HTC One S" in the thread mentioned above, the Bootloader screen locks slightly different, than mine.
First of all, mine only says "Unlocked" but NOT "Tampered" and second the first green line says:
VILLEC2 PVT SHIP S-ON RL
whereas in the video one can see the line
VLE PVT SHIP S-ON RL
I attached a pic of my bootloader.
So I think my phone is a newer One S, right? Is there already working Recovery out there?
Or am I missing something else?
Thx a lot in advance for any hint
Do you have CWM installed?
sure, as I wrote in my first post. I tried several CWM Recovery Images... the interim one, the actual original one for the One S... no image boots...
Well, it doesnt look like the your phone is rooted.
Try TWRP. Quality recovery.
Sent from my HTC VLE_U using xda premium
Tampered means rooted. Everything else looks updated. Try to root then see what happens. You may need to root to flash cwm over stock. Not really sure. I just do both always and they work.
Sent from my HTC VLE_U using xda premium
What am I missing?
I unlocked the Bootloader on htcdev.com, did the whole thing with entering the token, download the Unlock_code.bin, upload it to phone, said "Yes, unlock bootloader" and so on.. and the bootloader sais, it IS unlocked. If it where not, I wouldn't be able at all to flash a recovery image with fastboot, but this also succeeds (fastboot said "OKAY" when uploaded to phone and "OKAY" when flashed), right?
And the next step after unlocking bootloader IS flashing a recovery image like CWM for then using it to flash the Superuser.zip for gaining root, isn't it? Or am I completely wrong?
Try booting normaly and then connecting the phone to your computer and do adb reboot recovery i know i had problems similar to this when i first flashed a recovery and doing that for the first time fixed it
Sent from my HTC One X using Tapatalk 2
You can gain root access through stock recovery as long as you unlocked bootloader. Did you try Hasoon2000's all in one tool kit?
Sent from my HTC VLE_U using xda premium
Yeah Try the adb reboot recovery method, If that fails, flash the superboot root image, then use something like rom manager to download CWM to the phone.
@stumpyz9: This did not work, same as if i would start recovery from Bootloader
@dooshbag45: I re-locked and unlocked the bootloader again, nothing changed, it is "UNLOCKED" but not "TAMPERED". Yes, I also tried Hasoon2000's Root Kit and recognized, it just does nothing other, than 1. unlock bootloader and 2. flash a Recovery Image. This had the identical result...
I meanwhile tried these recoveries:
r2-modaco-recovery-clockwork-touch-ville.img
recovery-clockwork-touch-5.8.2.4-ville.img
recovery-clockwork-touch-5.8.3.1-ville.img
twrp217.img (inculded in Hasoon2000's Kit)
CWM5824.img (inculded in Hasoon2000's Kit)
Now I tried to recover the stock recovery image from the modaco.com site, named "ville_recovery_signed.img"
but this doesn't start either... WTF...
Tampered does not mean ur rooted I had that problem left phone on stock for a week then tried same method again must of been doing Something wrong learn how to do it manually but if u can't download all in one toolkit HTC.one s I think that's what's it called it will unlock bootloader flash and root
Sent from my HTC One S using xda premium
@azzledazzle: the superboot method didn't work either... downloaded it, fastbooted it, the phone boots but..... remains in the red-text screen as it does when try to boot a recovery image .... I really think it has something to do with the newer HBOOT Version and the "VILLEC2" thing.. something in booting images works other than in the version before...
Just download all in one toolkit HTC one s
Sent from my HTC One S using xda premium
@k1llacanon: The All-in-one toolkit didn't work as I posted earlier. This was one of the first things I tried...
I had that problem when rooting mine left it for a week learnt more about my phone and did it and it worked u must be doing Something wrong
Sent from my HTC One S using xda premium
Direct fastboot booting of a recovery image also does not work:
"fastboot boot r2-modaco-recovery-clockwork-touch-ville.img"
same result...
@k1llacanon: This is not the first phone I root... did it with the Wildfire S and the old Desire... it worked the same way... unlock bootloader, flash recovery image.. what can be done wrong with these 2 simple steps? What did you do other?
Have you got
Fastboot (unticked)
USB Debugging (ticked)
snoopy1978 said:
Direct fastboot booting of a recovery image also does not work:
"fastboot boot r2-modaco-recovery-clockwork-touch-ville.img"
same result...
@k1llacanon: This is not the first phone I root... did it with the Wildfire S and the old Desire... it worked the same way... unlock bootloader, flash recovery image.. what can be done wrong with these 2 simple steps? What did you do other?
Click to expand...
Click to collapse
Dont pay attention to that idiot, he obviously has no idea what hes doing either.
And if you think it is because of this newer version have you checked to see if anyone else with the newer version has been having the same problems? Just to confirm thats it
Sent from my HTC One X using Tapatalk 2
stumpyz9 said:
Dont pay attention to that idiot, he obviously has no idea what hes doing either.
And if you think it is because of this newer version have you checked to see if anyone else with the newer version has been having the same problems? Just to confirm thats it
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Stfu
Sent from my HTC One S using xda premium
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.
Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol
I've just received an update to android 4.2.2 with Sense 5 on my rooted HTC One SV (Vodafone Spain), and I'm not able to perform. After rebooting appears fastboot :
****TAMPERED***
***RELOCKED***
*** Security Warning ***
K2_U PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40a.00.04
OpenDSP-v9.2.0268.1214
eMMV-boot
Mar 29 2013.20:55:40:20204
and the menu for bootloader.
What's wrong? Is there any way to solve?
Security warning? Were you by any chance S-Off with any custom kernel, boot.img, custom hboot.img, etc???
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------
You said CWM in your thread? Do you by any chance still have a custom recovery on your device?
I will have to look into this personally as I have never seen this 'security warning' before. I find it very interesting
Sent from my C525c using XDA Premium 4 mobile app
re
Sorry, previously i've tried to perform upgrade, but CWM gives me an error reffered to access file and can't mount device, so i tried to install a boot.img from a backup. Then, the problem I exposed.
Thanks for your attention.
You can't upgrade with cwm from an over the air update. You must have your stock recovery for it to work. You can't install a boot.img with S-On unless you flash it through fastboot command, and not with a custom recovery. You have to unlock your bootloader before you can do any of this. Then relock your bootloader after you flash your boot.img and stock recovery.img.
Sent from my C525c using XDA Premium 4 mobile app
re
Modding.MyMind said:
You can't upgrade with cwm from an over the air update. You must have your stock recovery for it to work. You can't install a boot.img with S-On unless you flash it through fastboot command, and not with a custom recovery. You have to unlock your bootloader before you can do any of this. Then relock your bootloader after you flash your boot.img and stock recovery.img.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the question, I flashed boot.img and recovery img (from a backup) using fastboot command.
And there's more: I see the red text in bootloader after apply the OTA, so applied the info on "[MOD][4.1.2] Remove Red Text in HBoot/Bootloader (for k2u & k2ul) - S-Off only!" http://forum.xda-developers.com/showthread.php?t=2289357 with the same result as taking an aspirine. Then the same with
TUTORIAL: Remove *TAMPERED* & *RELOCKED* flag / HBoot w/o unlock_code.bin http://forum.xda-developers.com/showthread.php?t=2541843 . Guess the result??
yes, the same: none. I'm getting amused trying to get my phone having 4.2.2 and sense 5 from 4.1.2 and 4+, but I will not having a brick (nice brick anyway, but useless).
Ahhh, I forget to tell you, after applying remove tampered, and rebooting to fastboot, the warning has dissapeared, but tampered and relocked remains. Is not funny ?
As you can guess, I'm not a guru in this matter. I wish it were MS-DOS , then there will be a chance.
You CANNOT FLASH A CUSTOM HBOOT while you are S-On and with a locked bootloader. My tutorial which you posted requires that you are S-OFF which you are not. You are currently S-On. Had you read my instructions in that tutorial you would had seen that.
In addition, you currently have a CUSTOM recovery on your device with a LOCKED bootloader which was a huge mistake.
You HAVE to unlock your bootloader to fix your problems. Once you unlock your bootloader you will be fine. YOU CANNOT FLASH ANYTHING IF YOUR BOOTLOADER IS LOCKED.
1.) Unlock your bootloader with your unlock_code.bin file, then restore your phone with your backup. If you do not have your PERSONAL unlock_code.bin file then you need to head over to HTCDEV.com and follow their guide to receiving one which will be sent via email to you.
2.) Insure you do not have a custom hboot, custom boot, custom kernel, custom recovery installed on your device - if you do then RESTORE them with your stock IMG's.
3.) After you have unlocked your bootloader, restored your device with your backup, and insured you have no custom .imgs on your device...... THEN, AND ONLY THEN, will you relock your bootloader. After which you will be able to upgrade your phone.
Sent from my C525c using XDA Premium 4 mobile app
Modding.MyMind said:
You CANNOT FLASH A CUSTOM HBOOT while you are S-On and with a locked bootloader. My tutorial which you posted requires that you are S-OFF which you are not. You are currently S-On. Had you read my instructions in that tutorial you would had seen that.
In addition, you currently have a CUSTOM recovery on your device with a LOCKED bootloader which was a huge mistake.
You HAVE to unlock your bootloader to fix your problems. Once you unlock your bootloader you will be fine. YOU CANNOT FLASH ANYTHING IF YOUR BOOTLOADER IS LOCKED.
1.) Unlock your bootloader with your unlock_code.bin file, then restore your phone with your backup. If you do not have your PERSONAL unlock_code.bin file then you need to head over to HTCDEV.com and follow their guide to receiving one which will be sent via email to you.
2.) Insure you do not have a custom hboot, custom boot, custom kernel, custom recovery installed on your device - if you do then RESTORE them with your stock IMG's.
3.) After you have unlocked your bootloader, restored your device with your backup, and insured you have no custom .imgs on your device...... THEN, AND ONLY THEN, will you relock your bootloader. After which you will be able to upgrade your phone.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's a help
. No problem with 1 and 3, but 2... I think it will be a little difficult. I've just no idea how to do this, specially how and where to get stock images.
You don't have any idea about how much patient and helpfull you are. Thanks very very much
Pull the boot.img from your backup and copy it to your computer. Insure you name it boot.img.
Now go I into CWM and restore your device with your backup.
Now go into fastboot so you can flash your boot.img
fastboot flash boot boot.img
Now go into your recovery to confirm if it is stocked or custom. If shown a black screen with triangle then you are back to stock recovery. Otherwise it will still be CWM. If still CWM you will need to go to the link I will be providing in the below post and find a recovery.img suited for your device and flash it just like I told you to do with your boot.img
fastboot flash recovery recovery.img
At this point, I can only HOPE you do not have a CUSTOM HBOOT on your device but from the sounds of it you do not since you attempted that with a LOCKED bootloader which ultimately failed during its process.
So with that said, go ahead and relock your bootloader.
fastboot oem lock
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 10:39 AM ---------- Previous post was at 10:34 AM ----------
http://forum.xda-developers.com/showthread.php?t=2317379
Sent from my C525c using XDA Premium 4 mobile app
Let's have some fun:
I did everything as you told me, everything. So assume there's a stock boot and a stock recovery. Also CWM dissapeared from recovery.
entering in fastboot after reboot I get the same message except ****security warning*****.
including S-ON !!!
Well, at this point, using again fastboot oem lock, the future brick says "device was already locked".
Is it not fun?.
Awesome, I'm really having fun while learning. I hope not to annoy you, in that case I promise to be more serious an read much much posts here and other forums before have any question.
I know it would be silly, but will try to install by itself the OTA. I find it could be interesting to see what will happend
I'll tell you
Ohhhh! , at this moment it seems to work, thanks .
If is there any thing I could do for you, tell me please, need some file from the ota or backup??
just tell me.
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