Related
So I rooted my phone and flashed Krylon360's Stock + Root rom using this thread ( http://forum.xda-developers.com/showthread.php?t=1001759 ). Everything went perfectly until I rebooted from recovery mode. It sits there in the boot screen trying its hardest but just keeps randomly vibrating. Not sure what to do about this since It will not go back into download mode to retry again. Any help would be greatly appreciated.
Go back into download mode and try flashing kc1 instead
Sent from my SGH-T959V using xda premium
Nothing ended up working. Just kept sitting in the boot screen, vibrating some more. So I just flashed the original stock back onto it. Thanks for your help though.
caprisun5 said:
Nothing ended up working. Just kept sitting in the boot screen, vibrating some more. So I just flashed the original stock back onto it. Thanks for your help though.
Click to expand...
Click to collapse
Put your phone in download mode and flash the SMS-KJ6 one-click from here: http://forum.xda-developers.com/showthread.php?t=1358498
(yea, I need to update the kernel in that package... everything moves so fast)
Leave the one-click open, after the phone reboots from the first flash take the battery out (let it reboot all the way to the pink t-mobile screen, then pull the battery. It does boot into recovery and tries to do some csc update, just ignore any errors in that). put the battery back in and the battery case back on, hold vol+ and vol-, plug in the usb cable and let go of vol+ and vol- when you see the download mode screen come up.
Check the flash bootloaders and click flash again. This gets your phone on GB bootloaders, which if you're coming from froyo, you will need it (you can also get the same bootloaders from FBis251's ext4 starter kit).
After that is done, you should download octane 3 cwm zip and my latest kernel to your sdcard, reboot to recovery, wipe everything, flash octane 3 then my kernel. Let it sit for 30 minutes after rebooting to let everything juice up and soak in.
Also, never odin/heimdall flash on a low battery. Always charge your phone all the way up before doing this as not to brick because your battery died.
caprisun5 said:
So I rooted my phone and flashed Krylon360's Stock + Root rom using this thread ( http://forum.xda-developers.com/showthread.php?t=1001759 ). Everything went perfectly until I rebooted from recovery mode. It sits there in the boot screen trying its hardest but just keeps randomly vibrating. Not sure what to do about this since It will not go back into download mode to retry again. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I had the same problem. I booted into recovery cleared the cache and user data then restarted the ODIN process and it worked and booted fine.
was coming from CleanRom7
have TWRP V2.6.3.1
wiped cache, data, davik
installed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK)
flashed ZIP - successful message recieved (noting that boot times would be 3-5 minutes)
system reboot took me back to recovery
tried to restart several times - always back to recovery
reflashed zip file again -
now won't do anything except stick on Samsung Galaxy SIII banner
what is the recommendation?
bgbird said:
was coming from CleanRom7
have TWRP V2.6.3.1
wiped cache, data, davik
installed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK)
flashed ZIP - successful message recieved (noting that boot times would be 3-5 minutes)
system reboot took me back to recovery
tried to restart several times - always back to recovery
reflashed zip file again -
now won't do anything except stick on Samsung Galaxy SIII banner
what is the recommendation?
Click to expand...
Click to collapse
Wipe again and wipe system. If don't work try reflashing TWRP. Something is corrupt. Check MD5 of rom download.
still no joy
reflashed TWRP - went back to 2.5.0.0-d2vzw.tar - via ODIN - that went OK -
then retried the both the VRUCML1 and the cleanrom7 ROM flash - still no luck. it flashes SAMSUNG then Samsung GALAXYSIII and hangs
Can anyone you recommend an image (hopefully that won't quickly do the OTA) that I can ODIN that will enable me to start over?
bgbird said:
reflashed TWRP - went back to 2.5.0.0-d2vzw.tar - via ODIN - that went OK -
then retried the both the VRUCML1 and the cleanrom7 ROM flash - still no luck. it flashes SAMSUNG then Samsung GALAXYSIII and hangs
Can anyone you recommend an image (hopefully that won't quickly do the OTA) that I can ODIN that will enable me to start over?
Click to expand...
Click to collapse
Whoa! I thought I was the only one! 4.3 worked for the first boot, and then never booted after that.
Somehow (I really don't know how) I got it working without ODIN. When my phone got stuck at the "Samsung GALAXY SIII" screen, I pulled the battery many times and even tried reflashing CleanROM 7 many times, still getting stuck at the SIII splash screen on boot.
Since it was night, I retired for the day and plugged my phone in to charge (AC) over night (thinking that I'd have to ODIN too). However, in the morning, I picked up my phone, pressed the home button (seeing the battery icon at 100%) and then powered on the phone. It booted into CleanROM! From there I flashed the 4.3 Stock Deodexed and from then it has always booted!
So I guess what really happened was that I charged it to 100%, pressed the home button to wake the phone up and then booted into android.
Here's some things to note though:
1. If you have a custom splash screen, remove it; it doesn't work and only makes the phone reboot.
2. I lost everything on my internal storage, whether for better or for worse, so I actually formatted it again before flashing 4.3
Hope that helps
Here is where I'm at...
yosterwp said:
Whoa! I thought I was the only one! 4.3 worked for the first boot, and then never booted after that.
Somehow (I really don't know how) I got it working without ODIN. When my phone got stuck at the "Samsung GALAXY SIII" screen, I pulled the battery many times and even tried reflashing CleanROM 7 many times, still getting stuck at the SIII splash screen on boot.
Since it was night, I retired for the day and plugged my phone in to charge (AC) over night (thinking that I'd have to ODIN too). However, in the morning, I picked up my phone, pressed the home button (seeing the battery icon at 100%) and then powered on the phone. It booted into CleanROM! From there I flashed the 4.3 Stock Deodexed and from then it has always booted!
So I guess what really happened was that I charged it to 100%, pressed the home button to wake the phone up and then booted into android.
Here's some things to note though:
1. If you have a custom splash screen, remove it; it doesn't work and only makes the phone reboot.
2. I lost everything on my internal storage, whether for better or for worse, so I actually formatted it again before flashing 4.3
Hope that helps
Click to expand...
Click to collapse
Here is where I'm at...
1. rooted
2. unlocked bootloader
3. flashed CWM recovery
4. did factory reset
5. flashed VRUCML1_Stock_Root_Deodex (12.31.13) (after again checking MD5 hash)
6. after flash - it tried to boot - but always went back to recovery
7. did factory reset - tried again still no boot up. continues to loop to recovery
8. flashed CleanRom7 - not it tries to boot but get hung after 1 second on the Samsung GalaxySIII black and white logo
Guess that I'll have to either stay on the KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 that you gave me or move to the
ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_user_low_ship.tar.md5.7z that is out there
Is there anything that you can think of?
bgbird said:
Here is where I'm at...
1. rooted
2. unlocked bootloader
3. flashed CWM recovery
4. did factory reset
5. flashed VRUCML1_Stock_Root_Deodex (12.31.13) (after again checking MD5 hash)
6. after flash - it tried to boot - but always went back to recovery
7. did factory reset - tried again still no boot up. continues to loop to recovery
8. flashed CleanRom7 - not it tries to boot but get hung after 1 second on the Samsung GalaxySIII black and white logo
Guess that I'll have to either stay on the KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 that you gave me or move to the
ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_user_low_ship.tar.md5.7z that is out there
Is there anything that you can think of?
Click to expand...
Click to collapse
Hmm, the only other thing that I can think of is perhaps flashing the MF1 modem (the all in one package) and then flashing the ML1 modem.
so i have an S4 with verizon and rooted it successfully on 4.2 to Hyperdrive 10.1 using Safestrap.
i was running it for about a week or so and realized i never rebooted it, i tried to last night and got stuck on the download screen.
i think the reason this happened is because on that "Slot 1" (Hyperdrive) i never installed Safestrap and so i didnt try rebooting
using the option that is given in SS, instead i tried rebooting into recovery using the menu you get holding the power button.
is there some sort of simple fix to this seeing as how i have everything done correctly besides the fact that i cant get into SS?
if i do have to do a wipe and clean stock flash ._. can i get any data i may have on my phone?
Go to recovery and clear data and cache or flash stock rom thru odin..
Sent from my GT-S5830i using Tapatalk 2
Phone: Samsung Sprint S5 GM-900P
System: Windows 7
Build: KTU84P.G900PVPU1ANK4 (4.4.4)
Recovery Screen shows:
Android system recovery <3e>
KTU84P.G900PVPU1ANK4
Additional files available/used:
Odin v3.07
CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
philz_touch_6.57.8-klte.tar
ERROR shown after reboot into recovery:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I tried following the directions from this thread:
ODIN Installation (detailed)
http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Everything worked as I thought it should, but the phone hangs at the recovery screen with above error.
I flash phil's recovery, and the phone will then boot up as normal, but SuperSU reports unable to inject SU binary
I dont care about tripping knox, just looking for a stock build with root (recovery and system) added.
I have rooted my Epic, S2, S3 & S4 with no issues, and as far as I can tell, everything runs as it should, the phone just hangs after the reboot at the recovery screen and never starts the rooting process in the recovery.
I figure I am either missing something simple, or got an update that root wont take with.
Anyone have any tips as to what I am missing and/or doing wrong?
Did you try flashing them from a powered off state, ie battery pull or power off then booting to download mode? That's an essential step in each odin flash
Sent from my SM-G900P using Tapatalk
Yes I did, but I guess I can always try again to be 100%, thanks. :good:
I actually have been flashing for years, that is why I am so puzzled, as everything went how it is supposed to, it is just the rooting process does not start once the phone reboots into recovery.
I watched the vid to see if I just dropped a step, it all matched, but where the phone boots into recovery and asks to root, just never seems to kick off.
You can also try download supersu zip 2.36 then odin custom recovery and flash supersu then boot up. That's what I did on nk4
Sent from my SM-G900P using Tapatalk
banccalif said:
Did you try flashing them from a powered off state
Click to expand...
Click to collapse
This helped... I got it fixed!!
The version of ODIN I had, had auto-reboot checked, and grayed out so you could not uncheck.
I ODIN'ed philz_touch_6.57.8-klte.tarphilz
when ODIN showed the block with finished, and before the phone restarted, I pulled the battery (had back open) & the cable and didnt let boot
I ODIN'ed CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
Pulled battery/cable (no booting!!), then booted directly into Recovery
Waited, it came up into custom recovery, I selected reroot, and BAM!!
Glad to have helped!
Sent from my SM-G900P using Tapatalk
DCRocks said:
This helped... I got it fixed!!
The version of ODIN I had, had auto-reboot checked, and grayed out so you could not uncheck.
I ODIN'ed philz_touch_6.57.8-klte.tarphilz
when ODIN showed the block with finished, and before the phone restarted, I pulled the battery (had back open) & the cable and didnt let boot
I ODIN'ed CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
Pulled battery/cable (no booting!!), then booted directly into Recovery
Waited, it came up into custom recovery, I selected reroot, and BAM!!
Click to expand...
Click to collapse
^This did it for me, holy crap!
I followed the root procedure to a 'T' like you and it would get stuck exactly where yours got stuck.
Seems to me that the stock recovery after rooting is what may be the culprit if this happens???
Either way now I can get everything going hopefully and remove the bloat, some of the nag notifications, etc.
Thanks
I tried these exact steps and I am still getting errors.
y0c0nsci3nc3 said:
I tried these exact steps and I am still getting errors.
Click to expand...
Click to collapse
If autoroot doesn't work for you go and download supersu 2.37 zip (Google it) Odin custom recovery pull battery, boot to recovery and flash supersu them you should be good to go.
banccalif said:
If autoroot doesn't work for you go and download supersu 2.37 zip (Google it) Odin custom recovery pull battery, boot to recovery and flash supersu them you should be good to go.
Click to expand...
Click to collapse
I ended up flashing the NK5 4.4.2 ROM in ODIN then used towelroot.
So I followed the same steps and nothing happened it just froze at the screen on boot.
I was using 4.4.4 stock rom. I fixed mine by installing philz or some other recovery software.
I went into the setting under advance in philz recovery and ran reroot.
It rebooted and I installed supersu and it worked perfect after that.
Hope someone else can get theres to work but I think the problem is with 4.4.4 that people and me didnt read that it doesnt work properly and you have to take extra steps.
DCRocks said:
Phone: Samsung Sprint S5 GM-900P
System: Windows 7
Build: KTU84P.G900PVPU1ANK4 (4.4.4)
Recovery Screen shows:
Android system recovery <3e>
KTU84P.G900PVPU1ANK4
Additional files available/used:
Odin v3.07
CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5
philz_touch_6.57.8-klte.tar
ERROR shown after reboot into recovery:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I tried following the directions from this thread:
ODIN Installation (detailed)
http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Everything worked as I thought it should, but the phone hangs at the recovery screen with above error.
I flash phil's recovery, and the phone will then boot up as normal, but SuperSU reports unable to inject SU binary
I dont care about tripping knox, just looking for a stock build with root (recovery and system) added.
I have rooted my Epic, S2, S3 & S4 with no issues, and as far as I can tell, everything runs as it should, the phone just hangs after the reboot at the recovery screen and never starts the rooting process in the recovery.
I figure I am either missing something simple, or got an update that root wont take with.
Anyone have any tips as to what I am missing and/or doing wrong?
Click to expand...
Click to collapse
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk
djxn40 said:
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I already helped him get back to stock so he's at least up and running.
timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Use the twrp 3.0.2.0 tar.tar found via @tdunham moar for mm threads note 5 recoveries link. I had same issue until using it.
This thread can be closed. Mrmike2182 helped me fix my issue in another thread.
Please help me!
MrMike2182 said:
I already helped him get back to stock so he's at least up and running.
Click to expand...
Click to collapse
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.
N_MBU said:
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.
Click to expand...
Click to collapse
Download one of these for your phone. .
http://www.sammobile.com/firmwares/database/SM-N920P/
Make sure you uncheck auto reboot in Odin and as soon as it's done and says success disconnect the phone and immediately press and hold the volume down button and the power button at the same time and when the screen comes back up you HAVE to select factory reset wipe if you don't you'll be stuck again just let the little android dude install the update and then the phone will reboot and you'll be ok.
Unzip the md5 you get from the sammobile site and flash only the .tar
This is what he told me that got my phone up and working again. Be warned it is the nuclear option. All of your data will be lost upon recovery good luck.
I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??
hotspace said:
I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??
Click to expand...
Click to collapse
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore
Thanks for the reply. Earlier today I visited my local Sprint store and gave them a crack at it. After about 30 minutes in the store, the tech suggested I leave with it them and they were going to completely wipe it and load the stock image.
After about an hour I went back to the store and he gave me the bad news that he was unable to get it out of the boot loop as well. They've ordered me a new device.
I really trust what you say about letting the phone battery die...but I fear that would fix it and I'd be out a new replacement device.
954wrecker said:
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore
Click to expand...
Click to collapse
Dude!! It worked. I put the phone in download mode and just let it sit until it died.
Booted it back up and it went straight into hands free activation. And no reboots.
Why does this work?