Okay...So I'm having boot loop issues ever since I tried to flash Vincom's Superlite rom. Before attempting to switch to a different rom I had a a older version of CWM, not sure what it was....But I was under the impression I needed CWM touch to be able to use the Superlite rom. So I flashed sk8's CWM touch using a older CWM...With touch, I flashed the Dark Side Super Wipe 3x's and also did the wiped dalvek 3x's.....After all the wiping I flashed the superlite rom....my previous rom was CM10, by the way.....i got stuck in bootloop so I tried the darkside-wipe-cache, because that solved all my bootloop issues with the CM 9 and CM 10.......I tried to revert back to CM 10 via flash and got stuck in a boot loop....I tried multiple times to reflash and wipe with both superlite and CM 10...I couldnt get anything...So I gave up and flashed to stock firmware UCL6 via CWM Touch.....My phone is functional I just dont want this stock "rom"...I want to be able to use CM 10 again because the t-mobile radios dont work with the stock....Im thinking its the CWM....I tried using different kernels as well...and i still get a boot loop......
daygobaker said:
Okay...So I'm having boot loop issues ever since I tried to flash Vincom's Superlite rom. Before attempting to switch to a different rom I had a a older version of CWM, not sure what it was....But I was under the impression I needed CWM touch to be able to use the Superlite rom. So I flashed sk8's CWM touch using a older CWM...With touch, I flashed the Dark Side Super Wipe 3x's and also did the wiped dalvek 3x's.....After all the wiping I flashed the superlite rom....my previous rom was CM10, by the way.....i got stuck in bootloop so I tried the darkside-wipe-cache, because that solved all my bootloop issues with the CM 9 and CM 10.......I tried to revert back to CM 10 via flash and got stuck in a boot loop....I tried multiple times to reflash and wipe with both superlite and CM 10...I couldnt get anything...So I gave up and flashed to stock firmware UCL6 via CWM Touch.....My phone is functional I just dont want this stock "rom"...I want to be able to use CM 10 again because the t-mobile radios dont work with the stock....Im thinking its the CWM....I tried using different kernels as well...and i still get a boot loop......
Click to expand...
Click to collapse
Bump? Anybody?
Manually do the following wipes: wipe data/factory reset, cache, dalvik, format/data, format/system, format/cache all x3. Then reflash his ROM followed by gapps. Let it sit for 10 min as caches need time to settle and the initial boot always takes much longer.
Which version of cwm touch are you on?
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398[/QUOTE]
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
Clear cache clear dalvik cache flash radio if you has issues refresh Rom from scratch DO NOT REFLASH RADIO
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
Nope. Just wipe dalvik and cache and flash it. But it's likely to be an exercise in folly anyway, because it you have uclf5 and you flash uclf6, you still have the uclf5 libs. Changing the radio libs is a much more complicated procedure and without doing so you get limited benefit from flashing a new radio. But sometimes it does help anyway. Might be worth a try if you're getting poor connectivity.
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
No need to do a whole clean install simply to switch out the radio. I 95% positive you only need to wipe cache, dalvik, flash radio and reboot. I only changed radio once and it was during a clean install so I never really paid that close attention to the steps when you put it over the top of your ROM. Do what I said and you should be fine.
Or grab the torch and pitchfork. Jk there's nothing to worry about
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Still bootlooping...
Mike on XDA said:
Manually do the following wipes: wipe data/factory reset, cache, dalvik, format/data, format/system, format/cache all x3. Then reflash his ROM followed by gapps. Let it sit for 10 min as caches need time to settle and the initial boot always takes much longer.
Which version of cwm touch are you on?
Click to expand...
Click to collapse
Hey Mike,
I've been bootlooping as well. A little background...
I'm on CWM Touch 6.0.1.2 _sk8erwitskil_
I was on cm-10-20120812-EXPERIMENTAL-syyrocket-alpha3
Yesterday, I went to cm-10-20120912-UNOFFICIAL-skyrocket
I was ok until just a little bit ago I was on a call and the phone rebooted. Since then, bootloop-city.
I tried this procedure, reflashed 0912 and no joy. I think, at this point, the unreliability of CM10 (at this time) has worn thin (no dis to all the awesome developers out there) and I just want to go back to a stable CM9.
Any suggestions?
Thanks,
Bob
EDIT: Ya know, just when you think all is lost, there is Nandroid! I'm back to CM9 and no longer bootlooping!
Related
I'm currently using SkyRocket ICS (2.3.5 Gingerbread)
http://forum.xda-developers.com/showthread.php?t=1377087
and everything is awesome but my phone signal, att logo, wifi, notifications, doesnt appear on the top of the phone so i want to try out another ROM. This one in particular, NexusMod 4
http://forum.xda-developers.com/showthread.php?t=1426590
Do I just flash the new ROM in CWM recovery like I did to get my first ROM? Or is there more to it?
Thanks!
That's a problem on your end, that rom is flawless and you flashed it wrong
This is the guide I used to flash the ROM
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
I compared it with ones on xda and it was identical but more noob friendly which I preferred. I dont know what I couldve possibly done wrong.. I followed EVERYTHING step by step. I love everything about this ROM except this one major annoyance.
penance said:
This is the guide I used to flash the ROM
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
I compared it with ones on xda and it was identical but more noob friendly which I preferred. I dont know what I couldve possibly done wrong.. I followed EVERYTHING step by step. I love everything about this ROM except this one major annoyance.
Click to expand...
Click to collapse
It was a bad flash or bad download. Try to redownload and check the md5, then simply reflash it making sure to follow instructions and wipe properly
Sorry, but may I ask what an md5 is? And the specific ROM I want
http://forum.xda-developers.com/showthread.php?t=1377087
doesn't provide instructions, at least that I know of so I followed this guide
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
Only problem I can think of that I made was flashing the RC 6.75 Stock ROM and then wiping cache partition and flashing the 7.4 Stock Nonewipeupdate right afterwards which is exactly what the guide asked for. Was I suppose to reboot after flashing the stock RC 6.75 ROM before flashing the 7.4 Stock Nonewipeupdate?
penance said:
Sorry, but may I ask what an md5 is? And the specific ROM I want
http://forum.xda-developers.com/showthread.php?t=1377087
doesn't provide instructions, at least that I know of so I followed this guide
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
Only problem I can think of that I made was flashing the RC 6.75 Stock ROM and then wiping cache partition and flashing the 7.4 Stock Nonewipeupdate right afterwards which is exactly what the guide asked for. Was I suppose to reboot after flashing the stock RC 6.75 ROM before flashing the 7.4 Stock Nonewipeupdate?
Click to expand...
Click to collapse
You need to flash the base and boot it before flashing an update, like you said.
Before flashing any rom this is a general procedure
wipe data/factory reset 3x
Wipe cache 3x
wipe dalvik cache 3x
format system 3x
flash radio if need be
flash rom
reboot
dont touch phone for at least 10 mins
set up basics
if it has an update
reboot to cwm
wipe cache 3x
wipe dalvik cache 3x
flash update
reboot
Okk. ONE LAST question. The SkyRocket ICS (2.3.5 Gingerbread) ROM I'm using doesn't have or provide a radio file to DL on the page which I linked earlier. Does that imply that this particular ROM doesn't need it? Or am I suppose to find a radio to flash before flashing the ROM and update?
Thanks alot for your help/advice!! Really appreciate it!
penance said:
Okk. ONE LAST question. The SkyRocket ICS (2.3.5 Gingerbread) ROM I'm using doesn't have or provide a radio file to DL on the page which I linked earlier. Does that imply that this particular ROM doesn't need it? Or am I suppose to find a radio to flash before flashing the ROM and update?
Thanks alot for your help/advice!! Really appreciate it!
Click to expand...
Click to collapse
In about phone, what does it say for baseband? Kj2 is the 2.3.5 stock radio
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
If the radio you're using is working and you're flashing from gb to gb, you shouldn't have to worry about the radio. You'll still have the same one. Radios flash separately from roms. I don't think you'll NEED to flash a new radio unless you change to an ICS rom.
Sent from my SAMSUNG-SGH-I727 using xda premium
Android version 2.3.6
Baseband version I727UCKJ2
Kernal version 2.6.35.11+
Build number Sky-ICS RC7.4 Stock
When I purchased my phone and after I rooted it, I was v2.3.5 but after I flashed my first ROM (which is my current ROM) the android version changed to v2.3.6. So if KJ2 is the stock radio for v2.3.5 is there a possibility my problem of not having the att logo and wifi signal on the top of my phone due to not having the correct radio for this ROM? or for v2.3.6 in general? Or is it from what you said earlier, my flashing process was wrong? Or a mixture or not having the correct radio and flashing wrong?
boobah204 said:
If the radio you're using is working and you're flashing from gb to gb, you shouldn't have to worry about the radio. You'll still have the same one. Radios flash separately from roms. I don't think you'll NEED to flash a new radio unless you change to an ICS rom.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Well, I don't really know whether or not the radio is working. I suppose in my case it is working since I am able to recieve and make calls, text, and go on the web. However, I am unable to see the att logo, wifi/cell signal on the top of my phone. I don't know if this problem has anything to do with the radio though. Sorry for my lack of understanding..
I'm assuming the problem is more my fault in terms of not flashing correctly. I have no idea whether or not I need a separate radio for this ROM.
Sounds like a systemui /frame work problem
Wipe data/cache/dalvik
Reflash
Fully boot
Shutdown
Flash update
Wipe dalvik
Reboot.
The signals at the top wouldn't be affected by he radio. You would most likely get them back if you reflashed your from or flashed another. As long as it's a 2.3.5 or 2.3.6. And also follow the instructions (usually pretty standard, wipe data factory reset a few times, wipe cache partition, advanced, wipe dalvik cache a few times, go back, mounts and storage, format system a few times. Then install zip from SD card) oh and always backup first and make sure you can restore the backup. But yeah if you can make calls and use internet, your radio should be OK.
Sent from my SAMSUNG-SGH-I727 using xda premium
silver03wrx said:
Sounds like a systemui /frame work problem
Wipe data/cache/dalvik
Reflash
Fully boot
Shutdown
Flash update
Wipe dalvik
Reboot.
Click to expand...
Click to collapse
Thanks! That's what I figured the problem to be JK.
I'll give it go and hope for the best this time around.
boobah204 said:
The signals at the top wouldn't be affected by he radio. You would most likely get them back if you reflashed your from or flashed another. As long as it's a 2.3.5 or 2.3.6. And also follow the instructions (usually pretty standard, wipe data factory reset a few times, wipe cache partition, advanced, wipe dalvik cache a few times, go back, mounts and storage, format system a few times. Then install zip from SD card) oh and always backup first and make sure you can restore the backup. But yeah if you can make calls and use internet, your radio should be OK.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Alright thanks alot for your guide and clarification. Still learning day by day
penance said:
Alright thanks alot for your guide and clarification. Still learning day by day
Click to expand...
Click to collapse
Just do this and skip the radio step
xcrazydx said:
You need to flash the base and boot it before flashing an update, like you said.
Before flashing any rom this is a general procedure
wipe data/factory reset 3x
Wipe cache 3x
wipe dalvik cache 3x
format system 3x
flash radio if need be
flash rom
reboot
dont touch phone for at least 10 mins
set up basics
if it has an update
reboot to cwm
wipe cache 3x
wipe dalvik cache 3x
flash update
reboot
Click to expand...
Click to collapse
Not sure the deal with your cell/wifi signals not showing in your status bar, but, the carrier logo could have been removed in the ROM itself.
I would try out the nexusmod zero ics I'm running it now and I like it a lot more than nexus 4. Also when I went from the from you are on now I had to do a super wipe before I could get the ics rom to work without bootloop
Sent from my SAMSUNG-SGH-I727 using XDA
I have cm9 and want to go back to stock type roms.. less bugs..
anyway, how do I do this? I did a full wipe and restored hydro but the kernel stays on CM9 kernel.. and wifi wont turn on...
You need to flash the actual .30 zip from asus. That returns you to stock. Then do a custom recovery/root and THEN flash hydro.
thatisandwas said:
You need to flash the actual .30 zip from asus. That returns you to stock. Then do a custom recovery/root and THEN flash hydro.
Click to expand...
Click to collapse
Wow, that sucks..... thanks for the help tho. Think I'll just stick to cm9. I got it working well and its fast.
try hydro. Izs based on stock and is one of the fastest roms out there.
hdjoe said:
Wow, that sucks..... thanks for the help tho. Think I'll just stick to cm9. I got it working well and its fast.
Click to expand...
Click to collapse
Which recovery do you have? Flash the latest twrp recovery and you can flash hydro without the need to return to stock. Simply download the newest base for hydro. You can also flash clean rom over cm9 without returning to stock. Make sure that you wipe cache, dalvic, factory data reset, and format system.
dxwilliams40 said:
Which recovery do you have? Flash the latest twrp recovery and you can flash hydro without the need to return to stock. Simply download the newest base for hydro. You can also flash clean rom over cm9 without returning to stock. Make sure that you wipe cache, dalvic, factory data reset, and format system.
Click to expand...
Click to collapse
I'm on cwm. Still. Formatting system won't wipe everything off my internal memory will it? I have about 15 movies , and a bunch of snes games....
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
Click to expand...
Click to collapse
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Phizban said:
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Click to expand...
Click to collapse
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Droid111 said:
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Click to expand...
Click to collapse
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
mjwhirly said:
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
Click to expand...
Click to collapse
Thanks for the help. I'm going to try it within the next few days. Right now I have SKY-ICS going fine but I'll definitely try that.
What do the different kernels do?
Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Click to expand...
Click to collapse
I used TWRP and flashed over CM9 with no problems. Did it as an upgrade. Wipe system> install CM10> install gapps> Wipe cache
Several people have reported that TWRP worked for them.
Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!
shentheory said:
Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!
Click to expand...
Click to collapse
Couple things.... did u format data/system? Also what recovery are u using?
Deliberate said:
Couple things.... did u format data/system? Also what recovery are u using?
Click to expand...
Click to collapse
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!
shentheory said:
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!
Click to expand...
Click to collapse
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!
Deliberate said:
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!
Click to expand...
Click to collapse
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?
shentheory said:
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?
Click to expand...
Click to collapse
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.
Can you boot into recovery or not? If you can, just flash the rom. If you can't, yank the battery, replace it. Then, hold down both volume buttons, the press the power button, release all the buttons, you should be able to get into recovery.
Deliberate said:
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.
Click to expand...
Click to collapse
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!
You'll have to use odin, and reroot your phone.
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
shentheory said:
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!
Click to expand...
Click to collapse
I had the same problem, but while my phone was stuck on the MIUI boot screen i pulled the batter, got into recovery again and simply did a factory data reset just once and then it booted up, but my issue is that i get no data at all no mater what version of MIUI I try to flash.
mimart7 said:
You'll have to use odin, and reroot your phone.
Click to expand...
Click to collapse
Even if my stock rom is already rooted? I'm not against trying it, I'm just curious to how that could affect it. Thanks for your help!
hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
I will do this and update when I do, Thanks for your help!
hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
Ya I agree try downloading it again. Check the md5 and flash that ROM again. If it doesn't work your gonna have to Odin!
There were a lot of complaints of boot loops when flashing, so I pulled the DL link. I actually stopped using miui and moved back to CM or AOKP, depending on which one is most stable at the moment. Every once in a while I give miui a try, but I never stick with it. If you want miui, I suggest you follow Lithium's thread. His version is the officially supported miui rom.
I can confirm heres what i did to fix i had the boot loop.. all i did was run DARKSIDE Superwipe x2 Times. Then i installed MIUI Rom. Then i Factory Reset. Try booting wait a little bit. If still not going threw remove battery and boot to recovery and factory reset one more time then reboot. So once again.
1. DARKSIDE SUPERWIPE x2++ 2. Install MIUI Rom. 3. Factory Reset. 4. Boot. 5. (If still looping) Remove battery Then recovery. and Factory Reset and boot again. Your welcome
Can we move this to q and a?
Sent from my XT894 using Tapatalk 2
about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks
and to clarify , it was gapps 4.2.2
Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.
If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app
i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .
You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.
actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.
i figured out twrp. never gave it achance. ill see if that does the trick
tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks
Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?