Trouble Rooting UCLB3 Gingerbread 2.3.6 - Samsung Infuse 4G

- I am running Android 2.3.6. I flashed the UCLB3 via Heimdall. I have GB bootloaders from Heimdall
- I have the bootloaders from Samsung Kies Mini
- I have USB Debugging on, but when I connect to the computer it says “USB Connected” rather than “USB debugging connected.”
- I try rooting through Odin using jscott's tar.md5 files in the PDA window, but the window does not turn yellow (indicating the phone is not recognized) and after the process the Gingerbread setup greets me, but I do not have Superuser.
- SuperOneClick just freezes up when I try to root.
- I've tried to use the modified 3e recovery via replacing the “recovery” file in /system/bin but there is no recovery file there and the paste “fails” due to lack of superuser access, I presume.
- Basically, I'm stuck and unable to root or flash anything that has SuperUser unless I can either get Odin to recognize my device or find another way that does.
When I first got the phone it was on froyo. I stupidly tried to flash an ICS ROM (Dark Knight) because I assumed it was on GB. I successfully rooted using SuperOneClick and flashed CWM recovery, but got the rainbow distortion from lack of GB bootloaders. I then proceeded to flash the UCLB3 via Heimdall and got my phone working again, but with ranbow distortion on boot and in recovery mode (rendering the CWM recovery useless as it would not respond with the rainbow distortion. I then re-flashed UCLB3 using Heimdall and checked the “GB bootloaders” box this time, which got rid of the distortion. But now I'm stuck and unable to root or flash anything because Odin won't recognize my device (it says it's there but the window does not turn yellow) and no other methods give me SuperUser. Kies Mini recognizes my device and says there are no updates, so it's not the cord. However, Kies regular does not. I think it's something to do with USB debugging not working properly and allowing Odin to recognize the phone so it can root it.

JoeyofBladez said:
- I am running Android 2.3.6. I flashed the UCLB3 via Heimdall. I have GB bootloaders from Heimdall
- I have the bootloaders from Samsung Kies Mini
- I have USB Debugging on, but when I connect to the computer it says “USB Connected” rather than “USB debugging connected.”
- I try rooting through Odin using jscott's tar.md5 files in the PDA window, but the window does not turn yellow (indicating the phone is not recognized) and after the process the Gingerbread setup greets me, but I do not have Superuser.
- SuperOneClick just freezes up when I try to root.
- I've tried to use the modified 3e recovery via replacing the “recovery” file in /system/bin but there is no recovery file there and the paste “fails” due to lack of superuser access, I presume.
- Basically, I'm stuck and unable to root or flash anything that has SuperUser unless I can either get Odin to recognize my device or find another way that does.
When I first got the phone it was on froyo. I stupidly tried to flash an ICS ROM (Dark Knight) because I assumed it was on GB. I successfully rooted using SuperOneClick and flashed CWM recovery, but got the rainbow distortion from lack of GB bootloaders. I then proceeded to flash the UCLB3 via Heimdall and got my phone working again, but with ranbow distortion on boot and in recovery mode (rendering the CWM recovery useless as it would not respond with the rainbow distortion. I then re-flashed UCLB3 using Heimdall and checked the “GB bootloaders” box this time, which got rid of the distortion. But now I'm stuck and unable to root or flash anything because Odin won't recognize my device (it says it's there but the window does not turn yellow) and no other methods give me SuperUser. Kies Mini recognizes my device and says there are no updates, so it's not the cord. However, Kies regular does not. I think it's something to do with USB debugging not working properly and allowing Odin to recognize the phone so it can root it.
Click to expand...
Click to collapse
download mode:
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
profit

Thanks for quick reply and it worked!

I flashed a rom (Dark Knight) but every time I reboot, it goes straight to recovery. Do I need to change some settings or what? No matter how many times I flash it, the phone boots straight to CWM Recovery. What did I do wrong? What should I do now? I think I'm just stuck in a boot loop but I don't want to restore to stock and try again because I'll probably just keep making the same mistake. Instead I'd rather wait for someone to tell me why that flash didn't work and what I should do to make it work. Ive done work on a few other (newer) phones and I've never had this happen.

JoeyofBladez said:
I flashed a rom (Dark Knight) but every time I reboot, it goes straight to recovery. Do I need to change some settings or what? No matter how many times I flash it, the phone boots straight to CWM Recovery. What did I do wrong? What should I do now? I think I'm just stuck in a boot loop but I don't want to restore to stock and try again because I'll probably just keep making the same mistake. Instead I'd rather wait for someone to tell me why that flash didn't work and what I should do to make it work. Ive done work on a few other (newer) phones and I've never had this happen.
Click to expand...
Click to collapse
Read the OPs.
You need to flash CM9 twice, with a wipe in between.
If you accidentally did a reboot to recovery and suck in a loop, use the GB kernel flash in heimdall, wipe. Download mode, flash the Jt kernel and try again

qkster said:
Read the OPs.
You need to flash CM9 twice, with a wipe in between.
If you accidentally did a reboot to recovery and suck in a loop, use the GB kernel flash in heimdall, wipe. Download mode, flash the Jt kernel and try again
Click to expand...
Click to collapse
I read the instructions and i didn't see it say to wipe in between flashes, just to reboot recovery. I do follow directions you know but can't follow directions that aren't written in the spot I'm reading them and assuming them to be right. But thank you for telling me what I should havedone. So once I have jt kernel, I just flash, wipe, reboot recovery,and flash again?

I did the UCLB3 Repartition One Click and then wiped everything. Then I flashed JT's kernel and flashed the ROM. Before I could do anything else, it started on its own and everything is fine now. THanks for your help, I'm still a little confused but you pointed me in the right direction. Thanks will be given.

JoeyofBladez said:
I did the UCLB3 Repartition One Click and then wiped everything. Then I flashed JT's kernel and flashed the ROM. Before I could do anything else, it started on its own and everything is fine now. THanks for your help, I'm still a little confused but you pointed me in the right direction. Thanks will be given.
Click to expand...
Click to collapse
Glad it worked for you.
While in cwm recovery, re-boot into recovery means powering off and then turn back on with 3 finger salute.
Selecting "Reboot Recovery" may not work and may send a user into a loop recovery image.
I've found from experience that flashing a different kernel with different cwm version may erase that loop and let you start over.
As you have discovered what I've been saying along and if you read the ops on the heimdall thread, you will understand that rooting the official firmware is pointless if you are planning on flashing a custom firmware.
Root it only to run it with root permissions.
Flashing in download mode does not require root. Just flash the kernel with cwm recovery.
have fun

Related

my sk4g wont boot or enter recovery mode help!!!

ok so i rooted my phone using the superoneclick method and and installed CWM with rom manager and everything was fine but then when i tried flashing gingerclone v2 by ayoteddy the phone just got stock on the part that says t - mobile sidekick 4g ect. and i cant even enter recovery mode manually! what can i do? help please did i bricked my phone =/??
More than likely you've softbricked your phone. Follow the steps here to ODIN your phone back to stock. Once you get your phone up again, root again.
The CWM from Rom Manager doesn't seem to work on the SK. You're gonna need to do some manual file moving to make it work. Follow the steps here: http://forum.xda-developers.com/showthread.php?t=1124453
Once you've moved these files, you need to manually get into recovery mode (Power+volume). Click reinstall packages and you should be in CWM. From here, just follow the flashing instructions and you should be golden. Make sure you check your mounts...
If Odin doesn't work Try using Heimdall which is a lot simpler no extra files to download just make sure you have java installed an heimdall will ask you about installing drivers, tried this out on my phone for the hell of it an it worked fine. http://forum.xda-developers.com/showthread.php?t=1350060

ODIN will recognize my phone, but only when it ISN'T in download mode.

First, I'm on SGS4G on T-mobile.
For a while, I was running the Bionix Frost ROM (here), but it started giving me random reboots and crashes and I wanted to get Gingerbread on there anyway, so I used CWM to flash Valhalla Black Edition (here), which works fine, except that I get rainbow screens during boot (this isn't the problem, they only last for a bit), and when I boot into recovery it won't display properly and all I get is rainbow screen. Because of this, I decided to try ODIN-flashing the Official GB 2.3.6 (here).
I downloaded ODIN 1.85, and I have the SGS USB drivers installed, but for some reason ODIN will only detect my phone if it isn't in download mode. When I plug it in regularly, ODIN displays "<ID:0/003> Added!!". But when the phone is in download mode (even though it's displaying the triangle and everything), ODIN does nothing.
Also, pressing both volume buttons and plugging in the USB cable does nothing. I have to boot into download mode from the options screen you get by pressing and holding the power button in Valhalla Black.
So booting into recovery gives me a rainbow screen, and ODIN won't detect my phone in download mode. Any suggestions on how to get a different ROM to flash?
New Rom
Will your phone go into recovery mode, if yes then just place NEW rom .zip file on the root of your SD card and flash through recovery.
Try flashing another froyo rom, download quickboot and then reboot to download mode that way, then try flashing the official gb rom with Odin.
anoymonos said:
Will your phone go into recovery mode, if yes then just place NEW rom .zip file on the root of your SD card and flash through recovery.
Click to expand...
Click to collapse
Like I mentioned, when I boot into recovery all I get is a rainbow screen, which is why I'm trying to flash through ODIN.
FBis251 said:
Try flashing another froyo rom, download quickboot and then reboot to download mode that way, then try flashing the official gb rom with Odin.
Click to expand...
Click to collapse
I downloaded quickboot, but it doesn't give me an option for booting to download mode, just to recovery. The options it gives me are "Reboot", "Recovery" (which still gives me rainbow screen), "Bootloader", and "Power Off".
edit: I've also tried to use ODIN 1.7 flash back to the Froyo Stock+Root here, but ODIN 1.7 is giving me the same issue as ODIN 1.85 (won't detect in download mode).
I am a noob but it seems you went from Bionix Frost rom - looks to be a froyo rom - straight to Valhalla Black Edition - a GB rom. The rainbow screen sound like it may be a bootloader issue. You need the GB bootloaders which it seems you skipped that step.
Try using Heimdall One-Click Collection from bhundven which will give you UVKJ6 with all the bootloaders then try flashing Valhalla Black Edition again.
Click here for Heimdall One-Click Collection
Here is a very detailed tutorial using Heimdall courtesy of Bassmanjames in case you are unfamiliar with it - Click Here
Try the bootloader option in quickboot, if not find a guide on how to get set up using adb. Open adb on your computer and type in
adb reboot download.
lumin30 said:
I am a noob but it seems you went from Bionix Frost rom - looks to be a froyo rom - straight to Valhalla Black Edition - a GB rom. The rainbow screen sound like it may be a bootloader issue. You need the GB bootloaders which it seems you skipped that step.
Try using Heimdall One-Click Collection from bhundven which will give you UVKJ6 with all the bootloaders then try flashing Valhalla Black Edition again.
Click here for Heimdall One-Click Collection
Here is a very detailed tutorial using Heimdall courtesy of Bassmanjames in case you are unfamiliar with it - Click Here
Click to expand...
Click to collapse
I had some similar issues with getting back to stock. What did it for me was to use a Jig to get into download mode, Reinstall the Samsung USB drivers, and then go back to T595VUKF1 package that uses the Pit, PDA, CSC and Phone files. Got a very clean stock image, Used Odin to install a CWM then installed Valhalla 1.5 and then the New Valhalla Black, Which BTW is one of the coolest ROMs out there.
One thing to try is installing Heimdall and the related drivers, which are different then the Samsung drivers, then reinstall the Samsung drivers. In my case that seemed to clean things up.
With all due respect to
some of the answers you guys posted. It seems as if he can get into dl mode fine. its that his PC won't see the phone in which case make sure debugging mode is on for the USB wootimus
Sent from my SGH-T959V using XDA APP
goddi2010 said:
With all due respect to
some of the answers you guys posted. It seems as if he can get into dl mode fine. its that his PC won't see the phone in which case make sure debugging mode is on for the USB wootimus
Sent from my SGH-T959V using XDA APP
Click to expand...
Click to collapse
His real issue was the rainbow screen.
And difficulties with ODIN.
Which is why Heimdall was $uggested as a way to get gb bootloaders. He went straight from Froyo to flashing Valhalla Black.
I agree but also if debugging was off Odin wouldn't see the phone
Sent from my SGH-T959V using XDA App
I know it's been about 6 months (I ended up buying a different phone from a friend so it became a moot point), but I recently had to flash this back to stock in order to sell it to a friend of mine and the above method using Heimdall worked like a charm. Thanks!

[Q] Need help recovering my S3 -- TWRP ADB Sideload not working

I pulled a boneheaded move and ended up formatting my phone from within the TWRP menu. Now the stock operating system is gone.
I wanted to put on one of the Gummy Nightly builds, but I'm new to TWRP and selected the wrong options while wiping.
So now I have the Gummy ROM on my PC, the phone is connected to my PC and in TWRP (in the advanced adb sideload feature), but adb will not recognize my phone.
When I check device manager, SAMSUNG_Android_SCH-I535 is there, but with a yellow "cauton" symbol. When I look at properties, it tells me that "The drivers for this device are not installed (Code 28).
I went out to the Samsung page and got the exe to unpack drivers on my machine... I've tried "update driver" and pointing to the root of the directory containing the Samsung drivers, but my PC claims none of them are applicable.
So what I'm looking for here is:
(1) How do I get this ROM on my phone so that I can install the zip and have a working OS again?
(2) Assuming that using the ADB Sideload feature of TWRP is my best option, how do I get the device drivers for my galaxy s3 installed to my windows 8 PC and get adb to detect it?
Thanks in advance.
Ok, so it seems to have gotten worse.
I cannot get my windows installation to recognize the phone without it being able to boot an android OS, it seems.
I had it in TWRP 2.6.0.0, but as I was trying to reboot to see if I could get into download mode (my thought being to change out TWRP for Clockwork; I seem to remember Clockwork Recovery having a "mount as USB" option which TWRP seems to lack), it tried to root the file system.
After that, the screen went black and nothing happened... the phone was unresponsive. I would remove the battery and replace it to have it vibrate once and then not respond to any key presses.
I removed the battery, SD card, and SIM card, replacing only the battery and got it to turn on and show a Samsung Galaxy SIII logo... but it's just sitting there... I'm assuming it's frozen because there's no OS to boot on the internal storage.
Please help me recover my phone!
Ok, so I've found I can still get into download mode, but not into recovery.
Recovery seems to lead to a black screen with nothing on it.
Trying to boot normally leads to the statis Samsung Galaxy SIII logo.
Can I fix my phone from the download menu?
Please help me.
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
ThePagel said:
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
Click to expand...
Click to collapse
Thanks for the reply!
Sorry, I'm a little out of date on the flashing and stuff -- I was just over in the thread where the poster thought he half softbricked his phone and was asking about 4.1.2 vs. 4.3
I see this at the top of my screen sitting here in download mode:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
It seems my bootloader got relocked somehow -- is this why my phone just goes to black screen when I attempt to boot into recovery -- even if I have TWRP or CWR installed? Odin claims I just pushed philz custom CWR to my PDA section, but it still won't go into recovery.
What are my options here?
You are pre 4.3 I'll help you more in the morning if no one else does first.
ThePagel said:
You are pre 4.3 I'll help you more in the morning if no one else does first.
Click to expand...
Click to collapse
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
corrosivefrost said:
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
Click to expand...
Click to collapse
Once you in download mode, can your Odin see your phone?
buhohitr said:
Once you in download mode, can your Odin see your phone?
Click to expand...
Click to collapse
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
corrosivefrost said:
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
Click to expand...
Click to collapse
What stock version do you have on your phone right now?
buhohitr said:
What stock version do you have on your phone right now?
Click to expand...
Click to collapse
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
I'm really not sure what kind of state anything is in at this point -- other than Odin seemingly working and being able to get into download mode.
Again, short version of what happened:
(1) Accidentally did a full wipe (factory reset?) in TWRP -- this wiped the ROM I was going to install with TWRP off the phone.
(2) While trying to ADB sideload from TWRP and telling TWRP to reboot, TWRP tried to install supersu.
(3) After (2), I was unable to get back into recovery mode. I got into Odin and tried to flash philz customer clockwork recovery and it seemed successful. Reboot and attempt to enter recovery still fails. Samsung logo with recovery mode text appears, but then the screen goes black.
(4) Normal boot leaves the screen stuck on the Samsung Galaxy SIII logo indefinitely.
corrosivefrost said:
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
Click to expand...
Click to collapse
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
buhohitr said:
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
Click to expand...
Click to collapse
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
​
corrosivefrost said:
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
Click to expand...
Click to collapse
Yes, it's pre rooted stock image and yes flash with PDA.
buhohitr said:
​
Yes, it's pre rooted stock image and yes flash with PDA.
Click to expand...
Click to collapse
Standard auto-reboot and f_reset_time options? nothing else necessary?
corrosivefrost said:
Standard auto-reboot and f_reset_time options? nothing else necessary?
Click to expand...
Click to collapse
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
buhohitr said:
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
Click to expand...
Click to collapse
Alright, I'll give it a shot and report back.
Thank you!
corrosivefrost said:
Alright, I'll give it a shot and report back.
Thank you!
Click to expand...
Click to collapse
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
It did work! Hooray!
buhohitr said:
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Didn't need to go that far -- but now that I'm back up and running, signed into google play, and downloaded goo manager, can you point me in the right direction for getting it to install cwm recovery?
Thanks guys!

[SOLVED] Unable to root - Recovery is NOT SEANDROID ENFORCING

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

Help softbricked or hardbricked device?

Help softbricked device
well i was running more rom on the device when i droped it then i got the screen and digi replaced
and when the tech tuned it on for the first time after repair we got a udc start screen that says unknown error at the top
i can get to download mode though. but even after trying to restore the bootloader or flash a new modem i cant get to any recovery.
right now this is what it says in download mode.
odin mode
product name : SM-G900P
current binary: custom
system status : custom
knox warranty void 0x1 (4)
i can go to download mode or try and let it boot up to the samsung boot but it says recovery booting in blue and loops there on reboot.
i forget the name of the modem i was on in more rom. i think it was the one be4 ota6
but i want to update to latest version of modem and rom not sure where to start.
i cant seem to get back to stock or custom recovery at all. or even boot up to a rom now. and i honestly have no idea why? =( can someone help?
jackrabbit72380 said:
Help softbricked device
well i was running more rom on the device when i droped it then i got the screen and digi replaced
and when the tech tuned it on for the first time after repair we got a udc start screen that says unknown error at the top
i can get to download mode though. but even after trying to restore the bootloader or flash a new modem i cant get to any recovery.
right now this is what it says in download mode.
odin mode
product name : SM-G900P
current binary: custom
system status : custom
knox warranty void 0x1 (4)
i can go to download mode or try and let it boot up to the samsung boot but it says recovery booting in blue and loops there on reboot.
i forget the name of the modem i was on in more rom. i think it was the one be4 ota6
but i want to update to latest version of modem and rom not sure where to start.
i cant seem to get back to stock or custom recovery at all. or even boot up to a rom now. and i honestly have no idea why? =( can someone help?
Click to expand...
Click to collapse
Follow the instructions from this post. Since you are soft bricked at the moment, you'll need to start at step 4. If you have an extSD in your phone, you might want to pull it until after you're up and running because the "Android" folder from Kitkat needs to be deleted and rebuilt for Lollipop.
That's what I tryed first but it didn't work,
First step.... flash SM-G900P_OA6_FullRestore.
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
sense that didn't work i tryed... SM-G900P_NI3-Full_Restore_Unrooted (Compressed Archive)
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
then i tryed SM-G900P_OA6_FullRestore. again but still no luck im out of ideas
I cant get to any recovery.
please help.
jackrabbit72380 said:
That's what I tryed first but it didn't work,
First step.... flash SM-G900P_OA6_FullRestore.
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
sense that didn't work i tryed... SM-G900P_NI3-Full_Restore_Unrooted (Compressed Archive)
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
then i tryed SM-G900P_OA6_FullRestore. again but still no luck im out of ideas
I cant get to any recovery.
please help.
Click to expand...
Click to collapse
Are you using the wrong terminology? You have to use Odin and a PC to install the .tar. Also, the first boot into Lollipop can take about 20 minutes. You have to be patient. I see you posting in different threads and you seem to be digging deeper into a hole.
Are you using Odin and starting by downloading (to PC) the file in step #4? Then follow the remaining steps "exactly". Re-read those instructions and if you not already downloaded the needed files, do that first.
Ramer said:
Are you using the wrong terminology? You have to use Odin and a PC to install the .tar. Also, the first boot into Lollipop can take about 20 minutes. You have to be patient. I see you posting in different threads and you seem to be digging deeper into a hole.
Are you using Odin and starting by downloading (to PC) the file in step #4? Then follow the remaining steps "exactly". Re-read those instructions and if you not already downloaded the needed files, do that first.
Click to expand...
Click to collapse
Yes I downloaded the files to the pc.
Im using odin3.07
in pda I add the file Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel),
put phone in download mode.
flash file!
ODIN SAYS PASS
next phone reboots to samsung galaxy black screen with with blue letters at the top saying
RECOVERY BOOTING......
then boot loops there.
I CANT GET TO STEP 5
I am not able to boot to the rom or recovery
jackrabbit72380 said:
Yes I downloaded the files to the pc.
Im using odin3.07
in pda I add the file Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel),
put phone in download mode.
flash file!
ODIN SAYS PASS
next phone reboots to samsung galaxy black screen with with blue letters at the top saying
RECOVERY BOOTING......
then boot loops there.
I CANT GET TO STEP 5
I am not able to boot to the rom or recovery
Click to expand...
Click to collapse
Try this: Do a battery pull, then put the phone in Download mode, hook up to PC and then open Odin and then Odin custom recovery, either twrp or Philz. Uncheck auto reboot in odin and once it passes, pull the battery, unplug and boot into recovery. Also, you might update Odin, there's a link to Odin 3.10.0 in my post. Let's see if we can get that far and go from there.
ramer said:
try this: Do a battery pull, then put the phone in download mode, hook up to pc and then open odin and odin custom recovery, either twrp or philz. Uncheck auto reboot in odin and once it passes, pull the battery, unplug and boot into recovery. Also, you might update odin, there's a link to odin 3.10.0 in my post. Let's see if we can get that far and go from there.
Click to expand...
Click to collapse
ok used odin 10
tryied everything you said exactly phone reboots on samsung galaxy s5 boot logo everytime. Whether i try booting to recovery or the rom.
jackrabbit72380 said:
ok used odin 10
tryied everything you said exactly phone reboots on samsung galaxy s5 boot logo everytime. Whether i try booting to recovery or the rom.
Click to expand...
Click to collapse
Which recovery tar did you Odin? You pulled the battery after Odin said PASS, then unplugged the phone, put battery back in and immediately tried to get into recovery? If so, I'm stumped.
Ramer said:
Which recovery tar did you Odin? You pulled the battery after Odin said PASS, then unplugged the phone, put battery back in and immediately tried to get into recovery? If so, I'm stumped.
Click to expand...
Click to collapse
Yes I tryed
I pulled the battery after Odin said PASS
Yes I tryed
kt_twrp_recovery_boa6_firmware.tar
and
openrecovery-twrp-2.8.4.0-klte
and
philz_touch_6.57.8-klte
NOTHING!
when ever i try and boot the rom the phone vibrates 2 times and resets.
when ever i try to boot to recovery
i get
recovery booting....
recovery is not seandroid enforcing
set warranty bit : recovery
then phone reboots.
then it trys to boot the rom.
and vibrates 2 times and resets.
Im not new to using odin or flashing roms or recoverys i sort of know what im doing. not to sound cocky.
Im Stumped to!
jackrabbit72380 said:
Yes I tryed
kt_twrp_recovery_boa6_firmware.tar
and
openrecovery-twrp-2.8.4.0-klte
and
philz_touch_6.57.8-klte
NOTHING!
Im not new to using odin or flashing roms or recoverys i sort of know what im doing. not to sound cocky.
Im Stumped to!
Click to expand...
Click to collapse
I saw your post count, I knew you knew what you're doing, just wanted to double check everything. Sorry, I'm out of ideas. I did ask @tdunham to take a look at this thread, if he has some other ideas, but he's offline right now. Hopefully he'll check in later.
What about flashing back to an older version of android? Full tar flash.
---------- Post added at 12:38 AM ---------- Previous post was at 12:36 AM ----------
Like ne5, and nothing else, just see if you can get stock to boot, no messing around trying to flash recovery.
This is RWillco12's NE5 stock.. Have the phone in download mode and run the .exe
Thanks TD.
Ramer said:
This is RWillco12's NE5 stock.. Have the phone in download mode and run the .exe
Thanks TD.
Click to expand...
Click to collapse
I tryied ni3 already
but as far as i know you cant downgrade the bootloader.
if i could flash just the bootloader for ota6 maybe that would help.
i will try downloading ne5 now but my last rom was running a nkd modem.
im going to try and flash G900P_NKD_FullRestore.tar in odin if that dont work ill try ne5
and will report back shortly.
well nkd full restore boots up to
unknowen error!
wait..
done!
udc start.
power reset or
unknown
upload mode.
this is the way i got it back from retech after they replaced my bezel and digitlizer and screen
i never had an issue with anything software wize before that.
Have you tried flashing the phone without any sim cards inserted including the sprint card? You are flashing from a powered off state right? You know it wont work unless phone is powered off before going into download mode.
As a last resort attached is the pit file for the 16gb G900P. Unzip and put it into the pit section of odin and flash the stock firmware again. It will repartition the entire phone when it flashes the stock image.
tdunham said:
Have you tried flashing the phone without any sim cards inserted including the sprint card? You are flashing from a powered off state right? You know it wont work unless phone is powered off before going into download mode.
As a last resort attached is the pit file for the 16gb G900P. Unzip and put it into the pit section of odin and flash the stock firmware again. It will repartition the entire phone when it flashes the stock image.
Click to expand...
Click to collapse
Yes I was using the pit file and yes I know to go to download mode from power off state. and no sim card is in the phone.
flashing ne5 stock with fingers crossed.
brb
nope
is there any bootloaders only i can flash?
well tryed everything all it does is vibrate 2 times. same as be4 im dead in the water. i don't know what's wrong or what to do.
I have tryed everything i can think of.
I can boot to download mode and flash anything i want but nothing works.
no recovery. no rom.

Categories

Resources