Develop Bugs

[Solved] Question: How to root MyTouch Slide using OSX?

wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
EDIT: SOLVED!
So, I'm waiting for my Nexus one to come in the mail, and I think to myself, "Why not give rooting the slide another go?"
Worked second try. How's that for random....
So, here's how I made it work...Dunno if it was 'luck of the draw', but here ya go anyways...Hope it helps someone!
1. Instead of turning off the phone normally, I rebooted straight into recovery, with the phone being on first.
Code:
./adb reboot recovery
2. While rebooting, MANUALLY search for devices as soon as you can type it in, repeating rapidly (This made the difference for me).
Code:
./adb devices
3. You should catch the device in offline mode right before the recovery screen. Unplug device for 5 seconds or so, then plug it back in.
Code:
./adb devices
List of devices attached
HT05MPS02279 recovery
4. You should see your device in recovery, then you're good to go. If not try again.

How to you get the loop to stop? I have to quit Terminal app to stop it.
Click to expand...
Click to collapse
No, simply hit <control> c from inside the Terminal app to break out of the shell script.
Any other things to know?
Click to expand...
Click to collapse
Not really, it may take you several tries to get this as it did for people using M$ Winblows. I tried it about 20 - 30 times on XP and never was successful. After switching to my mac, I got root on the 5th try!
My suggestion is to follow Eugene's guide, it worked great for me! If you have problems, post them here and myself or others will try to help you.
Good luck!

wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
So I set up my camera to record myself rooting my phone using OSX and a couple friends walked into the room. I got distracted explaining what it was I was doing and didn't make the how to. If I have free time tomorrow afternoon I can make a how to vid. My girlfriend just got her slide yesterday and I believe she wants me to root it.

it's exactly the same doing it in Mac OSX as doing it in Windows except you don't have to worry about drivers. Make sure you get android SDK for Mac OSX and that you put it somewhere that is in your PATH variable.
But if you feel more comfortable doing it from Bootcamp Windows partition -- by all means do that.

Don't boot camp it... lol
I'll be posting a Mac OSX version of Eugene's Root Method shortly.

sk8rbebop, Fordude, stangri, Thanks for the quick replies! Wasn't expecting anything so soon!
I think I have tried to press CMD+C to stop the script, must have been my problem. lol.
@stangri What do you mean by PATH variable? I have the Android SDK installed in my home folder...
@sk8rbebop That's pretty funny . I'm going to have a go at it right now, I'll edit this post with my results.
edit: I don't know if this is right, but I stop the script when I see the device in offline mode. But when I unplug device, re-plug and run ./adb devices nothing shows up. The same happens if I don't unplug.
edit2: Still nothing. adb never recognizes device after I stop the loop.

I threw up a guide. Hope it helps.
Don't shut off the loop until something displays under the devices.

Re: Question: How to root MyTouch Slide using OSX?
When u connect the slide to your mac and type "adb devices", do you see your phone listed? Crucial first step before moving on.
To make things a little easier for me, I put the sdk tools folder in my path so I could issue adb commands in any directory I want to.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

@sk8rbebop Read the guide and i'm still stuck at the loop. I'm having the same issues as earlier, the device will show for a little bit but right before the recovery screen shows, it dissapears. I was stopping the script once I saw the device, before it "dissapeared". Stopping the script after it dissapears does the same...
BTW, I've noticed that I need to start the adb daemon before I run the loop in order for it to even see the device in the loop. Odd.
@Fordude Yes, if I run ./adb devices when the phone is on I get my serial number and it says "device".
edit: I found that I am running an out of date SDK revision, so I am updating to the newest (revision 6), lets see if that makes any difference...
edit 2: No dice. Lame. Oh well I guess...Try try again. My mac seems to be determined not to let this happen
update: So, I'm getting a nexus. Thanks all for your help, happy hacking!

SOLVED
post removed

Help, Please

So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!

if your not sure if it connected right, open the device manager and see if it is appearing on there.
As far as i know wiping your phone probly won't really help much either.

rstandi said:
So, I have tried all methods posted here. I have not gotten a new sdcard, so that could be it, but if you sift through all these threads, many people have gotten root with the card that came from verizon. Also, would it help to wipe out my phone? Not exactly sure how to do it, but would it help? Also, I hear my phone connect with the usb sounds, but it seems like sometimes I get a quick 3 tones and it doesn't connect. Not sure what that means either.
If anyone can please help, I would appreciate it!
Click to expand...
Click to collapse
There are about 10 threads on adb shell/rooting difficulties already. Why didn't you just bump an older one?

When you connect the usb to the phone what mounting setting did you select? It needs to be on charge only.

So, I have tried all methods posted here.
Click to expand...
Click to collapse
I have rooted two phones using various methods. The Easiest method? Who knows, but this is what I did, I in NO way take credit for this method. This is a culmination of various methods I found on various forums. Thank you to everyone here and on androidforums. Give it a shot.
1. Uninstall HTC sync and PDAnet (If installed)
2. Install drivers as specified for re-flash recovery from revoked team (HTML file has instruction in recovery zip - unrevoked.com/recovery/android-usb-driver.zip
3. Restart PC
4. Install PDANet - junefabrics.com/android/
5. Make sure to complete all steps for PDANet
6. Make default connection on phone, "Disk Drive" AND Turn on "USB Debugging"
7. Shut down the phone
8. Unclick the card
9. Volume down + Power into bootloader
10. Run adb shell in cmd prompt as loop(loop.bat)
11. Start recovery and wait .5 - 1 second after you hear the disconnect sound to click in your card.
12. You should see error device not found change to the other message IF LUCKY.
13. IF NOT,
- Let loop.bat continue to run
- Pull battery, unclick SD card
- Vol down + Power
- Recovery
- Listen for 2 tones (Count aloud..it helps)..
Quick - Insert card right after/during second (Change timing up slightly between tries)
Keep trying, my second root didn't take as long as my first but was easier. I think the unrevoked bootloader drivers with the PDANet usb drivers really make this easier. The other great thing is after you get root, you are set up to do the flash immediately using this method. Its just one more method that worked for me, hope this method helps you succeed. Good luck.

can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.

davisbs999 said:
can anyone definitively explain to me which type of usb connection (e.g. "charge only", "disk drive") is necessary to get into shell and why? I have looked at what the various threads have to say about this. In fact that's the problem--I have found contradicting opinions posted on this matter. In my admittedly inexperienced mind, it seems like I should be fine either way, as long as adb recognizes my device.
Click to expand...
Click to collapse
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.

Studmf said:
I used disk drive the first time, and can not recall what I used on my second device. I see that it is contradicting throughout. I really do not think it even makes a difference because you are doing a battery pull and it never reaches that step on the phone. The important thing in my opinion are the drivers and timing.
Click to expand...
Click to collapse
I rooted my cousin's Droid Incredible and I had Disk Drive enabled. I just want to say THANK YOU Studmf!!!!! I was stuck because I had HTC Sync installed and was stuck forever trying to root the Incredible. The instructions that I WAS following left that detail out.

Solved

Have pretty much everything done but when i do adb devices it tells me it is not recognized as a command. I updated the drivers already so i know thats not the issue. I think im having trouble here, "In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. %SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools." i dont think i edited it correctly, anyway someone could walk me through? Sorry for the hassle ive just been at this for hours and frustration is kicking in haha :laugh:

sorry for delay in getting back to you.
i don't really know. I use linux ubuntu.
kinfaux. a guide for beginners has all the answers.
http://forum.xda-developers.com/showthread.php?t=1552547
hope this helps.
also if you use the kindle fire utility, i think it contains adb & fastboot so no need for sdk. unless your having a go at building your own rom.
pm me if your still stuck.

Here you go
BrooksBlood said:
Have pretty much everything done but when i do adb devices it tells me it is not recognized as a command. I updated the drivers already so i know thats not the issue. I think im having trouble here, "In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. %SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools." i dont think i edited it correctly, anyway someone could walk me through? Sorry for the hassle ive just been at this for hours and frustration is kicking in haha :laugh:
Click to expand...
Click to collapse
Setting your path:
Right click My Computer > Properties > Advanced > Environmental Variables
There should be 2 boxes. Under the bottom box titled "System Variables" you should see a Variable named "Path". Highlight it and click Edit. Add your two paths to the end of the line. Using the above as an example:
%SystemRoot%;C:\android-sdk-windows\platform-tools; C:\android-sdk-windows\tools;
Hit OK a couple times and you are done.

[Q] newbie in over his head

the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.

boathead said:
the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.
Click to expand...
Click to collapse
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.

ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.

boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
Why can't you get into recovery?
Are you choosing recovery mode via the bootloader menu? I didn't think it was POSSIBLE to wipe recovery from within recovery.
Even if you can't, trust me, Doing a factory img restore, or using fastboot to flash custom recovery again is VERY easy. To get the SDK that has needed fastboot tools, go here http://developer.android.com/sdk/index.html#ExistingIDE
And grab the needed exe for your setup(windows 64 or 32bit). Make sure you are getting the "ADT bundle" it's what has needed platform tools. Then just run the exe and follow instructions.
Now u COULD also just Google search for Wugfresg toolkit, and download and use that. Its very easy to use as well. I just prefer to have adb and fastboot installed to my computer so that I can always be good to go. Plus I use Linux so Im not able to use Wugfresh, but knowing how to just use fastboot and adb also makes ya feel like a boss(even though is pretty simple lol)
Don't worry, there is hope, and it's not gonna be difficult. You'll be up again in no time.

because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.

boathead said:
because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.
Click to expand...
Click to collapse
Of course!
I'm always checking in these forums, and I use Tapatalk, and have actually grown fond of Tapatalk notifications, so I SHOULD get a notif if you post back or PM(though I prefer to keep in thread, that way someone else searching for answer to similar issue can find a helpful thread as well)
Yea it sounds like your little one got into twrp and most likely wiped all of /data and /system. Instead of just a regular factory reset which would have left your stuff like flashable zips and all still in /sdcard. That sucks! I've actually done that on accideHahaha
hile back(a mistake you only make once to wipe all of /data AND /system lol, even though can pretty easily be fixed)
Sounds like you could use adb sideload or push to get ROM/gapps zips back on the device, or just go with a total device factory restore, whichever you choose at this point should work just fine.
I'm not sure if there is a way to do this yet, but I've always wanted to put a pin code lock for TWRP. That way if my nephew ever did find his way into there when using my phone, he wouldn't be able to do any damage. If it's not a part of custom recovery yet (I haven't looked actually lol) it would be awesome if someone found a way to add that feature in. Could save a lot of us the hassle in cases like this! Hahaha
I'll check back in the morning and randomly tomorrow (some of the day I won't have a connection, I use Gnex strictly on WiFi) to see if you need any help/tips/clarifying of any steps needed. Once you do this restore process once, you'll be amazed at how easy it can be, and as long as you keep the files on your laptop, you'll be ready to go if you ever need to do it again.

success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.

boathead said:
success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.
Click to expand...
Click to collapse
That temperament is something that is gained. MOST of us have been in that "oh holy crap what do I do now?!?! Im not prepared for this!!" Moments (my first one was on my birthday back when I had DroidX2, and didn't have my own computer to restore it using RSDlite sbf flash.. I accidentally flashed something that didn't work, and was left with no OS stuck in bootloop with no way to get into the bootstrap recovery we had...was without device for 3 days until I could get to a coworkers laptop!! Lol!!!) But the stress goes WAY down after you've restored device once or twice and have the tools at the ready with basic understanding of the steps at least
And as for drivers, I apologize for not warning/informing about that. I forgot that you mentioned you had multiple driver packages downloaded and i was going to clarify which to use(on a Linux setup you don't need drivers and it been a while since I used windows for my device so drivers aren't usually on my mind lol) I think a lot of people use the PDAnet drivers. But if you are connected to internet and just put device in fastboot mode and connect to computer, I think it will automatically find and install the correct drivers needed for fastboot/adb access.(the toolkit can also be used to install correct drivers I believe)
And don't worry, I wouldn't call using toolkit the "cowardly way". SOME people detest/despise use of toolkit since they think it takes away from learning and understanding how to do it without a toolkit. But when you use a toolkit you usually see command prompt correct? (Or at least a setting so you can SEE what it is running as far as commands) so you get to see what its doing, which helps beginners start to grasp the concepts of what it is doing.
Trust me, if you can use the toolkit correctly, you can easily transfer that knowledge to just using fastboot or adb commands.
by the way, fastboot is what's used for factory image restore. ADB is for pushing/pulling files, taking logs, sideloading a ROM/gapps zip that isn't on device, taking/restoring adb backups of system and or data, things like that. Think of adb as the "taker and giver". And fastboot as the "img installer/booter"...imgs being anything from system img files, to data partition img files, boot.img(aka kernel), recovery.img, bootloader update img, radio imgs. Things like that
The reason the knowledge from using toolkit easily transfers over to using just straight up fastboot for example is because of how they word the choices and menus. You will see it says something like "use fastboot to flash new recovery img", which the fastboot command for that in command line equates to "fastboot flash recovery "NameOfRecoveryImage.img" "
(With no quotes of course, and replace "NameOf...." With the actual file name of the recovery.img you have downloaded, and you can rename the downloaded recovery img file to something easier to type out if you want to also)
Basic structure of using fastboot command would be as follows:
fastboot[space]command[space]partitioname[space]filetobeused
Which after used once or twice is very easy to grasp basic usage
So are you able to at least boot into OS now? Also, make sure if you are trying to flash a KitKat ROM, that you install the 2.7TWRP recovery, anything earlier won't work correctly for 4.4based ROMs.
Again, any trouble feel free to ask.
(And apologies for the long rambling posts lol)

yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.

boathead said:
yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.
Click to expand...
Click to collapse
what security do you use on your router? if WEP try changing it. the gnex has issues sometimes with using WEP secured WiFi AP's
also, if using a 5ghz network, I can only get mine to connect to that on channel 153. there are only a certain number of 5ghz channels supported.
might also want to just try forgetting WiFi network and re add?(if it restored the access points by any means including Google backup/restore)
and make sure your router isn't rejecting the Mac address for some reason(and some people will suggest reboot of the router to see if that helps fix it, which I've seen fix many connection issues)

well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.

boathead said:
well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.
Click to expand...
Click to collapse
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details

ashclepdia said:
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details
Click to expand...
Click to collapse
wpa2...but i've even disable all security to see....i've disable firewalls...nothing. it is an arris router that time warner cable provided when i moved to my new place.
and i my phone does show me as connected to my network...just can't get into google. and the phone works just fine at my work. as you know, i've been through several roms and an entirely new OS...so it cannot be the phone...can it?
been through this entire threads, and no joy.
http://forum.xda-developers.com/showthread.php?t=2110225
if you have any ideas, post away. i will be away from access to the internet for a few days, so i won't even have a chance to check in here, but any info in the meantime would be most thanked.

boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
my samsung s5 had the same problem. i wiped out everything and it says i have no os no nothing. i hope if anyone can help, i will be pleased.
the only question is that "how can i get an os and get my phone working"

ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
The same thing happened to me right now, while I was installing CM13 in my Lenovo Zuk Z1. I took a backup from TWRP and copied the same to my pc. Then I wiped all the data from my phone using TWRP. Then I plugged in the Usb back to copy the downloaded files of CM13 to my phone but my pc is not showing the Internal Memory of my phone. I am so freaked out right now. I dont have an OS in my phone and I am unable to restore what I backed up. I am just stucked in TWRP. Guide me through to install CM 13 or atleast revert back to where I started. Any help is appreciated.

Locked out of HTC M8

I have an HTC M8 phone and I set a pattern lock, and then stupidly forgot what it was. Everyone has been telling me to do a factory reset, but some of my photos are not backed up anywhere and I do not want to lose them. I need help either figuring out how to get into my phone, or how to recover the pictures that are on my locked phone. I have my Google account information, but that does not seem to be any help really. Please help!
Thank you!

Do you have a custom recovery? Even if not you should be able to boot to recovery, connect to pc, and in cmd prompt where your adb is(usually platform-tools in the Android sdk) type
adb pull /sdcard
That will download your entire sdcard to your computer. Could also just do adb pull /sdcard/DCIM to only get the camera pictures, other pics are in /sdcard/Pictures
Sent from my Nexus 6 using Tapatalk

After you enter the wrong pattern enough times, does the phone give you the option to sign on via your Google login?
Be aware that the security passwords and patterns exist for a reason, and its not commonly discussed here how to circumvent them. Such knowledge can be used by criminals that steal phones.
Also, I know this doesn't solve your issue, but its far too common to see posts like this. Waiting for a disaster to happen is not the right time to realize you should have been backing up your data. With all the options (SD card, sync to PC, cloud solutions - some built in) there is really no excuse not to be doing so.

redpoint73 said:
After you enter the wrong pattern enough times, does the phone give you the option to sign on via your Google login?
Be aware that the security passwords and patterns exist for a reason, and its not commonly discussed here how to circumvent them. Such knowledge can be used by criminals that steal phones.
Also, I know this doesn't solve your issue, but its far too common to see posts like this. Waiting for a disaster to happen is not the right time to realize you should have been backing up your data. With all the options (SD card, sync to PC, cloud solutions - some built in) there is really no excuse not to be doing so.
Click to expand...
Click to collapse
No , it does not give me that option which is frustrating as that is what many have told me to do. And yes I know, I'm kicking myself for not backing everything up. It has been a few months since I uploaded everything to my laptop. And at this point I was trying any possible option, and was given this forum to try to find help.

I am not sure to be honest... I'm not very knowledgeable about all this which is why I am having such a hard time. How do I boot to recovery? And every time I connect to my pc, it wont let me get any photos from the phone.
HolyAngel said:
Do you have a custom recovery? Even if not you should be able to boot to recovery, connect to pc, and in cmd prompt where your adb is(usually platform-tools in the Android sdk) type
adb pull /sdcard
That will download your entire sdcard to your computer. Could also just do adb pull /sdcard/DCIM to only get the camera pictures, other pics are in /sdcard/Pictures
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse

megan.marie42 said:
I am not sure to be honest... I'm not very knowledgeable about all this which is why I am having such a hard time. How do I boot to recovery? And every time I connect to my pc, it wont let me get any photos from the phone.
Click to expand...
Click to collapse
If the phone is stock (never rooted, bootloader unlocked, etc.); and you don't know what custom recovery is, than you don't have it.