Hey ,
I wouldn't consider myself a "noob" when it comes to flashing and the rooting of android but I seem to have encountered a issue a can't resolve.
A few days ago i flashed the cm9 rom , decided i didn't like it and re-stored back back to AOKP. After restoring franco's kernal was then gone. So i went and wiped the phone and re-flashed the rom and kernal. After re-booting the phone gets stuck on a bootloop and will not boot up from anything except my backups in clockwork. I have wiped the phone , cache and delvik.
Any other idea's what to do to fix this?
Thanks chaps,
J
Format system in recovery. It's under mounts and storage. Along with data and cache.
Obviously then flash a ROM of your choice.
Sent from my Galaxy Nexus using XDA App
And not restoring system data from a different rom on top of another also prevents conflicts.
Related
First, I would like to say im a newb with android and I'm stupid for doing this. Okay I have a tmobile g2 stock froyo rooted and I tried to install a different kernal called pershoots. Now when the phone rebooted, it goes into a bootloop.
Luckily I made a full backup 14 days ago in clockwork recovery. So I went into recovery mode, and did a advanced restore to restore system. That didnt fix it, so I restored boot. That seemed to do the trick and everything is working fine I hope . do I need to restore anything else that might have been associated with kernal? I don't know what I did wrong for this to happen, can anyone explain?
Pershoot works under Cyanogenmod only...
No cache? I've had problems when not wipe cache. dalvik cache wipe doesn't hurt with new kernel but make sure download was ok a lot of people have had problems with mirrors, websites,data etc etc. And if the rom is pre installed prior to installation id run fix permissions from recovery.
that is if ur using cwm recovery.
Sent from my HTC Vision using XDA Premium App
Hey, for some reason I just started having huge problems with clockworkmod recovery within the last few hours. I've had my nexus for a month just about and have been unlocked, rooted , and flashing roms since day one ( I've been flashing my phones for about two years now, just so you know I'm not a noob) and before tonight haven't had one issue. I was running aokp build 13 , and decided to check out the progress on cm9 kang. So I flashed it with no problem , rebooted, set up the rom, and then I went to flash Lean kernel 1.3.0 ( which should work for all 4.0.3 roms) and I ended up getting stuck at the "Google" boot screen, so I booted back into recovery and figured I would just restore my backup of aokp 13.... so I wiped data, cache, and dalvik and proceeded with the restore. The restore got to restoring data , and I got an error saying "data cannot be restored" or something like that. So I figured it was a fluke of some kind , so I tried again... still the same thing. So I tried another one of my backups , still the same thing . I can't figure out why none of my backups will install. So I had to download the stock recovery image and run the bat file just to get the phone working again , and everything was fine . I was back on android 4.0.1 and unrooted. So I rooted again and flashed recovery all over. Made a backup of the stock rom, and proceeded to flash aokp again and the install went smooth, but now any ics gapps I use end up in market force closes, so I figured " I don't feel like dealing with this again lol" , so I booted into recovery and attempted to restore my backup of the stock rom..... again it failed.....
I am beyond confused now what is going on with my recovery, especially since I started fresh a couple hours ago. If anyone has any idea what is going on or if anyone has some input it would be much appreciated. I'm going crazy over here
Edit: I also forgot to add that it seems recovery isn't wiping everything fully. As in I'll wipe data, cache , and dalvik , then install the same rom I was using ( the actual update.zip) , and everything will still be the same when I reboot , meaning all my apps are still there and my docks are still set up the same way like it wasn't wiped at all. Very weird , I've never seen that happen before.
Sent from my Galaxy Nexus using XDA App
Been a bit confused on this. When I initially got this phone i317 (rogers), I rooted no problem, got TWRP running no problem and first thing did a nandroid. Flashed the older stable version of paranoid android 2.54 (i believe) which is based on 4.1.2. No issue what so ever.
As well before i go on, I've been rooting phones a while. Never bricked anything and definitely know the concept of the search button.
After running PA for a day or so and not seeing too many people having issues flashing roms on this phone i flashed another ROM (unfortunately I cant remember which one, but it was one of the popular ones on xda) TWRP had no issues flashing.
When the rom booted and android itself loaded i then had three FC errors and android rebooted. Ok thought it was a bit odd. Said screw it and recovered a backup. However any backup i flashed the error continued. Tried flashing the original PA rom again, the issue continued. Eventually had to reflash in odin the original rooted stock rom.
As you have read this issue has been resolved. My question is what happened? Is this a common problem with this device? Is it perhaps an issue going between 4.1.2 and 4.1.1? Is this just an issue with the devices internal memory? I have yet to read anyone having similar issues, however am not on xda as much as i used to be.
I am really just making sure that i am not missing something obvious or if this was simply an isolated issue before i sample some other ROMS floating around this site.
Any input is appreciated.
Sent from my SGH-I317 using Tapatalk
Did you happen to wipe data before you flashed the new Rom? I have never experienced any force closes while flashing roms.
This is what I usually do when going in between roms.
1. Wipe data/cache twice
2. Flash rom
3. Usually start to hate the Rom after the first minute.
4. GO into recovery
5. Wipe data twice
6. Restore from CWM recovery.
7. Fix permissions (just in case there was a mixup (usually helps resolve force closes)
Hope this helps. If you do happen to wipe data then I am as lost as you are . Maybe try fixing permissions? I am fairly new to android but I have been picking up modding it pretty quick.
______________________________________
Phones: iPhone 4 - > iPhone 5 - > Note 2 (Always on AT&T)
ROM: International N7105XXDMA6 by miscom
LINK: http://forum.xda-developers.com/showthread.php?t=2016575
Kernal: Perseus alpha32.1
A lot of bloatware removed.
Screen on time after normal charge: 7-8 hours always.
I don't think this is a process thing.
I always full wipe before a new rom, clear dalvic and such. This was something different.
Have been stuck in many a bootloop, but never one that caused rebooting when a recovery is flashed or a different rom for that matter.
Sent from my SGH-I317 using Tapatalk 2
Some ROMs require a factory reset wipe on top of the cache and dalvik wipe. I've used PA, and when I did the standard cache and dalvik wipe to PA from JellyBeer, I had repeated FCs, which namely was System UI. Even a nandroid restore after a cache and dalvik wipe had no effect. I was still getting the same FCs. I ended up using all four wipes with TWRP and a clean flash of JellyBeer, then a nandroid restore, to get rid of the FCs. Of course, several of my settings got wiped, including DPIs. Some ROMs just don't play well with other ROMs without a factory reset after the cache and dalvik wipe, which gets rid of your settings for a clean flash.
The other possibility is you're going between 4.1 and 4.2 ROMs. 4.2 ROMs create a new directory that puts all your files into due to multi-user login capabilities. Switching to a 4.1 ROM would certainly cause confusion within the phone without transfer the files back outside of the new directory.
Thank you. That was exactly what I needed to know. Was a scary issue the day after I purchased this phone outright lol. Not an issue I've experienced before with any other device.
Cheers.
Sent from my GT-N7105 using Tapatalk 2
I was using Xylon 2.4.2 with AK Rubic r3 kernel for quite some days. Since yesterday the phone started to re-start randomly. So I decided to flash new version of AK Kernel.
Went recovery and flashed the new kernel (Diamond 99) then wiped cache and dalvik. --> ROM stuck in bootloop. Went back to bootloader and flashed Rubik -> Started, "Android is upgrading" -> Optimising app x of 214. Then stuck forever on "Starting apps".
Flashed the ROM again along with gapps -> Stuck on boot.
I don't know what to do :crying:
Any help?
I don't want to do a factory reset
unless you did a nandroid before you did all of that crazy flashing, i'm guessing factory reset and start over is in your future. not that big of a deal, you won't lose anything on your sdcard. plus, you get to start fresh and install the kernel you wanted to originally install.
1. Make sure you have the ROM, Gapps, and kernel you want on your phone.
2. Boot into recovery
3. Wipe cache, dalvik, and system
4. Flash ROM
5. Flash Gapps
6. Flash Kernel
7. Boot
If that doesn't work, you might have something screwy in your data partition that will require a factory reset.
I tried, did not work.
Ultimately restored a Nandroid taken 1 week back :/
What does wiping how /system do? It clears all installed apps ?
Sent from my Galaxy Nexus using xda app-developers app
Sounava said:
What does wiping how /system do? It clears all installed apps ?
Click to expand...
Click to collapse
It clears the entire /system partition (your ROM installation). Installed user apps are left alone (since they're stored in /data/apps). Most ROMs do that as part of their install scripts, but some still don't and they can sometimes have issues with files that are left behind from other ROM installations. I've gotten into the habit of doing it every time I change ROMs, even just on my Jellybro CM10.1 nightlies updates.
Ok great thanks for the headsup!
App data will remain intact if I wipe system right?
Sent from my Galaxy Nexus using xda app-developers app
App data should remain intact however some of your data left over can impact system apps also so if you have problems wipe it all. Also if you run into that problem again you can erase the boot partition and flash kernel again. That has worked for me in the past. In adb:
Adb erase boot
You can do the same for all partitions. If I really want to start squeaky clean I do this. Not sure if it matters or not butbit makes me feel all fuzzy.
G-Nexus Sent
I recently tried installing probam rom v4.4.9 from xda threads and followed all the instructions. everything worked fine up until the thread said to reboot the phone once more, anyway long story short i rebooted it and it was stuck at the galaxy note 2 logo (white letters black background) it was stuck like this for around 5-10mins at which point i pulled the battery and decided to go back to using rootbox rom.
Is their anyway i can install probam rom without this happening again?
I've also tried downloading and installing probam version 4.5.0 from their own website following the instructions given on xda, but once its booted from twrp it'll work until i have to reset, at which point i am back to square one, being stuck at the galaxy note 2 logo.
I have also tried installing pacman rom because i would like to use a 4.3 rom but the same thing happens, the rom will work fine until i have to reboot or it randomly reboots and gets stuck at the note 2 logo.
the only roms i am able to use without this happening are moon rom v10, rootbox rom and carbon rom, only thing is i would like to use different roms and check out their features, but i am somewhat limited to what i can use due to the above problem. Does anyone else have this issue? If so how did you get past it?
Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app
Machiel187 said:
Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
through twrp i went to wipe, format data typed yes, after this i swiped to factory reset then advanced wiped clicking cache, dalvik cache and system, if i've done this wrong could you please tell me how to do it the right way as i'm not really sure how to, thanks in advance :highfive:
i did what you told me to and flashed a stock rom through odin, went through the whole rooting process and flashed probam 4.5.0 again and this time it worked!! But no signal at all