Related
I recently purchased this SGS3, installed CWM and rooted it. Everything was going great - but then i was offered the most recent OTA update, so i reflashed the stock recovery via Odin, did the update which is:
4.0.4
T999EVLH2
same kernel
bld #: IMM76D.T999EVALH2
now, its saying the phone is no longer rooted (yet superSU is still there) but checkroot is saying that it isnt rooted, and no matter what i do, flashing CWM via Odin passes, but will not stick (as in, i boot into recovery mode and that damned stock recovery is STILL THERE, wtf?)
can anyone offer any assistance or insight into my issue.
Thanks
~Wikkid
Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.
Aerowinder said:
Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.
Click to expand...
Click to collapse
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.
mikewikkid said:
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.
Click to expand...
Click to collapse
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.
Aerowinder said:
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.
Click to expand...
Click to collapse
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.
mikewikkid said:
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.
Click to expand...
Click to collapse
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/jv6pHg8b
Aerowinder said:
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/sUJixYID
Click to expand...
Click to collapse
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!
mikewikkid said:
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!
Click to expand...
Click to collapse
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.
Aerowinder said:
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.
Click to expand...
Click to collapse
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."
mikewikkid said:
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."
Click to expand...
Click to collapse
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.
You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.
xanderman said:
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.
Click to expand...
Click to collapse
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
Aerowinder said:
You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.
Click to expand...
Click to collapse
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
Thistleknot said:
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
Click to expand...
Click to collapse
Umm, 2 things....
You realize this thread is over a year old and the last post was over 9 months ago?
And those links look like they are for the S4....
Sent from my SGH-T999V using Tapatalk 4
I rooted the phone 3 times, with and without the toolkit. It says successful each time and I can use Titanium backup. I tried to de-knox (wasn't told to do so) but it says it can't find root. Root checker says I'm rooted and I have TWRP.
What in the world could I have done wrong.
Any help would be helpful.
4.4.4
3.10.5-AELKernel-v4.5
[email protected] #1
SmoothKat deox v1
sesm-n910p
mdf 1.1 release 5
vpn v 1.4 release 2
wascapsfan said:
I rooted the phone 3 times, with and without the toolkit. It says successful each time and I can use Titanium backup. I tried to de-knox (wasn't told to do so) but it says it can't find root. Root checker says I'm rooted and I have TWRP.
What in the world could I have done wrong.
Any help would be helpful.
4.4.4
3.10.5-AELKernel-v4.5
[email protected] #1
SmoothKat deox v1
sesm-n910p
mdf 1.1 release 5
vpn v 1.4 release 2
Click to expand...
Click to collapse
Maybe a silly question but did you install a custom recovery?
Great question. Yes. I have TWRP
Did u check md5 on the rom u downloaded and update to the latest twrp
wascapsfan said:
I rooted the phone 3 times, with and without the toolkit. It says successful each time and I can use Titanium backup. I tried to de-knox (wasn't told to do so) but it says it can't find root. Root checker says I'm rooted and I have TWRP.
What in the world could I have done wrong.
Any help would be helpful.
4.4.4
3.10.5-AELKernel-v4.5
[email protected] #1
SmoothKat deox v1
sesm-n910p
mdf 1.1 release 5
vpn v 1.4 release 2
Click to expand...
Click to collapse
You should try philz recovery
Sent from my SM-N910P using JellyBombed Tapatalk 2
wascapsfan said:
I rooted the phone 3 times, with and without the toolkit. It says successful each time and I can use Titanium backup. I tried to de-knox (wasn't told to do so) but it says it can't find root. Root checker says I'm rooted and I have TWRP.
What in the world could I have done wrong.
Any help would be helpful.
4.4.4
3.10.5-AELKernel-v4.5
[email protected] #1
SmoothKat deox v1
sesm-n910p
mdf 1.1 release 5
vpn v 1.4 release 2
Click to expand...
Click to collapse
So the first thing I noticed is, you listed the bold above. That means the rom is flashed? Thats my rom. Its stock and you even show the correct kernel. (although I would update to a newer one). Next thing is, after you download use an MD5 checker and compare to the rom thread or AFH next time. This will indicate if there are issues with the download or the file itself after moving it. Report back for us so we can proceed to help you further
Have you tried full unroot through SuperSU app and reflash latest SuperSU via recovery ?
OK. So I completely bricked the phone trying to get this to work.
I was able to download the ORIGINAL stock unrooted rom.
I rooted it again after getting it back up. I tried to flash a couple of ROMS, but TWRP just continues to reset back to TWRP menu when I flash. So I changed to Philz. Aborts each time
It sounds to me like the best plan at this point would be to Odin back to stock and start over. Something went wrong somewhere!
Yeah. If you can get into download mode then you didn't brick. Download the stock tar and try again.
I already restored it back to stock. I've done this 3x now. I'm stock again now, but each time I use the toolkit and reboot, when I try to flash ANY rom, it says failed or corrupt.
I've tried philz and TWRP. Both are giving the same results
I've rooted several phones and no issue. I was able to install one earlier before I bricked the first time, but the radio/data kept having issues even after I did the fix so I tried another rom, but to no avail.
wascapsfan said:
I already restored it back to stock. I've done this 3x now. I'm stock again now, but each time I use the toolkit and reboot, when I try to flash ANY rom, it says failed or corrupt.
I've tried philz and TWRP. Both are giving the same results
I've rooted several phones and no issue. I was able to install one earlier before I bricked the first time, but the radio/data kept having issues even after I did the fix so I tried another rom, but to no avail.
Click to expand...
Click to collapse
you do know we could always skip the step thats probably not playing nice for you, the toolkit.
Odin Stock NK2 tar
Odin TWRP
Boot into TWRP
Flash Custom rom (all come prerooted nowadays)
Profit.
alternative to that is:
Odin Stock NK2 tar
Odin CF-autoroot
Odin Recovery Of choice
enjoy stock rooted or Reboot to recovery and flash custom recovery of choice.
Well, I just tried that also with the newest TWRP 2.8.4.0 and it didn't take through ODIN. The guy fell over when I went to see it as the the phone tried to do the update.
I used ODIN to download Philz and it took.
I then tried to flash Liquid Smooth and it aborted saying it can't open /storage/sdcard1/LS-LP-v4.0-2015-01-16- liquid_trltespr.zip (bad)
The I tried to /storage/sdcard1/cm-12-20150116-UNOFFICIAL-trltespr.zip (bad) and it aborted again
millerboy3 said:
you do know we could always skip the step thats probably not playing nice for you, the toolkit.
Odin Stock NK2 tar
Odin TWRP
Boot into TWRP
Flash Custom rom (all come prerooted nowadays)
Profit.
alternative to that is:
Odin Stock NK2 tar
Odin CF-autoroot
Odin Recovery Of choice
enjoy stock rooted or Reboot to recovery and flash custom recovery of choice.
Click to expand...
Click to collapse
Now that none of these options worked (for some strange reason), I went back to the toolkit and re-rooted the phone and got rid of knox, added busybox, etc... Now I AM rooted again, but none of the roms will install.
I have a rooted phone that can't flash.
I tried all of the roms that I downloaded to my sd card, but none seem to work.
Even though I have a new 128 gb sandisc ultra, is it possible that I have a bad card??
I'm just baffled. I've been rooting phones for years, but this one is strange.
Is there a way to use odin to flash a rom?? I know it would have to be a tar file
Definitely yes... Put the rom on the internal memory and you will be good to go!
wascapsfan said:
Now that none of these options worked (for some strange reason), I went back to the toolkit and re-rooted the phone and got rid of knox, added busybox, etc... Now I AM rooted again, but none of the roms will install.
I have a rooted phone that can't flash.
I tried all of the roms that I downloaded to my sd card, but none seem to work.
Even though I have a new 128 gb sandisc ultra, is it possible that I have a bad card??
I'm just baffled. I've been rooting phones for years, but this one is strange.
Is there a way to use odin to flash a rom?? I know it would have to be a tar file
Click to expand...
Click to collapse
Unless your card is bad (or your drivers on your pc) the problems you are experiencing are still unfortunately most likely internet connection or user related errors. You don't detail your steps carefully. This is important in this situation.
Try downloading a ROM to your computer and transfer it to the internal storage. Also, how are you using philz recovery, I thought only twrp worked for our phone. Download the right recovery here, flash with Odin in PDA slot from download mode. http://teamw.in/project/twrp2/266
UPDATE!!!!!
Thanks EVERYBODY... I used my old 4GB SanDisk mini card and it is still good.
I downloaded the rom to the card and it took immediately.
The 128GB card that I bought is junk.
It is rooted and I have an AWESOME rom now.
Thanks agian EVERYONE for all of your help
I'd appreciate any help I can get guys.
So today, for the first time ever I rooted my android.
Found a simple video on how to and it worked. I then wanted to try a custom rom [Cyanogenmod 12?] On a video it was said to have a custom recovery rom first. Well, I tried Flashing TWRP. It asked to reboot. I pressed "yes Please". After that it restarted and was stuck at:
"Could not do normal boot" Odin mode (High speed)
I did a reset and now its just at:
"Odin mode(high speed)"
I saw someone on a random forum describing the same problem. He said he fixed it installing a recovery rom. Im guess from odin
since I cant do things on my phone. But I don't even know how to go about it. I just now I need a Tar. file
Please give me direction .__.
Try TWRP tar from Odin with phone in download mode; TWRP recovery tar linked below.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
If that doesn't work, you may have to Odin the stock tar.
I'm wondering if you misread the CF Auto root prompt to update the su binary? Update the su binary but don't choose the TWRP option even if you have TWRP. If you get recovery working, delete the cache and dakvik cache and reboot.
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Sixgotfangs said:
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Click to expand...
Click to collapse
What version of Odin do you have? Should be 3.07 with C.F. auto root. What have you flashed in Odin? Not familiar with the Odin message you gave; did anything change with the new recovery tar flash in Odin?
Won't boot or flash recovery? If so, you need to factory reset and Odin stock tar.
https://www.androidfilehost.com/?fid=95853297432265112
The instructions for stock tar are below but it's important to remember when flashing stock tars to power down first prior to going to download. You may not have any choice but power down to reach download mode; pull battery if you can't power down.
http://forum.xda-developers.com/showthread.php?p=56853325
If you can't factory reset, Odin the stock tar and see if it boots.
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Sixgotfangs said:
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Click to expand...
Click to collapse
ok, check my post above for updates.
Also, don't use the phone to download tar files unless you're using Flashify from Google Play. Download the tars on PC, move to folder that Odin resides in to find easily. You'll need to open the archive and drag the files there if zipped. The stock tar should be zipped but not sure about the recovery tar.
Cant believe I didn't see the last section on that post. Sorry about that. Anyway, I am downloading those files. Looks like its gonna take some time though. I'll go through each step you said and let you know.
Forgot to mention that you should close Odin after each flash attempt. You may have already noticed by now.
To get to CM after stock tar:
1) Root with CF Auto root, update su binary/reboot (you should wait no longer than 5 minutes for Knox prompt from supersu.
2) Odin TWRP recovery tar using same method as stock tar; Odin will only write over stock recovery on this step.
3) factory reset and flash CM in recovery. But also follow suggested instructions in the ROM you choose.
So far so good. The lil blue loading bar is filling.
got back to rooting. but I didn't do anything else. haven't even went to super user
Sixgotfangs said:
got back to rooting. but I didn't do anything else. haven't even went to super user
Click to expand...
Click to collapse
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
samep said:
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
Click to expand...
Click to collapse
Yeah, things are back to normal. Thanks again. As for the next steps, pretty lost. Im going to check the play store for an superuser update but the SU binary update....that's where I start getting lost. sorry for not being up to date with the terminology. But I am gonna check back on those links and look for the TWRP. and then use it like I did for those last files...{that's what Im getting from your messages} correct me if im straying from the path lol. catch ya later
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
samep said:
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
Click to expand...
Click to collapse
Hey there, Ok so. After messing around I ended up getting that TWRP package to work. I thought It was a SINGLE file, that's where I got stuck. but the whole ?.rar showed up in the pda selection In odin and I ran it. Worked fine. didn't see anything about updates ...still.
I restarted and went to recoverymode. Teamwin popped up like ive seen from other videos. Guessing im on the right track. So right now I don't need to be worrying about SuperSu or Rashr? or should I be dealing with those two apps? ALSO is Rom installer anything to pay attention to?
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
samep said:
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
Click to expand...
Click to collapse
Thanks so much! The videos ive seen have been much simple-r for installing roms SO I may survive this whole experience after all...Yesterday was kind of a bad time to almost loose my phones functionality....being on the job hunt and all. need those phone calls Lol. So thanks again. Im hoping to try out cyanogenmod 12. I'll definitely shoot off a flare gun if I fail lol.
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
SUCCESS! Thanks again Sensei Lol
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
eh...celebrated too early I guess. Ever run into camera connection errors?
Sixgotfangs said:
eh...celebrated too early I guess. Ever run into camera connection errors?
Click to expand...
Click to collapse
Is the error while still on stock or CM?
Now that you can wipe data, you can factory reset and either Odin the stock tar or flash CM.
If you prefer to take least intrusive approach, try going into recovery and delete cache and dalvik cache and reboot. If still not working, the factory reset. If still having camera issues, then decide if you want to go with stock tar in Odin again or CM a clean install; wipe user data first.
Personally, I'd wipe everything except my titanium backups and go back to Odin stock tar and make sure stock works fully before going to CM. In a situation like you were in, I would have powered down, flashed the stock tar in Odin and let it auto boot. Flash the custom recovery so I could wipe everything and then power down again and flash the stock tar in Odin just to get a clean start with root and custom ROM.
Edit- what is camera connection error? Oh, I see; lost camera. New thread. Maybe someone on CM can help you.
So, I've got a 64gb black sprint Galaxy S6, non-edge. This morning, it had stock 5.11 on it, but I decided I wanted to root it, and ... I screwed up. I got Odin 3.10.6 and installed CF-Auto-Root-zerofltespr-zerofltespr-smg920p.tar.md5 which I now know does not work with 5.11. Since then, bootloop. Reboots every minute or so. I've tried everything I can find, wiping everything, flashing what purport to be stock ROMs, putting TWRP on there, and still within a minute of booting it reboots. I tried installing Smart Switch, but it can't get a connection because the phone just won't stay booted.
Rooting would be nice, but I just want my phone to work again. What can I do here? I don't have insurance and KNOX is flipped.
if you're sure you are on 5.1.1, flash any kernel (unikernel v8, etc.) that would fix your issue.
I should mention this is a SM-G920P, if that's significant.
I flashed the stock package through Odin, then TWRP, then installed Hacker Kernel through that. It's still rebooting repeatedly while i try to go through the initial setup process, and dumping me at the language select each time.
I tried unikernel too, didn't work either.
Okay, here's my current process, which is not working.
Boot to ODIN/Download mode, by holding power+volume down+home.
Open Odin 3.10.6, as administrator. Auto-Reboot is unchecked.
Flash what's supposed to be the latest stock rom, obtained here.
Wait until it says PASS, then reboot into ODIN mode again.
Flash the TWRP 2.8.7.0 tar, obtained here.
Wait until it says PASS, then reboot into recovery, by holding power+volume down+home until it reboots and then power+volume up+home to enter recovery.
Wipe Data/Cache/Darvik.
Transfer Hacker Kernel and SuperSU .zips, obtained here, to storage on phone.
Use TWRP to install Hacker Kernel, as instructed on that page.
Reboot into recovery.
Use TWRP to install Super SU. Note: In the section of the log reading Boot Image Patcher, I get Extracting ramdisk, Decompressing ramdisk, Failure, aborting. Important?
Reboot.
Now it's sitting on the Samsung Galaxy S6 screen, and not going any farther than that.
I tried flashing nothing but the stock 5.1.1 package, but that's not working either. It still keeps rebooting, and it won't ever get past the screen that says "Preparing your device for first-time use... This may take 3 or 4 minutes." Is there anything I can do? I can't afford to not have a phone and I can't afford to replace this one. Please, help me.
I've redownloaded everything, checking md5 sums, and those are all correct. Flashing the BOL1 stock gets me rebooting, flashing it and then Unikernel v8 gets me rebooting, flashing it and then Unikernel v9 gets me rebooting, flashing it and then Unikernel v9 and then TWRP has me rebooting.
It boots up and stays up for a minute or two, enough to get a little ways into the setup. The first boot, it stays on the Sprint screen for a while, then reboots after about a second on the language select screen. When it gets back there, I can select language, connect to wifi, accept the EULA, and then wait on the "Preparing your device for first-time use" screen for a little while before it reboots. Sometimes it'll get as far as asking me if I want to let Google collect diagnostic data.
Hardware issue...i had the same issue with similar process. I had to get a replacement phone
Is it possible that trying to install the Chainfire root package on a 5.11 phone just broke something permanently? Could it be something partition-related, maybe? I'm at a total loss here.
This should help
kafziel83 said:
Is it possible that trying to install the Chainfire root package on a 5.11 phone just broke something permanently? Could it be something partition-related, maybe? I'm at a total loss here.
Click to expand...
Click to collapse
I had the same issue also with the SM-G920P.
Problems:
*unikernal > v6 (v7 and above == bootloop)
*hackerkernal on non-teamsprint rom == bootloop
*cf auto root was not required for root
What fixed it for me:
1. Odin back to stock 5.1.1
2. Flash TWRP
3. Boot into recovery
4. Reboot (it should tell you that root is not installed or something like that, so if it asks to install root let it)
5. Once booted into os SuperSU will tell you to update the su binary, update then reboot
6. Congratulations you have root.
lodbldbol said:
I had the same issue also with the SM-G920P.
Problems:
*unikernal > v6 (v7 and above == bootloop)
*hackerkernal on non-teamsprint rom == bootloop
*cf auto root was not required for root
What fixed it for me:
1. Odin back to stock 5.1.1
2. Flash TWRP
3. Boot into recovery
4. Reboot (it should tell you that root is not installed or something like that, so if it asks to install root let it)
5. Once booted into os SuperSU will tell you to update the su binary, update then reboot
6. Congratulations you have root.
Click to expand...
Click to collapse
Did 1, did 2, did 3, did 4 but it didn't give any message like that, and now it's just repeating the "Samsung Galaxy S6 Powered By Android" screen over and over.
Unless when you say "Odin back to stock 5.1.1" you mean flashing 5.1.1 and then going through the setup to a functioning OS, because I have never been able to do that since I started.
kafziel83 said:
Did 1, did 2, did 3, did 4 but it didn't give any message like that, and now it's just repeating the "Samsung Galaxy S6 Powered By Android" screen over and over.
Unless when you say "Odin back to stock 5.1.1" you mean flashing 5.1.1 and then going through the setup to a functioning OS, because I have never been able to do that since I started.
Click to expand...
Click to collapse
To Odin back to stock 5.1.1 properly follow the steps on this page exactly with the files it tells you to use http://www.androidrootz.com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
Then you'll need a ROM, i recommend this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417
Once in recovery flash it (skip to step 7 in the link) then boot up, if that doesn't work I don't know what will.
Tried that, now it boots as far as the Sprint screen but hangs there and then reboots.
kafziel83 said:
Tried that, now it boots as far as the Sprint screen but hangs there and then reboots.
Click to expand...
Click to collapse
Hardware issue
Any advice on getting a replacement? I still have about $500 left on the monthly installments for this phone, and I don't have insurance. The Sprint stores I went to said to go to Samsung for a replacement for a malfunctioning phone, since I've had it for less than a year, since KNOX is flipped I'm guessing Samsung won't give me a thing.
I uploaded a file to Mediafire called 2016-03-20--04-15-35_G920P_Renegade_OJ7_v1.zip
This is a TWRP backup of my phone's system/radio/boot/efs, it should replace anything that doesn't work. I don't know if it'll work but it's worth a try.
Copy the zipped folder to TWRP/BACKUPS and restore your phone
Okay. Can you link to the mediafire page to download it?
kafziel83 said:
Okay. Can you link to the mediafire page to download it?
Click to expand...
Click to collapse
No, XDA won't let me put links to outside websites until I have 10 posts.
Same Problem
kafziel83 said:
Okay. Can you link to the mediafire page to download it?
Click to expand...
Click to collapse
Hi,
Same problem here,
Did you find a solution for your problem?
lodbldbol said:
I uploaded a file to Mediafire called 2016-03-20--04-15-35_G920P_Renegade_OJ7_v1.zip
This is a TWRP backup of my phone's system/radio/boot/efs, it should replace anything that doesn't work. I don't know if it'll work but it's worth a try.
Copy the zipped folder to TWRP/BACKUPS and restore your phone
Click to expand...
Click to collapse
If ever the EFS is cleared, deleted whatever. It re-builds from block 12, so there's no need to worry too much.
Sent from my SM-G925P using XDA Labs
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
kbashiri said:
Hi,
Same problem here,
Did you find a solution for your problem?
Click to expand...
Click to collapse
I would do a quick repartition, nand erase all, flash stock ROM boot it, and flash from there. Hope it goes well.
Sent from my SM-G925P using XDA Labs
Please Help
ChubbbySquish said:
If ever the EFS is cleared, deleted whatever. It re-builds from block 12, so there's no need to worry too much.
Sent from my SM-G925P using XDA Labs
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
I would do a quick repartition, nand erase all, flash stock ROM boot it, and flash from there. Hope it goes well.
Sent from my SM-G925P using XDA Labs
Click to expand...
Click to collapse
Should I do re-partition then nand erase all and then flash rom or should I do them altogether?
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.