Related
Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?
I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!
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
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz