Related
I'm a bit of a NOOB, so bear with my terminology. My phone was rooted and Nand unlocked (S=off), running Fresh 3.4. It will not accept calls so I have to take it to Sprint. I ran the latest RUU to get it unrooted, but I could not use Titanium Backup to restore my apps. I ran Universal AutoRoot.zip http://forum.xda-developers.com/showthread.php?t=838448 and went through what seemed to be the complete process. At the end I was left with the bootloader menu to boot into the recovery but my EVO will not go into recovery. When I try I get I get a phone with a red triangle. I have tried everything I know (I'm a bit of a NOOB), and I cannot get to recovery or Nandroid. I did a Nandroid Backup but can't get to it. My phone no longer communicates with my computer. I have just moved and need my phone to set up appointments. Please help, I'm desperate. I have posted this to multiple forums.
jminor4326 said:
I'm a bit of a NOOB, so bear with my terminology. My phone was rooted and Nand unlocked (S=off), running Fresh 3.4. It will not accept calls so I have to take it to Sprint. I ran the latest RUU to get it unrooted, but I could not use Titanium Backup to restore my apps. I ran Universal AutoRoot.zip http://forum.xda-developers.com/showthread.php?t=838448 and went through what seemed to be the complete process. At the end I was left with the bootloader menu to boot into the recovery but my EVO will not go into recovery. When I try I get I get a phone with a red triangle. I have tried everything I know (I'm a bit of a NOOB), and I cannot get to recovery or Nandroid. I did a Nandroid Backup but can't get to it. My phone no longer communicates with my computer. I have just moved and need my phone to set up appointments. Please help, I'm desperate. I have posted this to multiple forums.
Click to expand...
Click to collapse
If you ran the RUU and unrooted you WILL NOT be able to do a nandroid restore or be able to go into recovery. Those are things that are only available with rooting.
so how can I get my phone operational, rooted or unrooted?
Run the RUU again. That should bring back to a fully operational state. You won't be rooted though but at least it will work and you can bring it in to Sprint. Just make sure that the RUU you run is the correct one for your software version.
my phone does not communicate with my computer so I can't run the RUU exe. There must be a way to unlock the phone and access to the Nandroid or at least allow the phone to communicate with the computer.
jminor4326 said:
my phone does not communicate with my computer so I can't run the RUU exe. There must be a way to unlock the phone and access to the Nandroid or at least allow the phone to communicate with the computer.
Click to expand...
Click to collapse
Put your phone in fastboot and see if your computer sees it. Do you have the sdk setup by any chance?
jminor4326 said:
my phone does not communicate with my computer so I can't run the RUU exe. There must be a way to unlock the phone and access to the Nandroid or at least allow the phone to communicate with the computer.
Click to expand...
Click to collapse
There is no way to get the phone unlocked unless you ROOT. And as far as getting it to communicate with the computer. Get into your bootloader and use the USB option, I don't remember what its called but I believe it is the top option that should get you connected to your computer then the RUU should run successfully.
the computer does not see the phone in any mode (that I know of). I know someone who does have access to sdk. what needs to be done?
jminor4326 said:
the computer does not see the phone in any mode (that I know of). I know someone who does have access to sdk. what needs to be done?
Click to expand...
Click to collapse
If your bootloader runs then that should work, I have done it a million times when I borked my phone doing stupid stuff lol.
It was not clear the computer saw the phone in USB mode - I tried. Are you saying use the USB option. then what - use Sdk commands?
how do I know the Bootloader is working, or capable of doing the trick?. what signs. The computer still can't see the phone
jminor4326 said:
It was not clear the computer saw the phone in USB mode - I tried. Are you saying use the USB option. then what - use Sdk commands?
Click to expand...
Click to collapse
Nope, you don't have to use any commands at all. Just run the RUU you want from your computer. The RUU as in the script that runs from your computer.
Try fastboot, the top option. You on windows?
AdamHart612 said:
Try fastboot, the top option. You on windows?
Click to expand...
Click to collapse
There ya go, thats the option I was referring to. Sorry I was to lazy to boot into bootloader and see what it was actually called.
Once in fastboot you should see drivers install if its your first time, otherwise (if you can) cd to your android-sdk-windows/tools folder and run "fastboot devices". Your phone should show up in the output. If not then its still not seeing your phone.
If your phone is being recognized then run the RUU for your software version or higher. Sometimes running the RUU takes a few tries.
AWESOME! Thanks Yellowcard8992 and MetalHead. The RUU is running. I started from Bootloader and clicked the exe. Thanks a million! That was my first issue. How do I, or what program or app or whatever do I use, to root my phone 'enough' to use Titanium Backup. This is an invaluable app, when one has Root. I still need to take it back to sprint, and I don't want these Root / S-off issues again.
AdamHart612 said:
Once in fastboot you should see drivers install if its your first time, otherwise (if you can) cd to your android-sdk-windows/tools folder and run "fastboot devices". Your phone should show up in the output. If not then its still not seeing your phone.
If your phone is being recognized then run the RUU for your software version or higher. Sometimes running the RUU takes a few tries.
Click to expand...
Click to collapse
Follow what he is saying. And another thing to add is that you may need to restart your computer in order to get it to recognize your phone too, as well under fastboot to reboot the bootloader. These have both gave me the ability to run the RUU after doing that. And if you downloaded a folder that said it was the ruu thats not what we are talking about, you need to download the file we are referring to here...
http://shipped-roms.com/index.php?category=android&model=Supersonic
As for your question about how to be able to use titanium, your going to have to use a full root method with S-OFF. There isn't really a partial way to do it, so if your using Titanium, then you have to be rooted unfortunately.
Broncos - which is the most up-to-date RUU to use as far as Sprint is concerned? The link Shipped ROMS you provided shows lots of RUUs, I thought .651.5 was newest, but I see a .651.6. There are several permuatations... which one. What about Rooting. Is there a 'good' 'easy' way? Or is there a program like Titanium that doesn't need root. Can you suggest a method? thanks again for being so prompt in your responses. I really feel lots better.
jminor4326 said:
Broncos - which is the most up-to-date RUU to use as far as Sprint is concerned? The link Shipped ROMS you provided shows lots of RUUs, I thought .651.5 was newest, but I see a .651.6. There are several permuatations... which one. What about Rooting. Is there a 'good' 'easy' way? Or is there a program like Titanium that doesn't need root. Can you suggest a method? thanks again for being so prompt in your responses. I really feel lots better.
Click to expand...
Click to collapse
3.30 is the newest.
Root is necessary for backing up protected apps, etc. What hboot version are you? That currently dictates your rooting options.
jminor4326 said:
Broncos - which is the most up-to-date RUU to use as far as Sprint is concerned? The link Shipped ROMS you provided shows lots of RUUs, I thought .651.5 was newest, but I see a .651.6. There are several permuatations... which one. What about Rooting. Is there a 'good' 'easy' way? Or is there a program like Titanium that doesn't need root. Can you suggest a method? thanks again for being so prompt in your responses. I really feel lots better.
Click to expand...
Click to collapse
Your fine, there for awhile I thought that you were gonna have a heart attack. Just remember when your messing with your phone to ALWAYS take deep breaths. As far as the RUU goes you should be just fine running this one: RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe.
And as far as Titanium I'm not sure if there is one, it all depends on what you are trying to backup. What do you use it for?
I previously rooted using Gfree but I opted to use the "s -off" method only instead of doing the whole she-bang. I'm going back and performing all the steps now but I cannot get past getting a root shell. My Terminal Emulator closes but I cannot open it again the second time. It just freezes for awhile but never works.
How do I fix this?
Hey,
Probably a dumb question, but have you tried via ADB? the guide in my signature is the one that i used to get everything unlocked though ADB if you wanted to give that a try.
I use ADB to push the files and that's about it.
Terminal freezes as soon are you enter in su? Are you sure you were properly rooted before?
Also, are you trying the whole rooting process again (as in using rage to temp root)? This isn't necessary if you already have permanent root. You just have to run gfree as stated in the Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unlock_the_Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF
Yeah I'm already permanently rooted. I'll try ur advice later today. Thanks!
Sent from my HTC Vision using XDA App
I'm really trying to root my HTC MyTouch Slide (running 2.1 Build 1.35.531.1) and can't for the life of me figure out how to do it....This is a call for help lol! I need a simple solution if there is one for rooting this phone.
`
Please post any helpful tips
Thanks in advance!
Where are you getting stuck? There's a few methods. Although I don't know if there's some difference with any of the stuff you listed there.
YEA ME 2
Im really bad because when I try to get adb running at the 'adb devices' command my mac osX tells me: "no command found"
so pissed but I really want to gain S=OFF with the best possible procedure no matter how difficult! PLEASE HELP
SefEXE said:
Where are you getting stuck? There's a few methods. Although I don't know if there's some difference with any of the stuff you listed there.
Click to expand...
Click to collapse
First thing I need is to find a decent method eveything I've tired so far does not work. The most of them have been one-click methods so maybe thats the issue. What would you suggest?
i thought the root without a pc method was the easiest for me. i cheated and used a computer to move files over but i didnt really have too much trouble with it. i had a cliq before and could just do the one click method for rooting so i didnt have much experience beforehand.
Had a few questions here. I researched and found this tool. However, I can't post in the thread to ask questions because of my noobtasticness and I searched and couldn't find a similar problem elsewhere.
My first question is, can I use the root and backup tools in the toolkit with no access to the screen whatsoever? I damaged my phone and the touch and lcd screens aren't functioning, but I can plug it in and access memory via usb.
Secondly, I've received the replacement phone. Is there an order I should do all of this in? My first guess is to root/backup the old phone (if possible), then activate the new phone, then root/restore on the new phone. Does that sound about right?
aolbites said:
Had a few questions here. I researched and found this tool. However, I can't post in the thread to ask questions because of my noobtasticness and I searched and couldn't find a similar problem elsewhere.
My first question is, can I use the root and backup tools in the toolkit with no access to the screen whatsoever? I damaged my phone and the touch and lcd screens aren't functioning, but I can plug it in and access memory via usb.
Secondly, I've received the replacement phone. Is there an order I should do all of this in? My first guess is to root/backup the old phone (if possible), then activate the new phone, then root/restore on the new phone. Does that sound about right?
Click to expand...
Click to collapse
The phone with the broken screen isn't rooted already? If it is rooted this may help: http://forum.xda-developers.com/showthread.php?t=2353828
Cosmic Phoenix said:
The phone with the broken screen isn't rooted already? If it is rooted this may help: http://forum.xda-developers.com/showthread.php?t=2353828
Click to expand...
Click to collapse
Thanks, I found that thread too actually, but this phone isn't rooted. I was mainly contemplating root, if it's an option, as a way to take advantage of the more expansive toolset/backup options available to rooted phones in the toolkit. I just wasn't sure if rooting was an option for a phone with a broken screen.
aolbites said:
Thanks, I found that thread too actually, but this phone isn't rooted. I was mainly contemplating root, if it's an option, as a way to take advantage of the more expansive toolset/backup options available to rooted phones in the toolkit. I just wasn't sure if rooting was an option for a phone with a broken screen.
Click to expand...
Click to collapse
Oh, ok. I hope someone comes along to answer your question because now I'm curious... lol.
Edit: Also posted your link in that thread to possibly grab someones attention
Cosmic Phoenix said:
Oh, ok. I hope someone comes along to answer your question because now I'm curious... lol.
Edit: Also posted your link in that thread to possibly grab someones attention
Click to expand...
Click to collapse
Awesome, thanks. I checked on that post and someone responded about having usb debugging on...which I don't. So it looks like I may have to just do the straight backup without rooting unfortunately. :/
You don't need root to use my method, you just need a custom recovery...and remember NOT to boot into the system at all, only recovery or else the stock recovery will be reflashed
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
You don't need root to use my method, you just need a custom recovery...and remember NOT to boot into the system at all, only recovery or else the stock recovery will be reflashed
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Followed the instructions on the post, and when I get to "./adb devices", I get "Permission denied" in terminal. This is with booting into recovery.
That means that the adb binary on your computer doesn't have executable permissions. Nothing to do with the phone.
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
That means that the adb binary on your computer doesn't have executable permissions. Nothing to do with the phone.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Ok, so tried this again, as I'm less familiar with terminal on my Mac than I am on my PC. Got my device discovered, twrp.img loaded into tmp. But when attempting to install I get a "/dev/block/mmcblk0p18: cannot open for write: Permission denied"
Is there a working root method for 10.5.0?
Is the Bin4ry's Root not working anymore?
KF2 10.5.0
No, Bin4ry's Root dont work. it realy messes up the sytem. looking for new method.
xromz24 said:
No, Bin4ry's Root dont work. it realy messes up the sytem. looking for new method.
Click to expand...
Click to collapse
I rooted mine on 10.5.0 a couple weeks ago using Bin4ry's root. It seemed to work fine after that, but I didn't run it too long before attempting to put custom android on it. Ended up flashing the wrong boot loader and then replaced the motherboard. The New one was 10.5.0 as well and rooted using bin4ry then flashed correct boot loader. It's running android like a champ now. No more limited o.s. and haven't run into any issues as of yet.
Can you put up instructions please
Steve1698 said:
I rooted mine on 10.5.0 a couple weeks ago using Bin4ry's root. It seemed to work fine after that, but I didn't run it too long before attempting to put custom android on it. Ended up flashing the wrong boot loader and then replaced the motherboard. The New one was 10.5.0 as well and rooted using bin4ry then flashed correct boot loader. It's running android like a champ now. No more limited o.s. and haven't run into any issues as of yet.
Click to expand...
Click to collapse
I've been trying to figure out how to root my Kindle Fire 2 Gen for a few weeks now....can there be anyway you could like put a video how to do it so people don't get bricked devices and for beginners it would save a lot of people's time and money don't you think i think it would be fair to everyone if they were able to have this info on what software to use and what boot loader who else agrees because rooting devices is a open source process which should be shared with all like i said it would be great to know how to do this process if you can do thank you
Trainboy001 said:
I've been trying to figure out how to root my Kindle Fire 2 Gen for a few weeks now....can there be anyway you could like put a video how to do it so people don't get bricked devices and for beginners it would save a lot of people's time and money don't you think i think it would be fair to everyone if they were able to have this info on what software to use and what boot loader who else agrees because rooting devices is a open source process which should be shared with all like i said it would be great to know how to do this process if you can do thank you
Click to expand...
Click to collapse
I just went by the following guide...
http://forum.xda-developers.com/showthread.php?t=2100963
Followed it exactly as its posted and it worked. The first time I tried I used a different guide and ended up hard bricking to a state that it wouldn't even turn on. Replaced the motherboard with a used one and then followed the guide in the above link and it worked for me. I rooted first using bin4ry then just followed that guide. Then installed a custom android Rom. Make certain of which kindle you have before flashing anything to it.. it's a crappy feeling sitting there looking at a dead kindle. I'm not saying that method will work for everyone on 10.5.0, but I was able to get it to work for mine. First time I've hard bricked a device and it was because I downloaded and flashed a file which was meant for a different model kindle.
Good luck! If it doesn't work then hopefully someone can come up with a more modern method.
question
Steve1698 said:
I just went by the following guide...
http://forum.xda-developers.com/showthread.php?t=2100963
Followed it exactly as its posted and it worked. The first time I tried I used a different guide and ended up hard bricking to a state that it wouldn't even turn on. Replaced the motherboard with a used one and then followed the guide in the above link and it worked for me. I rooted first using bin4ry then just followed that guide. Then installed a custom android Rom. Make certain of which kindle you have before flashing anything to it.. it's a crappy feeling sitting there looking at a dead kindle. I'm not saying that method will work for everyone on 10.5.0, but I was able to get it to work for mine. First time I've hard bricked a device and it was because I downloaded and flashed a file which was meant for a different model kindle.
Good luck! If it doesn't work then hopefully someone can come up with a more modern method.
Click to expand...
Click to collapse
but what version of bin4ary did you use
Trainboy001 said:
but what version of bin4ary did you use
Click to expand...
Click to collapse
Root_with_Restore_by_Bin4ry_v30
Steve1698 said:
Root_with_Restore_by_Bin4ry_v30
Click to expand...
Click to collapse
i tried it and not when im on my kindle my screen is flashing the logo screen and it's really slow what do i do??
Trainboy001 said:
i tried it and not when im on my kindle my screen is flashing the logo screen and it's really slow what do i do??
Click to expand...
Click to collapse
I'm not sure. Mine didn't do that. It seems like the thing ran like **** after rooting, but after rooting I just went on with flashing 2nd bootloader and twrp then installing a custom Rom. So honestly I couldn't tell you much more about it... I just got it to work somehow. Sorry, good luck.
flopower1996 said:
Is the Bin4ry's Root not working anymore?
Click to expand...
Click to collapse
I delved into the guts of Bin4ry's Root a little bit. It uses 3 (IIRC) binaries, "getroot", "su" and "busybox" and plays games with remounting blocks as RW and using getroot to put things where you wouldn't normally be able to. It utterly failed for me on the first go because of the new tightened file permissions everywhere in 10.5.0.
Doing
Code:
C:\adb> adb root
before running Bin4ry's script helped out a lot, and everything seemed to go correctly until the busybox install phase when it ran into a permission error once again.
I may look into this some more tonight; and I may try running both Bin4ry and Qemu root sequentially as per
http://forum.xda-developers.com/showthread.php?t=2075959
That's how I rooted my KF2 once before.
Steve1698 said:
I just went by the following guide...
http://forum.xda-developers.com/showthread.php?t=2100963
Followed it exactly as its posted and it worked. The first time I tried I used a different guide and ended up hard bricking to a state that it wouldn't even turn on. Replaced the motherboard with a used one and then followed the guide in the above link and it worked for me. I rooted first using bin4ry then just followed that guide. Then installed a custom android Rom. Make certain of which kindle you have before flashing anything to it.. it's a crappy feeling sitting there looking at a dead kindle. I'm not saying that method will work for everyone on 10.5.0, but I was able to get it to work for mine. First time I've hard bricked a device and it was because I downloaded and flashed a file which was meant for a different model kindle.
Good luck! If it doesn't work then hopefully someone can come up with a more modern method.
Click to expand...
Click to collapse
I followed it too, and now have custom bootloader & TWRP. I would like to stress a few points:
1) Most of the adb commands didn't work on the first go. What worked for me was typing
Code:
C:\adb> adb root
C:\adb> adb shell
adb# <command>
adb# exit
C:\adb>
in place of
Code:
C:\adb> adb shell su -c "<command>"
2) DO NOT skip the backup instructions. They saved my butt; they may save yours. A fastboot cable is highly recommended.
These directions for grabbing the backups as files worked better for me:
http://forum.xda-developers.com/showpost.php?p=41956668&postcount=3
3) Before I found "adb root" I skipped Step 3 since I couldn't make it work and figured it might not be essential. Ended up with a bootloop. That was when I needed the fastboot cable and my backup files from when I rooted before the "upgrade" to 10.5.0.
4) I was never able to get to fastboot without a fastboot cable before I discovered "adb root". I suspect
Code:
C:\adb> adb root
C:\adb> adb reboot bootloader
will work, but I haven't tried it.
Stupid question...
Hi folks,
Can I ask a really stupid, noob question? I've not had any experience with rooting android devices in the past, but my son has a KF2, v10.5, and he'd like me to root it so he can access the play store. I've read a lot of posts on here about the signed roms and so forth, and because I'm new to the topic a lot of it is going over my head. So some questions:
1) I think, from reading here, that these warnings only apply to replacing the default rom on the KF2, to get a more android like shell. Rooting in itself is a prerequisite for doing this, and doesn't have the associated risk - is that right?
2) I should be able to root the device using the steps in this thread http://forum.xda-developers.com/showthread.php?t=1886460 ? That would then allow me to install the play store? The fact I'm using 10.5 doesn't impact on this?
2b) How much risk is there in this? I think most of the risk is in applying custom roms, and the advice to get a fastboot cable applies to that rather than simply rooting the device?
3) The latest version is v36, but v30 was mentioned below. Am I better going for the latest version or going with v30
Again, sorry for the dumb questions!!
Kev
---------- Post added at 06:14 PM ---------- Previous post was at 05:38 PM ----------
Also, if the bin4ry stuff is okay to use on 10.5, which option should I use when I run it? Been looking through the batch file, and I'm suspecting NEWSTANDARD?
kev1609 said:
Hi folks,
Can I ask a really stupid, noob question? I've not had any experience with rooting android devices in the past, but my son has a KF2, v10.5, and he'd like me to root it so he can access the play store. I've read a lot of posts on here about the signed roms and so forth, and because I'm new to the topic a lot of it is going over my head. So some questions:
1) I think, from reading here, that these warnings only apply to replacing the default rom on the KF2, to get a more android like shell. Rooting in itself is a prerequisite for doing this, and doesn't have the associated risk - is that right?
2) I should be able to root the device using the steps in this thread http://forum.xda-developers.com/showthread.php?t=1886460 ? That would then allow me to install the play store? The fact I'm using 10.5 doesn't impact on this?
2b) How much risk is there in this? I think most of the risk is in applying custom roms, and the advice to get a fastboot cable applies to that rather than simply rooting the device?
3) The latest version is v36, but v30 was mentioned below. Am I better going for the latest version or going with v30
Again, sorry for the dumb questions!!
Kev
---------- Post added at 06:14 PM ---------- Previous post was at 05:38 PM ----------
Also, if the bin4ry stuff is okay to use on 10.5, which option should I use when I run it? Been looking through the batch file, and I'm suspecting NEWSTANDARD?
Click to expand...
Click to collapse
Okay, in case anyone else is interested, it worked fine. I used the new standard method in bin4ry. Worth noting that I was able to run adb commands before starting. If you can't then you need to sort that out first
I've installed the google play stuff now, just trying to log into a google account...
I rooted mime with kingo root with a pc.
Im looking to put gapps on it while leaving it stock. The method I used before was moving google framework and a couple of other things yo /system/app. This no longer works.
I dont have secon bootloder or anything on it anymore. Is there a way anyone knows to just put google play no it, nust being rooted stock?
Wow, 2014!! lol
My stupid Kindle updated before I rooted it and now it keeps failing to root. I've tried binary root and king root with the pc and the app. I'm really irritated about it and even more irritating is how old this device is and the chances of someone fixing the issue being minimal at best. I was gonna use it as a car radio with CM.