Related
I have hboot 1.5 and rooted my Evo 3D using the HTC method.
Anyway my screen will work in hboot, recovery, and on the HTC splash screen, but after that it just goes black.
I know my phone is fully booting though because the notification light works when I get a new message etc, and I can swipe the lock ring and feel the screen vibrate on keypad for my pin.
I think this happened after flashing a kernel in joeykrim's flash gui app.
I've tried flashing new roms or restoring a backup in recovery but nothing works.
Considering that I still have recovery and hboot is there anything I can do?
lrrowley said:
I have hboot 1.5 and rooted my Evo 3D using the HTC method.
Anyway my screen will work in hboot, recovery, and on the HTC splash screen, but after that it just goes black.
I know my phone is fully booting though because the notification light works when I get a new message etc, and I can swipe the lock ring and feel the screen vibrate on keypad for my pin.
I think this happened after flashing a kernel in joeykrim's flash gui app.
I've tried flashing new roms or restoring a backup in recovery but nothing works.
Considering that I still have recovery and hboot is there anything I can do?
Click to expand...
Click to collapse
Try wiping everything (data, cache, dalvik) then do a factory reset, then flash a ROM and boot.
Twolazyg said:
Try wiping everything (data, cache, dalvik) then do a factory reset, then flash a ROM and boot.
Click to expand...
Click to collapse
I just tried that a couple times and the screen is still going black after the HTC screen
You may need to wipe more than just /data etc. Either go find a good super wipe or format /system /boot /cache and /data might as well wipe android secure on the sd card too. Most likely you have a few leftover modules from your kernel that aren't playing nice. After doing this load the rom you want on the sdcard. Then flash it from fastboot on the computer. You won't be able to use joeykrms gui since by formatting everything you won't be able to boot untill everything is replaced. Flashing through fastboot on the computer will accomplish this for you.
3VO Sent
lrrowley said:
I have hboot 1.5 and rooted my Evo 3D using the HTC method.
Anyway my screen will work in hboot, recovery, and on the HTC splash screen, but after that it just goes black.
I know my phone is fully booting though because the notification light works when I get a new message etc, and I can swipe the lock ring and feel the screen vibrate on keypad for my pin.
I think this happened after flashing a kernel in joeykrim's flash gui app.
I've tried flashing new roms or restoring a backup in recovery but nothing works.
Considering that I still have recovery and hboot is there anything I can do?
Click to expand...
Click to collapse
You shoot boot in bootloader then hit power button > connect usb > it should say fastboot usb> flash the boot.img from the rom you flashed using command fastboot flash boot boot.img ( make sure you copy boot.img in you fastboot folder) > then fastboot boot cwmxxxxxxx.img > then flash a 2.3.4 kernel not any other ( ziggy anthrax etc ) then try to reboot. If you have wiped you rom then flash boot.img from the rom you wanna flash then boot into recovey using fastboot > then flash rom.zip >then flash a 2.3.4 kernel
Sorry i wasnt able to explain clearly .....i wanna go to work
hope this helps.
Dont forget to thank if i helped you
mnomaanw said:
You shoot boot in bootloader then hit power button > connect usb > it should say fastboot usb> flash the boot.img from the rom you flashed using command fastboot flash boot boot.img ( make sure you copy boot.img in you fastboot folder) > then fastboot boot cwmxxxxxxx.img > then flash a 2.3.4 kernel not any other ( ziggy anthrax etc ) then try to reboot. If you have wiped you rom then flash boot.img from the rom you wanna flash then boot into recovey using fastboot > then flash rom.zip >then flash a 2.3.4 kernel
Sorry i wasnt able to explain clearly .....i wanna go to work
hope this helps.
Dont forget to thank if i helped you
Click to expand...
Click to collapse
Oh man thanks so much! It totally worked!
Am I going to have to do this same procedure every time I want to flash a rom from now on, or should things be fixed?
lrrowley said:
Oh man thanks so much! It totally worked!
Am I going to have to do this same procedure every time I want to flash a rom from now on, or should things be fixed?
Click to expand...
Click to collapse
I don't know exactly if you have to follow same steps for different roms. Flash image GUI is to flash. recoveries and kernel. I had only used that software twice for kernel and never tried it for recovery. It has some issues with few kernels. Some work some dont. I use. the steps posted in second post of infected eternity rom thread . I don't follow all steps as all of them are not necessary.
And I think only 2.3.4 kernels work on hboot 1.50 with flash image GUI.Roms and kernels are meant to be flashed from fastboot using PC. untill we get s-off.
I just did the biggest F-Up of my flashing life. While following QBKing77's Rooting & CWM with unlocked, at approx 3:50, during the flashing of the root SYSTEM.img file, rather than that file, I used the wrong file to flash used an IMG file that was meant for cwm, which is a completely different task.
So now I am trying to get into fast boot and try to do it with correct SYSTEM.IMG, then to find out I never got it downloaded, the link was deadand now I can not find where to DL it from. I must've not been paying attention and got ahead of myself.
Anyone know where I can a mirror of the file found here. Its the first link in the root section labelled "moto-fastboot flashable /system image".
Am I screwed? Does anybody have a copy of that system.img file laying around. I can not find any mirrors. That is the only way I can see this getting fixed bc I can still go into fastboot mode.
ckeck this ????
http://rootzwiki.com/topic/4137-pudding-photon-pudding-bootloader-unlock-updated-8302011/
Use at own risk. ???
Can u get into rsd mode and flash 154_5 sbf
Sent from my MB855 using xda premium
Important files
Thank shabbypenguin for those
If you can get into rsd mode and connected/recognized in rsd lite you should be able to flash one of those sbf files and return to stock.
I read the instructions carefully! It said to put the oven on 350 degrees for 10mins but for some out of this world reason I put it on broil and let it cook for 20mins :/
Sent from my MB855 using XDA App
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
enzyme said:
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
Click to expand...
Click to collapse
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
SOLVED!!! THANK YOU EVERYONE!
KTT16 said:
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Click to expand...
Click to collapse
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
enzyme said:
SOLVED!!! THANK YOU EVERYONE!
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
Click to expand...
Click to collapse
1) Format system is in the "mount" options. Although it's unneeded to flash a ROM. Personally I just wipe data/factory reset and then wipe cache and have zero issues. Others may tell you different though.
2) "Install .zip from SD Card" then select whichever .zip you're looking to install.
Sent from my MB855 using xda premium
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Flashing the 198_7 sbf unroots and relocks, so you're back to square one.
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Reboot into stock recovery, when you get the recovery logo thing push both volume up and volume down at the same time to get the recovery options. Then do a factory reset and it should boot for you. After that, root and unlock again. And you didn't have the Market because you forgot to install Gapps...
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
The reason cm7 didn't have the market is that you needed to flash gapps. Try doing a hard reset. http://www.hard-reset.com/motorola-photon-4g-hard-reset.html That should do it.
try the 154 sbf
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
i had the same problem i think and was going thru boot loops but some one told me to start into recovery when you try you get that ? android screen from there hold down volume up and down at same time then wipe phone booted up fine after that.
It worked like a charm. Thanks. I'm still very new to android and hate to admit it but will be running into problems like these again. The best way to minimize it for me is, not only follow certain directions correctly to get out of these binds, but to understand them.
- So theres an image of the stock ROM stashed away on the phone regardless? And it can be accessed only via the stock recovery? Because after I succeeded in flashing cm7.1, I did a factory reset once from settings>privacy and that restored me to a fresh CM7.1. The factory reset from settings>privacy and in CWM is the same, but both different from the factory reset via STOCK RECOVERY?
- Also what would be the correct method to go from one custom ROM to another? Would it be this? :
(in CWM)
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Or can I just jump to install from zip ?
- Also regarding SD Storage (internal), only holds storage files? So on any fresh ROM there shouldn't be anything in that partition relating to that new ROM yet right? So I can delete things without worry?
You should not have to reboot into recovery, once your wipes are complete, normally you can just flash your ROM of choice in the same recovery session.
Before I flashed anything I would make a backup with CWM so you don't have to keep rooting and unlocking. You can just restore your backup.
Sent from my MB855 using xda premium
After flashing 198 7 sbf, all u need to do is flash derpunlock not go through oem unlocking, then reflash recovery.
Simple generic process for going between roms (assuming already unlocked + cwm recovery flashed; process may be different for some roms, always make sure to read directions, but this is the general concept)
1. Download rom (and gapps if necessary) and put on your sdcard
2. Boot into recovery and make a nandroid backup
3. You made a nandroid backup right?
4. Secure your nandroid backup (move it to your pc or something).
5. You know where your nandroid backup is right?
6. Wipe data/factory reset.
7. Install zip from sd (flash), choose the rom.
8. Reboot system.
At this point your rom should be all set. If for some reason you don't like it, simply boot into recovery and restore your nandroid backup. You can even make nandroid backups of various roms if you want to swap between them for whatever reason.
So my Evo LTE is running 2.13.651.1, and is on what I understand to be the newest HBOOT (1.19). Naturally, I have S-ON as a result. This is my first Android device, and I've had it about a week since switching from an iOS device. I have root and the Teamwin recovery, which I used to backup the phone. I understand this is called a nandroid backup?
I plan to flash Cyanogenmod 10, in fact I already tried once. It resulted in a bootloop, and I restored from the nandroid backup. I have since learned I need to flash the boot.img from CM10 using fastboot, Flash Image GUI, or any other alternative. Once I do this, if I want to go back to Sense 4.1 like I have currently, how would I do so? Once I flash the boot.img from CM10, I won't simply be able to restore to my nandroid from teamwin, will I? I assume that if I tried to restore from the nandroid, due to S-ON I would be unable to write to the boot partition from a recovery utility and I would be left in another bootloop. How can I get a boot.img corresponding to my stock Sense 4.1 rom in the event that I want to revert to stock?
In the folder containing my nandroid backup, I see a file called boot.emmc.win and a boot.emmc.win.md5. I understand what the MD5 is for, but is the boot.emmc.win what I will need to undo the effect of flashing CM10's boot.img? If so, how would I use it (I do not recognize that file extension, and Flash Image GUI does not seem to like it either)? If not, where would I get something that will work?
I've done several searches here and on other forums, but I can't seem to find what I need. If someone has already answered this question, could you simply point me in the direction of that thread?
Thanks in advance,
Kristoffer
I have yet to restore a back up but to avoid any issues I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
When you reboot, do not boot to recovery, the boot partition has been replaced with a temporary twrp and all you need to do is reboot normally
om4 said:
I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
Click to expand...
Click to collapse
Once I flash CM and its boot, the boot for my Sense 4.1 will have been overwritten, no? I opened Dumlock in my Sense rom (as I have not yet flashed CM successfully), and it gives me a warning to make a backup of boot PRIOR to using the app, then just under that says the app will make a backup of the boot. If I go ahead and run Dumlock, I'm not entirely sure what is going to happen. It seems that it will move my recovery (TeamWin at the moment) onto the boot partition? If this is the case, why is this something that needs to be done? Does moving the recovery onto the boot partition allow the recovery to write to the boot without S-OFF, thereby allowing a simple restore of the nandroid to replace my rom AND boot at the same time, as if I were restoring with S-OFF? Sorry if I'm not making sense, but I don't really know what I'm talking about here, and thats the only thing that makes sense to me.
I see a button in Dumlock that says "restore original boot." If I install CM and the CM boot, will pushing this "restore original boot" button give me back the boot setup for the stock Sense rom? If it does, then I could just push that button, let it do its thing, and then restore my Sense nandroid with my recovery, right?
Thanks for your help, and quick response.
Install HTC dumlock
Open the app and back up boot
Once back up is successful, press execute
Once the phone restarts it will only boot to twrp, you then go to dumlock menu again and restore boot
Now flash a Rom or restore back up and reboot
Sorry to sound ignorant, but will this method will restore the stock boot regardless of what rom/boot combination I'm currently running? Or is this creating a backup of the currently installed boot, and saving it somewhere for future use? Specifically, do I want to follow this procedure before I upgrade to CM so I have a backup of the current boot, or is this something I want to do if/when I want to go back from CM to Sense that will magically put the boot back how it was from the factory?
Yes, its a workaround that gives access to boot partition and will let you flash normally, I would only use it for stuff like nandroids rather normally flashing because it writes to boot 3 times. It's a lot of unnecessary wear and tear
Awesome, thanks alot for your help. I'm excited to go and try my CM10 rom, now I know how to get back to stock if I don't like it.
Thanks again,
Kristoffer
Hmm. Now I don't know what I've screwed up. I flashed the boot.img from the CM10 zip using Flash Image GUI, then rebooted to recovery and wiped the System partition and cleared dalvik/cache. Then I flashed the CM10 zip using twrp, cleared dalvik/cache, and rebooted. Now, I'm stuck at the CM boot animation again, just like last time. This does not seem terribly complicated, and I don't know what I've done wrong.
I understand twrp cannot flash the boot due to S-ON, but I thought flashing the boot from inside my Sense rom using Flash Image GUI would fix the problem. I restored the Sense nandroid like before, rebooted, and then I got the Recovery boot logo (htc logo, with red text underneath). After maybe a minute, that went away, and I got a Sprint logo and then the normal boot screen with only an HTC logo. The phone then restarted, and this process repeated several times. So, apparently whatever I did to the boot sector with Flash Image GUI wreaked whatever was there before, and failed to replace it with something that would play nice with CM.
A factory reset won't fix the boot, will it? All it will do is overwrite my system partition and internal sd with the default files, and I still won't be able to boot. Any idea what I've screwed up, and how I can fix it?
EDIT:
I reflashed the CM10 zip, and it still gets stuck at the CM boot logo (spinning blue thing). What are the chances my CM10 download is corrupt? Is it worth trying to redownload it, reflash boot with fastboot, then move the new zip to the phone and flash that?
What version of twrp are you using, some people have had issues with the older 2.1.8
Ok, progress. I'm on twrp 2.2.1. I wiped everything again (wiped cache and dalvik, Factory Reset, and then wiped System) and reflashed CM10. It booted this time, so I assume the boot partition is fine. Apparently I'm the retard that can't understand a point-and-click system and follow simple directions
Once it boots, however, I instantly see an error "Unfortunately, the process com.android.phone has stopped." Once I click Ok, the error will either pop back up immediately, or wait for an indefinite period and them come back. Possibly this is the result of the CM10 release not being entirely stable as of yet, I don't know.
But thanks again, your help and your fantastic Don't Panic post together fixed the problem. I think I can figure out what is going on with this error popup and fix it. So long as I have voice service in the interim, which I do, all is well in the world.
It's normal, it pops up when you lose signal, its a bug but its technically a feature. If the phone loses signal, normally android is supposed to prompt you so you are aware. I think its for debugging purposes, normally this is disabled. Not sure if its really a bug in cm or they just haven't gotten around to disabling it, but its normal. It's not a real priority either since it doesn't adversly affect the phone
Hmm. This just gets better and better. So CM10 ran nicely for awhile, then last night I rebooted the phone and the internal SD card failed to mount. Both twrp and the actual OS cannot get it to mount properly. Is this something I broke, or does it sometimes occur at random? I read the following, but I don't quite know where to go with it.
om4 said:
You're card is beyond a simple reformat, the physical address linking the card and or entire card is corrupt. Don't panic, you have to start clean. Back up the info on you external or remove it, make sure you have a ROM available on your PC. Go into recovery and repartition your phone, this will wipe all memory. You then load up a working ROM (a bad back up may be responsible or just reintroduce the problem), after you have flashed the ROM (HBOOT 1.15+ must fastboot kernel, unless S-OFF) go ahead and boot into android and restore your apps.
Click to expand...
Click to collapse
Repartitioning seems simple enough; twrp> advanced >partition SD card>swipe (leaving all settings default).
After that, I can flash the new rom and boot using fastboot from my PC, right? I'm confident that my nandroid of the stock rom is clean, because I didn't develop this problem until after I had been using CM10 for awhile. Could I use fastboot to flash the boot, data, and system from the nandroid, and be good to go? If not, is the most current file avalible to download at http://stockroms.net/file/HTCEvo4GLTE/RUU? the appropriate file I would need to restore the phone to its stock unrooted state.?
Also, none of my nandroid files have a .img file extension. Is this normal? It has the normal .md5 files, but everything else has a .win extention. I've never heard of this one. My boot, for example, seems to be backed up as boot.emmc.win, with a boot.emmc.win.md5 corresponding to it. Cache, data, and system backups are named <option>.ext4.win. Does ext4 has something to do with the filesystem of the backed up partition? If this is the case, what is a .emmc? Can I flash these files with their strange (to me, at least) extensions using fastboot as if they were all .img files?
I can't imagine any of this is really as complicated as it seems. I've used a PC and a jailbroken iDevice extensively, and never managed to break something I couldn't fix. I guess Android just doesn't like me, or something.
Thanks again for all your help.
EDIT:
Apparently physically removing the external SD from the phone allowed me to mount the internal SD as a USB device. The phone still refused to allow me to read/write data to the memory, but somehow managed to allow my PC to see it. I formatted the internal SD to fat32 (one of the limited options) using Windows, and rebooted the phone to recovery. Now, it suddenly can detect its internal SD. I was able to wipe everything, and restore my Cyanogen backup and the SD card now works again. Weird...
Since I didn't have to repartition anything, was the "physical address linking the card and or entire card" corrupt, or did I have some other issue? Also, I'm still curious about my above question pertaining to file extensions and restoring a nandroid via fastboot.
Hi, I recently bought an unlocked HTC One X+ from Mobicity, it didn't have UK/US English installed. In HBOOT it states that it's unlocked at the top of the screen.
I then took a full backup that is still on the SD card (as well as a copy on my pc), and then installed OrDroid 3.2.1 - this completed successfully but when I rebooted it just hung at the white HTC logo screen.
I left it there for ages, no joy - everytime I'd reboot same thing. I went into CWM Recovery and restored the backup I previously took. This completed successfully but now when I reboot it just keeps going back into CWM Recovyer (5.8.4.0).
I tried using Hasoon2000's utility and this will flash CWM to a later version (6.0.2.7?) and I then retry the restore but upon reboot, it goes back into the previous version of CWM?
I've searched the forums for an Asia RUU/rom but the links to external sites aren't working any more, basically, I'm stuffed - I'll keep trawling through these forums but I could really do with some clear idea of how to fix this?
Thanks very much...
Make sure you're manually flashing the correct boot.img for your rom (this will need to be done with the "fastboot flash boot" command). If you ever restore from a backup, you'll also need to flash your old boot.img manually (this can be found in the backup folder).
NasaGeek said:
Make sure you're manually flashing the correct boot.img for your rom (this will need to be done with the "fastboot flash boot" command). If you ever restore from a backup, you'll also need to flash your old boot.img manually (this can be found in the backup folder).
Click to expand...
Click to collapse
Hi, thanks very much for the reply - so there should be the correct boot.img in the backup I took on the phone (that I copied to my pc as a precaution)? What are the correct steps to restore the backup - do I need to flash the boot.img before or after the restore, and then do I need to clear any caches? Basically, I'm a little unclear on the correct order - I thought I'd been good by taking a backup first, but I've spent ages trying to restore it but haven't been successful.
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
NasaGeek said:
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
Click to expand...
Click to collapse
Thanks again, will try that later and let you know how I get on!
NasaGeek said:
The order is not terribly important. Just boot into the bootloader by rebooting the phone and then holding the volume down button. Once there run the "fastboot flash boot boot.img" command where boot.img is from the backup you made. Then boot into recovery and restore from your backup. You could do a Wipe Data/Factory Reset right before restoring, but I don't think it will make a difference because the restore should put everything the way it was regardless (cache and all).
Click to expand...
Click to collapse
:laugh::good:
It's easy when you know what you're doing - I cannot thank you enough NasaGeek, that worked perfectly and now I don't have an irate wife any more!!!!! ARGH!! :silly: Anyway, thanks very much for that info - I flashed the boot.img that was in the backup folder, restored my backup and now have a working phone again!
Hello, my phone was running slowly so I decided to go back to a previous backup and run very few apps. I restore a Nandroid backup and when I did the phone told me an update was available, I tried to install it but it just kept restarting to recovery and I had to reboot into System manually and it never applied the update.
Someone told me I needed a stock recovery, I thought Well, since I'm flashing something, why not flash a JB file too? I went and downloaded a JB rom, flashed that and the recovery but it didn't boot (probably because my hboot is 1.20) so I tried a different rom, basically I tried different combinations but somehow nothing seemed to work, and now I can't boot my phone. I've read that you can brick your phone if you wipe the EMMC, I don't remember doing that but I tried so many things that I might have wiped it without noticing. Is there a way to verify the EMMC? I can boot into recovery with fastboot, but when I install any rom, it just doesn't boot, it gets stuck in the first HTC screen with the HTC logo and those red letters I got after rooting (this rom is property of HTC...don't distribute outside without written permission...etc etc).
So, do you think this can be an EMMC problem, or just a kernel problem? I tried flashing the boot.img from my Nandroid backup (actually it was called boot.emmc.win but I renamed it to boot.img following some instructions I found online) but even with the Nandroid backup that worked before the phone would not start.
If this is indeed an EMMC problem, is there a way to fix it?
Thank you very much.
You also restored your nandroid backup from stock? As your hboot is 1.20 (which is quite old btw), you cannot flash JB kernels to boot partition so JB ROMs won't work without a workaround. So try to completely restore your stock nandroid backup or else you could try running a RUU if your CID is compatible.
dansou901 said:
You also restored your nandroid backup from stock? As your hboot is 1.20 (which is quite old btw), you cannot flash JB kernels to boot partition so JB ROMs won't work without a workaround. So try to completely restore your stock nandroid backup or else you could try running a RUU if your CID is compatible.
Click to expand...
Click to collapse
Yes I read that you need at least hboot 1.25 to flash JB, that's why after flashing JB and seeing it wasn't starting, I tried to go back to my old ICS backup, but none of them work now, I have a Nandroid backup that was working before,here's what I'm trying to do:
1. Flash my old boot.emmc.win changing the name to boot.img and running "fastboot flash boot boot.img"
2. boot into TWRP-2.4.3.0 and do a Factory Reset, followed by a Restore of my backup, which restores System, Data and Boot, and gives me a "Restore Complete - Successful" message.
3. Install SuperSU right before rebooting
4. Reboot
After that the phone just gets stuck on the first HTC screen, the one with the red letters. I don't know much about android, but I think I'm following all the steps correctly, to restore my old Nandroid backup. Or am I doing something wrong?
My CID is ORANG309, I got a 4.0.1 RUU (at least that's what the person said) and I'm going to try to recover that one. It's not a ZIP file, it's a folder with files inside, so i'll probably have to restore it as a normal Nandroid.
Try flashing the system partition as well before restoring your backup.
dansou901 said:
Try flashing the system partition as well before restoring your backup.
Click to expand...
Click to collapse
You mean formatting the /system partition? I try that too, but it doesn't seem to work. Now that I was into TWRP, I saw the Wipe buttons and there is one called "Wipe internal storage" that I might have pressed before, it kinda rings a bell. So assuming I did press it, does that wipe the EMMC? Is there a way to recover it?
I've been trying to flash using Dumlock because it doesn't seem to work from the normal recovery. Here's then what I do.
1. Boot into normal TWRP recovery.
2. Click Advanced -> HTC Dumlock
3. Inside, I click "Reflash recovery" which supposedly reflashes the recovery into boot.
3. Tap "Reboot" and "System". This should reboot into the Recovery in the boot partition, but it gets stuck in a reboot loop.
So I can't boot into the recovery that should be in the boot part. And now when I enter into normal recovery, whenever I restore a Nandroid, right after doing it if I choose "Reboot", it says "No OS Installed!"
camilou said:
I've been trying to flash using Dumlock because it doesn't seem to work from the normal recovery. Here's then what I do.
1. Boot into normal TWRP recovery.
2. Click Advanced -> HTC Dumlock
3. Inside, I click "Reflash recovery" which supposedly reflashes the recovery into boot.
3. Tap "Reboot" and "System". This should reboot into the Recovery in the boot partition, but it gets stuck in a reboot loop.
So I can't boot into the recovery that should be in the boot part. And now when I enter into normal recovery, whenever I restore a Nandroid, right after doing it if I choose "Reboot", it says "No OS Installed!"
Click to expand...
Click to collapse
I don't know wat you are doing but just restore your nandroid backup in recovery and flash boot with fastboot
GtrCraft said:
I don't know wat you are doing but just restore your nandroid backup in recovery and flash boot with fastboot
Click to expand...
Click to collapse
Yeah, that doesn't work. I restore the Nandroid and then when I go to reboot, TWRP says "No OS Installed! Are you sure you wish to reboot"
Update: Using my old Nandroid, I tried this:
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash recovery recovery.img
All of them worked, except for the "data", but the phone does not work. Tried doing the same, then flashing data from inside of TWRP recovery, same thing. Phone is stuck on the HTC screen and it doesn't work.
Any ideas?
Tried Dumlock, but it doesn't seem to be writing the Recovery image to boot. I even went and copied a recovery.img file into "/sdcard/twrp/dumlock/<device>/boot/boot.img" and from the TWRP Dumlock menu, tried to "Restore original boot" to see if Dumlock would assume that "boot.img" was the file to flash into the recovery, but when I restart it's just the HTC screen. I'm using TWRP 2.4, and renamed TWRP 2.6 as "boot.img" because the difference in version number would let me know from where was the recovery being booted, but I can't flash into twrp 2.6, aka the fake boot.img.
Tried downloading some RUUs for Spain, but the recovery process failed.
So is it safe to assume that this phone is bricked? I have S-ON, like all other Desire X devices (I think) so can you brick a phone with S-ON? Is there a way to restore the original stock rom? Or at least a way that I can remove the red letters on the boot animation, the ones that say "This build is for development purposes" so that I can take it to the store and hopefully they won't notice that my bootloader is unlocked and maybe they will fix it under the warranty?
thanks
Nevermind, I flashed a ICS Nandroid with the adequate recovery (nexusrecovery) and it works now
ics nandroid
camilou said:
Nevermind, I flashed a ICS Nandroid with the adequate recovery (nexusrecovery) and it works now
Click to expand...
Click to collapse
Are you using htc desire S I'm also stuck at the HTC screen, I did HTCdev unlocking. On the recovery mode it shows unlocked, but I did not notice that S-ON was still on. Where can I find an ICS Nandroid of htc desire s? Thanks
Take a look at the HTC Desire S forum, this one is just for HTC Desire S. if you don't find it, ask there...