Develop Bugs

Reboot Loop in Fresh 3.0.1.2 Any suggestions?

My phone is just rebooting to the Fresh boot animation over and over again. Here is what I've done.
I did a full wipe (3 times), cleared storage in recovery, wiped dalvik cache, pulled the battery, fastboot, wipe cache partition, wipe data/factory reset in recovery and nothing works. I'm using Clockwork Recovery v2.5.0.1 and I rooted via this method for mac:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html
I'm pretty sure half the **** I did was not necessary but I had to try something. Any ideas on what to do next?

Usually clearing cache/dalvik works... And you've wiped everything else... Have you checked the MD5 of your ZIP that you're flashing from? Or tried a different ROM?
Furthermore, have you just let the phone sit for a bit? The first boot after wiping cache can take quite a while.
EDIT: Also, did you do NAND unlock/eng hboot when you rooted?

I never did a nand backup. What would happen if I nand backup while having these problems? How do I check MD5?

I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.

Well doing a Nandroid backup of a broken ROM won't do you any good.
As for MD5, you should be able to open adb shell, then use the "md5sum" command to get the MD5 of the file. For example:
Code:
adb shell
md5sum /sdcard/some_rom.zip
You can then compare the MD5 it outputs with the MD5 posted by the ROM maker. If they haven't posted an MD5, you might want to re-think about using that ROM, and the competence of its creator. For example, CM6 Nightly has the MD5 posted in a text file in the same directory as all the ROM zip files for flashing. Amon RA Recovery has the MD5 posted in the OP of the thread, etc.

Philosuffer said:
I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.
Click to expand...
Click to collapse
What I'm trying to do is get my phone to work again. Here's what happened:
I downloaded this Rosie Clear Taskbar zip file that I found in the Themes section and flashed it. It looked horrible and was showing distorted so I figured I'll just reset my whole phone and get rid of it. Well it didn't work and it put me in a boot loop. I have no idea how to do a logcat and I'm pretty much new at this unless you post instructions I can adb with my mac. I need my phone today because it's my daughters birthday and people are going to be calling me left and right for details on the party. My phone just keeps rebooting at the Fresh boot. I can enter recovery just fine:
Is there a command I can do in adb while in recovery to make it ''safe boot''? How do I flash Fresh again?
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.

It's that easy
gqstatus0685 said:
...
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.
Click to expand...
Click to collapse
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.

Jim M said:
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.
Click to expand...
Click to collapse
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.

Apparently in my case it isn't as easy as flashing from the zip. I downloaded the ROM from geekme and put it on my SD card. Flashed it and even though it was successful I still get boot loop. Could it be because I accidentally did a nand backup of the problem?
What else could I do. I'm using Clockwork but is there a way to flash the other recovery through ADB even though my phone won't boot.
I can't take this to Sprint as it's rooted and showing the Fresh boot screen.

I had the same problem. Turns out I had the wrong kernel flashed from a previous rom. I had constant reboots, couldnt access my sd card, and the usb quit working. I had to ship it back to Asurion. Just got my new one back.
Bottom line:
MAKE SURE YOU HAVE THE RIGHT KERNEL BEFORE YOU FLASH A NEW ROM!!

SD Card
Do you have another memory card that you could use? Try putting a copy of a rooted stock ROM on it and try to install that.
http://forum.xda-developers.com/showthread.php?t=743352

As others have mentioned clockwork does not always work well with Fresh, try Amon RA's recovery

TheBiles said:
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.
Click to expand...
Click to collapse
The dalvik cache is under /data but the android cache has it's own partition.

[Q] Having BIG problem, need help!

Okay, so earlier today I rooted my evo and flashed the CM6 ROM. A little later I tried to install Google apps.
I followed a tutorial on youtube on how to install gapps using rom manager.
Now my Evo is stuck in the Clockworkmod recovery screen and when I click reboot system now it reboots and goes back to the clockworkmod screen. I tried wiping data/factory reset and then re-installing the CM6 ROM, it did not work.
I really need some help here, I'm not too experienced and I don't want to brick my Evo. How do i fix this?? I am freaking out. Thank you!

I use AmonRA recovery personally and flash everything through recovery. I had too many problems when I tried flashing things through Rom Manager app. Do you have a nandroid backup? If so install the backup and then boot into recovery and reinstall CM6 and gapps back to back in the same recovery session. If no backup, download PC36IMG that corresponds with your hboot version and put it on the root of your sd card. Boot into bootloader by holding volume down and power at the same time. It will scan the sd card for PC36IMG and then verify it. It will then ask you if you want to update. Select yes and let it do its thing and then when it asks if you want to reboot select yes. This will put you back to stock and may unroot, so you may have to do the root procedure again. Then install CM6 and gapps in same recovery session.
Before all this try wiping cache and davlick cache and reboot. If that doesn't work try powering off phone through clockwork and then boot into bootloader. It will scan for PC36IMG and not find it then you will have options to boot into different things. Select recovery, and it will boot into Clockwork. Wipe cache and davlick cache and reboot. See if this works. If not you will have to nandroid or go back to stock probably unless someone that has had this problem and comes along to help you fix it. Always wipe cache and davlick when installing something new like gapps or kernels and full wipe when installing a new Rom, unless you are updating a Rom then just Davlick and Cache.
As long as the phone turns on it is not bricked.

housry23 said:
I use AmonRA recovery personally and flash everything through recovery. I had too many problems when I tried flashing things through Rom Manager app. Do you have a nandroid backup? If so install the backup and then boot into recovery and reinstall CM6 and gapps back to back in the same recovery session. If no backup, download PC36IMG that corresponds with your hboot version and put it on the root of your sd card. Boot into bootloader by holding volume down and power at the same time. It will scan the sd card for PC36IMG and then verify it. It will then ask you if you want to update. Select yes and let it do its thing and then when it asks if you want to reboot select yes. This will put you back to stock and may unroot, so you may have to do the root procedure again. Then install CM6 and gapps in same recovery session.
Before all this try wiping cache and davlick cache and reboot. If that doesn't work try powering off phone through clockwork and then boot into bootloader. It will scan for PC36IMG and not find it then you will have options to boot into different things. Select recovery, and it will boot into Clockwork. Wipe cache and davlick cache and reboot. See if this works. If not you will have to nandroid or go back to stock probably unless someone that has had this problem and comes along to help you fix it. Always wipe cache and davlick when installing something new like gapps or kernels and full wipe when installing a new Rom, unless you are updating a Rom then just Davlick and Cache.
As long as the phone turns on it is not bricked.
Click to expand...
Click to collapse
Where can I download the pc36img? Also, it seems that when I try to wipe dalvik cache, it doesn't do anything.

try here
http://forum.xda-developers.com/showthread.php?t=884060&highlight=unroot
If you are having issues getting the img on your SD card, if you have a card reader handy just use that to transfer it over

Tower1972 said:
try here
http://forum.xda-developers.com/showthread.php?t=884060&highlight=unroot
If you are having issues getting the img on your SD card, if you have a card reader handy just use that to transfer it over
Click to expand...
Click to collapse
I did find the correct one for my hboot version, but another question I have is do I need to flash unrevoked-forever-son.zip since I rooted using unrevoked 3.32? Or do I just put the PC36IMG on the sd card and flash it? Thanks.

Okay, I seem to have gotten it back to stock. Thank god, thought I lost my evo for a minute! Thanks to those who helped me out, its 4:45 in the morning and now I can finally go to bed! ;]

LOL glad ya got it back.. Yeah thats where I was heading before I seen your post..Its 5:46 am and Im not sure how many Evo people are actually on at this time so...anyway nite

I stayed on to help as long as I could, but had to go to work. Sorry I couldn't be here to help with more questions. Funny I was just getting up for work and you guys were just going to bed.
Glad you got it fixed for now. Remember to flash CM6 from recovery and not Rom Manager. Also, flash Gapps from recovery and not Rom Manager app. Flash CM then gapps and reboot. Make sure you do a full wipe first though. You could also look for Calkulin's tools thread in Dev section of EVO forum and find his wipe all zip. You just flash it like any other zip but it formats data, cache, boot and system partitions so that when you flash a new ROM nothing is left over from old one. Good luck my friend and happy flashing.
PS. I don't think the stock rom would give you s-on since you already had s-off, so you should be good to go. I could be wrong, but as long as you still have a custom recovery and s-off you should be good to flash any Rom.

evo camera
ok i have a root evo but my camara dosent work ... can some body help me to fx that problem

What rom are you using? Do they list camera issues or camera not working in the initial post with the rom?

Camera
Lets talk about the camera not working here:
http://forum.xda-developers.com/showthread.php?p=10983385

[Q] Need some serious help =/

I was in the middle of installing cm7 r2 and I managed to drop my phone and it got shut off. Now when I turn it on it won't get past the first screen, then it resets and brings me to clockworkmod recovery. So I hope there's a way to fix this since I have access to that, but I can't find anything cause really, I don't know what to look for. Any help would be grealy appreciated.

Kaymor said:
I was in the middle of installing cm7 r2 and I managed to drop my phone and it got shut off. Now when I turn it on it won't get past the first screen, then it resets and brings me to clockworkmod recovery. So I hope there's a way to fix this since I have access to that, but I can't find anything cause really, I don't know what to look for. Any help would be grealy appreciated.
Click to expand...
Click to collapse
If you can access the bootloader and recovery, then you're most likely fine, and have nothing to worry about. Unless, of course, something was damaged internally (hardware wise) when you dropped it. Do you have any nandroid backups that you made with clockwork recovery? If you do, all you should need to do is restore that backup. I like to do a full wipe (data/factory reset, cache, dalvik cache) before restoring a backup. If you don't have any nandroid backups, then just use clockwork recovery to install the rom. Assuming CM7 rc2 is already on your sd card ( if it's not, just put CM7 and Gapps on your sd card ), go into clockwork recovery, and select wipe. Wipe data/factory reset, wipe cache, wipe dalvik cache (under advanced). Go to 'install zip from sd card', find the CM7 rc2 zip. Select it, and let it flash. Once it completes, go back to install frm sd card, and flash the Gapps. Once that's done, reboot. That *should* get you going again. Good luck.

i would try wipe caches, restoring my back up and make sure everything works, then star the process to install cm7 all over again

k2buckley said:
If you can access the bootloader and recovery, then you're most likely fine, and have nothing to worry about. Unless, of course, something was damaged internally (hardware wise) when you dropped it. Do you have any nandroid backups that you made with clockwork recovery? If you do, all you should need to do is restore that backup. I like to do a full wipe (data/factory reset, cache, dalvik cache) before restoring a backup. If you don't have any nandroid backups, then just use clockwork recovery to install the rom. Assuming CM7 rc2 is already on your sd card ( if it's not, just put CM7 and Gapps on your sd card ), go into clockwork recovery, and select wipe. Wipe data/factory reset, wipe cache, wipe dalvik cache (under advanced). Go to 'install zip from sd card', find the CM7 rc2 zip. Select it, and let it flash. Once it completes, go back to install frm sd card, and flash the Gapps. Once that's done, reboot. That *should* get you going again. Good luck.
Click to expand...
Click to collapse
I'm pretty sure no hardware was damaged. Sadly I didn't care enough about the stuff I'd lose to make a back up. I did assume I'd be able to put the rom on my sd card but I can't find a single download for cm7...but thanls for the help, I'm glad to know my phone can be saved , now off to find this file...
Found it, will update if phone will work

Kaymor said:
I'm pretty sure no hardware was damaged. Sadly I didn't care enough about the stuff I'd lose to make a back up. I did assume I'd be able to put the rom on my sd card but I can't find a single download for cm7...but thanls for the help, I'm glad to know my phone can be saved , now off to find this file...
Click to expand...
Click to collapse
Look here, gapps are on the bottom of the page, CM7 will be somewhere in the middle
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Evo_4G
EDIT: you seem to have found it

Kaymor said:
I'm pretty sure no hardware was damaged. Sadly I didn't care enough about the stuff I'd lose to make a back up. I did assume I'd be able to put the rom on my sd card but I can't find a single download for cm7...but thanls for the help, I'm glad to know my phone can be saved , now off to find this file...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=956187
All the downloads you need should be in the first few posts of this thread. Don't forget about gapps, otherwise you won't have google apps. And once you get everything up and running and stable, I suggest creating a nandroid backup! It only takes about 5-10 minutes, and can save you some real hassles in certain situations. And, since you can't boot into the ROM, you have a couple options to transfer the files to your sd card. 1) Take your sd card out of the phone, and put it in a card reader/adapter, and into your computer. 2) Put it in a different phone to transfer the files 3) the easiest way, is while you're in clockwork recovery, there should be a setting called 'usb ms togge' or something similar to that (i use AR recovery, and that's waht it's called in Ar), and that should mount your sd as a disk drive to your computer. Good luck.
Edit: I took too long, you found it already! Nice. Let us know if it all works out, or if you need more assistance.

Hooray! Phone works again!!! Thanks everyone so much for the quick and helpful replies, I'm impressed by the such friendly community!

Kaymor said:
Hooray! Phone works again!!! Thanks everyone so much for the quick and helpful replies, I'm impressed by the such friendly community!
Click to expand...
Click to collapse
You're welcome! Glad you're back up and running again! And yes, XDA is a great community, and houses many knowledgeable, friendly, and very smart people. Welcome aboard.

[Q] Tips for re-flashing Installed ROM?

I've got a general question that I haven't really found an answer for - although I know the information is there, I'm just not 100% sure how to piece it together. I'm hoping all you experts out there can help provide some guidance.
Using my EVO as an example, I currently have Fresh 3.5.0.1 flashed and have been very happy with it. But, I've been dinkin' around with Titanium Backup and uninstalled a few things (i.e. LiveWallpaper) and generally (probably) made a mess of things.
Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
I have ROM Manager installed... is it as simple as creating a NANDROID backup, downloading the ROM again and flashing? Or, should I boot into recovery and clear caches, wipe data/factory reset? I'm not sure if a "wipe data/factory reset" from the CM recovery (3.0.0.5) is the right thing to do.
Guidance would be very helpful and much appreciated. Hopefully, others could use any information provided to do the same with their device if they're unsure how to do the same thing with other ROM's.

i usually like using amon ra recovery instead of clockwork recovery which is the one use by rom manager, if you want to try it rom manager has an option at the bottom that says flash different recovery and says amon ra, if you click it your recovery will become amon ra which i like better for wiping. but to answer your question, yes for a fresh start on a new rom you need to boot into recovery, then NANDROID BACKUP, then wipe 1.cache 2. dalvik cache 3. data and then flash your new rom and you are good to go

If you want to start fresh on the current 'Fresh' ROM then, yes, wipe fully and reflash.
sent from my

Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
Click to expand...
Click to collapse
Just do exactly what you did when you flashed it for the first time. Place zip on sd card, nandroid backup, wipe everything, flash rom.

CM7 final bootloop

So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?

i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App

KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.

If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed

snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?

Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk

Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.

eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.

Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?

teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.

Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!

I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.

Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.

SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?

when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu

Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk