Database Info

[Q] Possibly made redundant my Nexus S!!

9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!

mittu1 said:
9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!
Click to expand...
Click to collapse
If you have recovery, then you are fine. Just flash a rom. Flash the stock rom if you want. Any rom. Then you should be fine.

Sorted!! The solution was found here:
http://forum.xda-developers.com/archive/index.php/t-992114.html
New ROM up and running, no issues so far.

Help i think I bricked my phone

Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!

volume down button+power button try this combination until u get in the bootloader then select recovery. once in recovery just restore a backup if you have one, you should have one

i dont have a backup and i have nothing on my "sd" to i can install. I have formatted the ROM and thats why it wont boot..

If you can get into Recovery (CWM) in the advanced settings if i remember, there's a "format sd card" to make it work with the installation of a custom ROM

I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929

brwetz said:
I posted a tutorial for how to do this:
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
thanks for the guide but im getting error mounting /sdcard. and if i follow cannondale0815 solution for that problem when flashing the stock and cwm I cannot access recovery mode.

Clear Storage in fastboot and re-install CWM then try it. That's how I got mine to work

Ok if your bootloader is locked and you have a custom recovery first flash stock recovery then boot into fastboot and run "fastboot oem lock" After that restart your phone and boot back into fastboot. Then run the RUU for your model and cid. easy.

Follow the steps which might work
1, If you knows something about adb, you can just simply push a rom into the sdcard(You don't need to do this if there is already a flashable rom in the sdcard), flash the kernel in fastboot, go to the recovery, wipe and flash a new rom. Then everything(except your data) should be fine
2, If you are not able to use adb push, or you have never flashed a recovery/3rd-party rom/ or you have other issues:
Using the RUU updater might be safe and simple (of course everything except those in the sdcard will lost)
a, relock the hboot using "fastboot oem lock"(or the RUU will refuse to continue)
b, run the RUU updater, wait for ~10min, your phone will be "refreshed" to something like the 1st day you bought it, except the Hboot will say it is "RELOCKED s-on"(this should be LOCKED s-on at first)
c，unlock your phone again(if you have stored the .bin file for unlock, just push it to your phone in the fastboot mode which is enough already, it is not needed to do the whole process in HTCDEV again.)
IMPORTANT: the RUU updater and the phone must be the same area. for example an Europe's RUU can't be applid to an US's One S
This is also the only method to update the Radio software, unless the hboot is S-OFFed
Bure03 said:
Hey Guys,
I tried pretty much everything and don't know what else to do. My phone just stays stuck on the android screen. I forget that the "SD card" in this phone is actually part of internal storage, I did a factory reset and lost everything.
I tried flashing different boot.img and getting nothing. I'm afraid I need to get a rom onto the sd card but how is that possible if I cant get my phone to boot up.
Any ideas?
Thanks!
Click to expand...
Click to collapse

Bootloop problem, totally perplexed

Problem: After installing CWM, the phone won't boot fully. It goes to the HTC screen (with some new red text about this being a development-only build) and then reboots to the same screen over and over.
What I've done based on what I've read here:
Cleared the caches in fastboot and rebooted.
Run the unlock token script again.
Installed TWRP, wiped everything.
Attempted to flash CM9 through TWRP (fails).
Attempted to install Scott's Roms 1.85 ROM throught TWRP (failed).
Reinstalled CWM to try to flash Scott's 1.85, but CWM will not go into recovery mode (just goes to the HTC screen and starts boot loop again).
Attempted to install CM9 and Scott's 1.85 through flashboot, no luck because of missing text files (am I using the wrong package?).
Factory reset just takes me to TWRP, and when I try to factory reset from there it goes back into bootloop.
What does work:
I can get to Fastboot on phone.
With TWRP installed, I can into TWRP recovery.
Does anyone have any thoughts on this?
Thanks.

makanai said:
Problem: After installing CWM, the phone won't boot fully. It goes to the HTC screen (with some new red text about this being a development-only build) and then reboots to the same screen over and over.
What I've done based on what I've read here:
Cleared the caches in fastboot and rebooted.
Run the unlock token script again.
Installed TWRP, wiped everything.
Attempted to flash CM9 through TWRP (fails).
Attempted to install Scott's Roms 1.85 ROM throught TWRP (failed).
Reinstalled CWM to try to flash Scott's 1.85, but CWM will not go into recovery mode (just goes to the HTC screen and starts boot loop again).
Attempted to install CM9 and Scott's 1.85 through flashboot, no luck because of missing text files (am I using the wrong package?).
Factory reset just takes me to TWRP, and when I try to factory reset from there it goes back into bootloop.
What does work:
I can get to Fastboot on phone.
With TWRP installed, I can into TWRP recovery.
Does anyone have any thoughts on this?
Thanks.
Click to expand...
Click to collapse
Uhhhhh...try to relock your bootloader (fastboot oem lock) and run an RUU. You'll go back to stock. Then follow these steps:
1. Re-unlock your bootloader using the same unlock token you used before
2. Flash TWRP from fastboot (or a one-click)
3. Reboot into TWRP
4. Mount storage and put whatever rom you want into whatever folder you want on the sdcard (CM9 Alpha 5, CleanROM, AOKP M6.2, etc etc)
5. Factory Reset
6. Flash the rom and anything that needs to go with the rom (like Gapps if you're flashing CM9 or AOKP)
7. Reboot and enjoy, be sure to update your SU binaries immediately after booting by opening up the SuperUser app
Also, do not use CWM, our device is not officially supported by the CWM team. Only TWRP is an officially supported recovery for our HOX.

stnguyen09 said:
Uhhhhh...try to relock your bootloader (fastboot oem lock) and run an RUU. You'll go back to stock. Then follow these steps:
1. Re-unlock your bootloader using the same unlock token you used before
2. Flash TWRP from fastboot (or a one-click)
3. Reboot into TWRP
4. Mount storage and put whatever rom you want into whatever folder you want on the sdcard (CM9 Alpha 5, CleanROM, AOKP M6.2, etc etc)
5. Factory Reset
6. Flash the rom and anything that needs to go with the rom (like Gapps if you're flashing CM9 or AOKP)
7. Reboot and enjoy, be sure to update your SU binaries immediately after booting by opening up the SuperUser app
Also, do not use CWM, our device is not officially supported by the CWM team. Only TWRP is an officially supported recovery for our HOX.
Click to expand...
Click to collapse
Worked. I had to leave town for a week as I was reading your reply stnguyen, so I didn't get a chance to try it until I got home tonight. I'm up and running again. Thanks a ton!

[Q] Flashed new kernel, won't boot

I used Hasoon2000's HTC All-In-One Kit to root my phone. That all worked.
The issue came when i flashed a new kernel. I placed the boot.img from King Kang's new ROM (http://forum.xda-developers.com/showthread.php?t=1959099)
Anyway, When i boot I get the HTC, quietly brilliant logo, and this in red letters "This build is for development purposes only. Do not distrubute... "
i can boot into recovery (pwr+ vol down)
And i get the ***TAMPERED*** AND ***unlocked*** tags at the top
I don't know where to go from here...
Thanks for the help.

Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.

ccamwilkins said:
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
Click to expand...
Click to collapse
You mentioned in your original post that you could boot into recovery, so is that not working now? Factory reset might've fubared the recovery piece, so you could do one of two things:
1) download the original RUU version for your phone, relock your phone, and flash the RUU and start over.
2) try reinstalling TWRP.
This whole thing sounds like trying to install a kernel or fastboot flash a boot.img without SuperSU correctly installed. This is what happened to me when I first unlocked my phone and tried to fastboot flash the CM10 boot.img after failing the flash from recovery twice. Without that super-user permission, bad things tend to happen. If you decide to continue on with reinstalling TWRP, make sure SuperSU.zip is flashed successfully from
TWRP, then try your rom/kernel combination again (or even a different combination if you're apprehensive).
BEWARE: sometimes partially flashing these things can corrupt your sd card. I had to reflash the original RUU to fix my phone BEFORE I rerooted and flashed a rom/kernel.

Have you fastbooted a SU to your phone after you rooted and unlocked? I'd imagine you did if you followed the toolkit.. So your on 2.20... Just download cleanrom 5.1 on your computer. Mount sdcard via recovery and drag cleanrom onto phone. Flash entire rom in recovery. I bet it works
Once your on a stable rom, download king kang from your phone. Download flashgui. Open flashgui app, navigate to king kang and let it find the boot img and flash it for you.. Once successful, immediately boot into recovery and flash entire rom through twrp.
Success
Sent from my One X using Tapatalk 2

Multiple recoveries installed

I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.

theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.

I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.

It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img

cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.

theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe

Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!

theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk