So i was trying to flash a the Negalite WondeROM and after flashing it got stuck in a boot loop. I had selected the KT kernel. I used ODIN to unroot my phone but after i rerooted it using ODIN again it passed bit when i tried to load recovery it got stuck in the boot loop again. Any suggestions on how to get rid of it. I am getting out of the boot loop again by using ODIN to unroot again but i would like to flash a rom. So some help would be great to figure out how to fix this!
Thanks
Flash md9 through Odin then reroot
Sent from my SPH-L720 using XDA Premium 4 mobile app
---------- Post added at 01:12 PM ---------- Previous post was at 01:10 PM ----------
Also if you can root use goo manager first to install twrp first
Sent from my SPH-L720 using XDA Premium 4 mobile app
I have got it rooted. But GooManager is having trouble downloading/installing the recovery. It goes to the download page then just sits there then i get an MD5 checksum error after that when i try to download/install the recovery it says it cannot find one for my phone
Just use Odin to install TWRP recovery. Use 2.5.0.2. Version 2.6 works on the S4, but is not quirk free.
So after many of headaches. I fixed it all. I used ODIN to unroot, then root and install the recovery. Turns out that the KT Kernel on the Negalite rom was what was breaking it i tried a different kernel and it worked so now im happy
Related
Alright I have searched all day and can not seem to find a resolution to my problem. It is my fault I shouldn't fix something that isn't broke but it has resulted in issues and I would appreciate it if someone could help me.
I had twrp 2.5.0.2 installed running GE 4.2.2 ROM with MF3 radios installed and GE kernel v11. I saw twrp had a update to 2.6.0.0 and I decided to install it via goo manager it booted up in recovery with the "the software is unauthorized by att" screen and I can do volume down + power after that to reboot phone and not have issues as far as getting my phone booted and working on all the above. But the problem I am having now I have lost custom recovery. I have tried goo manger again as well as some on click root/recovery methods from these forums and all result in the same back to the unauthorized screen mentioned above its like it won't boot into a custom recovery. Any advice is greatly appreciated.
Sent from my Nexus 7 using xda app-developers app
Maybe try ROM manager and install cwm .it will pop up in ROM manager as the T-Mobile s4 but that's what I used to install the first recovery image,then I used that recovery to flash the auto Loki recovery.I have used the same plain auto Loki recovery since then.
Sent from my SAMSUNG-SGH-I337 using xda premium
Just tried that as well. Still not working. When I takes me to that unauthorized page top left it says "secure fail: kernel". But when I reboot the phone normal it comes up just fine....so that tells me its getting past with Loki to boot up my ROM and kernel but for some reason it will not take a custom recovery anymore when I have had one installed previously.
Sent from my SGH-I337 using xda app-developers app
If memory serves me right the Google Edition ROM will make TWRP / GooMananger think you have a 9505(G) and thus it will install that version. So you installed a non-loki'd recovery.
Use Odin, go back to AMDL firmware. (Take SIM out before doing so so it wont download the AMF3 update). Redo Root + Recovery. BEFORE you flash another rom, install GooManager and then update from there. You will be running stock firmware so it will identify the model correctly. Then flash your custom ROM.
Forgive me for being noob when it comes to Odin. But does this OTA the software or will I need to get Odin on my desktop?
Sent from my SGH-I337 using xda app-developers app
I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz
nomad836 said:
I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz
Click to expand...
Click to collapse
What firmware are you on? Please if you know how to flash ROMs you should know where to find it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Sent from my SGH-M919 using xda app-developers app
If you can boot into OS, download Goo Manager from Market and install TWRP 2.5.0.2 recovery
If you get it working--do a lot of reading--many variants and our bootloader is locked. Get to know loki-doki too, if you don't--
I installed twrp and it still gives me the att lock when I go into recovery. Should I try to install Loki with Odin?
Sent from my SGH-M919 using xda app-developers app
loki doesn't install thru odin--it installs thru recovery as a zip
if you still can't get into revovery you may need to odin back to stock--i never used odin, haven't needed too and on an iMac
there are some threads on using it and someone may help with that
loki bypasses samsung's signature verification on recovery and kernels and lets you flash a kernel that hasn't already been loki'd by dev--
Are you getting a lock on the Samsung screen? Or are you getting the warning saying that software is detected that is not authorized by AT&T.
If you are getting the first. Let it boot.
If you are getting the second, loki-doki patch. Google it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Or u can in fact use ROM manager just to flash a recovery "CWM".after flashing cwm get rid of ROM manager and use cwm to flash any of the recoveries. I use philz touch recovery .Google is badass though
Sent from my SAMSUNG-SGH-I337 using xda premium
ODIN emergency restore fixes it.
Sent from my Nexus 7
here ya go
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom
vedantgp said:
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom
Click to expand...
Click to collapse
This is the correct procedure...
Ok so i have been working on this for hours now. I have never rooted a my phone before and i decided to try. I rooted it no problem and set up a nandroid recovery with goomanager. Then i tried to enable hotspot using QBKing77's tutorial on youtube by adding custom files in the system folder. when i restarted i was stuck at the sprint yellow screen. I started recovery mode and tried to recover my previous back up. It did not work and i think it made things worse. Now my custom recovery is gone and i tried to install the original sprint rom in adin and it keeps failing at when i gets to nand write. I have no clue whats wrong. Is there any way to erase the entire phone are reinstall everything similar to a wipe and load on a computer?
We need a little more info, what software version were you on? MF9 MJA, MK2??? This is important because once you are on MJA or MK2 you cannot go back to the older versions because of the knox bootloader. The odin error you are reporting usually happens when you are trying to install an older than MJA version on an MJA or newer phone. Make sure you download either the MJA full tar file or the MK2 full tar file and try again. It's very important that you know what version you are on before you start installing mods, this is why your phone failed to boot after installing the hotspot mod.
TheHoboSlayer said:
Ok so i have been working on this for hours now. I have never rooted a my phone before and i decided to try. I rooted it no problem and set up a nandroid recovery with goomanager. Then i tried to enable hotspot using QBKing77's tutorial on youtube by adding custom files in the system folder. when i restarted i was stuck at the sprint yellow screen. I started recovery mode and tried to recover my previous back up. It did not work and i think it made things worse. Now my custom recovery is gone and i tried to install the original sprint rom in adin and it keeps failing at when i gets to nand write. I have no clue whats wrong. Is there any way to erase the entire phone are reinstall everything similar to a wipe and load on a computer?
Click to expand...
Click to collapse
i have the same issue, please if anyone can offer some guidance we'd both really appreciate it!
Thank you that was the issue. I downloaded the android 4.3 tar from samsung-updates.com and flashed the PIT files and it started back up.
TheHoboSlayer said:
Thank you that was the issue. I downloaded the android 4.3 tar from samsung-updates.com and flashed the PIT files and it started back up.
Click to expand...
Click to collapse
how do you flash the PIT files and where did you get them?
vcao333 said:
how do you flash the PIT files and where did you get them?
Click to expand...
Click to collapse
You may not need the pit file I would try it with out it first. This is where i got got my pit sxtpdevelopers . com /showthread.php?t=235
This is for the sprint galaxy s4 though. Don't use if you have a different carrier. Put the pit file in the in Odin in the pit tab and the Android 4.3 tar file in the pda tab. It should work then. Again I would try without the pit file first.
bootloop
I've also tried flashing for the first time, followed the ROM developers directions, and now I have a bootloop with the message at the top of the splash screen "Set binary bit: kernel".
Any guidance?
---------- Post added at 10:39 AM ---------- Previous post was at 10:34 AM ----------
The ROM I was installing is Stock(ish), but I can't post in that thread since it's a developer thread, and I'm a newbie on this site, so that's why I'm asking here.
same here.. please help
pcknox said:
I've also tried flashing for the first time, followed the ROM developers directions, and now I have a bootloop with the message at the top of the splash screen "Set binary bit: kernel".
Any guidance?
---------- Post added at 10:39 AM ---------- Previous post was at 10:34 AM ----------
The ROM I was installing is Stock(ish), but I can't post in that thread since it's a developer thread, and I'm a newbie on this site, so that's why I'm asking here.
Click to expand...
Click to collapse
i'm also getting the same thing when I turn my phone on and it keeps on rebooting please any1 out there help we would really appreciate it thanks in advance..
I've been looking so I could link you but I'm outta time! If you can still get to download mode you need a tar file of either mk2 or mja stock and then use Odin 3.07 and push it back in! Rooted or unrooted shouldn't matter but from what all I've seen and read this is about the only option you have!! Now this being if you were on mja or mk2 before you started!
Sent from my SCH-R970 using Tapatalk
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
Try this thread for the tar file
http://forum.xda-developers.com/showthread.php?t=2509605
Sent from my SCH-R970 using Tapatalk
bignick1215 said:
I've been looking so I could link you but I'm outta time! If you can still get to download mode you need a tar file of either mk2 or mja stock and then use Odin 3.07 and push it back in! Rooted or unrooted shouldn't matter but from what all I've seen and read this is about the only option you have!! Now this being if you were on mja or mk2 before you started!
Sent from my SCH-R970 using Tapatalk
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
Try this thread for the tar file
http://forum.xda-developers.com/showthread.php?t=2509605
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
thanks for your advice ill look into it, I believe I have done all your steps but I'll try again and look into the link you posted up thanks one again for your help..
bignick1215 said:
I've been looking so I could link you but I'm outta time! If you can still get to download mode you need a tar file of either mk2 or mja stock and then use Odin 3.07 and push it back in! Rooted or unrooted shouldn't matter but from what all I've seen and read this is about the only option you have!! Now this being if you were on mja or mk2 before you started!
Sent from my SCH-R970 using Tapatalk
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
Try this thread for the tar file
http://forum.xda-developers.com/showthread.php?t=2509605
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
i fallowed the steps from the link and i was able to get out of reboot loop now im stuck with the Samsung logo and a blue light at the top of my phone any ideas thanks...
The blue light probably says rebooting recovery! If so this worked for me. Pull battery then boot into download mode press up to continue wait for a minute then pull battery and try to reboot!
Sent from my SCH-R970 using Tapatalk
bignick1215 said:
The blue light probably says rebooting recovery! If so this worked for me. Pull battery then boot into download mode press up to continue wait for a minute then pull battery and try to reboot!
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
i was able to get it working again, i downloaded the tar file from the link you put up and used odin to flash theni got stuck on the Samsung logo so i took the battery out and put it on recovery mode and did a factory reset and rebooted and it did the trick thanks alot. if this helps you or any1 else out there remember to give thumbs up.
So, I installed TWRP 2.7 on my GS4 via mobile terminal. My device had the radio updated to MLD from @rockrat(which i thought was not effecting my recovery options how he extracted it) --upon updating to TWRP 2.7 i rebooted into recovery and got the "Software Not Supported by AT&T" locked bootloader message.
I have tried flashing .tar recoveries in Odin-- it fails auth
I have tried using mobile terminal to go back to older recoveries and all i end up with is the same not supported by AT&T.
Have i now fu#ked myself out of using a recovery besides Safestrap? I have a custom kernel on board, I have 4.4.2 and root is fine. I just _think_ from what I've read that I'm now trapped on a Galaxy with no recovery boat.
Crowd-- please say It ain't so
I think you forgot to flash loki again. Unless your recovery auto-loki, I believe you have to flash loki every time you flash something in recovery.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
If your firmware is MDB or MDL check out the post by dees_troy "TWRP 2.6.0 Recovery" in the development section and read the last couple of pages. This may help you. Good luck.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Thanks guys, I figured it out. TWRP team a) doesn't have a gs4 b) forgot to f'n Loki the recovery. c)I had never in all my flashing known the recovery sector needed Loki, also I was stumped because In using terminal emulator I thought if was reverting to a previous build but for some reason it wasn't. d)Flashify came in and saved the day.
Sent from my GT-I9505G using Tapatalk
Hey all,
Tried to update the twrp that was on a device that I just got.
Update went fine, reboot into new recovery.. Unauthorized software message..
Does this mean Odin back to MDL stock, re-root and such?
Thanks in advance.
Sent from my GT-I9505G using Tapatalk
You need to flash Loki. . . if you flash a stock (rooted) ROM, you will boot to ROM, then use triangle away app to get rid of the padlock on boot screen. Just remember to flash the Loki zip if you're flashing a ROM that isn't specifically for the jflteatt
---------- Post added at 11:37 AM ---------- Previous post was at 11:00 AM ----------
If you can't get it to bottom after flashing Loki, you'll need to Odin back to stock, reroot and whatnot.
Mystique said:
Hey all,
Tried to update the twrp that was on a device that I just got.
Update went fine, reboot into new recovery.. Unauthorized software message..
Does this mean Odin back to MDL stock, re-root and such?
Thanks in advance.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
The guy above is right. It's loki that you have to flash in recovery. But that issue is because of the the kernel. Loki is a att kernel patch.
So anytime you flash a new rom or kernel by itself just flash the loki doki zip and reboot and all will be well
~Sent From My Insane S4~
So,
I found out that trying to flash philz via Odin would fail, almost immediately; but then the rom would boot..
I was able to loki_run recovery recovery.img from my still working rom.. Then get into the flashed recovery..
Cycle, rinse, repeat a dozen times or so while I was figuring it out.. Before I figured out what was getting me back in..
Sent from my GT-I9505G using Tapatalk