Help!
I have a rooted Evo that I had MikG 3.11 on. I was in the process of flashing a new Rom: Energy_3.15.2012.Sensation.Sense.3.6_ICS.zip when just a short way into it, it rebooted back to recovery.
I'm using RA-supersonic-v2.3 for recovery.
To begin the flashing process, I:
Wipe CACHE
Wipe DALVIK-CACHE
Wipe BOOT
Wipe SDCARD:.android_secure
Wipe SDEXT
Honestly, I can't recall whether I also wiped SYSTEM or not and am wondering if I did and that created my problem?
The last thing I did was Wipe ALL userdata/factory reset.
Then I attempted to flash the new rom.
After the flash failed, I wiped All userdata/factory reset again and tried the flash the rom again. Of course, it failed again.
Then I tried to restore my nand backup of MikG3.11 and it did the exact same thing. It showed about 2 dots of the restore process and then rebooted again.
I have no idea what I did wrong or what I should do next.
While waiting for one of the experts here on XDA to help, I'm going to pull my sdcard and back it up.
Please help! Thanks.
I had an old nand of Myns rom from last May and it restored just fine. Wheh!
Now I'm trying to Wipe all and restore my current MikG nand and am getting an error when formatting SDEXT
E:Can't mount /dev/block/mmcblk0p2 (or /dev/block/mmcblk0)
(Invalid argument)
Error mounting /sd-ext/!
Skipping format...
Any ideas what would be causing this?
I mounted SD-EXT and then wiped it and that seemed to do the trick. I was able to nand back to MikG.
I have no ideas what may have happened or why the phone was behaving like it was. I've never seen that before.
Before attempting to flash Energy rom again, I'll redownload it I guess.
cpalenshus said:
I mounted SD-EXT and then wiped it and that seemed to do the trick. I was able to nand back to MikG.
I have no ideas what may have happened or why the phone was behaving like it was. I've never seen that before.
Before attempting to flash Energy rom again, I'll redownload it I guess.
Click to expand...
Click to collapse
I'm not sure why you think flashing that Energy ROM is a good idea. It's for the Sensation. I think you missed that in the title. The EVO doesn't have an ICS Sense ROM available.
Just be happy you didn't brick your phone trying to flash a ROM for an incorrect device on it. That's what messed up your partitions/mount points.
Related
Ok, I just finished formatting one of my memory cards and installed a new rom. It booted fine. I went back into recovery to wipe the cache and dalvik and when I go to reboot it stays stuck at the white HTC screen. This has happened with multiple roms. After that I went back into recovery to try to reflash the rom and this is when the errors from last night come back:
Gets all the way to formatting cache, then system, then copying files....
E:Failure at line 6:
Copy_dir Package: data DATA:
Installation aborted.
This is the problem I've been running into before I formatted the card. This is a brand new Evo, with the 2.02 boot, version 4.
If I wipe data
What does this sound like? Something go bad in the rooting process? Maybe something to do with Amon recovery? Maybe try clockwork or what?
I rebooted into recovery and wiped all 3 then went to install the rom on the card and it installed this time. I don't remember my last phone working anything like this at all... not sure what gives.
Jbroad572 said:
Ok, I just finished formatting one of my memory cards and installed a new rom. It booted fine. I went back into recovery to wipe the cache and dalvik and when I go to reboot it stays stuck at the white HTC screen. This has happened with multiple roms. After that I went back into recovery to try to reflash the rom and this is when the errors from last night come back:
Gets all the way to formatting cache, then system, then copying files....
E:Failure at line 6:
Copy_dir Package: data DATA:
Installation aborted.
This is the problem I've been running into before I formatted the card. This is a brand new Evo, with the 2.02 boot, version 4.
If I wipe data
What does this sound like? Something go bad in the rooting process? Maybe something to do with Amon recovery? Maybe try clockwork or what?
Click to expand...
Click to collapse
Ive seen this also with a new phone that has the older hBoot, just without the errors. Couldn't get it to take a custom ROM but you could flash kernels with no problem.
Have you tried running the RUU and then reflashing the recovery?
xHausx said:
Ive seen this also with a new phone that has the older hBoot, just without the errors. Couldn't get it to take a custom ROM but you could flash kernels with no problem.
Have you tried running the RUU and then reflashing the recovery?
Click to expand...
Click to collapse
I think it might be something with the recovery, because I tried to flash Clockwork via rom manager and it said it took, but Amon is still there. I'm going to flash the pc36 ruu that was originally used to see if it has any affect.
Solved.. thanks for the help
I am getting the exact same situtation going on. I hope I didnt break my phone. I really LOVE this damn thing. hahah Please help. What are the steps I need to do to get my phone working again.
so i have been using CM7 RC1 w/ stock kernel for a while now, without any issues. i was reading up and wanted to try the new incredikernel though, for the governor rather than using setcpu/juice defender for increased battery life.
so i did a titanium backup, then in Clockwork did a full backup before i started messing with anything. i then mounted to computer to put the kernel on the SD card. i did this, but was confused where to actually put the .zip file so that CW would see it. SD card or internal memory? i've had this issue before.
anyway, i didn't find the .zip when i booted into recovery, so i went to re-mount to USB to move it over to the other directory, and everything seized up on me. trying to mount USB basically froze my phone. re-booting did not fix, when i try to go into CM settings or try to mount USB same freezing would happen.
OK fine, i just did a nandroid backup so i figured it wasn't a big deal since i haven't actually made any changes yet and so i restored. then it would not boot. got stuck at the CM7 bootloader. ****. so i tried an earlier restore point, from a few months ago. that worked (also CM7-RC1 when i first put it on). i didn't wipe cache/dalvik when i tried the first time, so i wiped now and then tried to restore the most recent backup again. still, no luck.
so i've been living with the older restore trying to get everything how it was before. another note, i had installed a battery meter (RC1 did not come with one), and when trying to flash this, got stuck at the same bootloader screen again. another thing to note is that i have been updating CW to the latest version when it is available, but all versions are 3.xx. the latest i think i went from 3.0.0.5 to 3.0.0.8. just trying to include as much info as possible here...
any ideas? it's frustrating because i haven't actually been installing anything new. at this point i just want my phone the way it was, i.e. getting the latest restore point to work. it won't, but older restore versions will work. did CW mess up the backup, is it corrupt? is this a CM7 issue or CW? help please!
if this is in the wrong forum, apologies, it wouldn't let me post in the dev thread due to lack of posts.
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
k_nivesout said:
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i did not do that before. i just tried though, and same result. stuck in CM7 boot loop.
wtf happened to my backup!
That happened to me once. Try this. Save everything on your sd card to your computer. Reformat card. Then put just the nandroid back on card. It might help.
Yeah sounds like it may be an issue with the SD card or your backup..
Sent from my ADR6300 using XDA App
Hi,
Im currently running CM7 with CustomMTD partitions 150.40.
It was running perfectly till today morning.
I just wanted to hav a nandroid backup so i booted into recovery and performed a nandroid backup asusual it got hanged while backing up system around upto 30mins.
So, i powered it off by removing battery and started to boot normally and it got hanged at htc white screen.
Please guys solve my problem.
EDIT: Forgot it mention that when i boot into recovery its showing the following statements
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Try flashing the Custom MTD boot attachment before rebooting. If it doesn't work, then try reflashing the ROM again (without wiping - so you don't lose data), then flash the boot attachment and try again.
I jus flashed boot and system images from an old nandroid backup of the same ROM and it booted but data and apps are missing...
I tried what you hav said but thats not working.. So, i did the above steps.
I think that error means it can't read the last log written, its probably because your cache is full when you boot into recovery. Where is your dalvik cache?
I used to get the error all the time when I had a 5mb cache. Never caused a problem though.
Have you tried a different version of cement?????
Edit: cement???? Bloody predictive text at 7am!! I meant cwm.
Sent from my HTC Wildfire using xda premium
my cache partion is of 40MB as i used CustomMTD and around 38.1MB is still free in that partition.
Have you tried a different version of cement?
Click to expand...
Click to collapse
Nope...
I have the predictive cement problem too scratch!!! Lol
I've been having problems trying to flash radio for GPS fix,so I redid mtd to stock 250 40 then through rom manager 2.5.0.7 temp I flashed radio and rebooted let everything load/settle then changed mtd back to desired amount( 145 15 ) load/settle again then did nandroid backup. I now got newer radio back with working GPS and mtd.
My point here is try resetting mtd to stock then load it all up and then try nandroid. After which just redo mtd again and restore nandroid with new settings.
P.s you don't need to use the rom manager temp method as your only restoring a backup.
sent from my wilderbeast:buzz
Okay so to start off I had RSL14 Hyperdrive installed on the rom, ended up trying a new one and when going to wipe data, cache, dalvik, system as usual i ran into an odd error. I am using TWRP recovery and when going to wipe data, the phone just restarted, so i rebooted into recovery and tried again same thing.....which was odd. So i reinstalled twrp and then tried again same thing. Then I decided to install CWM 6.0.1.2 and it wipes data and everything fine, but when going to wipe cache, dalvik, or data it sometimes states E: unknown volume for path {/sd-ext}. On top of that everyonce in a while it says E: unable to format unsafe partition?
Please help its causing me problems and I am a flashaholic.
Regards,
Sean
sean82007 said:
Okay so to start off I had RSL14 Hyperdrive installed on the rom, ended up trying a new one and when going to wipe data, cache, dalvik, system as usual i ran into an odd error. I am using TWRP recovery and when going to wipe data, the phone just restarted, so i rebooted into recovery and tried again same thing.....which was odd. So i reinstalled twrp and then tried again same thing. Then I decided to install CWM 6.0.1.2 and it wipes data and everything fine, but when going to wipe cache, dalvik, or data it sometimes states E: unknown volume for path {/sd-ext}. On top of that everyonce in a while it says E: unable to format unsafe partition?
Please help its causing me problems and I am a flashaholic.
Regards,
Sean
Click to expand...
Click to collapse
Unsafe partition usually means your internal partitions got corrupted somehow.
I would suggest to flash a stock ROM via ODIN or ADB. You could try MSkips toolbox if your comfortable using it-http://forum.xda-developers.com/showthread.php?t=1703488
message brought to you by my GalaxyS3
So....
joeyhdownsouth said:
Unsafe partition usually means your internal partitions got corrupted somehow.
I would suggest to flash a stock ROM via ODIN or ADB. You could try MSkips toolbox if your comfortable using it-http://forum.xda-developers.com/showthread.php?t=1703488
message brought to you by my GalaxyS3
Click to expand...
Click to collapse
If I flash the stock recovery via odin will this fix the partition? I'd really hate to have to do that but reflashed both recoveries a couple different times and like the rom im currently on but if it must be then I guess I have no choice.
sean82007 said:
If I flash the stock recovery via odin will this fix the partition? I'd really hate to have to do that but reflashed both recoveries a couple different times and like the rom im currently on but if it must be then I guess I have no choice.
Click to expand...
Click to collapse
I think you need to flash both of them over.
message brought to you by my GalaxyS3
Make a backup, ODIN back to stock rooted, then reflash recovery and restore
CNexus said:
Make a backup, ODIN back to stock rooted, then reflash recovery and restore
Click to expand...
Click to collapse
I was gonna tell him that, but I figured with all the issues he was having, it was better to start from scratch.
message brought to you by my GalaxyS3
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.