Issue with installing ROM? - Galaxy Note II Q&A, Help & Troubleshooting

Hey guys,
While I am relatively new to rooting and such, I feel that I know what I am doing, however, I am having a problem when installing roms.
I was rooted and running a custom ROM - but I decided I felt like an update.
I go to the ROM screen, I install from sd-card and all goes as planned. The rom then tells me to reboot. I do this, but then it gets stuck in a boot loop. It perplexes me, as I have no idea what could be wrong.
Does anyone know what the problem could be? Could this boot loop be the ROM loading? I have no idea, but perhaps a more experienced user knows what could be wrong.
Thanks guys.

Go to CWM and do wipe data/factory reset - then reboot. If it doesn't help, reflash once more

Related

Cyanogenmod and other Rom Issues

I have a Cellular South CDMA HTC Desire. I have had problems flashing roms to the device. The only rom that I have successfully flashed is Cyanogenmod 6.1.0 CR. The first time I installed it, it went into a boot loop at the Cyanogenmod boot screen. I fixed itself after a force reboot.
Now, I can not install any rom without the device getting stuck at the HTC boot screen. The only exception is Cyanogen but it does get stuck in a boot loop at the Cyanogen boot screen.
Each time I try to install a zip from SD, I do a factory reset and wipe the cache. The last time I tried to install a rom from flash, I wiped the dalvik in addition to the others.
If anyone have any ideas as to what I am doing wrong, I would appreciate your input. I am a newbie at this.
Thanks!
Hi,
Something similar happened to me recently. Fortunately, before flashing I made complete backup of my Desire. Nothing helped me but restoring from backup.
If you do not have a backup (it's always a good idea to make backup before playing with your phone), you can try the following:
- boot your device without SD card
- flash any ROM and boot wihout SD card
- try to flash with stock ROM
If nothing helps, i'm out of idea...
One thing I know is GSM ROMs will not work on CDMA Desire. Make sure its a CDMA ROM when you dowload, the cyanogen rom you linked is, there is a MIUI ROM that is CDMA also, very few out right now. If anyone knows of others it would be awesome to know of them.

[Q] phone keeps restarting. need help

i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks
antn said:
i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks
Click to expand...
Click to collapse
wipe and reflash the rom. or wipe and try another rom and kernel. every time you wipe, you want to reflash.
yea i already tried doing that and it would do the same thing.
I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.
I'd rather flash the takju build via fastboot using efrants step by step instructions. If I were to buy a used phone I'd want to do all the rooting and flashing as if it were a new device.
- Google
kvirus11 said:
I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.
Click to expand...
Click to collapse
restore point? lmao! theres no such thing. you can restore a nandroid backup, but i doubt the previous owner would leave it in your sd storage considering all his/her personalinformation/data would be contained in it.
i got it to work now. i was able to learn and unroot the phone through the guide. at first i thought it wouldnt work cause i couldnt access the phone to put it in debugging mode but i guess it was already on and i did the whole unrooting process and flash stock image with no problems. thanks guys

My phone sometimes crashes, how can I rule out a software issue?

Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
marcusabu said:
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
Click to expand...
Click to collapse
ahsanali.pk said:
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
Click to expand...
Click to collapse
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
marcusabu said:
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
Click to expand...
Click to collapse
ok, if you want to get the total old look, relock the bootloader, and install official GNex image that comes straight from Google. Hope this sorts the issue out.
Yes, Custom ROMs are a bit time taking to setup in the start, but thats the whole point - a lot of options. I flashed alot of ROMs and luckily, I have had no boot issue still. I think following the proper instructions(which are simply wiping and formatting data, cache, and dalvik) are easily gonna keep the boot loops away.
You can rule out a sw issue by starting fresh.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250

Can't do a factory reset

Hey everyone,
so I've been using Cyanogen Mod 10.1 by Owl Project thus far, but I've decided to switch the ROM to Marvelous CM10. I followed the usual procedure, backed up what I needed, did a factory reset (that was always enough), flashed the new ROM, and rebooted. But it rebooted into the same ROM, not the new one. So I did a factory reset again, but this time I also wiped dalvik cache, battery stats and such. Re-flashed Marvelous CM10 again, but the phone still booted into the old ROM. Had no errors when doing the factory reset (I saw other people not being able to do it because some of the partitions could not be mounted, etc.). So what shuold I do? Any help would be really appreciated.
EDIT: I managed to restore my backed up stock ROM. I'll try flashing something of my choice in the near future. If anyone has any clues as to what caused the problem, it would be great if you shared your thoughts. Not necessary, though.
EDIT #2: Turns out the installer for the ROM I wanted to install doesn't work at all. So if any admin could delete the topic, it would be appreciated. I can't seem to figure out how to delete it on my own.

[Q] UID system Inconsistent- Solved

Hi Forum,
I was running Indie ROM 4.3, v19. I did the 3 wipes and installed Indie ROM, v20. After installation,
I got this message( "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
with a button that stays "I'm Feeling Lucky).
I research XDA , some stated to reflash the ROM using TWRP, and then fix permission. I am using Phil Touch CWM, which has fix permission. However, I still get the same message.
The phone is usable, but certain Google app wont install.
Anyone has an idea how to fix this? Would flashing a ROM from another Dev fix this problem?
Thank you for looking, and then some.... for your helpful suggestion.
OK, I got tired to flashing. Used TWRP to repartition the whole drive. This fixed all the issue.
I solved the problem. I install TWRP, wipes and fix permission. However, TWRP reported that fix permission has failed. I let the phone reboot. ROM start up with out problem. Guess I will be using TWRP from now on.
I spoke to soon. I was not able to install many of Google apps. Reinstall ROM again and now getting the the same message ...UID..
Anyone have any idea?
What does this mean - it's solved, but it ends with a question?
Okay. So I use philz 6.26.6 and never had an issue. I've had UID issue before, but only when dirty flashing roms. A factory reset (in the settings menu) always resolved it.
Probably the cleanest solution HERE

Categories

Resources