So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
U are in edl mode u need to search for blank flash it should get u back up and running
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
Did you get it running
Related
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.
Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.
Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.
Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Kopiok said:
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Click to expand...
Click to collapse
Try the solution in the last few posts on this thread. http://forum.xda-developers.com/showthread.php?t=2465695
I hope you get more knowledgeable advice than mine but, were I in your situation, my primary goal would be to get back to STOCK. Forget CM and modding for now. Either through TWRP or through the recovery settings on the phone itself I'd get to where I could do a factory reset. If you're continuously able to boot into TWRP I don't see how your phone could be bricked. My experience is, if I can get a phone to do ANYTHING I've got a shot at figuring out how to get out of whatever mess I've created. I don't know if this could be a factor but I'd put in a different micro SD card too, in case there's something on the card you've got in there.
Just an update. So, I got it to go back to fastboot this morning and I tried using the Razr Utility to flash back stock and stock recovery, but I got a "Failed" line with the reason "Remote Failure". Not sure what that's about. When it reset it got back to the Cyanogenmod boot graphic, but it never started. I left it there for a good 12 minutes.
Right now it's sitting in TWRP. I'm going to let it charge to 100% (it was a little less when I tried all of this) and attempt it again at 100% battery. Thanks for the help so far!
So, I tried using the Razr Utility to flash the system, kernel, radio and for system it was unsuccessful (something about too many threads or strings, something to that effect), but the rest said OK. Now my phone doesn't seem to turn on. My computer still makes the device plugged in sound when it's plugged/unplugged, but I cannot get the screen to show anything or seem to turn on the phone.
Is this it? Is it... bricked!? ;-;
Edit: I ordered the Factory Adapter as a last resort sort of thing. This is lame.
Edit Edit: I've seen the boot logo since my last edit! But... it's not coming back and I still can't even bring up the bootloader. I don't know why it will sometimes turn on or sometimes not. In any case, I'm now hopeful that not ALL is lost.
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
That's the plan! One odd thing happening now... My phone's screen isn't showing anything, so I assumed it was off. I left it unplugged and went to see a movie..... and the phone is still warm. This leads me to believe the phone is still drawing power, for some reason... God this is weird. I'll wait for the adapter and try again. Thanks for the help!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
according to the packaging on mine from tbh a chinaman made it, just sayin
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
cellzealot said:
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
Click to expand...
Click to collapse
thanks for making it either way, better to have and not need.
havent had to use it so far
bweN diorD said:
thanks for making it either way, better to have and not need.
havent had to use it so far
Click to expand...
Click to collapse
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
cellzealot said:
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
Click to expand...
Click to collapse
how many thousands, and whats the plan?
I got the Factory Adapter and used RSD Lite to flash stock. And it works! Yay! It's starting up reliably and everything.
Except... it won't start up without the cable attached, and the battery icon has a big question mark on it. It also won't connect to the cell network (but does connect to WiFi). What do I do now?
Edit: So I noticed that while the battery status said "Unknown", it did go from 2% to 3% charge level when I plugged it in normally for a little. My plan at the moment is to try leaving it plugged in for a while and then try taking the OTA update to see if that fixes everything. Good plan?
Edit Edit: Never mind! I just had to let it charge for a bit. It seems to be back in working order, now! Thank you so much for all the help everyone!
That is exactly what is supposed to happen. Congrats on fixing your phone!
The factory cable/adapter does not charge the device but powers it directly, allowing it to boot no matter what state the battery is in or even without a battery at all.
You cannot charge in bootloader, which is why the cable/adapter is so valuable. Once the device can boot/charge normally then you are all set.
Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!
whynottry said:
Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!
Click to expand...
Click to collapse
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!
Crap I forgot to mention I can't go into download mode. Sorry about that..
atmxpert said:
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!
Click to expand...
Click to collapse
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Hmm i installed the latest verison of twrp with my mac via fastboot ( followed directions from twrp site for the commands). I would try to get adb/fastboot to work on your mac first and maybe try to fastboot flash twrp again? and if that does not work i would just do a RUU honestly, but i'm sure someone smarter than me can chime in and get it resolved . For instructions to install adb/fastboot on a mac i followed this http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/ If it does not recognize your device try installing htc sync manager.
darthnix said:
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Click to expand...
Click to collapse
You could go find the ruumode-flashable recovery that I think is in one of dottat's ruu threads (5.0.1 one I think). Then change the name of the file to 0p6bimg.zip and flash it in bootloader. That should flash twrp to a phone without adb/fastboot.
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?