I have been trying a number of different methods to fully root my EVO, yet for the life of me, cannot get a new ROM to flash properly. Each time I try flashing a new ROM, I end up in an endless boot loop & must go back into my SD card & rename my stock ROM back to 'PC36IMG.zip' in order to get out of it. I have heard that this sometimes happens from not erasing the dalvik cache, yet I have tried that too & still no luck.
Does anyone maybe have some pointers on why I may be experiencing this issue each time? Any input would be greatly appreciated! Thanks!
you rename your stock rom to pc36img.zip? What is a stock rom? Where did you ever read to do that?
I don't know what directions you read, but Something is very wrong.
Well it's A stock ROM that I picked up during the many different methods of rooting I have tried... For some reason, that has been the only way to get my phone to boot after trying to flash a ROM to it...
Most of the time if you wind up in a boot loop after flashing a new rom it's because you didn't wipe data, cache, and dalvik cache before flashing.
If you are using clockwork recovery it may be your problem. It has been reported to not complete wipes fully leading to post flash boot loops. Try amon-ra recovery.
Related
I flashed CM7.1 and I'm stuck in a boot loop. I tried wipe cache partition, wipe date/factory reset, wiping dalvik cache and reflashing a different rom but still keep getting the boot loop. What else should I try doing to slove this ?
Could be kernel related, are you using an aosp and hopefully not a sense kernel? Need more info, what kernel, recovery are you using?
I'm using ClockworkMod recovery I'm not sure what kernel I using
Easy fix, recommend starting from new. wipe the entire phone in recovery at least 3 times, sd card also, backup sd card to computer if you need to via USb toggle, flash Cm 7.1, flash tiamat kernel, found in development section, reboot, good to go, nandroid once up and running, happy flashing
Thanks, okay I'm glad you said easy fix I'm not as worried now. I'm gonna follow your advice. Whats a roamer kernel ?
sorry swype acting weird, use tiamat kernel 4.1 something in development section
The FIRST Thing you should do is get rid of Clockwork Mod, and get Amon Ra, so you can wipe everything.
Just wiping Data/Cache/Dalvik when flashing a new ROM isn't enough.
Hey thanks again ! ! I followed your advice and got everything working again
I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.
If you have searched, and searched, and searched you would have realized that this is not development related.
for someone who's been around then, you should first off know that this belongs in q&a, not development.
that being said, which recovery are you using? i don't think that's your problem but a little more info would be helpful. also, which rom are you trying to use? when you're wiping, try using this, it'll wipe everything necessary. you only mentioned wiping your cache's so maybe that's it? in any case, flash the file i linked, then your rom. check the md5 on it and make sure it's a match. after you reboot, let your phone sit for 10 minutes and hopefully all will be well.
http://www.youtube.com/watch?v=JmvCpR45LKA
Mercuri82 said:
I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.
Click to expand...
Click to collapse
If you look in the darkside rom thread, and some of the other rom threads, you will see three recommended wipes: darkside super, kernel and darkside cache. I would suggest you do all three.
Sent from my SGH-T989 using xda premium
Here is a big problem as well. You wipe cache and dalvik AFTER you flash the rom. I usually do it before as well but always after. That's like wiping before you **** and not cleaning up after
Sent from my SGH-T989 using XDA
odin version
jabberbox said:
http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I used an old version I couldn't get the latest one to work. But it wouldn't even load for me. It been a min sence ive used odin. But my replacement phone is at the house I'll pm you the steps I'll take. Everyone else try to be nice even if you think the question is stupid. Try to show some love
sorry i read wrong. i thought you couldnt gain root. as far as boot loops follow darksides wipe method it work. as far as my replacement phone rooted after first boot. my usb port is broke on my old phone
anyone know how to get back to stock with out it?
sence we are asking crazy ass questions?
dam auto correct
Questions go in the Q&A section
To those of you who helped by answering my question, thank you.
To those of you who told me I posted in the wrong sub section, get over yourself. Especially the guy with 13 posts.
I am wiping cache/dalvik before and after.
I am using CWM from the market, so it should be the newest version.
Ill check out the darkside thread.
You really don't need to wipe dalvik cache after a fresh rom install, unless you didn't delete the data partition (wipe data). And you certainly don't need to do it before and after.
Wiping cache and dalvik cache is really only useful if you make changes to the system but don't want to format the data. This includes flashing themes, and other enhancements, because most of them are replacing system files. On your first boot the dalvik cache gets built. (This is why a lot of devs recommend letting it sit for a bit before using it, it's giving it time to build the cache.)
The reason they tell you to wipe dalvik cache is let's say you're installing a theme, and it replaces systemui.apk and framework-res.apk, located in the system partition. The dalvik cache is already built for these files, so in some cases if you don't wipe the cache you'll boot loop. When you wipe dalvik, you are letting it be rebuilt with the current files.
Also, while we're on the subject, another misconception I see alot of, you don't need to wipe the dalvik cache after you wipe data. Dalvik cache is located on the data partition, it's a folder there. If you wipe the data partition, you've already removed it. (Not to be confused with cache partition, which is used for different purposes. That is it's own partition.)
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
jethro650 said:
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1986893
This is the rom, i was using CMW to flash it, then it made me switch to TWRP (think its called that)......hope that helps.
Sorry I can't be of more help aside of redoing the installation of your recovery and redownloading the rom ( bad downloads happen) and making sure you do all the wipes (cache, dalvik cache and factory reset). If none of that works I'm sure someone more knowledgable than myself will chime in.
I've never run into a bootloop problem myself, but this might help you out :
hxxp://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Good luck
Have you had any luck with this yet? I've been unable to get my phone back up.
QuantumPSI said:
Have you had any luck with this yet? I've been unable to get my phone back up.
Click to expand...
Click to collapse
No luck, but then again i am a Mac user, so its a little more difficult for me to solve this problem.
Anirchy said:
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
Click to expand...
Click to collapse
Put another ROM on an sdcard. Take your battery out then press the button combo for recovery mode before you slip your battery back in. Then it'll force download mode. Reflash the new ROM after full wiping and you should be good.
Sent from my SGH-I317 using xda premium
Definitely a bad ROM. Run a MD5 checker against it prior to copying to the SD card. Note: your SD card could be the culprit.
If you have a recovery installed, ensure you WIPE everything, Fix permissions (i'm on CWM) and reflash the modem and carrier files POST rom install.
I experienced my first boot loop yesterday but I was able to recover from it thanks to a little common sense and patience. :fingers-crossed:
Good luck!
first of all, don't freak out, a bootloop isn't the end of the world. Sounds like it was a bad flash.
ppl above have obviously told you to wipe caches, and all that stuff and if it hasn't worked then you are still down and out.
I would suggest you get yourself into recovery - not going to explain that here as you said you were able to flash other roms and it didn't work and try flashing your nand backup - hopefully you have a nice clean backup from before you flashed. if so, clear caches, etc and then try flashing it it should be back to at least working.
your nand backup will have all your stuff in it as you would have had to backup from recovery, which means you'll at least still be rooted. you can then go ahead and get another rom - check the md5 and flash it
Short Questions: when I flash any ROM, besides official AOKP, my phone goes into bootloop. I'm using CWM. I do a factory reset/cache etc. then flash the new ROM, i.e. stock koodo, but they all just boot loop.
Long Story: I used to have a samsung galaxy ace, and I followed the same persedure, with CWM, and it always worked. I used CWM on my tablet, but the other touch recover has given me problems and never really worked correctly, it wouldn't even install properly. I prefer CWM. From searching around, there is some super wiper, or infamus whiper that clean the phone properly from the recover before flashing. I'm not sure if we're supose to use that before I flash a new ROM, maybe that's why its bootlooping?
What do you do before you flash a ROM? I know the ROM OP have instructions, but they end in a bootloop too.
I believe you have to be more specific if you want to get help, like the version of CWM, ROM you are trying to install and steps you are taking to insall the ROM.
Click mounts & storage, format system/data, yes. Then do all your other wiping like data and caches. Then flash ROM followed by gapps.
bobiscool07 said:
Short Questions: when I flash any ROM, besides official AOKP, my phone goes into bootloop. I'm using CWM. I do a factory reset/cache etc. then flash the new ROM, i.e. stock koodo, but they all just boot loop.
Long Story: I used to have a samsung galaxy ace, and I followed the same persedure, with CWM, and it always worked. I used CWM on my tablet, but the other touch recover has given me problems and never really worked correctly, it wouldn't even install properly. I prefer CWM. From searching around, there is some super wiper, or infamus whiper that clean the phone properly from the recover before flashing. I'm not sure if we're supose to use that before I flash a new ROM, maybe that's why its bootlooping?
What do you do before you flash a ROM? I know the ROM OP have instructions, but they end in a bootloop too.
Click to expand...
Click to collapse
You are not formatting system before installing a different base(ROM).
If you format system, data, cache, and delvik you should be good to go.
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.