Related
Hey there, apologies in advance if I have submitted this thread in the wrong section. I really looked as hard as I could before posting.
Well I rooted my phone, got super user on there, then got clockworkmod red, and then attempted to put the ice cream sandwich mod on my phone, thats where everything went sour. Phone would not go past screen that says samsung. I tried a few times to get it to go past that point, and just nothing. I then attempted to use odin to have my phone put back, but now I cannot even get the phone to open up clockworkmod.
To put it very simply. The only thing I have access to now is the download option (holding both volume up and down while inserting the usb cable from the computer) I have searched the internet high and low for something to run through odin to put my phone back to the way it was. I keep coming up with dead links and long dead downloads. I was able to use the gtg ultimate unbrick, but all that managed to accomplish was to have my phone say at&t instead of rogers.
Im still at the screen that says samsung, with no access to a recovery menu at this point. I only have the download option.
Can anyone help me salvage my phone?
edit: I appear to have been able to reput clockworkmod back on the phone with odin. Thats all I have been able to do.
When flashing any ics Rom/port from.gingerbread/red recovery you will need to double flash...I'm seeing a lot of people.with bricks lately and I think the problem is they are not reading enough before flashing ics...
So you have cwm correct? Boot into cwm by holding volume up down and power button. If you have no roms hen go to mounts and storage and mount USB then plug it into the pc and copy over the Rom...if its gingerbread Rom.just one flash...if its ics then flash, you will get stuck on Samsung screen so boot back into cwm...you will either boot into a blue or some distorted rainbowy cwm...just reflash he Rom
If you can't do that...then idk what else to do as I don't know much about rogers phones and what is and isn't compatible with them...but u would suggest qksters heimdal one click back to stock uclb3...its always worked for me...but not sure if it will work with rogers...
Sent from my HTC PH39100 using XDA
Mytheos said:
Hey there, apologies in advance if I have submitted this thread in the wrong section. I really looked as hard as I could before posting.
Well I rooted my phone, got super user on there, then got clockworkmod red, and then attempted to put the ice cream sandwich mod on my phone, thats where everything went sour. Phone would not go past screen that says samsung. I tried a few times to get it to go past that point, and just nothing. I then attempted to use odin to have my phone put back, but now I cannot even get the phone to open up clockworkmod.
To put it very simply. The only thing I have access to now is the download option (holding both volume up and down while inserting the usb cable from the computer) I have searched the internet high and low for something to run through odin to put my phone back to the way it was. I keep coming up with dead links and long dead downloads. I was able to use the gtg ultimate unbrick, but all that managed to accomplish was to have my phone say at&t instead of rogers.
Im still at the screen that says samsung, with no access to a recovery menu at this point. I only have the download option.
Can anyone help me salvage my phone?
edit: I appear to have been able to reput clockworkmod back on the phone with odin. Thats all I have been able to do.
Click to expand...
Click to collapse
If u can get to dl ur fine
Sent from my SAMSUNG-SGH-I717 using xda premium
http://forum.xda-developers.com/showthread.php?t=1331381
Use this link/program from download mode to get to stock 2.3.6.
Wait, if you can get to download mode, you can reflash JScott's option C from here, then get into CWM red, flash the ICS of your choice, reboot into CWM blue (press and hold vol up/vol dn/power 5 seconds when stuck at sammy screen), wipe data/cache/dalvik, reboot and you should have ICS.
I understand that some people will never get "it", but reading the entire post for flashing/modding firmware is a MUST.
I need help guys,
I used Odin to root the phone and did my first custom rom which is the clean rom...it went through the process and when it was about to reboot i got the system software not approved by verizon and take phone to store
I have been told to odin back to stock but it wont let me. The stock image on odin wont work it says fail
I tried the first method and used odin in download mode to flash the stock image
Failed:
This is what I get
added
Odin V3 engine
File Analysis
all threads completed (succeed 0 / Fail 1)
In the Odin Download mode on the phone the top left reads as follow
Odin Mode (Red Letters)
Product Name (SCH-I535)
Custom Binary Download : Yes (1 counts )
Current Binary Custom
System Status Custom
Qualcomm Secureboot: Enable
One thing I gotta mention is that when I got the phone last week it had an OTA update from Verizon which I did install and then a few days later I rooted the phone and when I tried to use Clean Rom it gave me the dreaded Verizon message
Sounds like you didn't unlock the bootloader.
Ya your bootloader is locked again ... unlock it and redo the steps everything should be fine after that
Guys I know that the bootloader is locked but i cannot get back to stock to unroot phone and then unlock the bootloader
Odin recognizes phone but the stock image goes into fail mode right away
I cannot get into recovery and the only thing I can do is go to download mode and Odin but nothing else
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Stranger_84 said:
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Click to expand...
Click to collapse
You are aware he can Odin flashed the latest OTA instead of that you have provided. Here it is :http://forum.xda-developers.com/showthread.php?t=2046439. This will also help fix his phone being that it is recent. Forgot this link to get him back on track: http://forum.xda-developers.com/showthread.php?t=1974114.
i thought thats what he already tried? but yes you can odin any ota file being that an unlocked bootloader isnt needed.
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
I'm not sure being ive never had that issues ... im sorry and good luck
try flashing odin stock ROM, not bootchain
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
Did you put the file in PDA in Odin they only work if you checked PDA.
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
I had a similar issue once. This helpful post by h3llsdr0id eventually got me up and running. Took a total of like 4 hours though lol.
http://forum.xda-developers.com/showpost.php?p=30569324&postcount=26
Make sure you have the correct files. This is for the original root66 so it's ICS. Once I booted up and activated I took the Verizon OTAs all the way to JB and then rooted/unlocked bootloader.
edit: I actually had to go back to ICS to reprovision my SIM so not sure you have to go through all of this. Try to odin stock JB ROM like mentioned above.
Thank YOU so much guys you have made my day.
After trying all last night and today I got it back to stock with the OTA file through ODIN. That is all I needed and it went right back to brand new stock phone using 4.1.1
WOW.
I thought I was going to have a dead phone.
Thank you all
Glad you got it up and working!!!!!
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
I'm having the same problem and can't get into download mode
Gatanater said:
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
You have to get into download mode to use Odin. It will go into download mode, if you will search, there are ways to pull battery along with button combo to get it there. After rooting, use EZ Unlock 1.2 and that will unlock your bootloader without then unauthorized message from Verizon. Make sure you use only that version, the others don't work.
Re: I'm having the same problem and can't get into download mode
mj76 said:
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
Click to expand...
Click to collapse
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
flammablepez said:
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
Click to expand...
Click to collapse
Thank you for your response. I tried pulling the battery out and holding volume down, home and power keys at the same time while putting battery in, even as i plugged it into my phone, but nothing but the unauthorized error screen comes up. I should note that my phone is note 2 not s3. I apologize for posting it here, but this thread seemed to be just like the problem i was having.
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
vax1170 said:
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
Click to expand...
Click to collapse
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
buhohitr said:
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
vax1170 said:
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
Click to expand...
Click to collapse
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
buhohitr said:
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
Click to expand...
Click to collapse
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
vax1170 said:
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
Click to expand...
Click to collapse
It's possible that the 4.3 bootloader already flashed and it's in the process of flashing the rom when you pulled the battery. In any case, if the software is half done you phone won't boot, and if you attempt to flash the old rom, you will brick your phone if the bootloader already locked. So you need to turn it on to see where you at or you can take a chance and try to Odin old stock rom, again if the bootloader already locked you will brick your phone and if not then you will be back to the older version. I would turn it on and see.
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there? I already did a print-pit on all 3 phones, but from what little I know it seems like the only differences are likely due to the memory sizes. 32 vs 16.
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
vax1170 said:
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there?
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
Click to expand...
Click to collapse
If you don't see the last 2 lines like I mentioned above, it should be the old bootloader...since the timing you pull the battery, no one really know what state it's in unless you boot it up.
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
vax1170 said:
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
Click to expand...
Click to collapse
Yes, you can boot up now and see what's going on...
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
vax1170 said:
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
Click to expand...
Click to collapse
I would try to use Odin and flash MF1 full firmware here http://www.androidfilehost.com/?fid=23134718111254196
Thanks for confirming ... I was poking around the forums and figured I should probably try the procedure to completely reflash my device back to stock. I'll try that later tonight. Thanks again ... crossing my fingers
[RESOLVED]
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
vax1170 said:
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
Click to expand...
Click to collapse
You're a lucky son of .....lol.
Hey guys so my phones kernel and stuff was slightly messed up I know this because wifi didn't always work and it wouldn't work at certain places and if I reset the phones settings or factory the wifi would show up. I then thought hey I need wifi so let me put a custom mod on it. I have rooted my phone easy but never put a custom mod.. I still dont know what it does or what a custom recovery is or whatever. I tried odin and it said failed a bunch of times. I then started trying to use apps like goo manager and busy box and such and had no idea what i was doing other than following instructions blindly and I ended up using an app that was glitched I believe and when ever I started the phone it went into recovery mode. Then I stopped using the phone for a quite a while and one of my friends said he could look at it and determined that it is screwed to the point of no return. So I thought why not go for one last swing at it did some more Youtbing and did another tutorial another tarp or md5 file or whatever it is. I now have that screen which says connect to Kies for emergency firmware recovery or something. I can still access download mode and such but the main problem is 1. odin is still not working 2. Kies is now not recognizing my S4 keeps telling me it doesnt recognize it. I have a Samsung S4 verizon build number is 2g6 I believe I know the ending is 6. Its curruntly on 4.4.2 kit kat.
TLDR: The phone says that i need to hook it up to kies for emergency firmare something but kies wont recognize my phone and I cant do a hard reset and When I flash with Odin it always says Fail when it gets to the boot part
Thanks so much guys you dont know how much any help would be. Please respond this is all I will be doing all day so I can give you all extra info asap.
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !
Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!
Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !
Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.
I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?