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
Related
Yesterday I tried updating to CM9 alpha 6 and when i updated i got stuck in a boot loop. it wasn't a clean install from 5 then when i got to the bootloop i did a factory reset and I'm still stuck. Someone told me it was possibly a bad ROM file. He told me to reflash a kernal and see if it boots up and if that doesnt work try flashing a newly downloaded CM6 Rom. I flashed the FF11 kernel and now i cant boot into recovery. If i hold power and up, it just boots normally put gets stuck in the CM9 animation. Any help would be greatly appreciated!
Try to Odin back to el29 that should do the trick just would have to start everything all over again.
Sent from my SPH-D710 using xda premium
yellowman82 said:
Try to Odin back to el29 that should do the trick just would have to start everything all over again.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ok so let me see if i got this process correctly, odin to el29 which puts me back on GB TW, then i boot into recovery then install the ROM? do i need to reflash gapps? also another question. I did a factory reset on my phone, that doesnt delete the internal storage partition that the phone reads as "sd card" correct?
Yes factory reset does not delete internal SD memory. You don't have to go back to gb. Just go into download mode, Download el26 cwm kernel and flash that through odin/PC and wipe everything. Flash cm9 alpha 6 and gapps. Should be good to go.
Sent from my SPH-D710 using xda premium
daniel4653 said:
Yes factory reset does not delete internal SD memory. You don't have to go back to gb. Just go into download mode, Download el26 cwm kernel and flash that through odin/PC and wipe everything. Flash cm9 alpha 6 and gapps. Should be good to go.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
sweet! im going to do it right now. thanks
armandosal said:
sweet! im going to do it right now. thanks
Click to expand...
Click to collapse
You're welcome. Let be know if it works.
Sent from my SPH-D710 using xda premium
it worked. thank you so much. I had a feeling that was what i was supposed to do but i completely bricked my last epic touch so now im very weary about doing flashes unless im 100% sure
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
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.
Alright, so I was running MIUI on my phone, and I decided to check out some other roms. I flashed the All Stars rom, wasn't too fond of it, then I flashed CM10. After flashing CM10, the default android keyboard kept crashing (it would continually pop up saying it has stopped every few seconds or so.) Also, my when I unlock my phone, there is no lock screen. Thirdly, my home button, well, doesn't do anything when I push it.
I'm really not sure what to do at this point, I flashed AOKP and the problems still persist. Any ideas on what I could do? Thanks.
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wolfygang said:
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
cwm 5.0.2.7
Here's an update, I unrooted my phone, flashed back to stock and everything worked fine, rooted again, still fine. Now whenever I flash a rom, the problem comes up again. The default stock browser isn't working either. Any help on what is going on would be greatly appreciated!
if you're using cwm 5.0.2.7, then you need to use darkside scripts.
merrygocow said:
if you're using cwm 5.0.2.7, then you need to use darkside scripts.
Click to expand...
Click to collapse
I am using them.
teeson24 said:
I am using them.
Click to expand...
Click to collapse
If CWM 5.0.2.7 is still not working for you, update to CWM 6.0.x.x or even better try flashing and using the latst TWRP recovery system.
Make sure you do the proper data/cache wipes before flashing the ROM again. Also, flashing the proper Gapps file for the specific ROM may help you fix the issue you are having with the home button and possibly the application issues you are having.
FineTalent said:
If CWM 5.0.2.7 is still not working for you, update to CWM 6.0.x.x or even better try flashing and using the latst TWRP recovery system.
Make sure you do the proper data/cache wipes before flashing the ROM again. Also, flashing the proper Gapps file for the specific ROM may help you fix the issue you are having with the home button and possibly the application issues you are having.
Click to expand...
Click to collapse
Actually, it's 6.0.2.7, I either mistyped or misread it, my bad. Going to try TWRP tomorrow, thanks for the help and will post updates.
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