Related
Hi,
I hope someone can help me out. I recently updated to 4.4.1 via Clockworkmod. The update worked fine but now I'm unrooted. I still have the SU app, it just doesn't do anything. Is there a way to remove it without rooting again? If not what's the easiest way to root the device (bootloader is unlocked and currently have stock recovery)? The first time I rooted the bootloader was locked and the process I used unlocked and rooted in the same step.
Thanks for your help!
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
simms22 said:
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
Click to expand...
Click to collapse
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=how+to+flash+custom+recovery+fastboot
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
simms22 said:
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
Click to expand...
Click to collapse
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
danotoriusodo said:
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
Click to expand...
Click to collapse
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Saturn2K said:
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Click to expand...
Click to collapse
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
danotoriusodo said:
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Saturn2K said:
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Click to expand...
Click to collapse
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
danotoriusodo said:
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
Click to expand...
Click to collapse
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Saturn2K said:
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Click to expand...
Click to collapse
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
danotoriusodo said:
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
Click to expand...
Click to collapse
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Saturn2K said:
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Click to expand...
Click to collapse
Thanks but that's what I've been doing and what's driving me crazy. ADB works when the phone is on. It recognizes my device and reboots on command. I get to the bootloader where it still recognizes my device. Once I select recovery, the phone comes up with the yellow triangle in device manager and I can't sideload after I select the option. A friend of mine who;s sideloaded before watched me do it and was just as confused. Any other suggestions?
**Update**
So for some reason the driver package installed via the SDK manager doesn't have the Nexus 5 "hardware id". I needed to add these three lines in the .inf file within the usb drivers folder:
;Google Nexus 5
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0232
One I added those and updated the driver I was able to sideload.
Thanks again for your help
Background
Use to own several HTCs and did the root thing and messed around with different kennels, roms, tweaks etc. Problem is I switched to iphone several years ago and now I am back with a brand new HTC M8. I am rooted with weaksause and Soff with sunshine ($25.00). Now I have been reading for three days and stuck. This ADB is totally new to me and the rooting process has change since i did it several years ago so now I am a noob.
This is where Im at. S-OFF and rooted with weaksauce. I loaded ADB. When I type in the command "adb version" it acknowledges the version. When I type in "adb devices" none are listed. My reasearch tells me I need to install drivers.
Can somebody walk me through installing the drivers into ADB and which ones are the right ones? I watched several vids but they are not clear and skip steps etc.. I need simple layman terms......I am trying to flash one of the recovery program so I can start tweaking but mannnnn I can not move forward. I am so close. So I guess what I am trying to do is install drivers to my computer so it can communicate with my phone correct?
Thanks
for any help
ok I got it to communicate. My device is listed when I type command adb devices. So now I need to figure out how to flash TWRP. Any really good instruction out there, I am sure there is....
Download the TWRP 2.7.0.2 img from the Teamwin website, rename the file to something easy like "twrp2702.img" and place that file into your adb/fastboot folder.
Boot the phone into the bootloader (make sure you first disable Fast Boot in Settings > Power)
Fast Boot is not to be confused with fastboot LOL
The former is a HTC feature to speed up boot time, the latter a protocol to communicate between PC and phone.
Open a command prompt from your fastboot/adb folder.
Hopefully you also have the fastboot drivers installed, try it with
Code:
fastboot devices
If you get the alpha numeric string, you're good to go
Next
Code:
fastboot flash recovery twrp2702.img
Once that is done
Code:
fastboot reboot
Uninstall Weaksauce if not done already.
Then download the flashable SuperSU zip and flash it in TWRP to gain permanent root.
Ok GOT IT!!!!
One more question, I am in TWAP program now, what to I need to do to get perm. root? I know to uninstall weaksauce. Is there anything else I need to do while opening it for the first time before I start flashing tweaks? Because on the sunshine site it say after you get S Off properly root you device?
As I was exiting the program it said your device is not rooted and to install SuperSu in which I did?
When I went into SuperSu loader in apps it said it needed to be updated from play store and I hit play and it went through TWRP and loaded and shut phone off. I powered it.
I would assume I am completely rooted at this point?
Looks like I finally achieved it! After going through the steps I am rooted. I downloaded SU Root checker and it verified that I am rooted.
swatcop1 said:
Looks like I finally achieved it! After going through the steps I am rooted. I downloaded SU Root checker and it verified that I am rooted.
Click to expand...
Click to collapse
Great! Now remember, before you do anything else, run a full nandroid of your stock system in TWRP (Backup, then just swipe the button) and copy it to somewhere safe as in: off the phone!
Congrats! Enjoy!
Been a while so i tried read up a bit. Thank you for taking the time to read this and/or dropping a little knowledge on me.
I Install Weaksauce. Run.
Install SuperSu.
Run firewater
can someone tell me where to get adb tools? have never really messed around with adb.
Install CWM or TWRP (which is more stable?)
nandroid
install custom rom
Correct order? and some help with the adb would be appreciated. Thanks again
If nobody else helps with adb stuff, I'll link in a little when I get on the computer. Try firewater first. If it fails and says it will never work with your device in the error, you will need to DL and use sunshine. It will cost you 25 dollars but worth it if you ever want to have control of your device.
After you use firewater or sunshine, whatever you have to use. reboot, uninstall weak sauce and SuperSU.
Then back into fastboot.
Definitely use twrp
After installing twrp with fastboot,
After you have twrp, flash SuperSU zip found here on xda in chainfires thread. This will give you your permanent root.
Then you can nandroid, and rom all you want.
silver04v said:
If nobody else helps with adb stuff, I'll link in a little when I get on the computer. Try firewater first. If it fails and says it will never work with your device in the error, you will need to DL and use sunshine. It will cost you 25 dollars but worth it if you ever want to have control of your device.
After you use firewater or sunshine, whatever you have to use. reboot, uninstall weak sauce and SuperSU.
Then back into fastboot.
Definitely use twrp
After installing twrp with fastboot,
After you have twrp, flash SuperSU zip found here on xda in chainfires thread. This will give you your permanent root.
Then you can nandroid, and rom all you want.
Click to expand...
Click to collapse
where do i put twrp.img
camf3xu said:
where do i put twrp.img
Click to expand...
Click to collapse
Youbplace the image in your adb folder in.....sdk/platform-tools.
camf3xu said:
where do i put twrp.img
Click to expand...
Click to collapse
Into the same folder where your adb.exe and fastboot.exe are.
To get adb/fastboot try this great little tool: http://forum.xda-developers.com/showthread.php?t=2317790
Make sure USB debugging is enabled in Developer Options.
Then open Device Manager on your PC, connect your phone booted to Android via USB cable and note any changes. You should see an entry for adb interface. If it doesn't have a yellow exclamation mark next to it, you probably have the correct driver installed. If it does, right click the entry and update the driver.
Check the connection with the command:
Code:
adb devices
from a command prompt opened from the adb folder.
If it returns a string of letters and numbers: Congrats, your adb is working.
Next boot the phone to hboot.
Connect it via USB and you should see a new entry for the fastboot interface.
Proceed as above.
To test the connection issue
Code:
fastboot devices
If you get the connection, the command to flash TWRP is
Code:
fastboot flash recovery twrp.img
Check out the 2 other posts many get firewater to work using superuser with weaksauce app instead of supersu. Check out the two other posts below first is the main one.
http://forum.xda-developers.com/showthread.php?t=2787587
http://forum.xda-developers.com/ver...firewater-s-off-fail-bottle-chugging-t2821691
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
TRiP_E said:
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
Click to expand...
Click to collapse
You can connect to ADB but the adb push command isn't working when you try to move the ROM.zip to the device?
Get a new OTG cable.
The nandroid backup you made should have been done in TWRP and stored on extsdcard instead of the online backup, online backup is crap because it only works in certain conditions, it's useless when the device can't connect to a network.
Sent from my SM-S903VL using Tapatalk
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
TRiP_E said:
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
Click to expand...
Click to collapse
Yeah, new cable seems to be your only option.
Sent from my SM-S903VL using Tapatalk
Alright then, I'm going to go see where I can buy one. Thanks for the confrirmation.
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
TRiP_E said:
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
Click to expand...
Click to collapse
Try rooting the device and then use the Stick Mount app, if your device has the hardware to support OTG, that should enable it, but if your device does not have the hardware to support OTG then it doesn't matter what you do softwarewise or what you modify, it has to have the hardware or it can't do it at all.
Things like this are why I'd never buy or own a ZTE device of any kind. Relatively soeakibg, they are all junk.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
TRiP_E said:
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
Click to expand...
Click to collapse
If you can use adb shell or fastboot, you can try getting a copy of system.img from someone with your exact device and dd or fastboot flash the img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
After reading other pols forums, it seems that I didn't have to delete the internal storage........
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
Sideloading a ROM won't work.
Try
adb reboot bootloader
If you can boot to bootloader or fastboot you can try finding the firmware for another device that has all of the exact same hardware components that your device has then try fastboot flashing it or extract the separate .imgs from the firmware and use the fastboot commands to flash the boot.img and system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
can't get into fastboot, ADB command says error: closed, while doing the command in terminal in the TWRP menu keeps me on ZTE screen (only reboot recovery works, not as ADB command but in terminal).
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
help.
equitube said:
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
Click to expand...
Click to collapse
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
filldapipe said:
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
Click to expand...
Click to collapse
Did you ever get the TWRP for this? I have it in my dropbox pm me.
The issue were running into is that the TWRP on this model can't see the ext sd. The backup is 1.5 or 2gb which is usually too large to fit on the internal SD
Slacker is working hard at modding the Fstab file to make TWRP see that storage. Any ideas please let him or I know([email protected] or here )
I'm also working on an EquiMods custom ROM for this. Bare bones battery saver, switchable to performance when needed.
Anyone know if and how these can be overclocked?
I have a deodex rom done for this phone and also should have the working twrp recovery by morning. The cm11.0 ive been working on is almost done. I hope Everytime i flash it to phone i get white screen. Also im going to install xposed on it in the morning. I think i found the fix for that to work
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
edsfunsite said:
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
Click to expand...
Click to collapse
They obviously got something to work since there are members in this thread that have TWRP installed on their devices, that means they can at least root the device but I doubt there are any ROMs for this device.
Sent from my LGL84VL using Tapatalk
I've rooted my N817 but never made an Nandroid backup. I still have TWRP up and working but I've tried to flash the 2 roms I know of....they both "install" but when I try to boot It stays in the ZTE screen...Help!
Let me explain what I did first. I rooted my phone and used with the stock rom for a while (I needed to use some apps). So, I decided to unroot and lock the bootloader again. I used one script and flashed the rom I downloaded. But... it was the wrong rom. My rom is the XT1929-5. I flashed XT1929-6. The problem is. It returned a lot of error during the installation and the bootloader closed in the end automatically. Now, my phone is running but without internet connection. So, I can't unlock the bootloader (I can't go through the initial setup part). I already tried to reflash using Rescue assistent, but it says that it can't find the right version of my system. It looks like my baseband is not working. I waited some months for a system update so I would be able flash it even with a locked bootloader. But It didn't work. I've been searching for solutions for a long time. I know it's possible to fix. I just need help to figure out how.
Thanks in advance.
AFAIK a device with locked bootloader only will run device's pre-installed Stock ROM.
Re-flash device's original Stock ROM. You achieve this with the "ADB Sideload" method,
jwoegerbauer said:
AFAIK a device with locked bootloader only will run device's pre-installed Stock ROM.
Re-flash device's original Stock ROM. You achieve this with the "ADB Sideload" method,
Click to expand...
Click to collapse
Hi, there. Thanks for your help. But I'm not sure about how I could do the ADB sideload method. This is one thing that I still didn't try. Could you help me with that? Maybe with a step-by-step tutorial. Thanks
You run the following ADB command sequence
Code:
adb devices
adb reboot sideload
adb sideload <FULLPATH-TO-STOCKROM-ZIP-ON-PC>
adb reboot
Thanks. Does it need to be the version that came with the phone? Or could I flash the last update?
jwoegerbauer said:
You run the following ADB command sequence
Code:
adb devices
adb reboot sideload
adb sideload <FULLPATH-TO-STOCKROM-ZIP-ON-PC>
adb reboot
Click to expand...
Click to collapse
I tried using the newest update. It returned an error in the string
adb reboot sideload
Also the installation was abosted in the phone in the string
adb sideload <FULLPATH-TO-STOCKROM-ZIP-ON-PC> (of course. I changed the name properly)
Any other idea?