Develop Bugs

HELP! Boot loop on stock ROM

Hi guys!
I am sorry if this has already been answered somewhere, but I searched pretty thoroughly and I couldn't find a solution
I am trying to S-OFF an HTC Desire for a friend of mine and install CyanogenMod using this guide http://forum.xda-developers.com/showthread.php?t=1016084.
We rooted the phone without any issues, but before going through Alpharev I decided to make a nandroid backup through the phone's original recovery image (just as advised on Alpharev's site: "We try to leave the current ROM and datastructures completely intact. It is, however, advised to ALWAYS nandroid backup your phone before you run this procedure.
You will then always have a correct/current backup to fall back on in case something breaks."). So I just went into the Backup and Recovery menu and I chose backup.
Unfortunately after backing up, the phone went into a boot loop. We tried taking-out the battery and even doing a hard reset but nothing helped. Eventually we flashed the original RUU from O2 (it's an O2 Germany phone) and this fixed the issue.
I am a bit concerned since I wasn't able to find anyone who had the same problem and it is a bit weird that the phone should go into a boot loop without even installing another ROM or anything - just trying to do a backup of the stock ROM. I am thus a bit hesitant to go on with the S-OFF...
Any help would be deeply appreciated!

Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?

Thanks! Do you know why the boot loop could happen?
Moscow Desire said:
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Click to expand...
Click to collapse

I suppose, there was some code that didn't get deleted due to the rooting process, if you used unrevoked. Although it rarely happens, sometimes it does.
Or maybe it didn't like some Application. Who knows. All it takes, is 1 peice of bad code.
With AlphaRev, although many use it, I believe it changes your bootloader code.
And, you can sometimes have problems as well.
But follow the steps I mentioned, and you should be ok.
Just make sure you create and use the Gold Card first.

The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App

TheGhost1233 said:
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Right - I thought about that, but then I was hesitant, because I figured if it went into a boot loop then it probably did not create the backup image properly... So can I still restore the backup image now? It is saved on the sdcard so it should be intact after the RUU, right?

It "should be", but, one can only assume so.
Typically, I make a couple of backups each week. One never knows. Yeah, it will tell you successsful. but, better safe than sorry.

Need serious help resetting phone

Ok so I used to have a Samsung Captivate and knew how to root and flash ROMs, was pretty used to it.
I tried to do the same on my HOX, but ran into a bootloop and subsequently I think I've deleted everything on my phone. I used Hasoon2000's All in one kit and unlocked my bootloader, flashed TWRP v 2.3.3.0, but my problem arose after I tried to flash the kernel. It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Anyways, I thought maybe I just needed to wipe things. I looked around and found a source that said to wipe cache, dalvik, factory reset, and system. Wipe those 4, but not external storage or android secure. So I wiped those 4 and I intended to try the backup again but it turns out that cleared everything on my phone. Now when I hit "restore" there is nothing to select. I also used to have a custom rom on the virtual sdcard, but that's gone too.
When in TWRP and I go into "install" the only thing in /sdcard is now TWRP. After looking around, it looks like my only option is to mount the phone to my computer via TWRP and somehow download the standard OS for my One X again. Also in the Mount menu it lists "mount system, mount data, mount cache, mount sd card" I can only check the first 3 options and when I do my computer asks me if I want to format it. I guess I can't mount the sd card because I deleted everything?
If anyone has the time to help me out that would be AMAZING. Right now I don't even care about being able to flash my custom ROM, I just want to get my phone back to functionality. I would love a conversation and would be willing to gmail chat if willing.
Also my phone is the ATT version, 2.20 (or I guess it was before I deleted everything).
Thank you in advance for any help.

I guess the fastest way to get your phone working again is using RUU file, you ll find how to do it here (method 2) or here
It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Click to expand...
Click to collapse
Restoring backup doesnt restore kernel ( boot.img ), you have to flash it manually with fastboot.

Dude. U think htc offers same freedom as Samsung . U are WRONG. If u flash a rom or restore a backup. U also need to flash boot.img separately from pc. Use fastboot flash boot boot.img. i assume you know the basics. Htc don't have s-off , so writing to nand protected system storage is restricted. If u read a little you might have got this. This will solve boot loop prob
Sent from my HTC One X using Tapatalk 2

Fixed
Thanks Yasounet. I managed to flash viper in the end.

[Q] Help! Rooted 4.3, Backed up, and now cant restore backup

Hello, I recently rooted my wifes Note 2 that was on the latest OTA 4.3. Was not easy BTW. I did a back up in recovery of boot, system, and data. I figured I was good to go and start trying out other roms.
The first one I flashed was Macks Allstar 5.0 rom. Everything was great. Then my wife informed me that she did not have all of her contacts backed up to google and some were only saved to her phone. So then I figure I could just restore the original backup and extract the contacts and be able to install them to any rom.
Thats when everything went wrong. Everytime I tried restoring the back up,it would crash and recovery would do like a reboot. After many attempts I figured id try another version of recovery. After flashing many earlier versions of twrp and trying to restore, I finally was able to complete a restore from version 2.6. I was ecstatic. But then my heart sank again when boot always hangs on samsung logo. And that is where I'm stuck. I am able to flash other roms no problem but cant restore my original backup.
Needless to say my wife is ready to kill me.
Please if anyone could help me I would really appreciate it. I have searched throughout this forum and internet for hours and can not seem to find any help with this issue.
I am thankful to have been able to get this far with the help from the XDA community posts I never needed direct help even with prior phone rootings but this one has got me stumped. Thanks in advance

You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.

tx_dbs_tx said:
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
Click to expand...
Click to collapse
Thank you for your reply. I am at work right now and left the phone with my wife with a working rom. I will try phils recovery when I get home. As far as backups, I have two copies. One on my SD card and the other on PC but if they're both fried I guess that negates my efforts in redundancy. It's hard to believe the backup got corrupt so quickly. I have another backup of the 2nd rom I flashed and that one wont install as well.
Is there something I am doing wrong? If the backup file is corrupt, is there a way to extract contacts seperately out of backup?

Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry

ColeTrain! said:
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
Click to expand...
Click to collapse
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:

alexandnen said:
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
Click to expand...
Click to collapse
That's exactly right. Bootloader isn't playing well with TWRP recovery. Phil"s 6.0.7.9 seems to be compatible in most ROM vs bootloader situations. Don't use latest version of Phil's recovery as it doesn't work as well and most people recommend this as well.
If Phil's recovery won't flash your restore then Odin all the way back to stock unrooted LK8 ROM then root it with the Toolkit and flash TWRP from the toolkit at the same time. Then see if you can restore at that point.

Looks like this project has come to an end. My wife likes her new rom and doesn't want to let me work on her phone anymore. She was able to get most of her contacts back I will make sure she backs her contacts to google and I will try to convince her to install Titanium backup to backup all her app data.
Unfortunately all I have is a work issued iphone that I have no interest in jailbreaking. I really don't see the point.
I am still confident that I could have eventually restored her backup successfully with the help here.
Thank you tx_dbx_tx and coletrain for your help.

Type Password to Decrypt Storage Data???

So this started happening last night, after i wanted to make a backup of a rom it said it failed and couldnt mount the /data and then it asked me to type a passwrod to decrypt storage data....i have never had a password enabled for that and nothing i do can get past that unless i format my data completely.... i did that last night, lost all my data but it worked so whatever! however, today i try to do the same thing, make a backup to flash a new rom and backup failed and here we are again! DOes anyone know what is going on? Or how to set the damn password myself?? I dont wanna keep doing this! HELP!

Simer03 said:
So this started happening last night, after i wanted to make a backup of a rom it said it failed and couldnt mount the /data and then it asked me to type a passwrod to decrypt storage data....i have never had a password enabled for that and nothing i do can get past that unless i format my data completely.... i did that last night, lost all my data but it worked so whatever! however, today i try to do the same thing, make a backup to flash a new rom and backup failed and here we are again! DOes anyone know what is going on? I dont wanna keep doing this! HELP!
Click to expand...
Click to collapse
More info required. What are you flashing? (ROM)
This sounds similar to the RUU Google Play Edition which changes the partition sizes. When you try to flash a sense rom it sees the partition sizes have changed an assumes it is unauthorised so brings up the password to decrypt message. - this is a security measure. It doesn't matter that you haven't set a password up.
This method works to avoid the decrypt storage message.
http://forum.xda-developers.com/showthread.php?t=2733523

grentuu said:
More info required. What are you flashing? (ROM)
This sounds similar to the RUU Google Play Edition which changes the partition sizes. When you try to flash a sense rom it sees the partition sizes have changed an assumes it is unauthorised so brings up the password to decrypt message. - this is a security measure. It doesn't matter that you haven't set a password up.
This method works to avoid the decrypt storage message.
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
so for more details, last night i was on Philz recovery, i was on ARHD 5.0 and i simply wanted to go from that to Liquid Smooth, an aosp rom, and bam, thats when it started happening and so i thought it was the recovery img, so i am using TWRP now.....but today, i tried going from Liquid to Slim rom, but before i could make a backup it said it couldnt mount the data which is weird because i had literally just backed up my apps with Titanium backup onto my internal storage....
will your method work permanently? Even going from a aosp to aosp?

Simer03 said:
so for more details, last night i was on Philz recovery, i was on ARHD 5.0 and i simply wanted to go from that to Liquid Smooth, an aosp rom, and bam, thats when it started happening and so i thought it was the recovery img, so i am using TWRP now.....but today, i tried going from Liquid to Slim rom, but before i could make a backup it said it couldnt mount the data which is weird because i had literally just backed up my apps with Titanium backup onto my internal storage....
will your method work permanently? Even going from a aosp to aosp?
Click to expand...
Click to collapse
The key part is the stock recovery wipe as this resets the partition info. From there you can restore what you want

grentuu said:
The key part is the stock recovery wipe as this resets the partition info. From there you can restore what you want
Click to expand...
Click to collapse
i formatted the internal storage via TWRP, it seems to work but could it be an app doing it, do you think? im just baffled as to why it happened twice in the past 12 hours

I'm having this problem too.
I was using Philz touch recovery to restore my stock nandroid to see if the location issues I was having was device or CM11 specific. I got the /data message the OP posted, but did not think anything of it as I did not really care about any data as the device was virtually untouched from purchase.
I am not able to boot into fastboot or recovery. Adb does not see the device. When I boot it connected to my PC via usb I can see this for a short period before the window closes on it's own.
View attachment 2917354
Device is Verizon branded
[UPDATE]A friend pointed out that if you use the stock "Close apps and reboot" option it is a slower boot. Once you select that hold power and volume down and you can get into fastboot. From there I was able to get into recovery and reflash CM11. Can not get my stock nandroid to work though.

I also have a problem
impossible:
1 - unlock bootloader
2 - enter to stock recovery
3 - install ruu
what to do ?? how to revive the phone ??

[Q] wifi problem after updating to lollipop

my device is rooted and modified so i used a cwm backup to update to lollipop
every thing is fine after updating except the wifi, i can't turn it on
some other ppl have the same problem too....
plz any one know a way to fix that
thaaaaaaaanks

Try wiping cache in recovery. If that doesn't work try doing a factory reset.

i did both of that but no luck

What was modified in your 816? Depending on the version of the 816 you have you could try a couple of things. Assuming the cwm backup is good you could try wiping everything except external SD card and formating data before restoring the backup again. Another option would be to find a twrp backup of Lollipop and just flash twrp. If those other options don't work you could always try finding the ruu file for your phone and go though the process of unrooting and relocking the bootloader.

pcjunky said:
What was modified in your 816? Depending on the version of the 816 you have you could try a couple of things. Assuming the cwm backup is good you could try wiping everything except external SD card and formating data before restoring the backup again. Another option would be to find a twrp backup of Lollipop and just flash twrp. If those other options don't work you could always try finding the ruu file for your phone and go though the process of unrooting and relocking the bootloader.
Click to expand...
Click to collapse
i did try all of that but nothing fix the wifi problem
and i can't find the ruu for my device