Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
@KoolCharisma, first off, you're not in bad shape at all.
Let's start your weekend with this in your rear view mirror. What rom was on your phone prior to doing any of this, Jellybean MJ4, or KitKat NAB?
Knowing the above will dictate how you get to where ya want to be...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Alright!
micmars said:
@KoolCharisma, first off, you're not in bad shape at all.
Let's start your weekend with this in your rear view mirror. What rom was on your phone prior to doing any of this, Jellybean MJ4, or KitKat NAB?
Knowing the above will dictate how you get to where ya want to be...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks for the help! I have a girlfriend, who is very upset with me, because she thinks I was very irresponsible to break it.
Ok, the phone originally came with Jellybean, but three days later, it did a system upgrade and I got kitkat.
It's possible maybe JellyBomb just wasn't designed for kitkat? I didn't see anything to suggest that.
The order of things was:
1: I used the autoroot or Odin to flash a new Recovery. Unfortunately I can't remember which.
2. The second was whatever I didn't do the first time.
3. From that point I tried to use the recovery to instal JellyBomb and as far as I could tell, it worked.
4. Reboot. Now it's stuck in a loop. it either kicks up the seandroid enforcing warranty: kernell. Or "" recovery.
5. I can get it into recovery by running a second autoroot, but it won't let me successfully install a ROM.
6. I can also go into download mode, but ODIN says fail on everything accept installing the autoroot.
7. I've gone ahead and tried going back to stock, but the tars are flawed or something.
So to summarize it, I've been running in circles and I'm starting to sort of loose track of what I've tried or what else I could try. I simply don't have the money to buy another $700 phone.
KoolCharisma said:
Thanks for the help! I have a girlfriend, who is very upset with me, because she thinks I was very irresponsible to break it.
Ok, the phone originally came with Jellybean, but three days later, it did a system upgrade and I got kitkat.
It's possible maybe JellyBomb just wasn't designed for kitkat? I didn't see anything to suggest that.
The order of things was:
1: I used the autoroot or Odin to flash a new Recovery. Unfortunately I can't remember which.
2. The second was whatever I didn't do the first time.
3. From that point I tried to use the recovery to instal JellyBomb and as far as I could tell, it worked.
4. Reboot. Now it's stuck in a loop. it either kicks up the seandroid enforcing warranty: kernell. Or "" recovery.
5. I can get it into recovery by running a second autoroot, but it won't let me successfully install a ROM.
6. I can also go into download mode, but ODIN says fail on everything accept installing the autoroot.
7. I've gone ahead and tried going back to stock, but the tars are flawed or something.
So to summarize it, I've been running in circles and I'm starting to sort of loose track of what I've tried or what else I could try. I simply don't have the money to buy another $700 phone.
Click to expand...
Click to collapse
You're girlfriend has a point, as the above is circuitous.
Now, download either the One-Click here, or stock tar here, flash either the one-click from it's own package (It contains an EXE file that does the entire restore for you) or the tar from PC Odin, and when complete, meet me back here.
While that's happening, download this NABD update zip here (it's a small file in the bottom of he OP, look for it and grab it from freeza's thread I just linked, and put it on your PC (it will eventually reside on your external SD, but you're not putting it there until you're back to stock). Do NOT flash recovery or root until you respond. And please quote this message, as I'll get an email when you do.
Then grab this recovery file (it'll go on your PC), this latest TWRP for KitKat V 2.7.0.0, and this SU 1.93 for our phone, just in case you need it (the latter will go on your phone). I am giving you choices. All of this should take no more than 20 minutes, planning included.
Write back if you need help.
Good luck!
Right On!
micmars said:
You're girlfriend has a point, as the above is circuitous.
Now, download either the One-Click here, or stock tar here, flash either the one-click from it's own package (It contains an EXE file that does the entire restore for you) or the tar from PC Odin, and when complete, meet me back here.
While that's happening, download this NABD update zip here (it's a small file in the bottom of he OP, look for it and grab it from freeza's thread I just linked, and put it on your PC (it will eventually reside on your external SD, but you're not putting it there until you're back to stock). Do NOT flash recovery or root until you respond. And please quote this message, as I'll get an email when you do.
Then grab this recovery file (it'll go on your PC), this latest TWRP for KitKat V 2.7.0.0, and this SU 1.93 for our phone, just in case you need it (the latter will go on your phone). I am giving you choices. All of this should take no more than 20 minutes, planning included.
Write back if you need help.
Good luck!
Click to expand...
Click to collapse
You've given me hope. I got everything I need here and I'm definitely seeing some new pieces that have been missing from the process thus far. So this returns me to stock, got it, but with the addition of SU and TWRP, does that open the choice up to root/and or flash other ROMS? I'm almost scared to fool with it now, but I definitely don't want to go to stock.
NAB file seems like it may take 12 hours to install, so unfortunately I can't give you immediate results. At least I'm not stuck with the same old pattern and expecting different results.
What ROM are you running?
KoolCharisma said:
You've given me hope. I got everything I need here and I'm definitely seeing some new pieces that have been missing from the process thus far. So this returns me to stock, got it, but with the addition of SU and TWRP, does that open the choice up to root/and or flash other ROMS? I'm almost scared to fool with it now, but I definitely don't want to go to stock.
NAB file seems like it may take 12 hours to install, so unfortunately I can't give you immediate results. At least I'm not stuck with the same old pattern and expecting different results.
What ROM are you running?
Click to expand...
Click to collapse
Do not worry about the rom I'm running.
There's no reason for this to take long.
Flashing the one-click or tar?
Sent from my SM-N900P using Xparent BlueTapatalk 2
It got worse
Just when things were looking up, the situation changed. Now it will only give me the "seandroid not enforcing warranty bit: recovery" message. From there it just cycles it will not allow the EXE file to recognize the phone nor can Odin see it. I assume of course because I can't get it into download mode.
So I'm really confused now. A few hours ago I had access to a broken recovery and a download mode that wasn't working. Now It seems I lost access to both. What gives?
WE GOT IT!!!
KoolCharisma said:
Just when things were looking up, the situation changed. Now it will only give me the "seandroid not enforcing warranty bit: recovery" message. From there it just cycles it will not allow the EXE file to recognize the phone nor can Odin see it. I assume of course because I can't get it into download mode.
So I'm really confused now. A few hours ago I had access to a broken recovery and a download mode that wasn't working. Now It seems I lost access to both. What gives?
Click to expand...
Click to collapse
I scoured all over this sight and online and didn't see mention of this app anywhere. Now You've fixed it!
So where do we go from here? I'm a big nervous going for a root a second time, but I simply can't use stock anymore.
KoolCharisma said:
I scoured all over this sight and online and didn't see mention of this app anywhere. Now You've fixed it!
So where do we go from here? I'm a big nervous going for a root a second time, but I simply can't use stock anymore.
Click to expand...
Click to collapse
Dude, you have to quote me or I'm not going to get realtime updates on your progress.
OK, so you have a working stock rom?
If yes, plug your phone into your computer, dump the NABD update file I gave you into into your SD card, and put the root file I gave you onto your phone's internal memory.
Now, power off your phone.
Boot into stock recovery (you'll get there, you may encounter recovery loops, don't panic, it's perfectly normal, just be patient, hold power + home plus volume up), you should be in stock recovery.
Now using the volume keys, navigate to apply update zip from external SD. Hit home to select, then navigate to the NABD zip file you copied. Install it.
After that, you're on NABD stock.
Next step is to install custom recovery.
After booting your phone on stock, skip past the setup screens, and just let the phone do its garbage setup, then reboot for good measure, then power off.
Now, open PC Odin (run as administrator from Windows), and put the TWRP file I gave you into the PDA slot.
Now, take off the casing, and hold the phone in your hand, have your fingers at the ready to hold volume up + home, don't do it, just be ready. Now put the phone in download mode (home + volume down + power). Plug the phone into the same USB port on your phone that you used to copy the files onto it.
Ready, hit start on Odin. That recovery file flashes in like 5 seconds. The moment it finishes flashing and begins to power cycle, hit those keys (volume up + home), and you're in TWRP.
From TWRP, navigate to the place on your SD card where you put the superuser zip, and flash it.
You now have a rooted phone with working recovery. From here you can do whatever you want.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
NABD
micmars said:
Dude, you have to quote me or I'm not going to get realtime updates on your progress.
OK, so you have a working stock rom?
If yes, plug your phone into your computer, dump the NABD update file I gave you into into your SD card, and put the root file I gave you onto your phone's internal memory.
Now, power off your phone.
Boot into stock recovery (you'll get there, you may encounter recovery loops, don't panic, it's perfectly normal, just be patient, hold power + home plus volume up), you should be in stock recovery.
Now using the volume keys, navigate to apply update zip from external SD. Hit home to select, then navigate to the NABD zip file you copied. Install it.
After that, you're on NABD stock.
Next step is to install custom recovery.
After booting your phone on stock, skip past the setup screens, and just let the phone do its garbage setup, then reboot for good measure, then power off.
Now, open PC Odin (run as administrator from Windows), and put the TWRP file I gave you into the PDA slot.
Now, take off the casing, and hold the phone in your hand, have your fingers at the ready to hold volume up + home, don't do it, just be ready. Now put the phone in download mode (home + volume down + power). Plug the phone into the same USB port on your phone that you used to copy the files onto it.
Ready, hit start on Odin. That recovery file flashes in like 5 seconds. The moment it finishes flashing and begins to power cycle, hit those keys (volume up + home), and you're in TWRP.
From TWRP, navigate to the place on your SD card where you put the superuser zip, and flash it.
You now have a rooted phone with working recovery. From here you can do whatever you want.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Trying now to go From NAB to NABD. I'm doing it in stock recovery. First off I realized that When it first pulls into recovery, the broken Android comes up. It let me navigate to install NABD and seems to reach the very end of installation but then it stops at "patching modem.bin img". nothing appears broken, but I'm I'm afraid to unplug it or to try and boot it back into stock.
KoolCharisma said:
Trying now to go From NAB to NABD. I'm doing it in stock recovery. First off I realized that When it first pulls into recovery, the broken Android comes up. It let me navigate to install NABD and seems to reach the very end of installation but then it stops at "patching modem.bin img". nothing appears broken, but I'm I'm afraid to unplug it or to try and boot it back into stock.
Click to expand...
Click to collapse
Those patch files are upgrading the OS build top NABD. Let it run its course.
Sent from my SM-N900P using Xparent BlueTapatalk 2
KoolCharisma said:
Trying now to go From NAB to NABD. I'm doing it in stock recovery. First off I realized that When it first pulls into recovery, the broken Android comes up. It let me navigate to install NABD and seems to reach the very end of installation but then it stops at "patching modem.bin img". nothing appears broken, but I'm I'm afraid to unplug it or to try and boot it back into stock.
Click to expand...
Click to collapse
It won't let me go through with it. Or at least I didn't have patients for it. I was able to get the phone back to a full reboot and then go back in and flash TWRP. TWRP works and is now my recovery, but I'm unable to upgrade NABD or Establish Root.
micmars said:
Those patch files are upgrading the OS build top NABD. Let it run its course.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
It won't let me go through with it. Or at least I didn't have patients for it. I was able to get the phone back to a full reboot and then go back in and flash TWRP. TWRP works and is now my recovery, but I'm unable to upgrade NABD or Establish Root.
Then...
KoolCharisma said:
It won't let me go through with it. Or at least I didn't have patients for it. I was able to get the phone back to a full reboot and then go back in and flash TWRP. TWRP works and is now my recovery, but I'm unable to upgrade NABD or Establish Root.
Click to expand...
Click to collapse
Then don't upgrade to NABD; if you attempted to root the device or flash recovery prior to upgrading to NABD, the update will never flash.
If you still lack the ability to start your phone, just reflash NAB One-Click or tar and call it a day. Move straight to flashing recovery and rooting. Or just recovery and a pre-rooted ROM.
Let me know what you'd like to attain, and we can take it from there. NAB is good enough.
If you stilll want to try NABD, note that the upgrade to NABD took me a while to get it right, as I had trouble getting into stock recovery. Please let me know if the upgrade to NABD file is the same file size as this. If yes, then skip NABD and go straight to recovery and root.
Almost there
micmars said:
Then don't upgrade to NABD; if you attempted to root the device or flash recovery prior to upgrading to NABD, the update will never flash.
If you still lack the ability to start your phone, just reflash NAB One-Click or tar and call it a day. Move straight to flashing recovery and rooting. Or just recovery and a pre-rooted ROM.
Let me know what you'd like to attain, and we can take it from there. NAB is good enough.
If you stilll want to try NABD, note that the upgrade to NABD took me a while to get it right, as I had trouble getting into stock recovery. Please let me know if the upgrade to NABD file is the same file size as this. If yes, then skip NABD and go straight to recovery and root.
Click to expand...
Click to collapse
We're definitely working with the same NABD while. So I guess I will do as suggested and go back to stock with the EXE. Then I will try to work my way back to a rooted phone with custom recovery.
I will say at this point that I'm certain I'll want another ROM. I can't stand stock. I'm just very fearful that with this whole KNOX bit, it is far less predictable to stay off the grid so to speak. There's also the question of which ROM. I never reach for the vastly different ones, but I don't want something simple like CM. My favorite ROM on the S3 was Liquidsmooth. I had trouble however upgrrading to KitKat on my S3 so now I don't know if I can trust that on my phone. I'm definitely open for suggestions.
Pick a Direction...
KoolCharisma said:
We're definitely working with the same NABD while. So I guess I will do as suggested and go back to stock with the EXE. Then I will try to work my way back to a rooted phone with custom recovery.
I will say at this point that I'm certain I'll want another ROM. I can't stand stock. I'm just very fearful that with this whole KNOX bit, it is far less predictable to stay off the grid so to speak. There's also the question of which ROM. I never reach for the vastly different ones, but I don't want something simple like CM. My favorite ROM on the S3 was Liquidsmooth. I had trouble however upgrrading to KitKat on my S3 so now I don't know if I can trust that on my phone. I'm definitely open for suggestions.
Click to expand...
Click to collapse
When this first started, you had been on an AOSP rom, yes? If so, then you need to decide if you still want that. If you want a reliable phone that has everything functioning as the manufacturer intended (and that is a very wide berth as to whether that is a good thing), then you should pick a TouchWiz KitKat ROM for now and run with it. If you want a working phone that is reliable with no bells and whistles, then go with one of freeza's Stocksh DeOdex or Odex rooted roms.
You should not be afraid of Knox, you should merely choose what you want and head that direction. You'll get there.
However, I understand the reticence; I get pretty anxious when doing this stuff, even over the smallest of things Those whom help me here can vouch for that, as I've driven many of hem insane.
micmars said:
When this first started, you had been on an AOSP rom, yes? If so, then you need to decide if you still want that. If you want a reliable phone that has everything functioning as the manufacturer intended (and that is a very wide berth as to whether that is a good thing), then you should pick a TouchWiz KitKat ROM for now and run with it. If you want a working phone that is reliable with no bells and whistles, then go with one of freeza's Stocksh DeOdex or Odex rooted roms.
You should not be afraid of Knox, you should merely choose what you want and head that direction. You'll get there.
Alright here we go again. I've reflashed stock and now I'm attempting to upgrade to NABD with Stock Recovery. Now I'm stuck again in recovery at the very end of the flash where it says: "Patching modem.bin img".
I was on Liquidsmooth, which I believe was a touchwiz, but to be honest, I'm not sure between the two, which probably explains a lot as to why I was having trouble flashing on the S3.
Where do I go from here?
Click to expand...
Click to collapse
micmars said:
When this first started, you had been on an AOSP rom, yes? If so, then you need to decide if you still want that. If you want a reliable phone that has everything functioning as the manufacturer intended (and that is a very wide berth as to whether that is a good thing), then you should pick a TouchWiz KitKat ROM for now and run with it. If you want a working phone that is reliable with no bells and whistles, then go with one of freeza's Stocksh DeOdex or Odex rooted roms.
You should not be afraid of Knox, you should merely choose what you want and head that direction. You'll get there.
However, I understand the reticence; I get pretty anxious when doing this stuff, even over the smallest of things Those whom help me here can vouch for that, as I've driven many of hem insane.
Click to expand...
Click to collapse
Alright here we go again. I've reflashed stock and now I'm attempting to upgrade to NABD with Stock Recovery. Now I'm stuck again in recovery at the very end of the flash where it says: "Patching modem.bin img".
I was on Liquidsmooth, which I believe was a touchwiz, but to be honest, I'm not sure between the two, which probably explains a lot as to why I was having trouble flashing on the S3.
Where do I go from here?
Is the problem hung up on the modem specifically, or is that just what the screen happens to be displaying at the time. It seems more to me that there is just one small piece of the whole puzzle that doesn't add up. I'm up supposed to do some full wipes and formatting to get my way through this?
KoolCharisma said:
Is the problem hung up on the modem specifically, or is that just what the screen happens to be displaying at the time. It seems more to me that there is just one small piece of the whole puzzle that doesn't add up. I'm up supposed to do some full wipes and formatting to get my way through this?
Click to expand...
Click to collapse
Just skip the NABD update and go straight to root and/or recovery.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
The ROM may not have Loki support...if you are using the older twrp version it may not auto lokify the ROM...try updating your recovery and give it another go
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would recommend trying out Philz ( cwm ) recovery possibly. There have been random issues like yours reported and usually updating the recovery or just trying a different ROM all together gets better results.
You shouldn't need to go back to stock mdk for anything since you're already rooted and have a custom recovery.
Sent from my SCH-I545 using Tapatalk
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
FranklinPIerce said:
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
Click to expand...
Click to collapse
Let me suggest trying liquid smooth 4.4
Awesome ROM to try.
Sent from my SCH-I545 using Tapatalk
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would try their suggestions. For future reference though, you can use heimdall instead of Odin on Linux. I love it I think its better than odin
Sent from my unknown using Tapatalk
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
FranklinPIerce said:
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
Click to expand...
Click to collapse
That's odd that flashing Philz didn't work for you. Its a pain I know but probably if you had wiped the phone with stock mdk then tried again it woukd have worked I bet. I had to do that with this phone when i got it. It came with twrp, but was acting real funny not always getting into recovery or just hanging up on reboot. But you have a working twrp so that's good too.
I don't believe liquid has the built in app permissions you're talking about but maybe I missed it. I don't really mess with permissions. Liquid has everything else though and then some!
I know some Roms were having problems with unified builds. I know liquid does not at this point. Maybe it'd be worth trying just so you're not on stock lol you may want to look into the Loki doki zip that you flash after flashing the ROM. I've seen some people on here using that when they were getting the same error you were. Just an idea.
Good luck man!
Sent from my SCH-I545 using Tapatalk
This firmware is the unmodified Lollipop (Android 5.0) firmware downloaded through Samsung Kies. In case you need a copy of the firmware so that you don't have to keep downloading it through Kies, I'm providing you with a copy via the link below. It's odin flashable. Use the "AP" or "PDA" button to flash it onto your phone.
1. Download the stock Android 5.0 ROM (Lollipop) - Sprint N900P ONLY! - androidfilehost.com/?fid=24391638059060029
2. Download the official Samsung Kies. - samsung.com/in/support/usefulsoftware/KIES/
3. Download Odin 3 or later. - samsungodindownload.com/download/
4. Open Samsung Kies, and connect your phone. Wait for it to install the needed drivers.
5. Open Odin and make sure that it says it's "Added!"
6. Click the "AP" button and open the downloaded ROM.
7. Wait for it to finish verifying the checksum.
8. Make sure that "Auto Reboot" and "F. Reset Time" are the only boxes checked. (The default)
9. Click "Start" and wait for it to go. (Sometimes it gets stuck when it says "Setup Connection" and then you need to unplug your phone and restart Odin. - BE CAREFUL! Make sure it really is stuck or you'll brick your phone!)
10. [Optional] Flash TWRP (twrp.me) or CWM. (clockworkmod.com) TWRP is more free than CWM in the sense that the CWM ROM Manager has a payware version. If you're feeling generous towards those who spend countless hours each day for fun and to make your life a bit easier, throw them a few bucks. Both are freely available.
WARNING: Odin can brick your phone if you don't know what you're doing. If you break it, just buy another $800 device. I'm providing these instructions and the ROM without any warranty. You do with them what you feel is best.
That this is a zip file, it is not seen my Odin.
THANK YOU THANK YOU THANK YOU! You helped me save what I thought was a dead phone with this!
Is there a mod to change the launcher to 5x4
mac01843 said:
That this is a zip file, it is not seen my Odin.
Click to expand...
Click to collapse
Not sure if you've figured it out yet but you'll have to extract the .tar file from the zip, then Odin will be able to see it, the .tar file that is.
Thank you, thank you, thank you. This totally saved my bacon after a moron at the Sprint Store (and perhaps me for letting him look at it) replaced the SIM and then said that there was nothing they could do for the phone since it had been rooted.. now I have a way to reactivate the phone before switching back to a decent ROM.
This worked like a charm!
Anyone have a mirror?
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
can I keep it unlock?
Can I keep my KITKAT 4.4.2 NOTE 3 Sprint unlocked after updating this stock firmware? I'm newbie and English is not my mother tongue.
Yes you can!
Anyone? On CM as well and would looove to have an Odin flashable Stock ROM
tusker559 said:
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
Click to expand...
Click to collapse
Or maybe point me (us) in the direction of finding something similar?
Anyone else getting invalid MD5 checks in ODIN with this one? Does anyone have an valid download link? Trying to switch back to Stock so I can pull the 6.0 OTA and fix my GPS issues.
Edit:Georgia Mirror is valid
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
iletumi said:
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
Click to expand...
Click to collapse
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
how did you access the georgia mirror?
404 error on file link.
Nevermind. Tried again and it downloaded.
misterkatanga said:
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
Click to expand...
Click to collapse
Factory reset and it works now! Thank u!!!!
Here's what I did with a new T-Mobile Samsung Galaxy S5:
- Started phone in download mode (started it with Volume Down, Home, and Power buttons) and connected it to computer.
- Started Odin3v185, saw yellow COM box.
- Clicked PDA button and selected philz_touch_6.26.2-klte.tar.md5 file.
- Clicked Start button, flashing went fine, phone reset and everything was cool, still with stock ROM. I was able to boot into Philz recovery to verify that flashing worked.
- As part of my goal of installing XtreStoLite ROM 2.2 (Lollipop), the following steps were to install the modem and bootloader for that ROM.
- Started phone in download mode and connected it to computer.
- Started Odin3.09, saw blue COM box.
- Clicked BL button, and selected G900T-LP-UVU1DOB1-BOOTLOADER.tar.md5.
- Clicked CP button, and selected G900T-LP-UVU1DOB1-MODEM.tar.md5.
- Clicked Start to flash. Phone reset, but it froze at the Samsung logo.
I gave it about a half hour just to make sure it wasn't just taking it's time with this first boot after the update, but it stayed at the Samsung logo. Only way to turn it off was to remove the battery. I'm still able to boot into Philz, so I figured a way to fix it might be to just go ahead and install the ROM. So I selected the "install from zip" option and installed XtreStoLite_ROM_v2.2_LP_XXU1BOD3.zip. Now the startup logo is a bit different, but it still stays frozen at the logo. I know from previous times installing this ROM that it does usually take awhile (maybe 5 minutes) on the first boot after installing, but I let it sit again for about 30 minutes with no luck.
The only thing I can see that I did differently this time, which I know realize was dumb, was skipping the step after flashing Philz where I boot into it and install UPDATE-SuperSU-v2.37.zip to root the device. I thought that I'd be able to install the bootloader, modem, and ROM and end up with a rooted OS, but I'm guessing that rooting is separate from those things, and they can't succeed until the phone has been rooted.
So... what can I do now? I'm trying to install the stock ROM (G900T_TMB_G900TUVU1CNK2_G900TTMB1CNK2_original.zip), but Philz gives me a "installation aborted" error before it even starts, with no other error messages. I also suspect I should install the original kitkat bootloader+modem, but I'm not sure where to find those (searching yields a lot of different results).
Any help would be greatly appreciated. Thanks!
The bootloop must be related to the bootloader/modem you've flashed. SU will allow root access once booted, but it won't prevent the system from booting if you skip it. Are you simply trying to root? FWIW, I'd recommend skipping Lollipop altogether, Marshmallow is night and day better than Lollipop. Flash the complete factory image of one of the Marshmallow releases, then flash your recovery and install SU. There are a couple of good, debloated Marshmallow roms available.
I was able to get out of the situation by flashing a stock ROM from here:
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
I first flashed the stock modem and bootloader, though I'm not sure that was required because I think they're included in the ROM itself.
Used the latest 4.4.2 ROM and NK2 bootloader+modem, just because I'm pretty sure it was 4.4.2 that was on the phone when I got it.
Retried my procedure, this time rooting + disabling KNOX before flashing the Lollipop bootloader+modem from the ROM's install instructions, but I still ran into the same "freeze at boot" problem. I don't know what could be the issue, as I've done this exact procedure with two previous S5s. Not really looking to check out Marshmallow ROMs, just because I'm short on time these days, and after trying out a handful over the years, the XtreStoLite is by far the best for me.... really the perfect combo of stock Android with some of the improvements offered by TouchWiz, with all the tweaks to fix annoying "features" that I want fixed (for example, the removal of that damn "are you sure you want to increase the volume? It could damage your hearing" warning when you connect headphones and try to turn up the volume). Also, just stable and fast, compared to most/all the others I've tried.
Sounds to me as if you need stock Marshmallow with a custom recovery and Exposed. Mine is fast as hell, extremely frugal on battery, and Exposed has got rid of all the annoying TW "features", like the volume warning you mention (also, expanded notifications on lockscreen, battery full notification gone, circle battery, etc, etc). There are also alternatives to stock that are good, I tried one a couple of weeks ago that I think I'm probably going to go back to. Lollipop is horrible after using KitKat, Marshmallow brings back the KitKat experience but with dramatically improved battery life. You'll also get some Stagefright improvements.
Sorry for the delayed response, been too busy to deal with this for a couple weeks. How exactly do I get a stock Marshmallow with custom recovery and Exposed? Don't I already have the custom recovery covered with Philz? What Marshmallow ROM would you recommend? Thanks for the feedback!
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Did you deodex GPI1 before exposed?
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Does this thread have the info I need for installing Xposed (I'm assuming "Exposed" and "Xposed" are the same thing)?
http://forum.xda-developers.com/showthread.php?t=3034811
Just install a .zip from TWRP, then install the .apk to manage installed modules?
I have "UPDATE-SuperSU-v2.37.zip". Is that sufficient for SU?
Well dammit, I've now spent multiple hours I didn't have trying to get *ANY* ROM other than the stock KitKat one to work. Was just about to give up after trying one last time with XtreStoLite, this time using KToonsez kernel instead of stock. Restarted and it was taking forever to boot, so I assumed it was frozen and was about to pull the battery and call it a night, when it actually made it into the OS! So perhaps there's something going on with the phone that won't let it boot with any stock kernel, other than 4.4.2. Bummer, because I was starting to get excited about trying Marshmallow.
It's because you have KitKat firmware. You just need to flash the entire MM package first.
What is the MM package, if it's not
G900T-(GPI1)-Bootloader.tar
G900T-(GPI1)-Modem-NonHLOS.tar
G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5
?
You don't need to flash the bootloader & modem separately. If you download the complete firmware, that's all you need to flash, it has all the necessary partitions in it. Just flash that, see if it works, then flash the recovery, etc.
I already tried G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5, both with and without the bootloader+modem packages.
I didn't see any mention of you having tried it in your earlier post. You should be able to flash just that package under AP (All Partitions, I assume), and it should install all the partitions it finds inside the tar. My guess is that Odin isn't completing correctly. What does it say in the log on the left? I had to use Odin 9, 10 wouldn't work on my setup for some reason, nor could I get it to work on XP, only on Windoze 8.