Why do I have such a problem with recovery on my phone. It seems that regardless of what I'm flashing I have a problem with the phone rebooting into recovery. At least since ICS first came out, maybe earlier, when I'd flash a rom, alot of the time it would reboot into recovery and I'd have to ODIN back to stock and reflash. I flashed PB 3 without any problems but I tried PB4 and it would not boot beyond recovery. It seems to do it in CWM and Devil. I restored to a backup of AOKP and still recovery, which is currently Devil. What am I doing wrong or what do I need to do? I also have a problem keeping it from booting into safe mode, when it does boot. Any suggestions?
From what I can gather from your post it really appears that you are flashing things wrong. First things first, read droidstyle's guide on hoe to flash rooms properly. Couple other notes to keep in mind, once you are on cm7, ics, or jellybean you cannot just go into recovery and flash a touchwiz rom. You also cannot three finger boot into recovery anymore.
Sent from my SCH-I500 using Tapatalk 2
shelby04861 said:
From what I can gather from your post it really appears that you are flashing things wrong. First things first, read droidstyle's guide on hoe to flash rooms properly. Couple other notes to keep in mind, once you are on cm7, ics, or jellybean you cannot just go into recovery and flash a touchwiz rom. You also cannot three finger boot into recovery anymore.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I haven't gone back to TW in a long time. As far as flashing wrong, I may be but I'll download the rom, boot into recovery, wipe, wipe, and sometimes wipe again. Then flash rom. When I do ODIN back I push the stock EC09 I think it is (I'm on a different computer), Atlas 2.2. Let it fully boot, shut it down. Then push CWM fixed for CM7. Immediately boot into recovery with the 3-finger method (the only time I use the 3-finger). I flash THS ICS Version 2. Allow it to boot then flashed whatever AOKP is latest. What have I been doing wrong?
At what point does it get stuck in recovery, is it after you flash aokp or after you try to restore a backup?
Sent from my SCH-I500 using Tapatalk 2
shelby04861 said:
From what I can gather from your post it really appears that you are flashing things wrong. First things first, read droidstyle's guide on hoe to flash rooms properly. Couple other notes to keep in mind, once you are on cm7, ics, or jellybean you cannot just go into recovery and flash a touchwiz rom. You also cannot three finger boot into recovery anymore.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
shelby04861 said:
At what point does it get stuck in recovery, is it after you flash aokp or after you try to restore a backup?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Usually after I flash aokp, or another rom. If all I'm doing is doing a restore it's ok. Now I've flashed jt's JB and I can't keep it from booting in safe mode.
This morning after a full charge I booted into recovery to wipe battery stats because I was having poor battery life. I'm running JT's JB by the way. When I rebooted it booted into safe mode. I tried pulling the battery and still safe mode. It took me rebooting 8 times before it did not go into safe mode. What could be causing it? I must be doing something wrong.
It could be a hardware issue or corrupt files. I know this may sound obvious, but I would Odin back to stock a d follow droidstyles guide exactly and start over. Do a fresh install of everything and reinstall all apps. Don't restore backups or anything. This will give you some clues.
Sent from my SCH-I500 using Tapatalk 2
That may be part of my problem. I've read and re-read that and the only thing I'm not doing is checking repartition when I Odin to stock. When I do, Odin hangs up at the beginning and will not do anything else. It works fine when I uncheck repartition. I'm doinloading a new copy of Odin on a different computer and am going to try.
Toddw said:
That may be part of my problem. I've read and re-read that and the only thing I'm not doing is checking repartition when I Odin to stock. When I do, Odin hangs up at the beginning and will not do anything else. It works fine when I uncheck repartition. I'm doinloading a new copy of Odin on a different computer and am going to try.
Click to expand...
Click to collapse
Are you flashing gapps in the same session after flashing rom?
Sent from my SCH-I500 using xda app-developers app
Related
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
Went to ICS, didn't like it, nandroided back to GB (Unofficial), when I got there the phone would boot but would hang up at the first touch. So I wiped, factory reset, reinstalled the ROM, no go. So I just odin'd back to stock, same problem, I can't do anything to the phone without it freezing and rebooting....AND now I've lost CWM and my counter has been tripped from Odin.
Any ideas what I have done/can do?
Please HELP!!!!!
Flash stock through Odin, re root, flash CWM again, flash ROM again. Flash country doesn't matter any more with the reset fix we now have.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I did flash back to Stock and I'm still having all of these issues, do you think redoing everything would help?
Yeah probably. Then once you're in CWM clear all caches and whatnot if you can get back to CWM
Sent from my SAMSUNG-SGH-I717 using Tapatalk
beall49 said:
I did flash back to Stock and I'm still having all of these issues, do you think redoing everything would help?
Click to expand...
Click to collapse
Yes...ics came with a new bootloader
Odin back to stock
(flashing/android back to stock and odin back to stock two different things)
Thur u arrrrrrgh
Sorry I'm lost now, what steps should I take?
Try following this:
http://forum.xda-developers.com/showthread.php?t=1506330 for getting GB back. If that doesn't work, post back.
EDIT: that's just the kernel, flash http://forum.xda-developers.com/showthread.php?t=1504999 with CWM then use odin to flash that.
wipe everything as if installing a new rom.
holycow1 said:
Try following this: http://forum.xda-developers.com/showthread.php?t=1506330 for getting GB back. If that doesn't work, post back.
Click to expand...
Click to collapse
Yes I have done that, with the same issues.
beall49 said:
Yes I have done that, with the same issues.
Click to expand...
Click to collapse
I've gotten CWR back on, and I've noticed that when I wipe it says 'Error mounting /sdcard'. It can't perform a factory reset.
FWIW, I went back to stock, put CWR on, nothing worked, finally flashed back ICS, and its working again. Lets hope it stays that way.
Ive found out how to fix this, but everywhere I go there are dead links. Damn megaupload. This isnt my phone and I dont know anything about voodoo. Any directions to where I may find usable links?
Flash back too stock and start over
Sent from my SCH-I500 using Tapatalk 2
If it is a fassy try this http://forum.xda-developers.com/showthread.php?p=23171859
Sent from my SCH-I500 using xda premium
mezster said:
If it is a fassy try this http://forum.xda-developers.com/showthread.php?p=23171859
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
That helps but Im always getting hung up on the movinand.bin when using odin.
slipmagt said:
That helps but Im always getting hung up on the movinand.bin when using odin.
Click to expand...
Click to collapse
I knew I had seen something about that before...
my search turned up this....
Basically make sure your doing the GB Bootloaders and recovery at the right time and proper way
Quote:
Originally Posted by ssewk2x View Post
The CI500_blahblahblah.tar file that you mention does, in fact, flash a bootloader to your phone: the old Froyo one.
The upshot is that every time you use this file to go back to stock, you should odin the GB bootloader again at some point during your process. I generally like to do this:
1. odin CI500blahblahblah.tar. reboot and let it come up.
2. power off and go back into odin. now do the gb bootloader. use PDA, check "update bootloader." reboot and let it come up.
3. power off and go back into odin. now do the old cwm for CM7 recovery. 3-finger reboot directly to that recovery (don't let stock rom boot or it will blow away that recovery you just flashed).
4. flash whatever ROM you are going to from that recovery.
5. Profit.
i actually do all my odin stuff without any reboots and never boot into stock. i flash all odin packages and then go straight to 3 finger recovery.
ThanksThanks
----------------------------------
Quote:
Originally Posted by Sheradrax View Post
i actually do all my odin stuff without any reboots and never boot into stock. i flash all odin packages and then go straight to 3 finger recovery.
It used to be important to let it boot through the stock recovery if you were re-partitioning the device, because the ext4 partitions were then built on top of the stock ones. ODIN couldn't create the MoviNAND partitions if they were corrupted, but the stock recovery could.
The new LVM formatter might be able to handle it, I'm not sure.
-------------------------------------------
.
Hi there,
I tried to flash a new rom and it some how is stuck on the reboot screen.
Any help in what to do, would be great!
Thanks!
Pull the battery, put it back. Hold button combo to boot to recovery. Flash the ROM again but do not wipe. Reboot and you should be good.
FFR please list which ROM you are coming from and the ROM you are flashing.
Sent from my SCH-I535 using xda premium
Thanks, for your help!
I ended up taking out the battery, and then rebooting it, and it went to the Recovery mode.
I actually did wiped everything all over again, like you were doing it from the start originally, and it seemed to work fine.
I cant even remember what I was coming from, I had it on my Phone for almost two years, and it was old and the battery life was terrible.
I tried RemlCS-JB its not bad, but I think I am going to try another one. Any suggestions? I have been away from this forum for over a year, so anything recent with good battery life and good GPS is ideal.
The rom did not seem to come with an app downloader such as google play, or Clockwork manager.
Anyone know how to get into reboot recovery mode without clockworkmanager?
When I try to download clockworkmanager online it does not let me really download it.
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
molson24 said:
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
Click to expand...
Click to collapse
Did you Odin back to stock before trying to flash a ROM that is a previous version of android? It could cause a lot of problems if you don't Odin back to stock first!
Did you flash gapps on the ROM that you said was missing apps etc?
Gapps is a package of Google apps that devas can't include in the ROM.
I wouldn't use ROM manager, in most ROMs, there is an option to reboot to recovery in power menu. You can also power down and use button combo to boot to recovery.
I highly suggest reading through some of the dev threads for any ROMs you are interested in. It will answer most of your questions and prevent future issues.
Sent from my GT-P5113 using xda premium
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
molson24 said:
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
Click to expand...
Click to collapse
You can get the gapps from the op of the ROM thread or go to www.goo.im/gapps
As far as Odin etc
If you are on an ICS or JB ROM and want to go back to a froyo or GB ROM, you need to odin to stock first.
General rule of thumb, you can flash up but to flash down, Odin to stock first.
Sent from my SCH-I535 using xda premium
Got a s4 today, followed the root guide here, using mdk pre release kernel. Did not unlock the boot loader. Loaded hyperdrive and after loading everything did the reboot. left me at the black samsung screen with an unlocked padlock and custom underneath. i can get into recovery and download. but no matter what i do will not progress screens (even tried full cache, dalvic, system, and data wipe and reloaded Hyperdrive. same results)
Should i re flash back to stock and try the entire process over again? if so, links please
also, what did i do to soft brick my phone? for future avoidance
and whats the difference between mdk and me7?
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
To clarify, your suggesting re downloading rls8, and try flashing that. Then, if that doesn't work, re flash the stock kernel (basically go through the Odin root guide again?)
Thanks!
Redownload rls8 verify the md5 checksum to make sure its not another bad download and then flash. As long as you can get into custom recovery of your choice and the download is good theres no reaaon it shouldnt work.
Sent from my SCH-I545 using Tapatalk 2
correct md5sum, same results.
both odin'd kernels have no effect, same boot problem. anyone know a fix?
Hopefully someone will. Same problem. Putting my phone back to stock rooted MDK works. The minute I try to flash Hyperdrive 8 and 8.1, it boots fine, then hangs on a restart.
Atleast, Will verizon exchange the phone seeing this?
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Addiso said:
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
and yet no one has yet been able to pinpoint what mistake i made in installing a rom i've used for 12 months (s3) and installing a new version on a new phone while following every instruction to the letter, suddenly ****s on me. so please, enlighten me, what mistake did i make?
You didn't make a mistake. Chances are, you just used the wrong recovery. I spent 7 hours last night trying to fix my phone. I factory reset this morning to the stock MDK and re-rooted and figured out how to use ADB to install the Clockwork Mod Recovery. It's difficult to get started and figure out how to install and use it, but there are resources out there that will help you figure it out. I reinstalled the new 8.1 Hyperdrive with CWM recovery and was delighted when the ROM actually rebooted without fuss. It did hang on the Custom unlock screen long enough to make me nervous though. Figure out ADB and add CWM. It will work.
Edit for your steps: Reinstall the stock MDK with Odin. Reroot as per the instructions in the MDK root thread. Instead of TWRP, use CWM Recovery (which isn't nearly as easy), then reinstall the latest Hyperdrive (or whatever you were trying to install).