i just got my phone back today and everything for rooting i find is for gingerbread and so i tried to use ruu on the stock phone i just got and for some reason the set up froze..
anthonyly said:
i just got my phone back today and everything for rooting i find is for gingerbread and so i tried to use ruu on the stock phone i just got and for some reason the set up froze..
Click to expand...
Click to collapse
Hi,
Look HERE
malybru said:
Hi,
Look HERE
Click to expand...
Click to collapse
Step 1 | Pre-requisites:
Be on the Stock RUU and be rooted (have superuser flashed). No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere.
How am i suppose to have it roooted with superuser flashed...?
nvm it said exception but... i did parts of it and then i ran controlbear exe
and its comming out like
Waiting ADB.... (41/60)ADB server didn't ACK
* failed to start daemon *
and lastly
Waiting ADB.... (60/60)
Test 2: Booting FAILED
Reboot device manually
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit.....
I tried with htc dev and then i got stuck on step 12... it said mine failed
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
anthonyly said:
I tried with htc dev and then i got stuck on step 12... it said mine failed
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
Click to expand...
Click to collapse
do you have adb and fastboot files installed?(sdk tools)
if yes go to the folder where you have adb and fastboot
put there the unlock token.bin code
open the command window there and then do the command
C:\AndroidSDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.167s
C:\AndroidSDK\platform-tools>
still not working...
anthonyly said:
C:\AndroidSDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.167s
C:\AndroidSDK\platform-tools>
still not working...
Click to expand...
Click to collapse
make sure that you have htc sync and htc drivers installed
Hi,
Windows 7 & 8 drivers are HERE
Sometimes it takes more than one go.
Keep trying.
I thought you're supposed to un install htc sync... Okay I'll try again
Sent from my HTC-Z710a using xda premium
malybru said:
Hi,
Windows 7 & 8 drivers are HERE
Sometimes it takes more than one go.
Keep trying.
Click to expand...
Click to collapse
how do you install drivers?
anthonyly said:
how do you install drivers?
Click to expand...
Click to collapse
Hi,
Plug the phone into the USB socket.
On the PC ,go to Device Manager.
Right click Either the "Android" or the MyHTC ,and go to update drivers.
Manually lead it to the Windows 7 & 8 drivers,and update.
Reboot, and go to the terminal..
malybru said:
Hi,
Plug the phone into the USB socket.
On the PC ,go to Device Manager.
Right click Either the "Android" or the MyHTC ,and go to update drivers.
Manually lead it to the Windows 7 & 8 drivers,and update.
Reboot, and go to the terminal..
Click to expand...
Click to collapse
I tried and it goes like
Android USB Devices>Android Composite ADB interface
then i press update so then i browse for the windows 7 driver
and in the end it comes out as "Window has determined the driver for your device is up to date."
Android Composite ADB interface
and for the HTC dev one, i have a sensation with Virginmobile Canada
So im suppose to click on all other supported devices right?
edit`````
well i uninstalled htc sync and everything else
then reinstalled htc sync (FULL)
no matter what i try i still get
C:\AndroidSDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.167s
Related
I believe I'm bricked, and when I installed the moto stock .img and tried to flash them, I get an <unknown error> in command prompt. Please help me! can anyone give me some step by step instructions for a fix? thanks!
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
This is how I unbricked my xoom it will take you back to stock 3.0, then you will have to wait for the over the air updates before you can root again. Any questions, please ask. I have bricked my xoom a few times. Lol.
tabletroms.com/forums/xoom-general-discussion/1268-how-unbrick-your-moto-xoom.html
Sent from my Xoom using Tapatalk
johnny0911 said:
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes I'm using adb, and yes, I'm in fastboot.
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
rohit3192 said:
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
Click to expand...
Click to collapse
I am in Fastboot protocol support. I try flashing the 4 stock .img in platform-tools, and I get errors.
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.253s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
See, it isn't working. any advice! I really hope I didn't pay $700 for a paper weight!!
I also get the OK, then it fails and says this...
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.727s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 1.319s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
C:\AndroidSDK\platform-tools>fastboot flash userdata userdata.img
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
rohit3192 said:
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
Click to expand...
Click to collapse
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
V0nice said:
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
Click to expand...
Click to collapse
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
hocplyr98 said:
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
Click to expand...
Click to collapse
Got it to work. I Google'd my issue, and I came up with a few possible issues. 1 being the usb cable, and the other being the usb port. Mine was a stock cable, so that wasn't the issue. But when I plugged the usb cable into the back of my pc (directly to the motherboards usb's) it worked, and I did not encounter the "command write failed"! successfully flashed the boot and system... ect img. and now my xoom is working!
Hi there,
I'm trying to install CWM Touch Recovery, but i'm running into problems.
here's my scenario:
HTC Sensation 4G S-OFF, Rooted. Currently using Virtuous Sensation XE ROM
I downloaded the .img recovery image AND the Windows ADB Files
Installed the Naked ADB Drivers successfully
ADB detects my device. Successfully rebooted into bootloader mode via ADB.
Typed 'fastboot flash recovery recovery.img' and got this:
Code:
sending 'recovery' (4876 KB)... OKAY [ 1.348s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.665s
I thought this was related to rooting and such, so i booted back into Android. I'm Using SuperUser 3.0-beta4 and updated to my binaries to 3.0.3.2, but i still get the same error.
What am i doing wrong? Can you guys help me?
You also can't read the forums rules.
This goes in Q&A
pedrohp said:
Hi there,
I'm trying to install CWM Touch Recovery, but i'm running into problems.
here's my scenario:
HTC Sensation 4G S-OFF, Rooted. Currently using Virtuous Sensation XE ROM
I downloaded the .img recovery image AND the Windows ADB Files
Installed the Naked ADB Drivers successfully
ADB detects my device. Successfully rebooted into bootloader mode via ADB.
Typed 'fastboot flash recovery recovery.img' and got this:
Code:
sending 'recovery' (4876 KB)... OKAY [ 1.348s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.665s
I thought this was related to rooting and such, so i booted back into Android. I'm Using SuperUser 3.0-beta4 and updated to my binaries to 3.0.3.2, but i still get the same error.
What am i doing wrong? Can you guys help me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1294779
so i followed this guide http://forum.xda-developers.com/showthread.php?t=1661631&highlight=66732337
and now i'm s off and i'm pretty sure rooted because it said some "Final reboot"
what do i do now?
edit:
So yeah i followed all the steps and i even used a root checker app to check if i have root
i tried flashing 4ext fomr the all in one kit and i got:
C:\Users\Anthony\Desktop\Sensation_4g_All-In-One_Kit_V2.0\data>adb reboot bootlo
ader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\Anthony\Desktop\Sensation_4g_All-In-One_Kit_V2.0\data>fastboot flash re
covery Recoveries/4EXT.img
sending 'recovery' (6116 KB)... OKAY [ 1.529s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.845s
C:\Users\Anthony\Desktop\Sensation_4g_All-In-One_Kit_V2.0\data>fastboot reboot
rebooting...
finished. total time: 3.318s
C:\Users\Anthony\Desktop\Sensation_4g_All-In-One_Kit_V2.0\data>pause
Press any key to continue . . .
what am i doing wrong?
Oh oH and
when i ran the root.bat and after the first reboot i had to reboot it a 2nd time but when i did it the second time it was just the status bar when it booted up and then so i rebooted it when it was like that.
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
3041 KB/s (837916 bytes in 0.269s)
2426 KB/s (22364 bytes in 0.009s)
3361 KB/s (843503 bytes in 0.245s)
REBOOT
1) PRESS ANY KEY WHEN THE PHONE BOOTED PROPERLY/COMPLETELY
Press any key to continue . . .
AGAIN REBOOT
2) PRESS ANY KEY WHEN THE PHONE BOOTED PROPERLY/COMPLETELY (When i got only the status bar)
Press any key to continue . . .
AGAIN!?
NOT FAILED YET ...ITS RUNNING GOOD THEN
EVERYTHING DONE..ROOT SUCCESS...ONE FINAL REBOOT NOW
anthonyly said:
so i followed this guide http://forum.xda-developers.com/showthread.php?t=1661631&highlight=66732337
and now i'm s off and i'm pretty sure rooted because it said some "Final reboot"
what do i do now?
Click to expand...
Click to collapse
flash a recovery if you haven't done it yet(suggest 4ext )
flash a rom and enjoy
rzr86 said:
flash a recovery if you haven't done it yet(suggest 4ext )
flash a rom and enjoy
Click to expand...
Click to collapse
OH really LOL? Because i did super cid from my memory before...
did i mess anythign up?
and where can i learn to flash a recovery :laugh:
and how do i check if the perm root went through 100%
anthonyly said:
OH really LOL? Because i did super cid from my memory before...
did i mess anythign up?
and where can i learn to flash a recovery :laugh:
and how do i check if the perm root went through 100%
Click to expand...
Click to collapse
from here only step 2
http://forum.xda-developers.com/showthread.php?t=1631861
if you used successfully the root tool from the guide you mentioned before then i suppose you are fine
C:\Senny\temproot-sensation-windows>fastboot flash recovery recovery.img
sending 'recovery' (6116 KB)... OKAY [ 1.495s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.812s
C:\Senny\temproot-sensation-windows>
anthonyly said:
C:\Senny\temproot-sensation-windows>fastboot flash recovery recovery.img
sending 'recovery' (6116 KB)... OKAY [ 1.495s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.812s
C:\Senny\temproot-sensation-windows>
Click to expand...
Click to collapse
did you use the temp_root_remove.bat to remove temp root?
rzr86 said:
did you use the temp_root_remove.bat to remove temp root?
Click to expand...
Click to collapse
when am i suppose to do that?
wasn't i suppose to do that after i finshed the whole wire process and then it boots as jsut a status bar then i run that
then i do the "root" one after?
edit:
well i just installed 4ext and then just flashed the recovery from the app so i guess i fixed my problem
Do you mean that you installed 4ext updater and then used it to install the recovery?
If yes then put the rom zip in the root of the sdcard
go to bootloader then recovery and flash the rom
Sent from my HTC Sensation Z710e using xda premium
hello, earlier today i had to downgrade from the rogers jb software to the 2.20 ICS ruu and when trying to re unlock the bootloader it will not re unlock.
Steps:
i ran the xfactor exploit result > CID already changed
in fastboot i reflash my unlock code result> unlock bootloader screen comes up i select yes, it reboots.
when device boots up i skip setup go and enable usb debugging then reboot to bootloader via adb
when the bootloader comes on it still says *** RELOCKED*** am i doing something wrong or....
Device: HTC One X (EVITA)
Hboot: 1.14.0002
Radio: 0.19as.32.09.11_2
Rom: 2.20.... 710 RD
any help is appreciated
fastboot erase cache
then unlock it again
absolutelygrim said:
fastboot erase cache
then unlock it again
Click to expand...
Click to collapse
alright, i will try that, i will report back and let you know how that goes
Update: I Tried that command and to no avail... heres the output on the CMD
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>fastboot
erase cache
erasing 'cache'... OKAY [ 0.125s]
finished. total time: 0.125s
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>fastboot
flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.140s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.140s
C:\Users\Development PC\Downloads\adb_fastboot_and_other_tools\Android>
any ideas?
fastboot flash unlocktoken Unlock_token.bin
Or whatever you have the filename as. I think its case sensitive
Sent from my One X using xda app-developers app
Factory reset then unlock
DvineLord said:
Factory reset then unlock
Click to expand...
Click to collapse
Nope that didn't work either
Sent from my HTC One X using xda app-developers app
USB debugging is enabled?
absolutelygrim said:
USB debugging is enabled?
Click to expand...
Click to collapse
yes, for all intents and purposes it does everything it is supposed to even shows the Unlock Bootloader screen where it says the warranty disclaimer and asks to choose yes or no, i choose yes the phone resets i speed thru the setup enable usb debugging then adr reboot bootloader and it still states "RELOCKED" if i could i would do a logcat but i dont know how or if it's even possible to logcat the unlock process or any fastboot process for that matter...
Can some one helps me with this:
I think i have unlocked bootloader, i tried to flash twrp but got something wrong:
C:\Users\Lucia\Desktop\Nova pasta>fastboot flash recovery "C:\Users\Lucia\Desktop\Nova pasta\RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME.img"
sending 'recovery' (12932 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.427s
i am just a biginner, please help me...
Manolovini2000 said:
Can some one helps me with this:
I think i have unlocked bootloader, i tried to flash twrp but got something wrong:
C:\Users\Lucia\Desktop\Nova pasta>fastboot flash recovery "C:\Users\Lucia\Desktop\Nova pasta\RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME.img"
sending 'recovery' (12932 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.427s
i am just a biginner, please help me...
Click to expand...
Click to collapse
Ok, first be sure that your Bootloader is unlocked, on dialer type:
*#*#7378423#*#* -> Service info -> Configuration -> Rooting status :
Bootloader unlock done
Then download TWRP form here:
https://www.androidfilehost.com/?fid=457095661767112082
To boot into fastboot mode, you should turn the M2 off and connect it to your computer using a USB cable while holding down the Volume Up button with the other end of the USB cable already connected to the computer, the led light should turn into blue.
Flash the TWRP recovery running:
fastboot flash recovery /path/to/the/twrp.img
Thanks bro! But I had already fix this problem. It was some problems with flashtool....
Manolovini2000 said:
Thanks bro! But I had already fix this problem. It was some problems with flashtool....
Click to expand...
Click to collapse
Nice to read that you"ve solved the problem.
Enjoy your M2 !
Manolovini2000 said:
Thanks bro! But I had already fix this problem. It was some problems with flashtool....
Click to expand...
Click to collapse
What problems do you had with Flashtool? because I have the same problem and I don't know how to resolve them
Kelzett said:
What problems do you had with Flashtool? because I have the same problem and I don't know how to resolve them
Click to expand...
Click to collapse
My problem with flashtool was that I couldn't unlock my bootloader, It was some folders and files that made me unable to do it. Try to find on YouTube "Fix bootloader on Flashtool", something like that, probably you will find... It's simple to fix. Hope I have helped.... Sorry about my English!