Wondering if someone has an hour or so to spare to walk me through the steps of making my phone work again. Last night I did these steps in this order; Revolutionary S-off, CWM, Permanent root, Install custom rom. I installed an AOKP rom and phone kept freezing at the initial setup welcome screen, after reflashing it twice I tried Cyanogen and got the same result. Now I am stuck at the Cyanogen screen and after researching I hear that it is best for me right now to restore my phone to stock through RUU? I am not sure how to go about that as I am looking at the guide and it requires SDK installed. I go to the SDK instructions and it says that I should enable my phone for USB debugging so SDK drivers can install successfully however my phone is in bootloop, how am i suppose to enable usb settings?
Still stuck, I do not think SDK installed successfully on my PC. If any developer has free time I am begging, please message me
what is your fw version?
I signed on really quick just to reply, I will be able to post later today (including my FW version)
Related
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
You don't use adb in bootloader. You use fastboot.
Locking the bootloader does not unroot by the way.
crespo80 said:
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
Click to expand...
Click to collapse
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Leauwie said:
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Click to expand...
Click to collapse
This is true, I've used Wugfresh toolkit too but I had some problem...
I've Nexus S 9023, with wug toolkit I had no problem to install driver with its very complete guide, this part can solve your problem but make attention on other function, for example with it I've also unlocked my phone but when I tried to root my device freeze.
So maybe that not all toolkit function will work well on all Nexus S.
Please stop with this toolkit nonsense.
Its not a driver issue at this point. Its the user using ADB instead of fastboot.
Remove this and that when he is just using the wrong command. This is the nonsense you see when all people know is some toolkit.
Yeah, I'm an idiot, that was not a driver issue
it's just because I usually root/unroot/unlock/lock my android phones once in a while (when I first buy and when I sell them), so I always forget some basic procedures and searching through the forums is always a mess, I spent three hours doing that, before posting...
I had forgotten ADB and fastboot weren't the same... anyway, I solved with WugFresh (I didn't know it, thanks for the tip) but I could have solved even with plain fastboot commands, I know
Anyway, I'm surprised to realize that the real stock ROM is more stable than the rooted and deodexed stock ROM I was using before, now the 3G/2G/airplanemode swithing is blazing fast and the performance drops on some games are gone... I'll never figure out this Android world
Thanks for all your help :victory:
Hi all,
I've had to root my HTC One S for school recently (yes, really), but now I can't install the update that's been released.
When I start the update my phone reboots and enters Clockwork..
I've been trying to unroot my phone, but there's a lot of (different) information out there, and I can't seem to put my finger on it.
For starters, I have no idea what RUU is and I have no idea which stock img I need, since their are more than 20 of them out there..
Can somebody please guide me through?
Thanks!
Tom
Edit: I can't seem to get a Android 1.0 USB driver working.. If I type adb devices it lists no devices.. I've tried like 5 different drivers but none are working.
Edit: My normal USB driver is working. ADB devices returns my device, but when I try to flash the recovery in normal mode, it just says 'waiting for device'.
Hi there,
I'm tearing my hair out here. I have an HTC sensation which I inherited off my girlfriend. I tried to update it OTA and it says something like "variant system version htc" etc. I thought oh maybe somehow the bootloader has been tampered with. I previously had a rooted HTC desire for a couple years. I thought oh I'll just root this as well. I've tried on two occassions over 6+ hours to unlock this sensation via HTC Dev and it just doesn't work. I download sdk and put fastboot and adb in a folder. Connect the phone with USB and go into terminal and type cd and drag the folder in to make sure location is right. Then type ./fastboot oem get_identifier_token and it has either said "permission denied" or most commonly "waiting for device". So after shedding tears of rage, I gave up on that route. I thought instead ok lets see if I can go via OTA. So I called HTC and they rain my IMEI and apparently this phone is French (I'm in Australia) and thats why the OTA updates aren't working. He recommended I call the French HTC support and see what they can do. Funny thing is, I don't speak French.
Before I throw this phone off the highest place I can, is there any way I can get this OTA French update online off someone or a download website?
Model number: HTC sensation z710e
Thanks in advance for any helpful comments. I've done lots of reading and seem to be going in circles. From what I've read there doesn't appear to be a one click root app for the Sensation as existed for my HTC desire.
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
you can easily unlock the device !!!
i think you are missing few points here
1. uncheck fastboot in settings -> power/battery
2. also enable "usb debugging" in settings ->developer options
3.then once you connect the phone from bootloader to the pc
( to go to bootloader ..power off phone ..remove battery , reinsert it ..then hold power + volume down buttons together until you get the bootloader screen a few seconds ))
4. if the connection is proper and you have proper drivers installed the phone says "FASTBOOT USB"
if the phone is saying :HBOOT" press power button once then it should say "FASTBOOT USB"
if the phone is just saying "FASTBOOT" that means connection is not proper or drivers are not installed
for proper connection : you can only use usb 2.0 ports ..usb 3.0 port and usb hubs dont work properly ..also if using pc connect to back usb ports
for proper drivers: you need to have HTC sync installed ..or if you have windows 7/8 32 bit install these drivers ..if you have windows 7/8 64 bit install these drivers (NOTE: if you plan to use these drivers .uninstall every HTC related software from control panel then reboot and install these ..and dont install HTC sync any more)
5. to check proper connection
type this command from your adb/fastboot folder
fastboot devices (it should list your device )
6. then continue with the rest of process
success
Thanks for your reply.
I have good news and bad news.
The good news is I have S-OFF and rooted my phone.
The bad news is that both JB roms I have tried I am unable to get passed choosing my language after the phone has started. I select any language (say english US) and it just freezes and then after 10 seconds restarts. This is with the CM 10.1 and AOSP 4.2.2 roms from development section. When installing these roms I make a nand backup, then wiped data and cache as well as dalvik cache. Then install the rom and JBapps. Any ideas on what to try to fix this? For now I have reverted to my backup.
Onto how I unlocked and rooted.
I was consistently getting an error in terminal when typing ./fastboot oem get_identifier_token
It would say .... ERROR
After a lot of googling I discovered that I was most likely getting that error because my HBOOT was too old for the HTCDEV method.
So I tried the revolutionary method which worked perfectly. Than installed clockwork recovery, gained root (did a dance for joy) and now here I am very close to JB goodness just need to figure out why it keeps on rebooting.
Any help is appreciated. :laugh:
lui8906 said:
Thanks for your reply.
I have good news and bad news.
The good news is I have S-OFF and rooted my phone.
The bad news is that both JB roms I have tried I am unable to get passed choosing my language after the phone has started. I select any language (say english US) and it just freezes and then after 10 seconds restarts. This is with the CM 10.1 and AOSP 4.2.2 roms from development section. When installing these roms I make a nand backup, then wiped data and cache as well as dalvik cache. Then install the rom and JBapps. Any ideas on what to try to fix this? For now I have reverted to my backup.
Onto how I unlocked and rooted.
I was consistently getting an error in terminal when typing ./fastboot oem get_identifier_token
It would say .... ERROR
After a lot of googling I discovered that I was most likely getting that error because my HBOOT was too old for the HTCDEV method.
So I tried the revolutionary method which worked perfectly. Than installed clockwork recovery, gained root (did a dance for joy) and now here I am very close to JB goodness just need to figure out why it keeps on rebooting.
Any help is appreciated. :laugh:
Click to expand...
Click to collapse
You've done soff via revolutionary means you've got 1.17 firmware.. For ics and jellybeans you need 3.32/3.33 firmware.. Grab the latest firmware from kohr-ah firmware thread in sensation development section and flash it.. Then flash any ics/jb rom
Sent from my HTC Sensation using xda premium
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
babaghanush said:
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
Click to expand...
Click to collapse
Find flow ROM with expansion .exe and try it to sew from a computer.
could you further elaborate please
lykosha said:
Find flow ROM with expansion .exe and try it to sew from a computer.
Click to expand...
Click to collapse
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
babaghanush said:
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
Click to expand...
Click to collapse
Try to find driver on the web-site of producer. Set them. Overload a vehicle in Bootloader. In the controller of devices on компе must be determined your device. Then on a computer start sewing - .EXE.
Did you get this problem resolved? I have the exact problem with the exact phone!!!
thank you very much
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Same here. Any help for us would be great. Thanks.
shd128 said:
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Click to expand...
Click to collapse
kijp15 said:
Same here. Any help for us would be great. Thanks.
Click to expand...
Click to collapse
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
smit.sanghavi said:
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
Click to expand...
Click to collapse
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
kijp15 said:
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
Click to expand...
Click to collapse
I disabled USB debugging. Rebooted to bootloader. Fired up 'fastboot devices' on cmd and could see my phone. This tells me that I do not need USB debugging on fastboot.
If you see an unknown device in Device Manager while in fastboot then use Universal Naked Driver to install the drivers. But since you don't, you'll need another PC to do this stuff. Once drivers are installed, you can do a 'fastboot reboot recovery' to get into recovery and fix the the problems. The first thing I advice is to flash a touch recovery. The rest is up to you.
Flash back the original soju firmware back onto your device by first using "nexus s root toolkit v.1.8.2 by wugfresh". It may take a little of your time downloading the roms and installing the drivers but trust me it should be working and your phone will boot into stock android 4.1.2. You can then root your device and install custom recovery as normal. Anything do pm me :laugh: ps, click the bricked option one the software is loaded up and remember to connect your device only and remove other phones from your computer