Does ADB not work when in recovery?
When my N7 is in recovery mode (CWM) my PC (Win7) doesn't see any attached USB devices and "adb shell" obviously tells me "no devices found".
My N7 is rooted, unlock bootloader, has CWM (non touch) installed and when in "regular", normal boot I can perfectly "shell in" via adb, just not in CWM recovery....
Does CWM not support that as of yet, or am I doing something wrong?
Not sure. Adb works fine for me in cwm
Sent from my Nexus 7
Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.
bagofcrap24 said:
Not sure. Adb works fine for me in cwm
Click to expand...
Click to collapse
OK, so it might just be something I'm doing wrong.
TECK said:
Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.
Click to expand...
Click to collapse
Counter question: Why not?
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing - also I might need it (or at least it's supposed root adb shell access) everytime I go to recovery, so why keeping the need to have to "fastboot boot" it everytime instead of just booting into it?
Also - as said above - adb and fasboot both work fine, just not in CWM.
I might try another driver, maybe that'll help.
HellcatDroid said:
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing.
Click to expand...
Click to collapse
The proper way is to tempload CWM, not install it. You want to be special and do it your way, feel free to... nobody is stopping you. Since you know what you are doing, then you should not have any issues.
HellcatDroid said:
I might try another driver, maybe that'll help.
Click to expand...
Click to collapse
What's wrong with using the default Google USB drivers? They work properly.
TECK said:
What's wrong with using the default Google USB drivers? They work properly.
Click to expand...
Click to collapse
See first post, not working in CWM for me right now.
Might not be the drivers, if you have any real help to give, feel free to share.
I would not use other drivers, except the Google USB ones provided on their developer site.
Based on my experience, you can have only headaches if you replace stock recovery with CWM. That's the main reason why I always temp load it, instead of physically install it. I know it is convenient to have it installed, but how often do we use it? Very rarely. The less I tweak on the phone, the safer it is. Are you running 6.0.1.0 on your tablet?
First, do you see the Android 1.0 driver marked as invalid in device manager?
If yes, then the fix is easy... Follow the procedure I posted in my signature to properly install the ADB drivers.
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
If not, this is what I would do in this situation: I would install the Google factory image (straight from console, no crazy toolkits) and restore everything back to normal. Then, I would test the stock recovery and see if everything works as expected. After that, I would tempload CWM 6.0.1.0 and see if there are any issues. I know is a ****ty deal, especially if you have lots of customizations on your tablet. The goal is to see if you can run all proper commands while using the stock recovery. If you cannot, that's a different ball game.
It's been the drivers.
i installed the ones from the Android SDK and everything works now (had drivers d/l'ed from the Asus page so far).
TECK said:
Based on my experience, you can have only headaches if you replace stock recovery with CWM.
Click to expand...
Click to collapse
Based on my experience it doesn't really matter - unless you are going to use some special functionality CWM breaks (like the full device encryption on the S2 with GingerBread 2.3.x - and I got even that to work with an own build).
Bottom line: every one does things differently and something perfect for one might be suboptimal for the other.
TECK said:
That's the main reason why I always temp load it, instead of physically install it.
Click to expand...
Click to collapse
I love the option to be able to temp-boot a kernel, my Droids so far (Samsung Galaxy S2 and S3) didn't support that.
Tempbooting a kernel is perfect for testing a new build as you don't have to reflash a working one if the one you tried doesn't work
Though, it'd be just more work for me to tempload CWM everytime I need it, but as said, that's just me.
TECK said:
I know it is convenient to have it installed, but how often do we use it? Very rarely.
Click to expand...
Click to collapse
Negatory, I use it alot.
Mostly for the rooted adb shell access though, yet that's rather often - and also quite often away from my home computer with everything loaded and temploading without the kernel image.... hmm, not really
TECK said:
The less I tweak on the phone, the safer it is.
Click to expand...
Click to collapse
Safety is overrated (disclaimer: that's a joke )
For me it's more like "the more I mod the hell out of it, the more fun it is - and if everything breaks, I restore/reflash factory and start over".
CWM won't stay for too long anyways, eventually I'll smack my own kernel and own recovery-kernel onto it.
Time to check out those sources
TECK said:
Are you running 6.0.1.0 on your tablet?
Click to expand...
Click to collapse
Yeah.
TECK said:
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
Click to expand...
Click to collapse
Nothing "fancy" but Samsung drivers, yes.
And getting rid of them is totally out of the question as my S2 and S3 won't work anymore, then.
But everything works now, got the Google SDK drivers for the N7 and the Sammy drivers for the rest and everything looks good
TECK said:
(straight from console, no crazy toolkits)
Click to expand...
Click to collapse
Yeah, that's exately how I do it, adb and fastboot all "by hand".
TECK said:
I know is a ****ty deal, especially if you have lots of customizations on your tablet.
Click to expand...
Click to collapse
All hail to the backups, just restore my data after the wipe :good:
Anyways, thanks for the help, after all it was that link to the tut that got me to install the Google SDK drivers
Related
This is a guide we should have just in case people want to go back to normal. Can anyone say step by step how do we unroot our phone and how do we uninstall a custom rom.
Thanks in advanced, this will help people if they ever want to go back.
EDIT.. I figured out one sure way to uninstall a custom rom, and that is to just restore your nandroid backup that you should have made before you installed the rom.
Just factory reset the phone.
if you run RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe it will be like the way you got it. Unrooted and stock
you can get it here http://forum.xda-developers.com/showthread.php?t=559622
fatkitty420 said:
Just factory reset the phone.
Click to expand...
Click to collapse
That won't work because when you load a custom rom, it effectively "becomes" the factory image.
kylez64 said:
if you run RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe it will be like the way you got it. Unrooted and stock
Click to expand...
Click to collapse
Does this also erase all data on the phone? Call logs, apps, etc.
Stevious said:
Does this also erase all data on the phone? Call logs, apps, etc.
Click to expand...
Click to collapse
yes it will make it so its just like you got it on day one new in the box
yup, RUU will unroot your phone, delete all installed apps and settings to include call logs, sms's, or anything else you have on your phone.
Pictures and some downloads are automatically downloaded to your sd card so those should be fine.
Stevious said:
Does this also erase all data on the phone? Call logs, apps, etc.
Click to expand...
Click to collapse
Yup, thats why you do a nandroid backup.. It's a life savior
goku14238 said:
Yup, thats why you do a nandroid backup.. It's a life savior
Click to expand...
Click to collapse
Trying to restore and nandroid is saying run " nandroid-mobile.sh restore" on console.. any ideas why.
I backed up nandroid on my PC and then formated the SDcard for App2sd but then realized that I formated off my pictures. Kind of hoping those were saved in the nandroid backup.
Has anyone actually attempted to un-root using this RUU utility?
A couple users at androidforums are trying to go back to stock and running into problems - the app it telling them something along the lines of 'you cannot use this utility with your phone, please use the correct utility'
I can't remember exact verbage atm - but something along those lines.
I'm running linux and don't really trust trying this through a Windows VM, else I'd answer my own question here.
cicada said:
Has anyone actually attempted to un-root using this RUU utility?
A couple users at androidforums are trying to go back to stock and running into problems - the app it telling them something along the lines of 'you cannot use this utility with your phone, please use the correct utility'
I can't remember exact verbage atm - but something along those lines.
I'm running linux and don't really trust trying this through a Windows VM, else I'd answer my own question here.
Click to expand...
Click to collapse
Yes I did when I had some problems and it works just fine. You have to be able to have your phone on, usb connected and seen by your computer for it to work. I then rooted the phone again.
kylez64 said:
if you run RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe it will be like the way you got it. Unrooted and stock
you can get it here http://forum.xda-developers.com/showthread.php?t=559622
Click to expand...
Click to collapse
Is the step for using this - put this file on SD card ( not root ) and run recovery< update.zip
Grinder16 said:
Is the step for using this - put this file on SD card ( not root ) and run recovery< update.zip
Click to expand...
Click to collapse
no you run that exe from your computer
goku14238 said:
no you run that exe from your computer
Click to expand...
Click to collapse
Would you mind posting the steps to take, (or should I start a new thread for that?) as afar as connecting the phone via usb and windows cmd prompt and adb and all that? I am actually happy with my rooted hero and modaco rom, but just in case...id like to know. Thanks in advance!
chalan30 said:
Would you mind posting the steps to take, (or should I start a new thread for that?) as afar as connecting the phone via usb and windows cmd prompt and adb and all that? I am actually happy with my rooted hero and modaco rom, but just in case...id like to know. Thanks in advance!
Click to expand...
Click to collapse
First download + install HTC Sync. Verify that HTC Sync can see your phone. If not, you need to uninstall drivers, unplug your phone, plug it back in and have windows find the drivers again for you. EDIT: Just a note, on my Vista comp HTC Sync didn't recognize it for me so I had to pull out a comp with XP on it. Windows 7 I don't know. Vista still works though, I just think I did something funky to the drivers on there.
Next, just exit HTC Sync or leave it running doesn't matter.
Now, while your phone is plugged in Download the RUU exe. Run it, follow directions. Voila. Everything wiped back to brand new out of the box HTC rom.
Thanks TOKi
I did but I dunno if my phone is unrooted or not. Anyway to check this?
Plus my phone is deactivated and I have no idea how to reactivate it. Haha.
redram38 said:
Yes I did when I had some problems and it works just fine. You have to be able to have your phone on, usb connected and seen by your computer for it to work. I then rooted the phone again.
Click to expand...
Click to collapse
I have tried several times. Each time I cannot get past the "waiting for bootloader" part. It must have something to do with replacing the recovery partition with RA-heroc-v1.2.3.
Anyone else have this issue?
I had this issue, but I unplugged and tried the process again and it fixed itself
Hello. Please help me. my phone can not use the rom manage. I have used one once, but can not be used again. when I turn on the program, still connected 3g/wifi but nothing more happened at all. I have copied the program into the correct directory. My phone rooted.This phenomenon occurs after I Flast 2.1
What doesnt work? Does it not install? Why are you copying the app at all? Why not install from Market?
I installed the application from Market but I can not use the rom manage.
I don't know!
duongthanhcong said:
I installed the application from Market but I can not use the rom manage.
I don't know!
Click to expand...
Click to collapse
Rom Manager*
You have to be rooted to use it.
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
dcontrol said:
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
Click to expand...
Click to collapse
Also, did you download it from the market, or did you steal the pro version from online? I am asking because you said "I copied it to the right directory"
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
Few options here, search for the standalone update.zip with Clockwork and do it that way OR wait a few hours and try again.
The 1st choice I had to do once because RM wasn't liking my phone and the 2nd choice sometimes the server is down.
First, my phone t959 rom UVJI6 normal. Then my rom to version 2.2 T959UVJFD. I do not feel satisfied so I returned to the Odin 2.1.
My phone has a normal root and fix lag.
but then, I could not manage to use the rom again.
Sorry for my english level is limited. I'm from Vietnam
blizzard1017 said:
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
.
Click to expand...
Click to collapse
Yes. this is my problem. How do I do now?
Thanks!
If youre trying to flash another rom you need to disable the lagfix first.
Sent from my SGH-T959 using XDA App
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
blizzard1017 said:
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
Click to expand...
Click to collapse
(See attachment)
Master™ said:
(See attachment)
Click to expand...
Click to collapse
Always living up to your name...
I had mine fixed up through some trial and error hopefully this gets the OP in the right direction.
Just finished the 3.1 update. Here's a few notes.
Update appears to freeze at some points but finishes eventually. don't worry
update does not remove root! yay!
resizing widgets is cool
still no quick controls in browser =[
samsung camera app is updated slightly. seems the same but a couple of the icons a little bit different
seems more responsive overall
scrollable list of recent app is awesome
installed apps now have a "open" icon in the market instead of just saying "free"
wifi icon is a bit different in the system bar
added ability to set different image for lock screen
there's a new usb debugging image. it's an android bee. pretty cool
the samsung app store("Samsung Apps") and music hub are gone.
is it just me or is the browser much better now?
"talkback" keyboard now available
home key now takes you to the most recently used home screen rather than the middle one
did I miss anything else?
Can you still boot into fastboot?
smaskell said:
Just finished the 3.1 update. Here's a few notes.
Update appears to freeze at some points but finishes eventually. don't worry
update does not remove root! yay!
resizing widgets is cool
still no quick controls in browser =[
samsung camera app is updated slightly. seems the same but a couple of the icons a little bit different
seems more responsive overall
scrollable list of recent app is awesome
installed apps now have a "open" icon in the market instead of just saying "free"
wifi icon is a bit different in the system bar
did I miss anything else?
Click to expand...
Click to collapse
my lockscreen now has a different image. it used to just show my wallpaper. is anyone else experiencing this or did mine just get screwed up?
never mind this. this is on purpose. updating original post.
Did the update add google books? It is still listed as incompatible with my device (IO GT 10.1) on the market.android.com website.
camblue said:
Can you still boot into fastboot?
Click to expand...
Click to collapse
I've never tried to reboot into fastboot. why would I need to? the bootloader comes unlocked...
just tried it now and it did not work.
@tau_
I can't comment on this. Google books is not available in Canada anyway so I can't say whether the update made any difference. I just installed it myself with adb.
in case you didn't see the update to my original post, "adb reboot recovery" no longer works. I am highly unimpressed
edit: "adb reboot recovery" doesn't work but "reboot recovery" while in adb shell still works. thank god..
tau_ said:
Did the update add google books? It is still listed as incompatible with my device (IO GT 10.1) on the market.android.com website.
Click to expand...
Click to collapse
I now have Google Books 3.0.1-117394 on the system.
How is the quality of the images in the gallery. 3.0 did a poor job of displaying the initial image. And would improve drastically when you zoomed in a little. has this been fixed?
And setting wallpapers any better then 3.0? Images were cropped terribly with 3.0 when set as wallpaper.
All The I/o wallpapers are gone
"reboot fastboot" doesn't do anything. did it before?
"reboot bootloader" works but I was not able to do anything from there. neither adb nor fastboot recognized the device.
I never really noticed any problems with image quality before so I don't know what to say about that.
the wallpapers are the same. this is not a bug. they did it on purpose. it does that so that the moving up effect looks cool when you open the app drawer.
and falconeight is right. i/o wallpapers gone =[. they should be in the system image I posted somewhere, right?
falconeight said:
All The I/o wallpapers are gone
Click to expand...
Click to collapse
I had one and lost it. That is a shame.
Well considering that fastboot was the only way to load cw recovery it is pretty important. Odin is a pin in the butt to flash in.
smaskell said:
I've never tried to reboot into fastboot. why would I need to? the bootloader comes unlocked...
just tried it now and it did not work.
@tau_
I can't comment on this. Google books is not available in Canada anyway so I can't say whether the update made any difference. I just installed it myself with adb.
Click to expand...
Click to collapse
Can one of you guys pull the 3.1 update and post it? It may be usable for us to root the retail versions.
camblue said:
Well considering that fastboot was the only way to load cw recovery it is pretty important. Odin is a pin in the butt to flash in.
Click to expand...
Click to collapse
good point. I wasn't thinking about that. I never bothered to install clockwork before so I never had to use fastboot(on the galaxy tab. obviously, I have on all my other devices). Anyway, couldn't someone make a clockwork image that we could flash via recovery? or could we not use rom manager to flash the recovery?
cosimoss said:
I had one and lost it. That is a shame.
Click to expand...
Click to collapse
let me know what folder they are in and i'll pull them and post them
thepro8 said:
let me know what folder they are in and i'll pull them and post them
Click to expand...
Click to collapse
already done.
http://forum.xda-developers.com/showthread.php?p=14580792#post14580792
they're not in a folder though. they're part of the launcher apk
Google books is there
falconeight said:
All The I/o wallpapers are gone
Click to expand...
Click to collapse
I found someone else uploaded them here:
http://forum.xda-developers.com/showthread.php?t=987277
thepro8 said:
let me know what folder they are in and i'll pull them and post them
Click to expand...
Click to collapse
Cheers already got them from this thread.
Thats the only thing holding me up,,,well other than it not updating due to i think root, busybox, and cw mod installation, it keeps failing, might be a good thing though since i am sure someone will do a workable zip to install this update
smaskell said:
good point. I wasn't thinking about that. I never bothered to install clockwork before so I never had to use fastboot(on the galaxy tab. obviously, I have on all my other devices). Anyway, couldn't someone make a clockwork image that we could flash via recovery? or could we not use rom manager to flash the recovery?
Click to expand...
Click to collapse
So a friend thought it would be hilarious to add a screen lock to my phone and lock me out of my Gmail, but google sends my unlock code to a text on my phone.... Frustrating to say the least. And he can't remember the code he used cause well drinking.
I do not have USB on, so when I connect to the computer I only get the music folder or something stupid.
I really just want my pictures off the phone. Everything else can just be wiped, but I don't know how I can do that even.
Can anyone help?
You should be able to use adb to pull stuff from the phone while it is in recovery mode
jmjoyas said:
You should be able to use adb to pull stuff from the phone while it is in recovery mode
Click to expand...
Click to collapse
This is your best bet...
Alternatively you can make a NAND backup and extract it from a PC. Do you have a custom recovery / Safestrap?
jmjoyas said:
You should be able to use adb to pull stuff from the phone while it is in recovery mode
Click to expand...
Click to collapse
What's adb?
NighthawkXL said:
This is your best bet...
Alternatively you can make a NAND backup and extract it from a PC. Do you have a custom recovery / Safestrap?
Click to expand...
Click to collapse
I don't have any back ups. I used the get.cm installer.
How would I make a nand backup if I can't see anything from the USB though?
Jeffrey000 said:
What's adb?
I don't have any back ups. I used the get.cm installer.
How would I make a nand backup if I can't see anything from the USB though?
Click to expand...
Click to collapse
Adb = android debug bridge. You can try that or the last choice would be to reset with Odin. That really sucks though. You should always have your own lock screen so others can't do this to you. Also, backups are made in recovery, which is probably either twrp or cwm for you. Good luck!
I can't find this anywhere. Every guide seems to assume that everyone has a micro SD in their phone. Currently, I don't have one. I'm wondering if an S7 Edge root is possible without an SD card.
diraga said:
I can't find this anywhere. Every guide seems to assume that everyone has a micro SD in their phone. Currently, I don't have one. I'm wondering if an S7 Edge root is possible without an SD card.
Click to expand...
Click to collapse
try this
mashardpro said:
try this
Click to expand...
Click to collapse
I have tried the CF-Auto-Root method twice now, both resulting in being stuck on boot like the other times. However, maybe I needed to wait longer? Next time I attempt a root I will leave the phone alone for at least 15 minutes before I call it a failure. Still, the post you linked seems to be for older firmware. Would you still recommend the method for Nougat? Thanks for the reply.
diraga said:
I have tried the CF-Auto-Root method twice now, both resulting in being stuck on boot like the other times. However, maybe I needed to wait longer? Next time I attempt a root I will leave the phone alone for at least 15 minutes before I call it a failure. Still, the post you linked seems to be for older firmware. Would you still recommend the method for Nougat? Thanks for the reply.
Click to expand...
Click to collapse
then you can try twrp , and use adb sideload if you don't have sdcard
mashardpro said:
then you can try twrp , and use adb sideload if you don't have sdcard
Click to expand...
Click to collapse
I think I've isolated the problem. After using adb sideloader to install magisk and antiroot remover, I'm prompted to reboot. In other guides, there is a further options screen after pressing the reboot button which has a couple checked boxes and a button that says "Do Not Install". I see this screen for maybe a third of a second after selecting Reboot before the device reboots on its own. Just tried this and now I'm stuck on the Samsung boot logo once again.
Note: There are many errors in the adb sideloader log relating to being unable to mount/unmount /data/ and stuff like that that I know are related to having an SD inserted.
Edit: I should also note that I am new to android. Fresh newbee from iOS, but I have been jailbreaking for the past 9 years. Still in over my head I think.
diraga said:
I think I've isolated the problem. After using adb sideloader to install magisk and antiroot remover, I'm prompted to reboot. In other guides, there is a further options screen after pressing the reboot button which has a couple checked boxes and a button that says "Do Not Install". I see this screen for maybe a third of a second after selecting Reboot before the device reboots on its own. Just tried this and now I'm stuck on the Samsung boot logo once again.
Note: There are many errors in the adb sideloader log relating to being unable to mount/unmount /data/ and stuff like that that I know are related to having an SD inserted.
Edit: I should also note that I am new to android. Fresh newbee from iOS, but I have been jailbreaking for the past 9 years. Still in over my head I think.
Click to expand...
Click to collapse
hmmmm, I am a bit confused as well. I am successful with that way. Or read this for other options. But I do not know work or not, because the last link I had never tried
mashardpro said:
hmmmm, I am a bit confused as well. I am successful with that way. Or read this for other options. But I do not know work or not, because the last link I had never tried
Click to expand...
Click to collapse
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
diraga said:
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
Click to expand...
Click to collapse
Well, it seems like all I know already I mentioned, better use of existing first now while waiting for someone who can help you. btw, the root will be used for what?
diraga said:
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
Click to expand...
Click to collapse
Once data is wiped in twrp then reboot back to recovery and connect usb to pc. You should be able to copy SuperSU zip via mtp and your phone should show up on pc. Flash SuperSU zip once copied
mashardpro said:
Well, it seems like all I know already I mentioned, better use of existing first now while waiting for someone who can help you. btw, the root will be used for what?
Click to expand...
Click to collapse
Deleting stock apps, installing adblock, exploring non-Google Play apps, possibly installing custom ROM. I enjoy seeing what my phone can do.
ASHLEY117 said:
Once data is wiped in twrp then reboot back to recovery and connect usb to pc. You should be able to copy SuperSU zip via mtp and your phone should show up on pc. Flash SuperSU zip once copied
Click to expand...
Click to collapse
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
diraga said:
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
Click to expand...
Click to collapse
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
diraga said:
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
Click to expand...
Click to collapse
so you have twrp now?
ASHLEY117 said:
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
Click to expand...
Click to collapse
That's... a really good idea. Going to try right now!
mashardpro said:
so you have twrp now?
Click to expand...
Click to collapse
I've had no trouble installing TWRP whatsoever. I've done it five times today!
diraga said:
That's... a really good idea. Going to try right now!
I've had no trouble installing TWRP whatsoever. I've done it five times today!
Click to expand...
Click to collapse
seems nice, good luck. maybe lacking some finishing touches you need to do. I remember well my first too so, and the key is I have to format the data in twrp
ASHLEY117 said:
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
Click to expand...
Click to collapse
mashardpro said:
seems nice, good luck. maybe lacking some finishing touches you need to do. I remember well my first too so, and the key is I have to format the data in twrp
Click to expand...
Click to collapse
Update: Still stuck on Samsung boot logo after 15+ minutes after successfully loading from usb drive. TWRP still skipped right by the reboot options screen after the install... I have no clue why it's doing that. It's like it's taking the command to reboot after I press the button and processing it while it is going to the next screen. I don't know. Hopefully someone does. It's so close!
EDIT: IT WORKED!!! Had to format and then installing from usb drive worked great! Thank you so much!!
diraga said:
Update: Still stuck on Samsung boot logo after 15+ minutes after successfully loading from usb drive. TWRP still skipped right by the reboot options screen after the install... I have no clue why it's doing that. It's like it's taking the command to reboot after I press the button and processing it while it is going to the next screen. I don't know. Hopefully someone does. It's so close!
EDIT: IT WORKED!!! Had to format and then installing from usb drive worked great! Thank you so much!!
Click to expand...
Click to collapse
I am glad to hear it. Like I said, just need the final touch that you might forget
mashardpro said:
I am glad to hear it. Like I said, just need the final touch that you might forget
Click to expand...
Click to collapse
False alarm! Root checker says my phone is not rooted... I'm lost... At least my phone booted?
diraga said:
False alarm! Root checker says my phone is not rooted... I'm lost... At least my phone booted?
Click to expand...
Click to collapse
so if you have twrp and your phone is booted, then take a look this. quite easy to understand
mashardpro said:
so if you have twrp and your phone is booted, then take a look this. quite easy to understand
Click to expand...
Click to collapse
Currently following this tutorial and awaiting boot past the Samsung logo. Hoping it works. I see no reason why it shouldn't.
Edit: Running a rooted Android. Thanks