Related
I was running Strongsteve's blue rom and wanted to update to his latest version, so I wiped my cache and delvik and used CWM to install. When I rebooted, the phone never got past the SGS2 boot screen. I took out the battery and rebooted a bunch of times with no luck. I was able to get back in to CWM by holding pwr and up, and I reflashed the rom with no luck. I had Blazer's rom on the internal drive already and flashed that, but it still hung at the SGS2 boot screen. Now, I can't get back in to CWM and I can't charge my phone. I can still get in to USB mode but i've never used it before.
I rooted using auto-root, and i'm going to try using ODIN but i'm not sure what i should flash on there if i can even get my computer to connect to my phone...another ROM, the stock ROM, zedomax root? any advice?
i think i'm gonna go with the stock rom (http://forum.xda-developers.com/showthread.php?t=1479677) but not sure if there's other steps or things i should be doing instead...please help!
If you hold the power button + power down, can you boot into download mode?
yes...
i'm going to try odin but i'm not sure what file to flash...any thoughts?
Find the stock tar file in the epic 4g touch development. Someone just posted one not too lon ago. When you flashed the update did you follow all instructions to a t? I have run into similar problems because i thought skipling a step wouldnt matter.
Sent from my SPH-D710 using XDA App
As long as you can get into download mode, you're good.
Use this: http://forum.xda-developers.com/showthread.php?t=1383678
yeah i followed the instructions but something must have gone wrong. i'm going to try odin when i get home...i'll let you guys know how it goes. thanks!
one more question...do i need to flash the kernel too?
Keep in mind, if you flash the EL29 listed earlier, it will disable the reset ability of the USB jig (will still get you to ODIN D/L mode, just won't reset ODIN flash stats)
I suggest you flash the pre-rooted EL29 ODIN One-Click in my signature, but it is up to you.
mistatwo said:
one more question...do i need to flash the kernel too?
Click to expand...
Click to collapse
No, not if u odin. The kernels in there
Sent from the future
fixed! used the el29 odin root method (http://forum.xda-developers.com/showthread.php?t=1433101)
THANK YOU GUYS FOR ALL YOUR HELP!
Just a quick question..
Can you avoid all the above steps if you do a nandroid restore? I thought if I just did a nandroid restore and reflash from scratch I should be goodl. I did a nandroid back up when I rooted with the stock ROM and figured if I ever ran into problems I could retore and start fresh? Am I thinking about this the right way or do I need to go through the steps above when/if I get stuck a the boot screen..thx
For all who like to flash. Get md5checker from the market.Use it love it. Never flash a bad ROM again. Saves alot of headaches and time. Not to mention clutter.
---------- Post added at 09:03 PM ---------- Previous post was at 09:03 PM ----------
pawmbi1 said:
Just a quick question..
Can you avoid all the above steps if you do a nandroid restore? I thought if I just did a nandroid restore and reflash from scratch I should be goodl. I did a nandroid back up when I rooted with the stock ROM and figured if I ever ran into problems I could retore and start fresh? Am I thinking about this the right way or do I need to go through the steps above when/if I get stuck a the boot screen..thx
Click to expand...
Click to collapse
You are correct. As long as you have custom recovery.
btw it might have been a bad download. grab the md5 checker from the market like the guy above me a couple posts said. also redownload the rom if it is.
Phone stuck at logo screen
Hi, pls help..
Yesterday i have try to root my phone and today i have decided to restore to stock firmware.
As i didnt backup my files, and i try to restore by following this website from cnet.co.uk
after restore, my phone stuck at logo screen...
I can't turn off my phone nor entering download mode and boot screen.
:crying:
First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.
If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.
lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app
I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX
I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A
Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium
You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary
Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app
Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.
I currently have CM 10.1 stable installed on my gs3, but have been getting terrible battery life. I'm thinking of going back to the stock ROM for awhile, but can't find the best way to do it. I used to have a backup of the old stock image, but somehow it got deleted and I guess I didn't have it backed up on my computer. Is there an easy way to revert back to the stock ROM, preferably with root? I was hoping to just flash it with CWM, but can't seem to find this anywhere?
I don't care about resetting the flash counter or anything, just hoping to get the stock rooted ROM back
There are stock rooted roms in development. After flashing with Odin, you will have to perform a factory reset when it boot loops. Don't freak, this is normal. A word of caution. Performing the factory reset in stock recovery will wipe your internal memory so back up the stuff you want to keep
mrhaley30705 said:
There are stock rooted roms in development. After flashing with Odin, you will have to perform a factory reset when it boot loops. Don't freak, this is normal. A word of caution. Performing the factory reset in stock recovery will wipe your internal memory so back up the stuff you want to keep
Click to expand...
Click to collapse
This is probably a stupid question, but how do you factor reset if it boot loops?
Set it to download mode, then just reflash with Odin. Boy this would've made me feel better about my phone this morning... here I thought I screwed something up royally in Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ishttp://forum.xda-developers.com/showthread.php?t=1739426 this the ROM I want if I want to stay rooted? I'm pretty sure this is what I used when I first rooted, but just want to make sure this will work. Thanks for the help
diiggidy said:
This is probably a stupid question, but how do you factor reset if it boot loops?
Click to expand...
Click to collapse
Just pull battery, and go Vol. Up+ Power +Home and go down to wipe data/factory reset. (Be weary, this will wipe internal sd card content.)
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
diiggidy said:
Ishttp://forum.xda-developers.com/showthread.php?t=1739426 this the ROM I want if I want to stay rooted? I'm pretty sure this is what I used when I first rooted, but just want to make sure this will work. Thanks for the help
Click to expand...
Click to collapse
You can use that, but since it is 4.1.1, you won't be able to OTA to 4.1.2 unless you're 100% bone stock.
Hey hey,
Today I had a SuperSU update through the Play Store which I installed. When that was done it told me I needed to update my binary or something along those lines. Since I have an HTC it told me I should install it through a custom recovery like TWRP. I already had TWRP installed, so I went ahead and did that. After it did its thing, it rebooted. Or well, tried. I stared at the boot animation for about 10 minutes, and then I rebooted. I still didn't get past the boot animation. Then I shut it off, went into my bootloader and via there into the recovery. Downloaded the latest SuperSU zip and flashed it through TWRP. Rebooted, but no dice. A couple of reboots later and I'm unable to properly shut off my phone or get into the bootloader/recovery. When I try to shut it off with Power+Volume up it simply reboots. I also can't see my phone through ADB.
My M8 has been converted to Lollipop GPE and have had no issues at all before. I am sort of familiar with ADB, recovery's etc, but I would not call myself an expert. Right now I'm at a loss, and any help would be great.
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.
Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
jsmits447 said:
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.
Click to expand...
Click to collapse
Since you can now boot recovery, restore your nandroid that you made.
redpoint73 said:
Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
Since you can now boot recovery, restore your nandroid that you made.
Click to expand...
Click to collapse
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.
jsmits447 said:
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
Click to expand...
Click to collapse
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
jsmits447 said:
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.
Click to expand...
Click to collapse
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.
redpoint73 said:
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.
Click to expand...
Click to collapse
Yeah, for once I decided to create a backup when I'm told to. I'm actually not sure it's the Lollipop nandroid. I made it 10 februari 2014, but there's a chance it's the one from Kitkat before I upgraded to Lollipop. Any way I could figure out? Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Thanks for clearing up what a factory reset does! Great to know.
jsmits447 said:
Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Click to expand...
Click to collapse
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.
redpoint73 said:
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.
Click to expand...
Click to collapse
Alright, will do. Be right back.
Just restored the nandroid from the 10th of december in twrp. It now asks me if I want to install SuperSU. Should I?
I went ahead and also installed SuperSU when it asked me to. Didnt even get to the boot animation then. Only saw "Google" and the little open lock. I have now restored to my Lollipop nandroid I just made.