Related
I was running MIUIwiz and I tried to switch kernels or something and I suppose long story short I was able to recover my phone from an infinite bootloop however I can't restore my back up in clockwork. I actually can't flash any ROM that isn't the odin stock ED01. It's rooted because superuser works. But I'd really like to get back to my MIUIWiz backup.
I think it might be a kernel problem. I honestly don't know which one I need or what.
I realize this information probably sucks but I can answer any question if you just ask it.
Please someone help me!
EDIT: I think I've resolved the issue. I downloaded like 5 kernels and seems like the first one I used is going to work.
what happens when you try and flash a rom?
worst case, odin back to stock and start over.
Or if you think it's a kernel problem, flash a new kernel and try again.
elarson006 said:
what happens when you try and flash a rom?
worst case, odin back to stock and start over.
Or if you think it's a kernel problem, flash a new kernel and try again.
Click to expand...
Click to collapse
That's the thing. Usually I can fix these type of problem. However I've odin'd to stock multiple times. Tried to flash the MIUIWiz ROM and it just stays on the Samsung logo. Same goes for trying the restore. I've used this to get to ED01 mutliple times as well as manually flashing the updates and I still can't flash anything.
Can you suggest an ED01 MIUIWiz compatible Kernel? Because I don't know what is good or compatible or anything.
Horus.Campbell said:
That's the thing. Usually I can fix these type of problem. However I've odin'd to stock multiple times. Tried to flash the MIUIWiz ROM and it just stays on the Samsung logo. Same goes for trying the restore. I've used this to get to ED01 mutliple times as well as manually flashing the updates and I still can't flash anything.
Can you suggest an ED01 MIUIWiz compatible Kernel? Because I don't know what is good or compatible or anything.
Click to expand...
Click to collapse
Did you wipe data before flashing the ROM? Reading the first few posts in the MIUIWiz thread, it says you have to wipe date before flashing the ROM and that the most common cause of the ROM not loading is not wiping data.
which recovery did you use when you did the back up?
I was running the Spike Pure ICS on my SGS2, before which I had the ICS version of MIUI. I tried flashing Lite'ning Rom 3.6 through Odin, but was unsuccessful. Also, that's time I noticed the 7.2 version of CM and decided to flash that and that's when the problem occurred.
Although I could flash CM 7.2 properly and could also install the GApps through CWM, on rebboting it through the CWM, my phone got stuck and it wouldn't go into Recovery any more.
Luckily, it would boot into Download Mode and I could flash the stock rom through Odin and get my phone back to stock, thereby losing the Root and CWM.
I wanna know as to what could cause such an issue to arise. so that I can prevent it later!
Your help and time are appreciated!!
Why start a 2nd thread ?
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
And you couldn't make another post to your initial post along the lines of 'Why did this occur in the first place ?' You could even easily change the title of your initial thread to reflect your desire to know the answer to this question.
One of the main rules of XDA is don't spam.
I'm extremely sorry if I've spammed as it wasn't my intention at all!
This thread was and still is a genuine question which I want to know!!
Also, could you please tell me about the occurrence of such a problem on my phone??
gadgyfreak said:
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
Click to expand...
Click to collapse
I think answer was there but might be not clear......
When you flash gb over ICS you have to wipe, when you mix stuff after that, meaning trying different kernels to fix the issue it might get worse.
Because recovery is somewhat linked to kernel in s2, you won't get recovery in a messed up system.
So when you flash a complete firmware using Odin and then do data cache wipe, it get fixed.
Hope this helps.
But then how is it possible that my phone didn't get all messed up when I flashed CM 9(Nightly) over my pre-existing CM 7.1, while it happened when I tried it vice versa?
already told you, when you go from ICS newer kernel to GB older kernel, wipe is necessary. Going from GB to ICS will work but wipe is better there too.
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Flash a GB rom.
gadgyfreak said:
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Click to expand...
Click to collapse
save data
Wipe dial *2767*3855#
Flash GB Rom, preferably stock using Odin.
Should boot now, if not go into recovery and wipe data cache.
It will boot now.
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?
Hello everyone,
I have SGS II (I9100) for about 2 years now. Im still on GB 2.3.4 KI4 (yeah dont ask why thats not my main issue here), rooted while ago with ZergRush exploit, and running HellCat's kernel. About two months ago, I fire up my phone and saw that I have no network. Went to About phone noticed that there is no baseband set, did *#06# and saw that my IMEI is empty. Luckily I had my EFS backed up with kTool, restored and was good to go. Today it happened to me again. Again restored with kTool and still good to go. So here is some facts regarding it, and I would like to know what might have causing it since I really dont update ROM's every 24 hours.
- 2 yearish old phone
- custom kernel with CWM
- did only one update from 2.3.2 (i think, cant recall what ROM was it shipped with) to 2.3.4
- didnt do factory reset after ROM upgrade
- happened before with soon-to-be-dead battery, but also with new one I got couple of days ago
- had running Dr.Web AV pretty much last year or so (I think only resident program running in background apart from loads of bloatware from Samsung)
Any info is more than welcomed since even I do have EFS backup, somehow I dont believe this is "expected behavior"...
Shall I (finally) upgrade to JB via Odin(Mobile Odin Pro?) and do factory reset/root after?
Can it be bad external card? Can internal memory can somehow be corrupted like hard drive with bad sectors or something? Really any info is more than welcomed.
Thank in advance
Here you go http://bit.ly/1bx9zPv
If you have actually read my post, before sending me to google, you would actually realized that I have EFS backup, and that I have recovered IMEI twice with kTool... Question is not HOW, but WHY. There is difference there. But hey, thanks for most ignorant reply you can actually think of. GZ you have just won the interwebs!
Hi,
i dont think its an hardware problem. I think that problem comes with your longtime running system und maybe that you didnt do a reset. Maybe you should finally upgrade to Jelly Bean - best way with Odin and a complete full wipe (save your data befor )
But keep cool, Jelly Bean looks very different to Gingerbread
Andi
andi2398 said:
Hi,
i dont think its an hardware problem. I think that problem comes with your longtime running system und maybe that you didnt do a reset. Maybe you should finally upgrade to Jelly Bean - best way with Odin and a complete full wipe (save your data befor )
But keep cool, Jelly Bean looks very different to Gingerbread
Andi
Click to expand...
Click to collapse
Thanks for the reply Andi. Actually I did that, and so far there is no issues with it (4.1.2). Did full wipe and so far all looking good, and I really like how it handles now. Still have EFS backup, just in case
Hi,
EFS Backup ist ever ever the first step after rooting don´t understand some guys who didnt do that or forget it.
Did you 4.1.2 root? If not, i recommed the philz kernel easy way, no triangle
have a nice day
Andi
andi2398 said:
Hi,
EFS Backup ist ever ever the first step after rooting don´t understand some guys who didnt do that or forget it.
Did you 4.1.2 root? If not, i recommed the philz kernel easy way, no triangle
have a nice day
Andi
Click to expand...
Click to collapse
Actually had some issues there... on 2.3.3 I had Hellcat kernel, wanted BLN, and some custom UOT Kitchen mods. Did full wipe from phone, and got it stucked in bootloop.
Let i a while, then said, **** it, and used Odin to flash 4.1.2 in from download mode. Stock ROM, so no binary counter issues. Started to boot up, showed me language selection and then crashed into bootloop... Assuming that it didnt finished wipe previously... Couldnt even got in into recovery (or was too stressed, but its 3 keys to press, dunno). Then, switched to download mode, flashed 4.0.3 that I had lying around, went to recovery, did wipe, and it booted up. Played with it, and in one point I said, "meh, Ill leave it on ICS"... Then something else said "You wuss! It took you 2 years to flash damn thing, and now you will stick to ICS?!?". Downloaded Mobile Odin Pro that I have purchased a while ago, flagged autoroot and flashed 4.1.2 from it. Again wiped it (just in case) and it booted up nicely. About 3 hours of stress, googling and browsing XDA Wife actually told my kid to stay away from me )
Then, wanted again BLN and thats the reason i skipped Philz and went for Siyah kernel instead. All nice and dandy so far *knock on the wood*
Still have EFS backup on numerous locations ofc
Cheers mate and thanks for participating
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good: