Database Info

[Q] Can't access root and Google apps

I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.

SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!

I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?

Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.

Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?

Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.

Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.

Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.

1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.

3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.

Where do I go to get the recovery image?

The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.

Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.

There isn't a link...

Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.

It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.

I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.

I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.

Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back

Can't flash recovery/ROMs/achieve root?

I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?

New Jer-Z said:
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
Click to expand...
Click to collapse
You skipped right over the "can't seem to able to flash a recovery."
Please explain in detail the instructions you followed AFTER unlocking via HTCdev.com. This includes files you downloaded, where you put them, how you attempted to flash, etc.
These details will be very helpful. Don't worry, sounds like you're not in any serious trouble at all. Just don't go flashing anything you see.
Also, please post this to the Q&A forum or General next time. This development forum is intended for development posts ONLY (ie. ROMs, Kernels, Radio's, etc). Just a heads up. Welcome to the forums

Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?

Moved To Q&A​
Please post all questions in the Q&A section​

New Jer-Z said:
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Click to expand...
Click to collapse
Ahhh, not to stir up the pot here, but you're getting vague again with what's going on. You say "when I try to reboot into recovery, I don't get very far". What do you mean by this? Details are extremely important in helping you. Sounds like you're saying that recovery was successfully pushed, but then I didn't get any details as to what's going on when you attempt to load recovery. Also, which recovery file did you use? Use this one
I'm not trying to get on to your case here, but you've got to be really specific when you say stuff doesn't work, because that doesn't help us diagnose your issue. When your recovery is done flashing, you should be able to access the bootloader by holding Pwr + Vol-Down for like 5 secs, then choose recovery (that or fastboot>recovery....I cant recall if recovery is a main menu item). What happens after you choose that? Mine shows the htc splash screen, with a development message in red, and then it boots Clockworkmod.

No, no, lol I totally understand, I guess I am being vague.
I was going to go into details, but I was at work. Interestingly enough, my phone died, and when I plugged it and let it charge for a little bit, the phone booted right into CWM touch - so odd! So I was like, ok, i've achieved root - well, no, cuz I opened ROM Manager and it says SU couldn't be found.
BEFORE, when I would do what you said I should do, it would take me to the HTC splash screen where it was in red text, some disclaimer about some proprietary information crap, then it would skip recovery and just boot into Android -___-
Let's see if I can replicate booting into recovery now. (What method are you using to flash your recoveries?)
EDIT: Well it looks like I can't get back into recovery. Same thing as mentioned above. I can get to the fastboot screen, but if I click recovery, it takes me to that HTC disclaimer screen, the little loading bar loads then - poof - screen goes blank and Android boots up.

I have the same problem -_-! Can someone help please
The recovery image was flashed succesfully from Hasoon2000's toolkit. But when i go to the bootloader and select Recovery, I get the red warning for from HTC about how this is for development purpose only... then the phone's screen goes black, then it boots into the stock ROM.

Cant flash recovery
Hello everyone.
I have a similar problem. I successfully proceeded with the bootloader, but now I can't install the recovery. It simply wont flash.
I was following the xda tutorial that's in this very forum, but i got stuck: In my desktop i downloaded the needed files (or so I believe), and so i have in my desktop a folder called "carpeta" (random name) with these files within: adb.exe, adbwinapi.dll, fastboot and 3 different recovery images i have tried to flash.
I use mac, so i open the command prompt for mac (terminal) and go to the "carpeta" folder and after that, I type "cd fastboot flash recovery xxxxx.img" (the xxx are the names of the recovery images that i have in the folder, one at a time) but it simply wont flash anything. I attach a screenshot to ilustrate what happens...
Please help me
http :// img710.imageshack.us/img710/6026/capturadepantalla201205.png

Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps

I'll give it a shot later tonight on my lunch break.

batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...

alexjuanes said:
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
Click to expand...
Click to collapse
Make sure that you navigate to the proper folder using the "cd" command.(for example" cd C:\Fastboot ", if your adb and recovery are in that location)
Make sure that the Clockwork Mod recovery file is in the same folder as the adb and make sure that you type the file name correctly
I used these file and put the recovery image inside the folder after unzipping
http://www.mediafire.com/?50baad8rykng2j0
Here is the recovery I used :
http://loadbalancing.modaco.com/download.php?file=r2-modaco-recovery-clockwork-touch-ville.img
But your running Mac so I don't know if the method I used will work for you because I'm on Windows

Doesnt work...
I have the bootloader (when i start in bootloader mode my phone says ***tampered*** and also ***unlocked***.
BUT
I've been 2 days trying to flash my recovery on my htc one s from my macbook, and after i use the command prompt to get to the folder where i have adb, fastboot, my recovery .img file,etc... this is what happens:
-----
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$ fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
-bash: fastboot: command not found
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$
-----
ive already updated all that i could in the sdk manager, or whatever its name is...
please some help?

batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
This actually worked for me. I am rooted, and am now running a custom ROM.
Thanks so much for all your help!

Hey everyone
i seem to have made a very tiny bit of progress here since now i can type the commands and make it start, but only that... starting.
my command box is stuck in a "waiting for device" message that will start nothing, and my phone is just there, untouched.
i never thought flashing a recovery would give me this much of a long headache...
help anyone? how do i make my pc stop "waiting for device"?

Have you tried a different USB cable/port? I had a similar problem but moving to a different port worked.
Sent from my HTC VLE_U

I have the same problem i did everything as in the guide posted here http://forum.xda-developers.com/showthread.php?t=1583427
But when i flash recovery through fastboot ( fastboot flash recovery recoveryname.img) everything goes ok but when i want to boot into recovery i get stuck on the HTC screen.
Than i wanted to go to recovery trough fastboot ( fastboot boot recovery ) i get message cannot load recovery.
If you need more info for help i can provide you guys with the screenshots.
Thanks in advance Nikola.

Cant boot into recovery...HTC screen only

I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!

From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast

E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?

http://forum.xda-developers.com/showthread.php?t=1754018

gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?

rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?

rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1

veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast

E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...

Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app

c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:

Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app

veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?

rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!

veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?

http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!

Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.

Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.

slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.

im getting the same error and im using the recovery ending on evita

[Q] Flashed boot.img, did a reboot, but phone keeps restarting after splashscreen

I'm trying to load the CM ROM to my HTC One S device. I was able to unlock and root the device. Next, I flashed the boot.img (fastboot flash boot.img) from the ROM zip file to the device and restarted it (cm-10.1-20130304-EXPERIMENTAL-ville-M2). Now my device just cycles through the HTC splash screen with the red letters "this build is for development purposes only..." -> Android Splash Screen. Phone does not properly boot up. I think I missed a step in the flashing process. Any ideas on how to proceed?

fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.

tivofool said:
fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.
Click to expand...
Click to collapse
Sorry, the command I used was "fastboot flash boot boot.img" The CM boot.img definitely got written to the device. I missed the step of copying the ROM to a folder on my device. I wasn't clear on this step since I'm not sure how to view folders on the device. Is there a way to load the ROM from my PC instead of copying the files to the device first?
I'm using TWRP 2.6.0.0. I'm also not clear on the back up portion since there is no SD card on this device. Is it possible to perform a backup? I thought I did one during the initial step, but now that I'm trying to restore, I don't see a backup available.

yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)

tivofool said:
yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)
Click to expand...
Click to collapse
Thanks for clarifying. I successfully loaded the ROM on my device.

My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens

Mhord said:
My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens
Click to expand...
Click to collapse
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.

tivofool said:
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.
Click to expand...
Click to collapse
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen

Mhord said:
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen
Click to expand...
Click to collapse
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.

tivofool said:
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.
Click to expand...
Click to collapse
mmm yeah tried what you said, and still got stuck in "entering recovery".
I used eyeballer recovery which is the one CM recommends on their wiki
EDIT: My HBOOT says VilleC2 in that case S3 recovery would be the correct one?
EDIT: Yep found the correct recovery back in business, many thanks Tivofool

Booting only takes me to TWRP

So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.

Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?

Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.

I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk

edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...

cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!

I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.

Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app

The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.

hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.

So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?

tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)

RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk