Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Hoezack said:
Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yea, It almost ruined my phone as well. I ended up having to restore to an older version. It wouldnt let me flash anything, constantly hung or restarted, and never actually told me that it finished, though when I rebooted it turned out that it did finish flashing, although much of it was messed up, almost like it only flashed certain parts of the rom.
I've had very similar experience with 6.0.1.4.
I'm glad I'm not alone, I thought it was just something I did wrong.
Sent from my SGH-T989 using xda premium
mth785 said:
I'm glad I'm not alone, I thought it was just something I did wrong.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Why they have released the update is puzzle to me? Its bad. 5.0.2.7 is the best.
ksrikanthreddy777 said:
Why they have released the update is puzzle to me? Its bad. 5.0.2.7 is the best.
Click to expand...
Click to collapse
5.0.2.7 cache wipes and fix permissions do not work for ics hence the scripts. 6.0.1.2 worked great. i've had problems with 6.0.1.3 and eventually started using twrp. no regrets.
I'm using sk8's CWM 6.0.something touch recovery and everything is working.
Sent from my SAMSUNG-SGH-T989 using xda premium
I didn't flash 6.0.1.4 from ROM Manager (blackwing version), but I flashed it from CWM and I just got a boot loop while trying to install CM9 09-23 Nightly.
Did a battle pull, and tried to do stuff in CWM6 and it was super slow and nothing would flash. I couldn't even wipe caches or do a factory reset.
I ended up doing a Restore (which never finished) but did a battery pull and luckily I was able to boot into my previous ROM.
I never had any issues with 5.0.2.7 thanks to Darkside Super Wipe and Cache scripts, even flashing ICS and JB ROMs.
freedom_xda said:
I didn't flash 6.0.1.4 from ROM Manager (blackwing version), but I flashed it from CWM and I just got a boot loop while trying to install CM9 09-23 Nightly.
Did a battle pull, and tried to do stuff in CWM6 and it was super slow and nothing would flash. I couldn't even wipe caches or do a factory reset.
I ended up doing a Restore (which never finished) but did a battery pull and luckily I was able to boot into my previous ROM.
I never had any issues with 5.0.2.7 thanks to Darkside Super Wipe and Cache scripts, even flashing ICS and JB ROMs.
Click to expand...
Click to collapse
Yeah I had the same problem so I had to go back to 5.0.2.7.... Wit this version I have no problems backing and restoring roms.....Also with this version I can flash any rom ics, aokp, gb
Sent from my SGH-T989 using xda app-developers app
I'm currently using sk8's cwm6.0.1.4 and no issues so far.
pepe7053 said:
Yeah I had the same problem so I had to go back to 5.0.2.7.... Wit this version I have no problems backing and restoring roms.....Also with this version I can flash any rom ics, aokp, gb
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I had the same issue with 6.0.1.4 non-touch. But the touch version is working just fine.
Make sure you wipe dalvik cache and wipe partition before flash.
wow, I also had flashed the non-touch recovery and that's when I started getting all my problems.
I'm still using v5.0.26 and darkside superwipe, no issue at all roms
Twrp 2.2.2 is stable
another case of a product becoming a paid product while losing quality in the process.
Im currently running a Nandroid backup using 6.0.1.4 and its hella slow... like 20+ mins and still running, this is beyond bad. On 5.0.2.7 it ran in about 5mins.
Is the touch recovery better?
Edit: Now its at almost 40 mins... yeesh
Hoezack said:
Ive been using recovery 5.0.2.7 and I flashed new Recovery 6.0.1.4 threw rom manager today and it almost screwed my phone. I booted into 6.0.1.4 and it would not flash anything. I rebooted and my phone was stuck on boot loop. Luckily I made a backup on the old recovery. it took forever when i restored (30 mins stuck on restoring). and it didnt even say complete. I had to pull battery, powered back on and restore had actually completed (lucky) ....Has anybody flashed recovery 6.0.14 and experienced this issue?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I had the same exact problem with it yesterday. I was trying to restore my backup, so I tried to do a wipe/reset and it wouldn't do anything. So I just restored my backup anyway and it would always just stop at restoring secure.android. So I took out the battery and rebooted and my backup was restored. So I tried ROM manager to flash back to 5.0.2.7. But it constantly forced closed. So long story short, I'm now using twrp and I like it better.
Omg I thought I was the only one with this problem. Took me forever to get my phone working again. Had to Odin back to stock. 6.0.1.4 touch was working fine though (installed using Odin)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hmm.. ROM manager flashed 6.0.1.4 just fine on my phone. I've done this procedure about 4 times too. Weird.
Sent from my SAMSUNG-SGH-T989 using xda premium
Khameleon said:
Im currently running a Nandroid backup using 6.0.1.4 and its hella slow... like 20+ mins and still running, this is beyond bad. On 5.0.2.7 it ran in about 5mins.
Is the touch recovery better?
Edit: Now its at almost 40 mins... yeesh
Click to expand...
Click to collapse
on 6.0.1.4 and 6.0.1.5, mine just hangs on "backing up .android_secure" and the progress bar never moves. I've waited up to 40 minutes with no progress. I've never completed a backup since I switched from 5.0.2.7. I'm going to switch to another recovery.
Related
So after flashing the Hitman 1.5 with Touch Recovery, my recovery doesn't work. I tried flashing other kernels via Odin, to no luck. Tried flashing EG30 rooted, still no luck. Basically whatever recovery I flash, I can see it boot to its name, but then it quickly reboots. I've seen others report of same issues, but no fix?!
you need to odin completely back to stock with a full rom.
just flashing kernels is not going to fix it.
lafester said:
you need to odin completely back to stock with a full rom.
just flashing kernels is not going to fix it.
Click to expand...
Click to collapse
Yup, that's what I had to do.
A lot of the bootloops and bricks seem to have the Touch Recovery in common...
Dalmus said:
A lot of the bootloops and bricks seem to have the Touch Recovery in common...
Click to expand...
Click to collapse
after i flashed back to stock i ran into a bootloop when i left fb09. i pulled the battery and booted into recovery wiped data/factory reset rebooted and everything was dandy.
Hmm, having issues going back to gingerbread from ics leak. Flashed complete system, then recovery. I can boot into it fine, although errors a lot and doesn't see internal, only SD. Installs, but doesn't boot up fully. Reflashed full ics leak again and it works fine again. Bah!
Sent from my SPH-D710 using XDA App
afive720 said:
Hmm, having issues going back to gingerbread from ics leak. Flashed complete system, then recovery. I can boot into it fine, although errors a lot and doesn't see internal, only SD. Installs, but doesn't boot up fully. Reflashed full ics leak again and it works fine again. Bah!
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I'm not sure what to tell you my friend.
Sent from my SPH-D710 using xda premium
I'm new to Samsung Android phones, and new to the E4GT, so I need a little help.
I always flash the zip for the EL26 CWM5 recovery like instructed, soooo, here is my issue.
I'm running AOSP and thought I would try CM10 JB, soooo, I flashed into EL26, performed a full nandroid to my Ext SD. I flashed JB and gave it a shot. For issues known to all, I wanted to switch back
So, I went into recovery, flashed the EL26 recovery and rebooted recovery, I then restore the nandroid backup I just made, rebooted, went to the Samsung screen (with the yellow !). After some time, about 20-30 seconds, it goes to a black screen indefinately until I pull the battery.
Any ideas? I have yet to get a nandroid to work on this device. Had no issues at all on my 3D. I'm sure I'm doing something wrong.
TIA,
Tee Jay
You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA
g_ding84 said:
You need to flash the AOSP kernel. Well first can you boot into recovery or download mode
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yeah I can get into recovery fine, so I flashed an AOSP kernel and then my wifi didn't work.
Is it not connecting?
Sent from my SPH-D710 using XDA
g_ding84 said:
Is it not connecting?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Nope, won't even turn on. But if I do a full clean flash of the exact ROM, it works fine.
I'm by far no expert but I'd say the kernel is being replaced by the gb recovery kernel when you flash back for your safe recovery.I personally keep a couple various recoveries so I can nandroid backup on the kernel native to the Rom and then the backup will contain the proper kernel.I think I got that right.so....nandroid b4 recovery has been my habit.
Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app
dante32278 said:
Had this issue before, minus the yellow triangle....anytime you're on an aosp rom and do a nand via el26, the nand stores the last kernel used (which is GB el26). After you restore, wipe cache and dalvik and then flash an aosp kernel, probly one from chris41g. Reboot and should he good to go.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Right, I tried that with my AOKP backup, I was able to boot. But then my WiFi wasn't working because of something to do with the Kernel I'm assuming
I flashed TWRP 2.5 and then flashed Task's AOKP 4/9 ROM and everything went down hill from there. The phone kept rebooting after a minute or so, so I did a factory reset and reflashed the ROM. That didn't help, it actually made it worse in that it would not get past the kernel splash screen. So I did another wipe and the same thing. I wiped again and flashed an older version of AOKP 4/5 and again would only get to the kernel splash. After another hour or so I decided I'll just go back to rooted stock, so using Odin 3 3.07 I flashed my trusted root69.stock_ATT_I747UCALG1 image and now it just stays on the Samsung screen.
I've run out of thoughts on what the hell is the problem and thought I'd ask.
Anyone have any suggestions on what I can do to get this paper weight working again?
dhostetter said:
I flashed TWRP 2.5 and then flashed Task's AOKP 4/9 ROM and everything went down hill from there. The phone kept rebooting after a minute or so, so I did a factory reset and reflashed the ROM. That didn't help, it actually made it worse in that it would not get past the kernel splash screen. So I did another wipe and the same thing. I wiped again and flashed an older version of AOKP 4/5 and again would only get to the kernel splash. After another hour or so I decided I'll just go back to rooted stock, so using Odin 3 3.07 I flashed my trusted root69.stock_ATT_I747UCALG1 image and now it just stays on the Samsung screen.
I've run out of thoughts on what the hell is the problem and thought I'd ask.
Anyone have any suggestions on what I can do to get this paper weight working again?
Click to expand...
Click to collapse
Not sure about the problem with aokp. But your bootloop just pull the battery, reinstall battery, go into stock recovery, factory reset and voilà
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Not sure about the problem with aokp. But your bootloop just pull the battery, reinstall battery, go into stock recovery, factory reset and voilà
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This will do it. Flashing back to 4.0.4 will bootlopp until you factory reset in stock recovery
Sent from my SAMSUNG-SGH-I747 using xda premium
Same thing happened to me. Boot loop with 4/9 AOKP task so I Odin to the same file as you but that ran just fine. I would try to Odin again.
Oh and after stock with root I flashed 4/9 and all was good. By chance did you have custom boot animation?
Sent from my SGH-I747 using xda premium
drock212 said:
Same thing happened to me. Boot loop with 4/9 AOKP task so I Odin to the same file as you but that ran just fine. I would try to Odin again.
Oh and after stock with root I flashed 4/9 and all was good. By chance did you have custom boot animation?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Yes I had a custom boot image.
Getting ready to factory reset and reboot. Hope all goes well.....
dhostetter said:
Yes I had a custom boot image.
Getting ready to factory reset and reboot. Hope all goes well.....
Click to expand...
Click to collapse
I think it's the custom boot causing this issue. Anyway good luck. I know my heart skipped a beat when my phone would boot loop while to get into recovery. Once I Odined back to stock with root first/only thing I downloaded was goomanager and installed TWRP then flashed 4/9.
Sent from my SGH-I747 using xda premium
drock212 said:
I think it's the custom boot causing this issue. Anyway good luck. I know my heart skipped a beat when my phone would boot loop while to get into recovery. Once I Odined back to stock with root first/only thing I downloaded was goomanager and installed TWRP then flashed 4/9.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm back up and running again. A little embarrassed I forgot the factory reset last night.
Thanks for the reminder!
AOKP is a great ROM.
When flashing ROMs always follow these steps and you will be fine.
1- nandroid backup
2- format system
3- wipe cache
4- wipe Dalvik
5- factory reset.
Most suggest doing each 3 times.
6- install ROM and reboot
7- flash gapps
Let sit for 10 minutes.
Follow those instructions and everything will be fine.
Sent from my SGH-I747M
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
I think most people still recommend 2.5.0.2, because 2.6 is so buggy...
Sent from my SGH-M919 using XDA Premium 4 mobile app
Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
Yes, TWRP has issues, use CWM. I'm using it for a while. So far so good
Sent from my SGH-M919 using xda app-developers app
TWRP is my preferred recovery and I've had zero issues with version 2.5.0.2 since I got this phone.
Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
I had exactly the SAME expirence.although I'm not new at rooting and using custom roms this being a new device for me I took everyone's advice and installed twrp. it was so buggy that it almost bricked my device. it got stuck on the introduction screen I couldn't get into tecovery or get out of the screen.i Eben pulled battery and it continued on that screen. finally finally I was able to get into the recovwry system, I rebooted and immediately I downloaded cwm recovert touvh wick has been wonderful ever since. That said, I thought this expirence with twrp was mine alone until ive heard of similiar complaints. I would NOT recommend twrp to ANYONE myself.i couldn't even flash a rom on it. I'm stocking with cwm recovery where its solid and works well
Nexus 6 said:
why didnt i start with clockworkmod instead of twrp. for hours now i thought i was doing something wrong while trying to restore a rom. it turns out the newest twrp is buggy. why are people recomending the latest twrp when it it so buggy.
Click to expand...
Click to collapse
I am clueless as to why anyone would want to use TWRP as well lol. CWM has always done its job.
When I restore a backup that I made, do I have to wipe anything before or after the restore process?
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Have you tried PhilzTouch yet?
Alex9090 said:
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
lalec said:
Have you tried PhilzTouch yet?
Click to expand...
Click to collapse
Never used philz and never thought of just reflashing the kernel. I may try that though. Now to find the kernel. I should mention that I end up using Odin to reflash stock. Then I root and then custom recovery. That boots fine and for the most part all I'm ever doing is trying to restore a 4.4 rom I backed up.
Flashing a kernel worked. lol my phone doesn't think it's the stock kernel but it booted at least.
I do find this interesting. I would think when you restore a nandroid backup that it would restore the kernel that was with the rom you are restoring. I guess this isn't the case?
Using the latest clockwork has always worked for me.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had Rom Manager Premium since my Defy days. I'm a firm believer in it. I was just surprised I would have to reflash a kernel after restoring a rom.
Corwinder said:
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
Click to expand...
Click to collapse
I use OUDHs Touch recovery v1.0.3.3 in conjunction with Rom Manager and I have NEVER had that problem. Also, when I use Rom Manager to "Back Up Current Rom" I can NAME the backup file, and it goes into the recovery and uses the filename I have already typed in and it's a seamless operation. Even using restore via Rom Manager works seamlessly and it has NEVER balked on me.
The only time I had a problem was once using My Backup Pro and trying to do an on-line system backup. MMS, SMS, Call Log has always been absolutely perfect! No out of sequence messages, and all the pictures are restored correctly too!
Aloha and Good Luck!
BTW, I am on a Stock 4.2.2 with the latest M919UVUFNB4 (modem.bin) Flashed for the radio and it's reception qualities are better than it's ever been before!