Installed king kang rom on my i717 4.0.4 from the development page and got a boot loop. wtf I'm so sick of boot loops. luckily i made a backup, restoring now.
This happen to anyone else? how can one fix that?
Boot loops are of course common. but can generally be blamed on the device not being clean when flashing a new build.
Wiping the old data is critical before flashing new roms.
Wipe cache
Dalvik cache
Data
System
Kernels, and other images being flashed to the device before or after the ROM can also give you problems.
Review the OP in the ROM thread carefully that you intend to flash, as it often contains information that will prevent such an occurence.
1000's of users are running this ROM without any boot loops, so it must be a dirty device, or the wrong data being left, or placed during the flash.
And always verify the MD5 sum of the build with your downloaded copy, to verify a good file has been copied......g
gregsarg said:
Boot loops are of course common. but can generally be blamed on the device not being clean when flashing a new build.
Wiping the old data is critical before flashing new roms.
Wipe cache
Dalvik cache
Data
System
Kernels, and other images being flashed to the device before or after the ROM can also give you problems.
Review the OP in the ROM thread carefully that you intend to flash, as it often contains information that will prevent such an occurence.
1000's of users are running this ROM without any boot loops, so it must be a dirty device, or the wrong data being left, or placed during the flash.
And always verify the MD5 sum of the build with your downloaded copy, to verify a good file has been copied......g
Click to expand...
Click to collapse
Hmmm okay i'll try the MD5 thing. Though I get the links for the downloads right off the developer's threads and they don't always have it.
All That wiping is redundant... if you look at the log in recovery you'll see Wiping data as in a factory reset also wipes /cache
And dalvik is on the data partition so it's also wiped.
And any dev who's Rom is worthy of flashing will have the script format /system.
All I do is wipe data/factory rest(same option on recovery not separate choices) then flash Rom.
I'd lean more toward corrupted download over anything else, improperly wiping would more likely cause instability in a Rom than cause it to bootloop completely, from my experience anyhow.
Whereas corruption in the Rom zip could easily do it... just one .apk or .jar in the the /system/framework folder for example.
If no md5 is available, go ahead and download the Rom again fresh.
And as Greg said.. if you're flashing anything after the Rom, consult the op for compatibility.
Or better yet, just flash the Rom and let it settle... then once you see its working correctly and only then, flash anything else.
thanks for the tips...i reset and reinstalled and its working great now! had a few bugs but fixed them by searching the forums here. this rom is friggin powerful. im gonna finish setting it up and make a nandroid backup!
Related
So...I can't install either of the two CM based ROM's I've downloaded. However, on the first try, I installed VEGan, and then tonight TNT Lite, with no issues. Any CM ROM I try to install just sits on the loading screen, regardless of how long I wait. Is there something special that needs to be done to install them, different than what I do for other ROM's? (Clear data/cache, flash the ROM, clear data/cache again, reboot.)
sfreemanoh said:
So...I can't install either of the two CM based ROM's I've downloaded. However, on the first try, I installed VEGan, and then tonight TNT Lite, with no issues. Any CM ROM I try to install just sits on the loading screen, regardless of how long I wait. Is there something special that needs to be done to install them, different than what I do for other ROM's? (Clear data/cache, flash the ROM, clear data/cache again, reboot.)
Click to expand...
Click to collapse
I believe you have ClockworkMod 0.8 recovery, since you were able to flash Vegan Rom.
In general, before you flash the different rom
1. Back up your current rom
2. wipe data (factory reset)
3. wipe cache
4. flash the rom
5, flash gapps
6. reboot
Hope this helps
There have also been some reports of G-Tablets coming out of the box with incorrect partitions.
Using NVFlash has cured those issues. You should then be able to flash CM7 Roms through CWM like everyone else.
I repartitioned with 2048/0, shouldn't that rule out any partitioning problems?
I'm trying it again right now with flashing the rom then gapps.zip, waiting for it to boot...or just stay on the boot screen.
Format system and data, then follow those steps again. I ran in to similar issues when I hadn't formatted.
Also, do the three wipes again after installing the ROM and gapps.
Holy crap! I see the CM boot screen now! Thanks for the help guys. Now, do I still need to do the market fix (http://forum.xda-developers.com/showthread.php?t=865245)? It looks like from their changelogs that the latest version of Flash is cooked into the ROM so I shouldn't have to do that part from the guide, but I'm wondering about the market.
Well, the market seems to have everything, including an app (power control plus) that none of the other rom's let me see, so I seem to be good to go! Thanks again guys!
Thanks for the suggestion - and I'll readily admit I'm WAY out of my comfort zone with Android.
When I format the /system /data do I have to mount first?
What order do the steps run in? Do I partition and then format /system /data?
cannot install cm based roms
I was trying to reset from factory rest but failed when my gtablet stucked and apparently did something wrong along the way. Now when I turn it on, I get the 3 birds screen, followed by G-Tabdevs screen, then dead. I do have clockwork mod installed on it.
1 when I clicked factory rest, it just return to the manue and said cannot find the file.
2 when I did a back up, it went through boot image,recovery image,system and then taskbar stopped in the half at settings.apk and then dead.
3 when I tried to followed this link http://forum.xda-developers.com/showthread.php?t=865245
to use the external tf card to flash, Gtablet doesnot recogonize the external card, while I can read all the files in gtablet. I can copya single small file but cannot paste a recovery and update.zip on gtablet. Each time I copied a file from gtablet, then it is dead. I have to return on by pressing power and volume+.
4 I tried adb to push update.zip to gatblet,also failed. I feel my gtablet can only allows me to read it and refuse me to do anything on it.
Any ways to reboot my gatblet brick?
Please help! I've been reading forums all weeks trying to figure out how to fix it and am not having any luck!
Appreciate any suggestions
Hi - first time trying to root. I successfully rooted, installed Entropy's Kernel, and I thought successfully installed TurkbeyRom (I don't think this is a question specific to this rom, so I"m posting here...).
After booting back up, I get this message: " The process com.android.phone has stopped unexpectedly". This takes out my wireless signal, and keeps popping up with the error even when clear that screen out.
I realized that I didn't do any sort of data wipe before installing this rom...could that be the issue? I was under the impression that when installing them, it asked if you would like to wipe data, and it didn't.
My question is - if I wipe the data now, how much will I lose? Obviously I don't care about apps/contacts/etc..I'm wondering how far it'll set me back in the rooting process. Meaning if I wipe, will it completely wipe out my kernel...etc.
Thanks!
Boot into cwm and wipe data factory reset...then see if it fixes the issue. It wont go backwards in the root process
Sent from my SGH-I777 using xda premium
Please read before posting. Check the FAQ question [21].
- ROM install doesn't ask you to wipe, you have to do it yourself. (FAQ [21] has steps how to do it in CWM. For that, it is assumed that you followed this guide all the way through.
- any type of wipe will NOT remove your kernel. Wiping will remove stuff like your apps/contacts/etc
Wipe data/factory reset will remove any user installed applications and personal settings that have been set since the flash. It will not make any changes to the kernel or system partition, so the rom will be just like if you wiped first and then flashed the rom. That should solve any issues, but if there are still problems after the wipe, then try flashing the rom again.
Most roms here don't do an automatic wipe, afaik. You must do the wipe first, usually from ClockworkMod Recovery. It is always recommended to wipe when changing from one rom to another, from stock to any rom, etc. You can usually get by without a wipe when doing a minor upgrade of the same rom, assuming there is not change of base within the rom.
Thanks guys. It works perfectly now after wiping.
Sorry about not seeing that in the FAQs. I did look there, but I must have had a different "question" in mind than "[21] Install Custom ROM from CWM" and glanced past that one.
I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2
Lately i'm experiencing problems with flashing custom roms (i.e. UltimaROM , Xperianze, whatever)
What i did is:
1: flash the latest CWM , touch and non -touch with Odin
2: download ROM of choice , copy to internal SD-card
3: reboot recovery, fact-reset, wipe cache + dalvik
4: flash rom ( with aroma installer )
5: boot phone
with booting it keeps hanging on the Samsung i9300 logo txt. It doesnt matter which rom i flash. it always keeps hanging.
I've tried alternative methods like flashing TWRP and do the same as above but again, no success. I also tried factory-reset after flash, cache wipe etc. no success.
The weirdest thing is: when i try to flash CM or MIUI ( current running MIUI ) , it works like a charm, but normal "custom" roms are not approved it seems.
does anyone have a suggestion for me what to do? or explain what i am doing wrong , or even better, can explain why CM-based ROMS work?
Have you checked the MD5 of your downloaded ROMs when they are on your SD card? Format system, data and pre-load before flashing? Tried flashing an alternative kernel/radio before you boot the first time?
If only stock based ROMs are a problem then it maybe something that is unique to them, probably a direct hardware hit via the kernel.
Try returning completely to stock to test, flashing Samsung's vanilla EMB5 via Odin - including stock recovery and full wipe. If that doesn't work then you may have a hardware issue that CM or MIUI doesn't use.
yeah good idea to return to stock and try all over again.
to your other questions: no i didnt flash another kernel after i flashed the custom rom. i've tried with several kernels which options were given to me in aroma installer ( boeffla, syah, stock )
md5: did that
format system and data: nope. kinda relied on the fact-reset + cache/dalvik
what do u mean with pre-load?
if I were you I would format data & system again manually after the fac. reset thing, or even more clean use the mega wipe flashable zip to have a clean slate to start from (it will format anything but the ext. sd-card). Then flash the rom from your ext. sd-card and see how it goes.
additional possibly helpful hints
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
magnamentis said:
try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
Click to expand...
Click to collapse
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
thanks for the explanation which makes totally sense, so my feeling which i could not explain was right always better to learn exactly why than just guessing
no thanks button found in your post however, so i want to thank you this way.
regards
So, I made a custom PAC ROM zip for my phone with the pac_i9100-nightly-20150128.zip modded for my phone by removing the device check so it will install on my S959G. And reason for me doing this is the same for OmniRom, all SGH-I777 zips for PAC ROM and OmniROM are deleted for some reason so the I9100 is next in line for me.
Here is my process for installing this rom
Wipe user data/Factory reset
Wipe Cache partition
Wipe Dalvik cache
Installed Mr.Cooks ROM wipe script
Installed pac_i9100-nightly-20150128.zip
Installed Render-KK-03-22-CWM.zip
Installed GAPPS 4.4.4 Pico zip
Wipe user data/Factory reset
Wipe Cache partition
Wipe Dalvik cache
Reboot into PAC
I thought my steps was enough, and I'm coming from Resurrection Remix 4.4.2 KitKat v5.1.5 By SteveMurphy
Is there a step I missed in the flashing process or an app I have installed causing Random Reboot or Reboots in general.
I also checked the last_kmsg file and it said something about rebooting
<0>[ 6993.848196] c1 Rebooting in 1 seconds..
Including a link to the file on my MEGA below
My last_kmsg file
You should be wiping /system before installing the ROM, along with the usual cache wipes. You do not have to do those wipes again after installing. No idea what would be causing random reboots, except the usual suspect being a faulty power button. Try your install again, but wipe /system as well and don't use the ROM Wipe Script. There have been (old) reports of that causing some issues.
One other thing could be the kernel, as Render's kernel is really outdated - could be another cause!
SteveMurphy said:
You should be wiping /system before installing the ROM, along with the usual cache wipes. You do not have to do those wipes again after installing. No idea what would be causing random reboots, except the usual suspect being a faulty power button. Try your install again, but wipe /system as well and don't use the ROM Wipe Script. There have been (old) reports of that causing some issues.
One other thing could be the kernel, as Render's kernel is really outdated - could be another cause!
Click to expand...
Click to collapse
I have CWM recovery installed and it only can wipe data/factory reset, cache and dalvik cache. I could install Omni TWRP to be able to wipe /system. I do have the Shift kernel 1.0 to 5.0 zips as well, i could flash hem but i have no idea if they are compatible with STweaks since I only use it to enable the BLN for the bottom keys. Plus I random rebooted twice today, you want another last_kmsg log from it?
Also logcatting on my Ubuntu 15.04 laptop in terminal with the following command
Code:
adb logcat *:W *:F *:E
for Warnings, Fatal Warnings and Errors until a random reboot occurs
last_kmsg2
Sent from my SGH-I777 using XDA Free mobile app
CWM wipes /system, it's in a sub menu somewhere but I don't remember because I've not used CWM in a very long time. I know it's there because I used to do it! My suspicion is it's kernel related, but you'll need a KK kernel that's updated with the necessary blobs and I don't think there is a newer one for i777.
Unless someone else pops in with another suggestion, I'm out of ideas. Maybe it's time for you to update to LP?
SteveMurphy said:
CWM wipes /system, it's in a sub menu somewhere but I don't remember because I've not used CWM in a very long time. I know it's there because I used to do it! My suspicion is it's kernel related, but you'll need a KK kernel that's updated with the necessary blobs and I don't think there is a newer one for i777.
Unless someone else pops in with another suggestion, I'm out of ideas. Maybe it's time for you to update to LP?
Click to expand...
Click to collapse
I tried CyanideL 5.1.1 ROM for I777 and it would random reboot, but on this PAC ROM, I think I fixed it by turning off Dynamic statusbar colors on screen to disabled and has not rebooted yet but I'm still crossing my fingers still.
Also read about Mr.Cooks ROM Wipe script on Omni 5.1, seen it sticks some S2 phones on the Samsung Galaxy S2 screen for awhile, Not good