okay so my problem is that i accidentally partitioned my SD card which erased almost everything on the SD card and so.. well long story short i was trying to install a sense 3.5 ROM by flashing with CWM and so now I'm missing the CWM files on the SD card and so my phone cannot boot into CWM so i was wondering if someone can post the latest CWM files that would be found on the SD card so i can reboot back into recovery because when i boot my phone it just get stuck at the HTC logo ... ( i know really really stupid mistake ) or help me with trying to get it out of this mess up.
P.S: I'm pretty sure i can factory reset and it'll install everything again.. ( I think..) and I'm pretty sure i would lose my root and everything.. but i want to consider this a last resort.
EDIT: NEVERMIND did some tinkering of my own and was able to solve my problem (thank god) anyways this thread can now be closed i guess, sorry for the useless thread.
Do you have a nandroid backup? If you have the ENG Hboot you can flash the recovery.img from your nandroid backup from your PC to your phone using the fastboot.exe from the Android SDK. And then you can boot from the bootloader to recovery and flash a different ROM.
There might be another way too that I'm not aware of...
Yeah i just realized that i had that on my comp, and was able to make it boot up so now its running like normally thanks
Related
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.
Apologies for what is probably an often asked question, but the search seems to be down at the moment. I'm currently running Ras 2.3 and when I make a nandroid backup of my MIUI, it always runs into an error when trying to restore? I don't even know where to begin looking for solutions to the issue, is this a common thing? Should I just re-flash Ras or something?
Seems the backup was corrupted, reflash your recovery, then make a new one.
Yeah every backup I do seems to get corrupted. I'll try reflashing AmonRa.
thegregbradley said:
Yeah every backup I do seems to get corrupted. I'll try reflashing AmonRa.
Click to expand...
Click to collapse
Let me know how it goes. Also make sure to have at least ~500mb available for a backup.
So I finally re-flashed AmonRa 2.3, and my nandroids STILL show an error! It gets like one dot into resotring and says "oops! an error occurred, check the logs" or something like that. What is happening
first thing would be to check your memory card to see if you have enough space like the post above says. if that doesn't work move the recovery.log via your recovery screen to the sd card and post it here. that should get some questions answered.
edit: also i had this happen to me a couple times when trying to restore it only happened when i changed big things like the radio or the hboot or switching from aosp to sense. that kinda stuff. you might just need to start over and flash a new rom. good thing you used titanium...right? p.s. just relized you were trying to restore not backup so the memory card issue shouldn't apply sry.
I have my MIUI backup so it's not so much of a big deal since that works, but I'd like to have a 100% working nandroid backup in the event that I wanna try out a new rom. Where to I find the recovery log so that I may post it up on here? Thanks for the help guys, I'd be lost without xda
So I just tried moving my recovery log to the SD card and I got the same message, "Oops... something went wrong! Please check the recovery log!"
WTF is going on here?
Potential causes and solutions:
Corrupt SD card. You're screwed, reformat SD card and flash the rom over again.
Corrupt Nandroid file. You're screwed, delete from SD card and flash the rom over again.
Corrupt Recover. Download Rom Manager and re-flash recovery (if you use clockwork, flash alternate then back to clockwork or vice versa if you use amon ra). If this doesn't work, it's likely one of the two above.
However, this is usually the problem when they mess up.
Is there a space in the name of the Nandroid backup? Nandroid backups can NOT EVER have a space in the title. Go into your favorite file manager and remove the space if it has one and it should work just fine.
For example:
MikFroyo 4.61 is NOT an acceptable name. There's a space between the o and the 4.
KonisEliteSeriesIII IS an acceptable name. Notice, there's no spaces.
Hit the thanks button if I helped. Toodles!
Don't use ROM Manager to reflash Amon Ra. Just use the PC36IMG
Trust me on this.
Is it possible that your original nandroids were with clockwork and now that you have updated to amon that they will not work?
Okay so I've re-flashed Amon Ra and reformatted my SD card and I STILL can't get the nandroids to work or my recovery log to move over to the SD card! I've only used Amon Ra for as long as I've been rooted, and nandroids previously worked. Also, these are nandroids that I made within the last 2 weeks or so, they're not old and I have not renamed them. Should I maybe try an older version of AmonRa or something?
OMG I figured it out! Here's the story:
So I bought a new SD card a few weeks back and put it in with just a straight copy of my old SD card in there. This included my nandroid folder. I had been making backups and deleting old backups, but the folder under sdcard/nandroid/HT089HL02240 simply needed to be deleted. I kept sdcard/nandroid, deleted HT089HL02240, then made a new nandroid so that the recovery could simply make this folder itself. Somehow this worked, I don't know why, but it seemed like it might help being that you can't restore nandroids between phones. Perhaps the recovery thought I was attempting to do this, given the SD card switch. Well it works now!
alright i have cwm recovery 5.5.0.3 and went to restore a previous rom but now it wont pick up my sd card. i downgraded to 5.5.0.3 cause 5.5.0.4 was giving me problems but looks like that was a mistake. what can i do guys? i already wiped everything and am trying to either mount the sd card to load another ROM so i can flash. what should i do?
Wow, I thought I fried my phone tonight. So, since I'm a noob and managed to get my phone back up and running with a little creativity and luck, I thought I'd share so other relatively inexperienced folks could perhaps do the same thing.
I flashed CM10 tonight and followed the instructions (flashed recommended CWM non touch, factory reset, wipe /system, flash rom, flash GApps, flash darkside cache wipe, reboot). When I restarted the phone i saw the CM boot anim for about 2 seconds, and then it froze and the screen went completely black. I thought no problem, i'll just flash the Nandroid I took with the recommended CWM before I got started. (Note: ALWAYS DO THIS.) Anyway, during the restore the recovery locked up on .android_secure. Read about it and tried a rollback - got into download mode and used Odin to flash 5.0.2.6 which I had a TAR for (I didn't have a flashable on my computer for 6.0.1.1 and my internet was tweaking...couldn't download it). All fine, but then realized that Nandroids are not backwards compatible. So I'm thinking, SH*T I have a soft brick that I need to flash stock firmware for now.
Then I remembered...before I changed recovery based on the recommendation, I had TWRP installed and had a Nandroid from earlier today. Additionally I had moved both the install zip and the backup to my external SD card. I was able to re-flash TWRP from CWM and restore my backup - I could have cried when my phone booted properly.
Here were my takeaways, which I'd like to share as I think they may help newer folks:
(1) IT NEVER HURTS TO HAVE TWO BACKUP SOLUTIONS. Flash an alternative and take a Nandroid with it...then switch back if you want to. Then, if one Nandroid or recovery fails for any reason you're good to go with another. Keep flashables both on your external SD card and your computer.
(2) Keep your flashables and backups on your External SD card. Both of the popular recovery solutions allow you to access the external SD, and you're safe should you wipe your internal storage. Flash the alternative recovery, reboot into the new recovery and restore.
(3) For the love of God, DON'T PANIC. You'll probably make things worse, or pollute the forum with posts asking for help before trying to fix your own issue. I did all kinds of dumb crap tonight and got my phone into a wicked loop where the flash was going on and off randomly. It was like a freakin dance party in my living room.
Of course there are other solutions I'm sure, but under my particular circumstances this worked well - and I did it on my own which is a GREAT confidence builder for me as a noob. I hope this helps others.
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.