Hi Everyone,
sorry in advance for what is probably a dumb question. I have a HOX on Orange UK. It is successfully rooted but still on stock firmware - Android 4.0.4, HTC Sense 4.1, Software 2.17.61.3.
When checking in about I am told that there is an update available. I have downloaded it and can see that the file is called OTA_ENDEAVOR_U_JB_45_S_ORANGE_UK_3.16.61.6-2.17.61.3_release_3015.zip. However when I click in stall the phone reboots into teamwin recovery project v2.3.3.0. I then select Install adn browse to theis file which is in /sdcard/Download but the install keeps failing MD5 check. Unckecking the MD5 check still results in a failure since the error message is that the signature verification fails. Unchecking that still results in a failure- this time because of an "assert failure" whatever that is.
So a few questions.
1) Is this update worth having?
2) I am new to Android (10 years on a blackberry). Am I on ICS now and is this update to JB?
3) I am interested in a custom room. I really like the look and feel of the HTC sense and I have seen here that there are a lot of Sense custom roms. I presume I should stick to one of those. My main question is which one to install and what are the advantages. The honest truth is that apart from the Orange boot up and shut down logo there isn't much bloatware on this phone.
Thanks in advance for helping out a noob...
Yes its worth it, you have to flash back the stock recovery ! After that you can update.
Download this file and rename it to recovery.zip and copy it to your fastboot folder on the pc
http://db.tt/U5CK4noo
After that you put the phone in the bootloader/fastboot usb mode
Open a command prompt inside the fastboot folder and flash the stock recovery with these commands
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Reboot the phone and try to update again
Mr Hofs said:
Yes its worth it, you have to flash back the stock recovery ! After that you can update.
Download this file and rename it to recovery.zip and copy it to your fastboot folder on the pc
xxxx://db.tt/U5CK4noo
After that you put the phone in the bootloader/fastboot usb mode
Open a command prompt inside the fastboot folder and flash the stock recovery with these commands
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Reboot the phone and try to update again
Click to expand...
Click to collapse
Thank you. I am afraid I need you to spell it out in a little more detail since I rooted my phone using the Hasoon toolkit so that did all the command prompt side of things. I do know how to launch command prompt but that is about it!!! Sorry
Well you can check if the toolkit you used is capable of flashing a self providided recovery.img
Otherwise you have to install the HTC drivers and download the fastboot files from me
http://db.tt/ldx3qOOU
Place the files in a folder just like this
C:\fastboot\fastboot files i gave you
Then you open a command dosprompt inside the fastboot folder
Then you keep the phone on the homescreen and type
adb reboot bootloader
This will reboot the phone into the bootloader and you should see there FASTBOOT USB (connect the phone to the pc)
Then you do the commands i posted earlier
(Make sure usb debugging is enabled in the settings menu of the phone)
after flashing the stock recovery and updating root is lost, but superSU still there. How can we obtain root back? thanx
You have to reroot the rom again just like you did on ICS
geomad said:
after flashing the stock recovery and updating root is lost, but superSU still there. How can we obtain root back? thanx
Click to expand...
Click to collapse
u have to unlock the bootloader again over at htcDev http://www.htcdev.com/bootloader
*happy new year Mr Hofs!
beanbean50 said:
u have to unlock the bootloader again over at htcDev http://www.htcdev.com/bootloader
*happy new year Mr Hofs!
Click to expand...
Click to collapse
Happy newyear Mr Bean
And if he had the unlock_code.bin file he can flash it with fastboot
Fastboot flash unlocktoken unlock_code.bin
Mr Hofs said:
Happy newyear Mr Bean
And if he had the unlock_code.bin file he can flash it with fastboot
Fastboot flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Do I have to flash clockwork first or can it be done with stock recovery? Thanx!
Happy new year!
you can do this with the stock recovery because you flash directly from the bootloader and not from the recovery
Well im trying to flash via fastboot but I get :
Code:
C:\onexroot>Fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.292s
PS. when in fastboot the phone state at the top is *** UNLOCKED ***
When I type 'su' in terminal
Code:
[email protected]:/ $ su
1|[email protected]:/ $
but apps still doent have superuser privilages
geomad said:
Well im trying to flash via fastboot but I get :
Code:
C:\onexroot>Fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.292s
PS. when in fastboot the phone state at the top is *** UNLOCKED ***
When I type 'su' in terminal
Code:
[email protected]:/ $ su
1|[email protected]:/ $
but apps still doent have superuser privilages
Click to expand...
Click to collapse
So the bootloader is actually unlocked ! Then forget the unlocktoken step !!! Now you have to flash the custom recovery and from there the super user root.zip
Mr Hofs said:
So the bootloader is actually unlocked ! Then forget the unlocktoken step !!! Now you have to flash the custom recovery and from there the super user root.zip
Click to expand...
Click to collapse
Thank you! so my problem is I'm still in stock recovery? cause superSu is still in my apps from ICS.
Lets get it straight...you updated the phone to JB and after that you restored apps (titanium backup ?) You need to reroot the stock JB rom properly again like flashing the root script from a custom recovery
i updated from OTA , so i didnt restore any apps. and when i write 'su' at terminal i dont get any errors. doesnt that mean su is installed?
If SU is installed you should see the SU app in the apps list ... My recommendation would be to reflash the custom recovery and re-apply the root
Mr Hofs said:
If SU is installed you should see the SU app in the apps list ... My recommendation would be to reflash the custom recovery and re-apply the root
Click to expand...
Click to collapse
yes, i can see the SuperSU app. but it seems that the apps ingore it. Don't know.. I'll reflash recovery and root and let you know! Thanx anyway!!
Its the best thing i can think of at the moment
Done - everything works perfect now! Thanx guys
Nice !
CASE CLOSED
Related
Hello
Yesterday i unlocked bootloader on htc one x. Then i tried to root it but when i finished my hox did reboot and then reboot all the time. It goes on start screen of android and then reboot again. I cant do anything. Any idea or help?
How did you root it?
Did you flash a ROM without flashing its boot.img and fastboot erase cache?
Did you install a custom recovery?
What screen are you stuck on? "htc quietly brilliant"?
I remember when this happened to me when I first tried to root my phone (First Android phone actually) lol I freaked out.. In my case it's because I didn't make a full wipe after unlocking bootloader and flashing Cyanogen, just booted into Recovery, full wipe/wipe cache and it worked.
Tell us what you did like BenPope said, did you flash the boot.img for the ROM you installed?
the first i did was to unlock bootloader from htcdev. Afther that i tried to root by a guide from this forum:
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot r3 - DOWNLOAD (ROMraid) - MD5: a16bff582cb0e25fd3b422652d753ca7
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r1 - DOWNLOAD (ROMraid) - MD5: c79821d5d75d57dff8a5ffe7493241fd
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
That was the steps. I didnt tried to put a custom rom yet. And the worst is that i need my number and i dont have an another device with micro sd. :/
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
BenPope said:
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
Click to expand...
Click to collapse
I tried the first one and after i saw that my hpox rr all the time i tried the second one.
You mean this method?
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
I do now and nothing. Cant get the command.
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Edit: ahh, is it "command not found" when you try to run fastboot?
BenPope said:
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Click to expand...
Click to collapse
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
Click to expand...
Click to collapse
You could just flash a rooted rom and kernel now, it should work fine.
Flash this recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Install a rom from recovery, you can mount usb from recovery to copy rom to phone.
Then flash the kernel from fastboot that acompanies the rom.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
Click to expand...
Click to collapse
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
BenPope said:
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
Click to expand...
Click to collapse
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
RohinZaraki said:
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
Click to expand...
Click to collapse
He did. Thanks for playing.
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
The command you did was correct but you flashed the stock recovery, flash clockworkmod recovery to proceed.
BenPope said:
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
Click to expand...
Click to collapse
I used that command fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
So i think i didnt something wrong.
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
BenPope said:
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
Click to expand...
Click to collapse
Ok sry. I mean i tried boath of them.
IoSpy said:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Click to expand...
Click to collapse
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
BenPope said:
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
Click to expand...
Click to collapse
Ok i did and i have this screen now.
I decided earlier today that I'd try to root my one X, but I wound up screwing up to the point that I'm lost. I accidentally wiped the system while in recovery, and when I rebooted, it kept looping. By pressing the power/down button, I can get into the bootloader, and from there into recovery. In the recovery, I was able to look around using a file manager but only found empty folders.
I used adb push to try to get a rom onto the phone, but I'm not able to flash it. When I go to reboot, it informs me that there's no OS installed.
If anybody has any idea what I can do, it would be much appreciated.
im assuming you already unlocked your phone
1.Enter fastboot by holding power + volm down.
2.Select fastboot
3.plug in USB
4.flash recovery with the command: 'fastboot flash recovery <name of recovery here>
5.flash the boot.img that came with the ROM, usually it's located within the zip file
6.erase cache using command: 'fastboot erase cache'
7.select Hboot to return to main menu
8. go to recovery
9. wipe data/factory reset, wipe cache, wipe dalvik from advanced options, format system from mounts and storage menu
10. in mounts and storage, select mount usb
11. copy over ROM zip
12. Install from ZIP
13. reboot system
PS. your phone is only bricked if it can't turn on. obviously it's not going to boot up if there is nothing to bootup, lol
Just ensure your recovery is a recent version, like clockworkmod 5.8.4.0, otherwise mounting won't work.
Thanks for the quick reply. I don't entirely understand how to flash the recovery, however.
I assume I'm running the command on the computer. How do I know what to type in as the recovery?
Mate, did you even do your research before attempting any of this?
Anyway,
Make sure you got HTC sync installed, also Android SDK
1/ Open to a command prompt by going: start -> type in cmd
2/ browse to your folder containing fastboot and adb using the 'cd' command
e.g. My fastboot folder is located at "C:/htc/fastboot" so I would type: 'cd C:/htc/fastboot'
If you're using the one from SDK it could look like C:\Users\Steven\AppData\Local\Android\android-sdk\platform-tools
3/ enter the commands -fastboot flash recovery ...., fastboot flash boot.... etc.
Not nearly as well as I should have. I learned the hard way I guess. Thanks for putting up with my cluelessness though.
I've done as you said, but when I tried to boot into the recovery, I got stuck on it looping the "htc quietly brilliant" screen.
You sure you flashed it Successfully?
and downloaded clockworkmod from here?
http://forum.xda-developers.com/showthread.php?t=1594819
Code:
D:\Android>fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
< waiting for device >
sending 'recovery' (5742 KB)... OKAY [ 1.021s]
writing 'recovery'... OKAY [ 1.506s]
finished. total time: 2.528s
D:\Android>fastboot flash boot boot.img
sending 'boot' (4988 KB)... OKAY [ 0.885s]
writing 'boot'... OKAY [ 1.257s]
finished. total time: 2.142s
D:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.116s]
finished. total time: 0.116s
Could it be that I have a bad boot.img? I'm using one out of the renovate 8.1.0 ROM.
I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?
seaneschen said:
I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?
Click to expand...
Click to collapse
what command are doing? to unlock i mean
or better yet run through the steps u do to unlock bootloader
ali3nfr3ak said:
what command are doing? to unlock i mean
Click to expand...
Click to collapse
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev
seaneschen said:
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev
Click to expand...
Click to collapse
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2
elmonen said:
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I have the US version.
seaneschen said:
I have the US version.
Click to expand...
Click to collapse
i would suggest that you post this in the in the AT&T, Rogers HTC One X, Telstra One XL forum as thiforum is for the international one x
Oh my....... never noticed. Please don't use Clockworkmod and instead use TWRP, you might brick
dear all
i am using GN 4.2.2 stock
at the moment i can go to fastboot and i flash clockwordmod recovery v6.0.1.9
i did this because my phone startted to reboot
at the GB logo
.
now problem is i cant flash ROM to sdcard.
here is the output
=================
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.435s
==========================
sending 'radio' (12288 KB)...
OKAY [ 1.353s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 2.060s
===================================
in recovery when i am trying to mount sdcard.
===============
Error mounting sdcard
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
amith007 said:
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
zakisays said:
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
Click to expand...
Click to collapse
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
zakisays said:
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
Click to expand...
Click to collapse
Perhaps you didnt read the post, so I will quote it here:
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
Zepius said:
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
zakisays said:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
Click to expand...
Click to collapse
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
samersh72 said:
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
Click to expand...
Click to collapse
i gave the following command
H:\Galaxy Nexus (yakju)>adb -d push "H:\Galaxy Nexus (yakju)\Stock-Unroot Jelly
Bean GNex GSM.zip" /sdcard/
its almost 2 hours now the command hasnt finished executing, hope all is going ok
ok i cancelled the previous command .
rebooted to recovery , mounted /data and /system
then reran push command.
got the zip file into sdcard
then tried installing , error generated
finding update package
opening update package
installing update
Installation aborted
!!!!!
please help
thanks
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
well i followed the steps.
i got error as below
===================
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe flash bootloader bootloader-magu
ro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.507s
================================
i hope now its clear what i am facing.
i can boot to fastboot and to recovery , but cant do anything else
if i flash something then the "Too many links error" comes
thanks for the help , is there anything else i can try
========================
ok i found something interesting
when i flash something i get the error " Too many links"
then when i run fastboot.exe devices , i get
???????????? fastboot
and after reboot i get
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe devices
My IEMI number fastboot
y is this happening
*sigh* ...
Op, uninstall all drivers, reboot your system;
Connect device in fastboot to PC, manually update drivers, disconnect device, reboot PC
Connect device again, flash recovery, after it finishes, disconnect USB, use volume keys to "reboot recovery", reconnect USB, manually update drivers again
'adb devices' should return your SN
'adb push ROM.zip /sdcard/' or if that doesn't do it, 'adb push ROM.zip /data/media/'
Sent from my Nexus
Hi guys,
I flashed stock back to my phone and relocked the bootloader by "fastboot oem lock".
I been stuck with this for the last 2 days searching for solution on how to get my phone unlocked and rooted again.
This is what I have tried so far:
1. Rumrunner 1.10.605.10 and 1.10.605.15 firmware (flashed 1.10.605.10 and updated to 15) - Run just fine, but it does not change anything on the phone. Still shows RELOCKED S-off and NO Root.
2. Firewater (temp-root method) - Temproot: Root acquired. Firewater: "there really isn't a helluva lot to do here. bye bye"
3. Flashing CM recovery - failed remote not allowed
Could someone please help me to get back Root access and UNLOCK my phone?
Thank you in advance.
If your s-off, all you have to do is fastboot flash a custom recovery.
Code:
fastboot flash recovery name_of_recovery_file.img
Then flash superuser zip thru recovery. Then you will be rooted. Also it is a myth that you need to relock the bootloader to do an ruu, so that wasnt really needed. Not sure exactly how to unlock the bootloader again.
cmlusco said:
If your s-off, all you have to do is fastboot flash a custom recovery.
Code:
fastboot flash recovery name_of_recovery_file.img
Then flash superuser zip thru recovery. Then you will be rooted. Also it is a myth that you need to relock the bootloader to do an ruu, so that wasnt really needed. Not sure exactly how to unlock the bootloader again.
Click to expand...
Click to collapse
Thank you for your reply.
I have tried to flash recovery several times, and both TWRP and CWM gives the same error: FAILED remote not allowed
Code:
sending 'recovery' (8784 KB)...
OKAY [ 1.097s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.134s
I tried the following recoveries:
openrecovery-twrp-2.6.3.3-m7vzw
recovery-clockwork-6.0.4.4-m7vzw
recovery-clockwork-6.0.4.7-m7vzw
recovery-clockwork-touch-6.0.4.5-m7vzw
recovery-clockwork-touch-6.0.4.7-m7vzw
NELORAO said:
Thank you for your reply.
I have tried to flash recovery several times, and both TWRP and CWM gives the same error: FAILED remote not allowed
Code:
sending 'recovery' (8784 KB)...
OKAY [ 1.097s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.134s
I tried the following recoveries:
openrecovery-twrp-2.6.3.3-m7vzw
recovery-clockwork-6.0.4.4-m7vzw
recovery-clockwork-6.0.4.7-m7vzw
recovery-clockwork-touch-6.0.4.5-m7vzw
recovery-clockwork-touch-6.0.4.7-m7vzw
Click to expand...
Click to collapse
Ok try this then.
1. Download this file http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser http://vzw1files.dyndns.org/Superuser/superuser.zip and you will be rooted.
.
NELORAO said:
Hi guys,
I flashed stock back to my phone and relocked the bootloader by "fastboot oem lock".
I been stuck with this for the last 2 days searching for solution on how to get my phone unlocked and rooted again.
This is what I have tried so far:
1. Rumrunner 1.10.605.10 and 1.10.605.15 firmware (flashed 1.10.605.10 and updated to 15) - Run just fine, but it does not change anything on the phone. Still shows RELOCKED S-off and NO Root.
2. Firewater (temp-root method) - Temproot: Root acquired. Firewater: "there really isn't a helluva lot to do here. bye bye"
3. Flashing CM recovery - failed remote not allowed
Could someone please help me to get back Root access and UNLOCK my phone?
Thank you in advance.
Click to expand...
Click to collapse
Enable USB Debugging in Settings.
To do so, go to build information and tap it 7 times.
This will enable the Developer options in settings.
In there, check the box for Usb Debugging.
You should then be able to fastboot flash the recovery as per usual.
Good luck! :good:
cmlusco said:
Ok try this then.
1. Download this file http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser http://vzw1files.dyndns.org/Superuser/superuser.zip and you will be rooted.
.
Click to expand...
Click to collapse
Dude, there just aren't enough words to say thank you.
Again, thank you so much, everything works like a charm now.
santod040 said:
Enable USB Debugging in Settings.
To do so, go to build information and tap it 7 times.
This will enable the Developer options in settings.
In there, check the box for Usb Debugging.
You should then be able to fastboot flash the recovery as per usual.
Good luck! :good:
Click to expand...
Click to collapse
Thank you, I was finally able to flash your KitKat Rom that I have been dreaming for the last 3 days. :laugh:
Again, thank you so much.
cmlusco said:
Ok try this then.
1. Download this file, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser and you will be rooted.
.
Click to expand...
Click to collapse
Holy crap dude. I thought my phone was bricked. Thank you so much for that!
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?
cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.
edit: nvm...
Both download links link to the same file. splashscreen.img
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...
MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.
This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?
error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830
im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?
Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.