I had TWRP custom recovery installed, but I wanted to run an OTA update so I tried to flash back to stock recovery. My phone is now stuck in a reboot loop. It sits at a black screen with a small picture of an M8 and a red triangle and exclamation mark over it, then eventually it reboots. It boots to the white screen with the green "htc" logo, then goes back to the same black screen. I've tried holding down the power button, holding down Vol down+Power, holding down Vol up+Power, and holding down all three, but the reboot loop continues. Fastboot does not see my phone at any stage.
Here are the steps that I followed to arrive at where I am now:
1. Booted to Fastboot
2. Connected my phone to my PC
3. Opened a CMD prompt and accessed the fastboot directory
4. Ran this command: Fastboot oem rebootRUU
5. Ran this command: fastboot devices
6. Ensured that my phone was listed
7. Ran this command: fastboot flash recovery stock-recovery-4.4.3.img
8. Received a message stating that it was successful
9. Opened HBOOT on my phone
10. Opened Recovery on my phone
11. Phone went to a black screen with a small picture of a phone and a red triangle and exclamation mark
12. Phone stays there for a little while, then reboots to this screen, then the cycle starts over again
I did some searching but I couldn't find anything that helped. Anyone have any ideas?
Sorry, I mistakenly posted this in the wrong forum. Mods, could you please move this to Help & Troubleshooting?
UPDATE: I was able to get into fastboot by quickly holding down Vol Down + Power in between boot cycles, and fastboot is seeing my device on my PC. The problem now is that I don't know what to do from here.
craichead said:
UPDATE: I was able to get into fastboot by quickly holding down Vol Down + Power in between boot cycles, and fastboot is seeing my device on my PC. The problem now is that I don't know what to do from here.
Click to expand...
Click to collapse
What you are seeing is stock recovery. That is normal so relax.
What it sounds to me that you are wanting to do, is put your phone into a stock enough state in order to take any upcoming OTA correct?
I suggest at this point, that you take the latest available RUU (which has the latest OTA firmware included) which is also pre-rooted.
You will need to be able to get into Hboot however and you can do this by doing the following:
Hold Power+Volume up until the screen shuts off and goes black, then IMMEDIATELY hold power+volume down until you boot into hboot.
Once in hboot, you can always fastboot flash back TWRP to get your custom recovery back and flash custom roms.
I would do that first if there are things on your internal memory that you wish to save and off-load to your pc prior to taking the RUU.
If there is nothing you wish to save and you're ready to return to stock (but rooted so you can get back into the custom game later if you like), then follow the instructions outlined in the OP of this thread (which will provide a link for you to download the RUU needed): http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
If S=ON, select the S=ON link.
If S=OFF, select the S=OFF link.
Neo
Forum Moderator
ΠΣΘ said:
What you are seeing is stock recovery. That is normal so relax.
What it sounds to me that you are wanting to do, is put your phone into a stock enough state in order to take any upcoming OTA correct?
I suggest at this point, that you take the latest available RUU (which has the latest OTA firmware included) which is also pre-rooted.
You will need to be able to get into Hboot however and you can do this by doing the following:
Hold Power+Volume up until the screen shuts off and goes black, then IMMEDIATELY hold power+volume down until you boot into hboot.
Once in hboot, you can always fastboot flash back TWRP to get your custom recovery back and flash custom roms.
I would do that first if there are things on your internal memory that you wish to save and off-load to your pc prior to taking the RUU.
If there is nothing you wish to save and you're ready to return to stock (but rooted so you can get back into the custom game later if you like), then follow the instructions outlined in the OP of this thread (which will provide a link for you to download the RUU needed): http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
If S=ON, select the S=ON link.
If S=OFF, select the S=OFF link.
Neo
Forum Moderator
Click to expand...
Click to collapse
I actually don't think that it's in stock recovery. It still won't power on and is stuck in a reboot loop unless I hold Vol Down+Power during the reboot.
craichead said:
I actually don't think that it's in stock recovery. It still won't power on and is stuck in a reboot loop unless I hold Vol Down+Power during the reboot.
Click to expand...
Click to collapse
Hold down Volume UP+Power for about 10 seconds until the screen goes black and then immediately hold Volume Down+Power until you get into hboot.
ΠΣΘ said:
Hold down Volume UP+Power for about 10 seconds until the screen goes black and then immediately hold Volume Down+Power until you get into hboot.
Click to expand...
Click to collapse
I can get into HBOOT just fine, but no further. It's almost as if recovery isn't even installed.
craichead said:
I can get into HBOOT just fine, but no further. It's almost as if recovery isn't even installed.
Click to expand...
Click to collapse
You DO NOT NEED to flash stock recovery if you are wanting to return back to stock.
If there is nothing on your internal memory that you are wanting to save, then follow the instructions for flashing the RUU in hboot via rename and sdcard. I gave you the link you needed to follow which outlines precise directions to get you completely functional again in the phone state you desire.
ΠΣΘ said:
You DO NOT NEED to flash stock recovery if you are wanting to return back to stock.
If there is nothing on your internal memory that you are wanting to save, then follow the instructions for flashing the RUU in hboot via rename and sdcard. I gave you the link you needed to follow which outlines precise directions to get you completely functional again in the phone state you desire.
Click to expand...
Click to collapse
Everything I've read says that you do need to flash stock recovery in order to receive OTA updates, which is what I'm trying to do. I'm not trying to flash a zip.
craichead said:
Everything I've read says that you do need to flash stock recovery in order to receive OTA updates, which is what I'm trying to do. I'm not trying to flash a zip.
Click to expand...
Click to collapse
You need to be on stock firmware in order to take a OTA. That means stock firmware with FOTA enabled, and stock recovery.
Flashing a RUU returns you to a stock state of re-locked hboot, stock recovery, and stock rom with FOTA enabled. I can't help you any more if you don't follow the directions sir.
Flash the RUU and profit.
Good luck,
Neo
Flashing the RUU will flash the stock recovery.
Sent from my HTC6535LVW using Tapatalk
ΠΣΘ said:
You need to be on stock firmware in order to take a OTA. That means stock firmware with FOTA enabled, and stock recovery.
Flashing a RUU returns you to a stock state of re-locked hboot, stock recovery, and stock rom with FOTA enabled. I can't help you any more if you don't follow the directions sir.
Flash the RUU and profit.
Good luck,
Neo
Click to expand...
Click to collapse
I appreciate your help, but this isn't about me not following directions. I'm trying to figure out why my stock recovery doesn't seem to be flashing properly and, no disrespect intended, but you haven't addressed that issue directly.
craichead said:
I appreciate your help, but this isn't about me not following directions. I'm trying to figure out why my stock recovery doesn't seem to be flashing properly and, no disrespect intended, but you haven't addressed that issue directly.
Click to expand...
Click to collapse
None taken. I have not addressed the failed recovery flash because it could be a number of different reasons. I don't dwell on why things don't/didn't work.. I focus on the primary objective. Your primary objective was outlined in the OP of this thread and is as follows:
craichead said:
I wanted to run an OTA update
Click to expand...
Click to collapse
If the rom currently on your phone is in a completely stock state and simply rooted with no system files deleted or modified, then what you attempted to do with simply flashing a stock recovery would have been the minimally required thing to do.
If however you've deleted system files or flashed to a custom rom, then you will need to return your device to a stock rom, with fota enabled, and stock recovery flashed. The easiest method to achieve this directive is to flash a RUU, which contains all of the above requirements for being in a state to receive any OTA on top of updating all of your firmware to the latest OTA that we've received to date.
I do see your point, and loading the RUU might well work. But I would prefer to be able to back up my apps beforehand and I can't do that if I can't boot up. I did successfully re-flash TWRP recovery, but for some reason it still won't boot up; it's stuck in the reboot loop that I described (though I am still able to get into HBOOT).
craichead said:
I do see your point, and loading the RUU might well work. But I would prefer to be able to back up my apps beforehand and I can't do that if I can't boot up. I did successfully re-flash TWRP recovery, but for some reason it still won't boot up; it's stuck in the reboot loop that I described (though I am still able to get into HBOOT).
Click to expand...
Click to collapse
Dirty flash (without wiping) the rom you are currently on. If S=ON, fastboot flash the included boot.img with it as well.
ΠΣΘ said:
Dirty flash (without wiping) the rom you are currently on. If S=ON, fastboot flash the included boot.img with it as well.
Click to expand...
Click to collapse
Does that mean just restoring my backup in TWRP? I am S-OFF.
craichead said:
Does that mean just restoring my backup in TWRP? I am S-OFF.
Click to expand...
Click to collapse
That should work also, yes.
ΠΣΘ said:
That should work also, yes.
Click to expand...
Click to collapse
That worked! Thank you. I have all of my apps and they're all organized the way that I had them. I'm guessing the next thing I need to do is do a back-up, then flash the RUU, then the OTA should work?
craichead said:
That worked! Thank you. I have all of my apps and they're all organized the way that I had them. I'm guessing the next thing I need to do is do a back-up, then flash the RUU, then the OTA should work?
Click to expand...
Click to collapse
Yes. However, if you flash the latest RUU, you won't receive any OTA because the latest RUU contains all the firmware from our most recent OTA lol. You will be in a state though to receive any future OTAs should they come.
Make sure to back up your internal memory to either your sd card or your computer as the internal memory gets wiped in a RUU.
So I downloaded the RUU, but I can't seem to be able to copy the file to the external SD card as instructed. I go into ES File Explorer and access Device\storage\ext_sd and try to paste it there, but it says "not enough space". Which is weird, because it says that the directory is empty (and hidden files are enabled).
Related
I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.
hocplyr98 said:
I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.
Click to expand...
Click to collapse
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!
okantomi said:
Can you get to the "starting fastboot protocol" screen?
Click to expand...
Click to collapse
yes if you somehow get into fast boot your problems can be solved.
I do not know whether by pressing vol up at boot time you can go to fastboot protocol screen.
okantomi said:
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!
Click to expand...
Click to collapse
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore
hocplyr98 said:
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore
Click to expand...
Click to collapse
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.
okantomi said:
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.
Click to expand...
Click to collapse
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...
hocplyr98 said:
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...
Click to expand...
Click to collapse
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518
Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.
Saintfyre said:
Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.
Click to expand...
Click to collapse
Keep an eye out on ebay, I just got a xoom on there with launcher force closing repeatedly for $264
Sent from my ADR6400L using XDA App
davidsos said:
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518
Click to expand...
Click to collapse
Not impossible but not as likely as you would think with the 100 "I think I bricked My xoom threads floating around.
To the OP...if you do not even know whether clockwork modified recovery is installed on your device then I am not sure you have the knowledge necessary to be messing with your device...I guess most people need to learn the hard way...
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up or go to recovery… well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, have found a way to unbrick your device! after bricking my phone and finding different ways how to do it...
Because we are not able to swap or get the sdcard out from the phone, it makes it difficult on how to add a ROM.zip and re-install. Another issue I found is that CWM will not be able to read the sdcard if you do an adb push ROM.zip /sdcard/ROM.zip or by mounting the sdcard adb shell mount /sdcard . If you have this issue will explain later
So let's get started.
Step 1: Turning Off Your Phone and Reboot to Boot-Loader
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to turn off by pressing the volume down + power button until the phone shuts off then turn on to boot-loader by pressing volume down and press for 3 seconds the power button. once in boot-loader select fastboot.
Step 2: Adb push to SD card
I assume that you have install CWM, if you don't you can download it from HERE. Once downloaded install CWM fastboot flash recovery CWM.TOUCH.5.8.3.1.img, where your done go back to boot-loader and select recovery. Once in recovery do an adb push of a ROM, in this example I used "Energy ROM" you can get the ROM from HERE. Once you have your ROM rename ROM.zip and push adb push ROM.zip /sdcard/ROM.zip, you will get a message stating the size of the the push.
If you can't do a push because you got an error message will explain later.
Step 3: Wipe The Phone
Make sure to do a Factory Reset / Wipe before installing ROM
Step 4: Reboot back to fastboot
Once you install the room you will need to make sure you have a boot.img for the ROM your using.
adb reboot bootloader
fastboot flash boot Recoveries/boot.img
YOUR DONE
If your the unlucky one's that can't do an adb push to the SD card do the following.
- Reinstall STOCK Recovery fastboot flash recovery recovery.img
- Lock OEM fastboot oem lock
- Unlock OEM fastboot flash unlocktoken Unlock/Unlock_code.bin
- Reinstall CWM Recovery fastboot flash recovery CWM.TOUCH.5.8.3.1.img
That should fix the problem on how to push back to the sdcard
If you have other methods post them below...
Sticky!!
But this won't work if you flash a wrong radio, will it? I thought that if you flashed a wrong radio, you couldn't get anything done, even not booting into bootloader, because it boots the radio first?
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
This tutorial already exists as a sticky in the Q&A section:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC VLE_U using Tapatalk 2
Nice writeup.
For every new Phone I own, the first thing I do after flashing a Custom Recovery is Making a Nandroid Backup of the stock Rom. If something goes wrong after flashing a bad rom I just restore to Stock rom.
A real life Saver for me.
snwman said:
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
Click to expand...
Click to collapse
It worked for me when I bricked my phone and had to find ways how to be able to load a ROM back to the SDcard and reflash it...
This is a combo of a tutorial cannondale wrote and one I wrote myself.
His is stickied in Q&A section, mine is in Android Dev section...
Not sure why this is here lol.
i get the error 155 when trying to install the RUU
420haxr said:
i get the error 155 when trying to install the RUU
Click to expand...
Click to collapse
Try to relock your bootloader first.
In fastboot:
fastboot oem lock
Sent from my HTC One S
Issue
Ok, still running into an issue. No errors when I push, I locked, unlocked, tried everything again. Reset everything, installed fresh CWM, tried it all over...
What's happening is that it's saying it pushed the file over, but I can't find it anywhere after it's done. This happened the first time I installed custom...I just can't remember what I did to get it to work...
Anyone has the link of stock recovery for HTC One S z560e(ville c2)?? i get error 155 when i try to install with RUU.
After i flash the cwm touch recovery I cant boot into recovery... my phone is stuck on the HTC boot logo with the red text underneath. Is it a problem with recovery or should i try install an RUU. My phone is HTC One S villec2 (S3).
Not even sure where to start. I've had my One S (TMO) for about 2 weeks now. I immediately followed all the guides to unlock my bootloader, install custom recovery and install custom ROMs. Was running Viper OneS for a while and then switched over to TrickDroid (both 7.0.0 TMOUS and 8.1.0). All of the ROMs seemed to give me some odd issues.
With Viper OneS (after patching my services.jar) I was able to install SManager and run the V6 supercharger script, but after reboot, I was no longer able to get into the ringtone and notification sounds options on the device. When I went to either screen they were just blank and I couldnt choose music from any location on the phone.
With TrickDroid 7.0.0 TMOUS, I was able to patch services.jar and run the supercharger script without any issues at all. However, after a few days of usage, I noticed that calls were no longer forwarding the voicemail number I setup using an MMI code. From there I went to TrickDroid 8.1.0 but even after patching my services.jar, my supercharger settings would not stick after reboot.
Here's where I think something went wrong. I wanted to go back to stock but rooted. Since there were no 2.35 RUUs available for download anywhere, I decided I would download the 1.84 RUU and then get the OTA update. I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems. Unlocked the bootloader and installed TRWP 2.2.2 so that I could flash supersu and root the phone and noticed that the phone was not acting right. From TWRP, its almost impossible to get the phone to reboot. When I choose to reboot, the screen goes blank, flashes once or twice and the notification light keeps turning from orange to green and then back again. I have to hold power down for about 10 seconds, then hold volume and press power to get into bootloader just to turn the phone on.
Decided to try going back to a custom ROM and noticed something else that is strange. I wanted to flash TrickDroid 7.0.0. and during the flashing, it hung on flashing the kernel for like 5 minutes when it usually takes just a second. I then flashed the fusion v2.1 kernel and it hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds. After the flashing was done, I booted up the ROM and when I went into settings, the new kernel was not installed. I flashed it again in recovery and booted back to the ROM and still the stock kernel was showing.
Could I have somehow really screwed up my phone throughout this whole process? Is something corrupted on the NAND that is causing issues with rebooting recovery and flashing things?
[email protected] said:
I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems.
hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds.
Click to expand...
Click to collapse
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.
dc211 said:
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.
Click to expand...
Click to collapse
Thanks for the info! Glad to know I didnt mess anything up .
One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
EDIT: Wow.... i feel really dumb now. All posts I found while searching included the extra "recovery" in the commany. I just ran fastboot boot recovery.img and all is well.
[email protected] said:
One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
Click to expand...
Click to collapse
.
I doubt that the actual recovery img is named recovery.img. If I am correct that is your problem. You would be trying to boot a recovery img that doesn't exist. It should be:
fastboot boot recovery [name of recovery file].img
Example:
fastboot boot recovery cwm_5.8.3.1_ville_recovery.img or something to that effect (not sure what the actually file name is)
if you are not sure on exact name as behold mentioned, just right click on the file (.img) wherever you have it on pc, check properties, and it will tell you exact name. at that point i just copy and paste it to command window--
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
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Moogagot said:
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Click to expand...
Click to collapse
Flash the boot.img from the stock system image. This has been mentioned many times around this forum. Search is your friend.
cntryby429 said:
This has been mentioned many times around this forum. Search is your friend.
Click to expand...
Click to collapse
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Well, it's actually everywhere. However, you have to discern what apply to you and what do not. That's the danger of a public forum such a this. Everyone has an opinion. Sometimes, an inaccurate answer is provided. Most other times, the incorrect question was originally posed.
In your case, you don't need to go back to the original stock image. Assuming your bootloader is still unlocked, just flash 7.1.1 and get on with your life. Download 7.1.1 stock image from the Google developers' web site. Extract it. Edit the flash-all.bat file to remove the -w switch if you don't want to lose userdata. Boot the phone into bootloader. Execute flash-all.bat. Then you have 7.1.1.
If you don't have a recovery backup, then you're taking a risk. I have not only a recovery backup, but more importantly, a complete set of Titanium backup on my laptop.
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
robocuff said:
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
Click to expand...
Click to collapse
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Moogagot said:
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Click to expand...
Click to collapse
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
quangtran1 said:
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
Click to expand...
Click to collapse
I broke recovery. I just says "No Command"
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
Come on man, you can do it next time. Please?
http://lmgtfy.com/?q=no+command+stock+recovery+pixel
krelvinaz said:
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Click to expand...
Click to collapse
No menu appears. I just get a flash and back to no command.
I can get into the bootloader, but again, any option leads to the No Command screen.
Ok, from the bootloader I was able to manually flash a different image and things are looking a little better.
I now have the dancing dots and ADB see's a device attached. PROGRESS!
The devices throws errors on bootup, but it runs for now.
Please ignore. Posted to wrong thread. Sorry!
Here's the easiest way I've found to update. You'll need TWRP, so go ahead and download it - https://twrp.me/devices/googlepixel.html. Put the img file on your computer and the zip file on your phone. You'll boot into TWRP by using the "Fastboot boot" command. DO NOT "fastboot flash" it or you'll have to re-flash the boot image to get your phone out of a bootloop.
Now that you're in TWRP, you'll need the OTA file. I've only tested going up one increment so I suggest doing it that way. If you're brave, go ahead and download the latest OTA - https://developers.google.com/android/ota. Worst case TWRP won't flash it and you'll have to go back and do them incrementally.
Now that you're in TWRP and have the OTA and TWRP-RC1.zip on your phone, flash the update just like you would a rom. As soon as it successfully flashes (and before you reboot), flash the TWRP zip.
I did this incrementally from NMF260 > NMF26U > NMF26V without any issues. I believe it'll work as long as you're moving up an OTA just as the phone would have normally received them. Just remember to flash TWRP every time after you install the OTA as it gets overwritten with each OTA.
Sent from my Pixel using Tapatalk
Google needs to start voiding warranty for people who want to unlock bootloader
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
I Know this post is old, I am just researching but, sounds to me like you really need to search, read, and actually learn before you attempt anything on your phone. I am not being hateful or rude, just pointing out the obvious....