[Q] Bricked? - Legend Q&A, Help & Troubleshooting

Hi,
yesterday I tried to upgrade to CM7.2 from a nightly. As I've been doing, I put the .zip in the sdcard and flashed it with ROM Manager (wiping everything). After flashing it, my phone stucked at HTC white screen and there is no way to switch it on, it stays at this screen all the time.
For my disgrace, it's S-ON, so I can't boot into recovery and restore anything. I've tried to restore a nandroid with fastboot and it doesnt't work (says "Failed (remote: signature verify fail)").
Any ideas? It's definetly bricked? Is there any hope of repairing it?
Thanks in advance (and please forgive my poor english xD)

vitiin92 said:
Hi,
yesterday I tried to upgrade to CM7.2 from a nightly. As I've been doing, I put the .zip in the sdcard and flashed it with ROM Manager (wiping everything). After flashing it, my phone stucked at HTC white screen and there is no way to switch it on, it stays at this screen all the time.
For my disgrace, it's S-ON, so I can't boot into recovery and restore anything. I've tried to restore a nandroid with fastboot and it doesnt't work (says "Failed (remote: signature verify fail)").
Any ideas? It's definetly bricked? Is there any hope of repairing it?
Thanks in advance (and please forgive my poor english xD)
Click to expand...
Click to collapse
What do you mean you cant boot into recovery because you are S-ON?
All you need to do is put the recovery file other wise known as flakeflash "UPDATE.ZIP" into the root of the SDcard, turn off your phone (Pull Battery), then press the down button and power button together, wait for the phone to do its stuff, then select recovery in the menu, the phone will reboot into red exclamation mark, press volume up and power, it will then go into stock recovery menu and will then look for the "UPDATE.ZIP" if all is well you should then go into the fakeflash version of clockworkmod recovery.

Does it boot when USB cable is plugged in (soft usb brick)?

ranger4740 said:
What do you mean you cant boot into recovery because you are S-ON?
All you need to do is put the recovery file other wise known as flakeflash "UPDATE.ZIP" into the root of the SDcard, turn off your phone (Pull Battery), then press the down button and power button together, wait for the phone to do its stuff, then select recovery in the menu, the phone will reboot into red exclamation mark, press volume up and power, it will then go into stock recovery menu and will then look for the "UPDATE.ZIP" if all is well you should then go into the fakeflash version of clockworkmod recovery.
Click to expand...
Click to collapse
Thank you very much, now I can boot into cwm, but I'm having some troubles when trying to flash CM7.2 (or even trying to restore any nandroid backup).
First, when I try to install CM7.2, it does it very fast, without showing any error, but when I restart the phone it gets stuck again on HTC screen.
Then I try to restore a nandroid backup but it doesn't find boot.img, system.img and data.img, skips all steps and restores nothing.
My last shot, try to install the last nightly I used, fails at the same point as when I try it with CM7.2.
I don't know what else can I do, any ideas? I hope there's still any chance for my Legend (and again forgive my bad english xD)

A few points, make sure the rom zip file you are going to flash is not corrupt or incomplete.
Boot into cwm recovery,
Make sure to format the boot, system, data, cache & ext, it wouldn't hurt to delete the dalvik cache too before flashing new Rom. Just remember NOT TO FORMAT SD card.
Using this method I have always been able to flash a new Rom.
Sent from my HTC Legend using xda app-developers app

ranger4740 said:
A few points, make sure the rom zip file you are going to flash is not corrupt or incomplete.
Boot into cwm recovery,
Make sure to format the boot, system, data, cache & ext, it wouldn't hurt to delete the dalvik cache too before flashing new Rom. Just remember NOT TO FORMAT SD card.
Using this method I have always been able to flash a new Rom.
Sent from my HTC Legend using xda app-developers app
Click to expand...
Click to collapse
I've tried this way but it didn't work
Ideas?
Thank you for your help.

vitiin92 said:
I've tried this way but it didn't work
Ideas?
Thank you for your help.
Click to expand...
Click to collapse
Prepare a new SD card in your PC (FAT32), put UPDATE.ZIP on it and a stock ROM, reboot into recovery, wipe all you can (factory settings) and flash the stock ROM, see if that works. If so, you could try to flash a custom ROM.
That is what I would try...

I'm too.
I can't up CookROm by Rom Manager,
but when i use ClockworkMod recovery, its OK

wim69 said:
Prepare a new SD card in your PC (FAT32), put UPDATE.ZIP on it and a stock ROM, reboot into recovery, wipe all you can (factory settings) and flash the stock ROM, see if that works. If so, you could try to flash a custom ROM.
That is what I would try...
Click to expand...
Click to collapse
I also tried your way but it's still broken
I don't know what else to do, seems dead xD
Thank you.
Some new ideas?

Related

GOD I feel like a noob! Optimus V, CWM, and rom issues

I rooted my device using Gingerbreak.
I have 2.2.2 installed out of the box. I installed CWM. I installed busybox.
Busybox failed. I tried all the versions that it contains.
I checked root status, and RootCheckBasic says I'm rooted.
I installed Flash ClockworkMod Recovery. It will not reboot to CWM.
It only reboots to the standard Android recovery.
I'm trying to install Bumblebee ROM 2.4.
Here are some things I am having issues understanding with it...
Backup current apps and their data with Titanium Backup (available in the Market). Is this required? The phone is new. I have nothing to back up.
Do a nandroid backup in recovery before doing anything else below.
And the nandroid backup is done with CWM? Again CWM won't reboot, only the standard Android recovery boots.
Required if installing BB 2.x for the first time: Wipe. Wipe it all. Data, cache, system, dalvik-cache, sd-ext if you've got it (might need to look under Advanced or Mounts in recovery to do the last two, and while you're there format /system). I assume you wipe it all with CWM while in recovery?
If upgrading from BB 2.3, wipe cache (and only cache) in recovery.
Does not apply to me
If not upgrading from 2.3, install Wiper zip (see below), just to be extra sure that all is wiped. Don't reboot yet. Installing wiper.zip is done by sideloading using adb commands?
Install ROM zip (see below).
I assume this too is done by copying the zip to the external SD, then selecting update from SD card in recovery... right?
Please someone shed some light on this for me.
In standard Android recovery it says e3. I know on my Captivate I had to use Odin to install GB loaders to get it to work.
THANKS!​
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
tvall said:
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
Click to expand...
Click to collapse
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
bulltproof said:
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
Click to expand...
Click to collapse
Oh, okay, um... are you using the reboot into recovery option in rom manager right after flashing?
After flashing what?
I reboot into recovery through rom manager and get:
Android system recovery <3e>
reboot system now
apply sdcard: update.zip
wipe data/factory reset
wipe cache partition
_________________________________________________________
Android System recovery...
Do not pull out the battery!!
After hitting flash clockworkmod recovery, immediately hit reboot recovery
After hitting anything in CWM it did nothing more than reboot into the standard android recovery.
This phone has 2.2.2 on it. Problem? Probably.
I followed instructions at androidcentral and got it to work.
Needed Xionia_CWMA_12518.6_VM
Installed BACKside-IHO-VM670-11222011
using Xionia_CWMA_12518.6_VM_Recovery-signed
Had a little problem today and needed to activate the phone. BUUUUT......
the rom didn't allow activation.
So I installed Bumblebee. No go.
Then I tried [rom] basic stock rom.
Neither of these will let my phone boot. It gets stuck at boot.
Nothing happens.
I can still boot into Xiona_CWMA. But no roms will work.
PLEASE HELP!!!!
Dude i m noob, and i m facing same problem,
I did root with super one click soc, and it is rooted and i am using root needed apps,
But when i m trying to clobk work recovery (i did flashing CWR from rom manager and aft that i select boot from cwr option from rom manager) it just factory reset i did this 3time all time just factory reset, then i again did but while rebooting i click home button so it gave me same option which came to above member said some e3............
And i try to select any option from it with menu button it was not applied, and no use so i removed battry and place again and start then device started dont know more what to do, help
Sent from my LG-P500 using Android-HQ App
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Bullet if u found solution pls tell me too
Sent from my LG-P500 using Android-HQ App
bulltproof said:
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Click to expand...
Click to collapse
I believe that may be due to the newer display in your phone (I'm new to this device so I dont know much yet). From the little bit of information I've gathered, devices manufactured recently have a different display that requires a kernel that supports it. In the iho roms this is included, on others you'll need to flash a kernel right after the rom.
For the stock rom I can upload what I use if you need it. Its basically the one posted here just with the boot.img swapped with one from a nandroid backup I made before switching roms
I think you're spot on with that idea.
I loaded CM7 variant, and it worked.
My question is, how do I get another ROM on it if it has the newer screen?
I loaded different kernels that were supposed to fix it, but no go.

bricked, again

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.

Softbrick after flashing theme - how to restore without losing sd content

Hi,
so I tried to install a new theme and during the install the phone froze. I tried to access the recovery again, but I can't, the phone stucks at galaxy s3 screen. However I can access download mode.
My question is, what do I have to do to keep my SD Card content (like pictures)? Which firmware should I flash? I was on Wanam Lite Rom.
Thanks for Help
Matt
MadMatt89 said:
Hi,
so I tried to install a new theme and during the install the phone froze. I tried to access the recovery again, but I can't, the phone stucks at galaxy s3 screen. However I can access download mode.
My question is, what do I have to do to keep my SD Card content (like pictures)? Which firmware should I flash? I was on Wanam Lite Rom.
Thanks for Help
Matt
Click to expand...
Click to collapse
Flashing a theme will not mess your recovery partition so it cannot happen that you have lost recovery..so try again..
Once you are able to boot into recovery flash the ROM which you were using without a wipe first...you will not loose anything..if you face problems then wipe data/factory reset in CWM ..even then you will not loose the data on your internal SD..
zoot1 said:
Flashing a theme will not mess your recovery partition so it cannot happen that you have lost recovery..so try again..
Once you are able to boot into recovery flash the ROM which you were using without a wipe first...you will not loose anything..if you face problems then wipe data/factory reset in CWM ..even then you will not loose the data on your internal SD..
Click to expand...
Click to collapse
I know that it seems strange but I'm not able to access it. I tried to install
http://forum.xda-developers.com/showthread.php?t=1844756
on my wanamlite since someone wrote it would work (I did a nandroid backup first). However the installation froze and I had to pull the battery. Since then it won't boot or boot into recovery (the syiah kernel flash screen doesn't show up either).
MadMatt89 said:
I know that it seems strange but I'm not able to access it. I tried to install
http://forum.xda-developers.com/showthread.php?t=1844756
on my wanamlite since someone wrote it would work (I did a nandroid backup first). However the installation froze and I had to pull the battery. Since then it won't boot or boot into recovery (the syiah kernel flash screen doesn't show up either).
Click to expand...
Click to collapse
Then flash CWM using odin.. Then flash the ROM after a full wipe or restore your backup
sent from here, there, somewhere!!
zoot1 said:
Then flash CWM using odin.. Then flash the ROM after a full wipe or restore your backup
sent from here, there, somewhere!!
Click to expand...
Click to collapse
thanks for that
by the way, do u have any idea how this could happen? i mean it was just a theme file and im a bit confused... what shoud I do next time if a cwm installation freezes? Is it okay to pull the battery? any other opportunities?
Cheers

Think I bricked my Desire X…can't flash any Nandroid or Stock rom.

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...

Bootloop (Device Always Boots Into CWM)

Hi everyone, I have a problem with my phone.
It is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as what the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go", expecting that it would work. It said "Rebooting..." and booted to recovery mode, so I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. And, this is where I discovered that CWM has a rainbow color mode. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted to Recovery Mode.
I tried . . .
Odin, but since it boots only to recovery, Odin isn't detecting it.
Wiped the data, cache partition, and Dalvik cache. Then restore.
Can this be fixed? I badly need help.
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Any inputs will be very much appreciated. Thanks.
No intention of giving the "Rashr" app a bad name. I just didn't know how to use it.
Endroyed said:
My device is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and I got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go" with expecting that it would work. It said "Rebooting..." and it booted to recovery mode. And I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted into Recovery Mode. Can this be fixed?
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Click to expand...
Click to collapse
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Cheers!
manojkumar8552 said:
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Click to expand...
Click to collapse
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Finally fixed it!
What I did:
1) Flashed the stock Recovery. I was surprised it was able to boot to Android cause I was thinking that the zip is only the stock recovery. It had errors though. Home Screen won't appear or load.
2) When rebooted, it got stuck in SAMSUNG boot animation, but it was all good cause Odin was still able to detect it which means it can still be rooted. So . . .
3) Flashed CWM Recovery v6.0.3.6
3) Wiped data, cache partition, and Dalvik cache.
4) Restored the backup.
Endroyed said:
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Click to expand...
Click to collapse
No Problems Buddy !!!
Step by step getting all f,,,, Fundas of Android soon

Categories

Resources