Related
SHG-T989 on TMO. I was running CM 9.0 but wanted to update to 9.1. NOW I CANT DO ANYTHING!!! Here is what I did:
1. Downloaded the CM9.1. 2. did a backup through CWM. 3. wiped data through CWM, "wipe data/factory reset. 4. wiped cache partition through CWM. 5. did a Darkside Super Wipe through "install zip from internal sd card" (last time installing CM9 i got stuck in the boot screen and had to go back using Darkside Super Wipe, reinstall CM9 and it worked fine). 6. Reboot to recovery. 7. installed CM9.1 through "install zip from sdcard". 8. installed gapps through "install zip from sdcard". 9. Reboot.
It came up and was stuck in the CM9 boot screen. So I went back in through CWM and tried to "wipe data/factory reset" and it wont work! Tried to go back to stock through Odin and it wont work! When i try to wipe data, the process starts and completes the "formatting /data, then gets stuck at formatting /cache. Does the same thing if I try to wipe the cache.
Im completely stuck and have no phone.
Which recovery version are you using? It might a corrupted recovery.
Try this recovery TWRP is cwm flashable:
SGH-T989_TWRP_v2.2.2.0.zip - 6.72 MB
Then TDJs super wipe and then install the stock ROM or any other ROM.
http://forum.xda-developers.com/showthread.php?t=1858435
Sent from my SGH-T989 w/AOKP JB Sept-12-12 using XDA app.
any updates to this? i'm having basically the exact same problem, formatting cache or anything to do with that partition freezes up on me.
using cwm 5.0.2.7 did a darkside super wipe, flashed on a JB rom (P.A.Cman), flashed gapps (20121011), wiped cache, wiped dalvik cache, rebooted then got stuck on boot animation. rebooted back into cwm to try and wipe again and reinstall, no luck got stuck on formatting cache.
loaded up my nandroid which went fine, ended up installing twrp instead to see if that would help, rebooted into recovery and was stuck on the "teamwin" blue screen and wouldn't go further multiple times. so, put cwm back on (6.0.1.5) to see if the updated version would work. nope, same thing- can't do anything with the cache partition.
any ideas??
luckily my phone still works fine with the backup i made. running aokp ics build 40, streamline #27 kernel, uvle1 radio. been running that setup since july with no real problems, just wanted to try out JB finally and seems now i can't
any help is appreciated! thanks!
edit: will try the above post^ later tonight, just thought i'd see if i could get some more options to try out. thanks.
wwwwd83 said:
SHG-T989 on TMO. I was running CM 9.0 but wanted to update to 9.1. NOW I CANT DO ANYTHING!!! Here is what I did:
1. Downloaded the CM9.1. 2. did a backup through CWM. 3. wiped data through CWM, "wipe data/factory reset. 4. wiped cache partition through CWM. 5. did a Darkside Super Wipe through "install zip from internal sd card" (last time installing CM9 i got stuck in the boot screen and had to go back using Darkside Super Wipe, reinstall CM9 and it worked fine). 6. Reboot to recovery. 7. installed CM9.1 through "install zip from sdcard". 8. installed gapps through "install zip from sdcard". 9. Reboot.
It came up and was stuck in the CM9 boot screen. So I went back in through CWM and tried to "wipe data/factory reset" and it wont work! Tried to go back to stock through Odin and it wont work! When i try to wipe data, the process starts and completes the "formatting /data, then gets stuck at formatting /cache. Does the same thing if I try to wipe the cache.
Im completely stuck and have no phone.
Click to expand...
Click to collapse
Ok, the wipe scripts in CWM recovery v5 are broken! Got experience there because I got stuck on the PACman ROM boot animation.
So, for factory reset, use Darkside Super Wipe. Install zip from sdcard and choose the wipe. From there, install rom, then gapps, and then use the Darkside Cache Wipe. After that reboot and it should work (hopefully)
However the most important thing is that the wipes don't work in CWM recovery v6! It will do bad things!
So yeah, use super wipe to factory reset. Use cache wipe for cache. But follow the instructions to install the ROM.
Sent from my SAMSUNG-SGH-T989 using xda premium
m tr4nch said:
any updates to this? i'm having basically the exact same problem, formatting cache or anything to do with that partition freezes up on me.
using cwm 5.0.2.7 did a darkside super wipe, flashed on a JB rom (P.A.Cman), flashed gapps (20121011), wiped cache, wiped dalvik cache, rebooted then got stuck on boot animation. rebooted back into cwm to try and wipe again and reinstall, no luck got stuck on formatting cache.
loaded up my nandroid which went fine, ended up installing twrp instead to see if that would help, rebooted into recovery and was stuck on the "teamwin" blue screen and wouldn't go further multiple times. so, put cwm back on (6.0.1.5) to see if the updated version would work. nope, same thing- can't do anything with the cache partition.
any ideas??
luckily my phone still works fine with the backup i made. running aokp ics build 40, streamline #27 kernel, uvle1 radio. been running that setup since july with no real problems, just wanted to try out JB finally and seems now i can't
any help is appreciated! thanks!
edit: will try the above post^ later tonight, just thought i'd see if i could get some more options to try out. thanks.
Click to expand...
Click to collapse
got it all working again.. ended up odin flashing twrp 2.2 and i was able to boot into it, wipe everything, and install the new rom stuff.
Similar problem, but cannot make zips to work - HELP NEEDED
HI,
I hope you guys can help me. My T989 got stucked in the splash screen when I tried to update to a nightly CM10 ROM. I entered into Recovery MOde (ClockworkMod 6.0.2.7), then tried to use Darkside Super Wipe... but apparently the phone cannot open zip files. When I hit install zip from sdcard and then select one of the zips (I have tried different ones) it says "---Installing: /sdcard/sgh-t989_darkside.supe.wipe.zip"... but it does not move from there. After 3-4 minutes it reboots by itself and gets back to the splash animation, but never goes beyond that point.
I tried to sideload using ADB, but the phone is not recognized by my PC.
As you said, I think that the recovery mode is corrupted... but I cannot install a new version using a zip
Is there another way to reinstall a version of CWM that allows me to install zips so that I can follow the process you suggested (super wipe + installing ROMS)?
Help will be very much appreciated
Thanks for your time,
Enrique
thatdude02 said:
Ok, the wipe scripts in CWM recovery v5 are broken! Got experience there because I got stuck on the PACman ROM boot animation.
So, for factory reset, use Darkside Super Wipe. Install zip from sdcard and choose the wipe. From there, install rom, then gapps, and then use the Darkside Cache Wipe. After that reboot and it should work (hopefully)
However the most important thing is that the wipes don't work in CWM recovery v6! It will do bad things!
So yeah, use super wipe to factory reset. Use cache wipe for cache. But follow the instructions to install the ROM.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
kikorras said:
HI,
I hope you guys can help me. My T989 got stucked in the splash screen when I tried to update to a nightly CM10 ROM. I entered into Recovery MOde (ClockworkMod 6.0.2.7), then tried to use Darkside Super Wipe... but apparently the phone cannot open zip files. When I hit install zip from sdcard and then select one of the zips (I have tried different ones) it says "---Installing: /sdcard/sgh-t989_darkside.supe.wipe.zip"... but it does not move from there. After 3-4 minutes it reboots by itself and gets back to the splash animation, but never goes beyond that point.
I tried to sideload using ADB, but the phone is not recognized by my PC.
As you said, I think that the recovery mode is corrupted... but I cannot install a new version using a zip
Is there another way to reinstall a version of CWM that allows me to install zips so that I can follow the process you suggested (super wipe + installing ROMS)?
Help will be very much appreciated
Thanks for your time,
Enrique
Click to expand...
Click to collapse
Do NOT use that darkside superwipes with CWM recovery v6.X.X.X. Does bad things.
Use the scripts only for CWM v5.X.X.X.
Anyway, the damage is done and bad things have happened... So maybe check here
http://forum.xda-developers.com/showthread.php?t=1513359
Either that or you can search the forum and Google around and see what you can find. I am in by no means an expert, but depending if you can access the recovery mode or not might be the key here.
I wish you luck, and hope that you don't have a very expensive brick.
Sent from my SAMSUNG-SGH-T989 using xda premium
Use Odin. There is a tutorial on how to revert to stock GB (might be ICS) in the T989 development forum. It should be a sticky in that forum.
Ditto issues.. Thank good for search function. Read.. Read.. Read..
Sent from my SGH-T989 using xda app-developers app
Tried your suggestion, but Odin won't recognize my phone
Hi there,
Thank you very much for the answer. I actually spent hours trying to find something before I posted my question. Even before posting I found and tried the method using Odin... but my phone is not recognized by Odin. I followed the instructions but on step 4 I actually do not get any "warning" screen... and then the phone is not recognized.
In the meantime, I can get into recovery, but I cannot install any zips. I have tried to complete a factory reset, but the process gets stuck at "Formating /cache..." and then reboots. When I try to install a zip (any zip, the radio, a new ROM, gapps,... any zip really) it gets stuck too.
Any other ideas? I really appreciate your help.
thatdude02 said:
Do NOT use that darkside superwipes with CWM recovery v6.X.X.X. Does bad things.
Use the scripts only for CWM v5.X.X.X.
Anyway, the damage is done and bad things have happened... So maybe check here
http://forum.xda-developers.com/showthread.php?t=1513359
Either that or you can search the forum and Google around and see what you can find. I am in by no means an expert, but depending if you can access the recovery mode or not might be the key here.
I wish you luck, and hope that you don't have a very expensive brick.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
kikorras said:
Hi there,
Thank you very much for the answer. I actually spent hours trying to find something before I posted my question. Even before posting I found and tried the method using Odin... but my phone is not recognized by Odin. I followed the instructions but on step 4 I actually do not get any "warning" screen... and then the phone is not recognized.
In the meantime, I can get into recovery, but I cannot install any zips. I have tried to complete a factory reset, but the process gets stuck at "Formating /cache..." and then reboots. When I try to install a zip (any zip, the radio, a new ROM, gapps,... any zip really) it gets stuck too.
Any other ideas? I really appreciate your help.
Click to expand...
Click to collapse
The only other possible option I can think is to try and install another recovery....
However!
I have no clue how to do it, and in the end you might just end up making the issue worse.... Like hard brick it.
I might think of something later, but I don't know what else I can do for you. I will search around, but no promises...
Best of luck to you
--edit--
Ok try here possibly
http://forum.xda-developers.com/showthread.php?t=1777970
I have seen a few posts saying that they just install this recovery and then restore a backup.
Ok to be honest, try restoring a backup first and see if anything happens there, and then try this thread.
However like before, this may make the problem worse! Proceed with caution and read and understand everything before attempting.
Hope you can get your phone back to functional!
Sent from my SAMSUNG-SGH-T989 using xda premium
samsung jig
Thanks again for the answer. A couple of days ago I tried to install a functional backup that I had from CWM... but it does not work It runs for a long while, then reboots... but it still freezes on the splash screen (my theory is that the backup is not recovered, as I know for sure that the ROM I backed up did work fine)... I think that CWM is corrupted and not working properly.
Then I tried the solution from the thread you mentioned... but adb cannot find the phone when it is connected
I found somewhere that I can use a samsung jig (microUSB with a resistance) to make the phone enter into download mode, then reinstall CWM using ODIN and then try flashing a stable ROM... What do you guys think?
thatdude02 said:
The only other possible option I can think is to try and install another recovery....
However!
I have no clue how to do it, and in the end you might just end up making the issue worse.... Like hard brick it.
I might think of something later, but I don't know what else I can do for you. I will search around, but no promises...
Best of luck to you
--edit--
Ok try here possibly
http://forum.xda-developers.com/showthread.php?t=1777970
I have seen a few posts saying that they just install this recovery and then restore a backup.
Ok to be honest, try restoring a backup first and see if anything happens there, and then try this thread.
However like before, this may make the problem worse! Proceed with caution and read and understand everything before attempting.
Hope you can get your phone back to functional!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
kikorras said:
Thanks again for the answer. A couple of days ago I tried to install a functional backup that I had from CWM... but it does not work It runs for a long while, then reboots... but it still freezes on the splash screen (my theory is that the backup is not recovered, as I know for sure that the ROM I backed up did work fine)... I think that CWM is corrupted and not working properly.
Then I tried the solution from the thread you mentioned... but adb cannot find the phone when it is connected
I found somewhere that I can use a samsung jig (microUSB with a resistance) to make the phone enter into download mode, then reinstall CWM using ODIN and then try flashing a stable ROM... What do you guys think?
Click to expand...
Click to collapse
I've heard about the jig method as well, but have no idea on how to go about doing it. Might be worth a shot. I don't think the jig costs that much anyway. I will see if I can find anything later.
Sent from my SAMSUNG-SGH-T989 using xda premium
Hello and thank you for reading.
So I got an HTC One V almost a week ago and I'm digging it so far. I unlocked the bootloader, rooted it and then went to install a recovery. First I tried CWM because that's what I used on my Optimus V, but it didn't work. Then I gave TWRP a shot which was awesome because not only did it work, but I also thought the touch option was a nice addition to the recovery. So I found a Jellybean ROM for the One V and gapps, put them on my sd and went to flash them. Wiped Cache and Dalvik Cache just fine, but when I went to wipe the system I got an error message. Ended up soft bricking then spent another hour or so getting the stock ROM back on there. The next day I unlocked and rooted again and I even found a CWM recovery that worked. Wiped everything fine then went to install, but once again I softbricked.
So that being said, here's my question. What step am I missing? I thought I was following all the instructions, but I missed something, right?
you have to factory reset from bootloader
Sent from my HTC One V using xda app-developers app
Thanks for your reply. Please correct me if I'm wrong about the order of things here:
Go into my recovery, wipe cache, wipe dalvik cache, reboot into bootloader, factory reset, reboot to go into recovery again, flash ROM and gapps then reboot system
I came across something that said I had to flash the boot img that came with the ROM too so I guess that would be my last step. Sorry if it seems like a total noob question, I'm still learning. Once again your help is appreciated.
Yes flash to boot.IMG for cm10
Sent from my One V using xda premium
Flash with latest kernel
hit thanks if I helped u!!!
You guys are awesome! I just want to double check and make sure I have the order right, though because this would be the third attempt and I don't want to have to go through the process of installing the stock ROM, unlocking and re-rooting of the phone again. Even though it's easy, it's still a bit of a pain, you know?
So...
-recovery
-wipe cache
-wipe dalvik cache
-reboot into bootloader
-factory reset
-reboot to go into recovery again
-flash ROM and gapps then reboot system
-flash boot.img (in bootloader I'm assuming?)
-flash kernel (Once again..bootloader, right? I heard Hellboy was decent, but I'm going to read about that now)
I know it's kind of a pain, but a list in the correct order is the best thing for someone still somewhat new to this like myself. If there's something out of order or I'm flashing something in the wrong section, I'd like to know before I do it rather than find out the hard way :laugh: Once again, thanks for the replies. The person that got me into this suggested this forum over all others and I'm happy he did.
Do these steps in order-
1. Put rom+gapps in root of sdcard.
2. Boot into bootloader and select fastboot then connect phone to pc or lappy.it should say fastboot USB.
3. Now flash the latest updated kernel.
4. Then go into recovery from bootloader and factory reset,wipe cache partition and wipe dalvik cache.
5. Then flash rom.zip,boot into rom.
6. Then again boot into recovery and flash gapps.
Sent from my HTC One V using xda app-developers app
Trolls Royce said:
You guys are awesome! I just want to double check and make sure I have the order right, though because this would be the third attempt and I don't want to have to go through the process of installing the stock ROM, unlocking and re-rooting of the phone again. Even though it's easy, it's still a bit of a pain, you know?
So...
-recovery
-wipe cache
-wipe dalvik cache
-reboot into bootloader
-factory reset
-reboot to go into recovery again
-flash ROM and gapps then reboot system
-flash boot.img (in bootloader I'm assuming?)
-flash kernel (Once again..bootloader, right? I heard Hellboy was decent, but I'm going to read about that now)
I know it's kind of a pain, but a list in the correct order is the best thing for someone still somewhat new to this like myself. If there's something out of order or I'm flashing something in the wrong section, I'd like to know before I do it rather than find out the hard way :laugh: Once again, thanks for the replies. The person that got me into this suggested this forum over all others and I'm happy he did.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1996665
hit thanks if I helped u!!!
mihirengg19 said:
Do these steps in order-
1. Put rom+gapps in root of sdcard.
2. Boot into bootloader and select fastboot then connect phone to pc or lappy.it should say fastboot USB.
3. Now flash the latest updated kernel.
4. Then go into recovery from bootloader and factory reset,wipe cache partition and wipe dalvik cache.
5. Then flash rom.zip,boot into rom.
6. Then again boot into recovery and flash gapps.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Factory reset never seemed to work when I did it in recovery mode. Though I was skipping a few steps when I tried it so I'll give this a shot during the weekend and get back to you. Funny thing is I posted a reply as you posted your's :laugh:
bahubali67 said:
http://forum.xda-developers.com/showthread.php?t=1996665
hit thanks if I helped u!!!
Click to expand...
Click to collapse
So many more steps from the Optimus V :laugh: I'll give this a shot and get back to you. Thanks guys for all your help!
flash the boot.img(thé kernel) in fastboot,not in bootloader..here is the link to latest hellboy kernel.
http://forum.xda-developers.com/showthread.php?t=1954967
Just to clarify u are gsm right?
Sent from my HTC One V using xda app-developers app
mihirengg19 said:
flash the boot.img(thé kernel) in fastboot,not in bootloader.if factory reset from recovery not working do it from bootloader.here is the link to latest hellboy kernel.
http://forum.xda-developers.com/showthread.php?t=1954967
Just to clarify u are gsm right?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
CDMA, sorry for not being more specific about that.
Oh thats where u r going wrong!
Download the proper cdma kernel and rom! Use cm10+jmz primoc!
And use the recovery for Primoc! If u flash gsm images to ur cdma phone u will regret it!
Sent from my HTC One V using xda app-developers app
Depends on the ROM
First thing, for cdma, TWRP seems to work better so you're better off using that. After that, it depends on the ROM. I've found that AOKP is the easiest to flash. Get the AOKP ROM and the gpps, extract the boot.img from the rom. Boot to recovery, wipe everything from there (including factory reset so you don't have to go back to bootloader for that) flash rom and gapps, go to bootloader, flash the boot.img through fastboot then reboot. For other roms you have slightly different processes you have to follow. You can find the info on the thread for each
i have been running the kiss kernel for a while now, last night i tried to flash the hellboy kernel and retern to my pacman rom. but it still boots, i have cleared all my caches formated everything but my sd card, have tried flashing all kiss kernels and multipul hellboy kernels, but never gets passed the boot screen.. any ideas?
i managed to get it to the android is upgrading.. starting apps thing, but it gets stuck there.
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
lilrob1213 said:
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
Click to expand...
Click to collapse
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
JARR3DF15CH3R said:
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
Click to expand...
Click to collapse
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
lilrob1213 said:
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
Click to expand...
Click to collapse
yeah i installed it after, pacman http://forum.xda-developers.com/showthread.php?t=1948770&page=12
im with telus gsm. the rom was working fine, but i went to change the kernel to hellboy cause i herd it was a bit better and now im in this bootloop
also not running the newest version of that rom, i am running v15a
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
lilrob1213 said:
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
Click to expand...
Click to collapse
thanks anyways, ill be sure to give that a try:silly:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
bahubali67 said:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
Click to expand...
Click to collapse
yeah i always wait a little while, i have chosen latest kernel, has not made a difference, i have gotten better results using an older one of the titanium kiss, hellboy doesnt seem to work with my phone for some reason
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
mihirengg19 said:
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
Click to expand...
Click to collapse
i am using the all in one tool kit to flash my kernel, yes i am in fastboot, a window pops up runs through code and my phone reboots, i have changed the kernel on it before, but for some reason this time it wont boot properly at all, the phone is currently at the " android is upgrading" screen, it was the starting apps box with the spinning circle
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
thank you so much 1ceb0x! my phone has been in this bootloop for an entire 24 hours,
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel:
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
chikuera said:
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
Click to expand...
Click to collapse
Thats the old version.... See the changelog code and flash dat in future..... Right now.... Here u go....
http://www.mediafire.com/?waggdha1ir1lxz0
Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...
akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Happy to help you bro
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
LegatoExia said:
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
Click to expand...
Click to collapse
You flashed the TWRP in wrong way. You need to flash it by this method.
Mirhawk said:
You flashed the TWRP in wrong way. You need to flash it by this method.
Click to expand...
Click to collapse
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method (including your tutorial in your signature, which I'm trying as I write this) solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Edit : finished following your tutorials, everything seems to work for the moment, hope it will stay stable this time... thanks for your help )
LegatoExia said:
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Click to expand...
Click to collapse
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Mirhawk said:
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Click to expand...
Click to collapse
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the Lollipop Pure AOSP rom, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. After installing the ROM, I followed your recovery tutorial using "openrecovery-twrp-2.8.5.0-LT26i.img", hope I did the right thing this time, hahah. Thank you again for your help !
LegatoExia said:
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the rom AND the recovery, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. Thank you again for your help !
Click to expand...
Click to collapse
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Mirhawk said:
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Click to expand...
Click to collapse
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
LegatoExia said:
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
Click to expand...
Click to collapse
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Frostymoon said:
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Click to expand...
Click to collapse
I guess You are on stock firmware and flashed the "stock-6.1.A.0.452-twrp-2.4.0.0.elf" or the twrp.img file via fastboot directly. Flash the DoomKernel from here via flashtool as kernel and it will work with stock and have recovery too. Use the blue coloured "Download Now" button and the extension of file is .elf.