Why can't this be one click like on my old HTC G1?..
Anyways, I am trying to root my Legend to install CyanogenMod. I made a goldcard that I think works (how do you tell?). But when I run the r4-legend-root step1-windows.bat I get thrown:
Erasing 'cache'... FAILED (status malformed (1 bytes))
... FAILED (status malformed (1 bytes))
About to start flash...
sending 'zip' (121756 KB)... FAILED (command write failed (unknown error))
sending 'zip' (121756 KB)... FAILED (command write failed (unknown error))
Rebooting to bootloader...
rebooting into bootloader..
What am I doing wrong? I really want to get this phone rooted, so any help is greatly appreciated. Thanks guys!
bradtraver said:
Why can't this be one click like on my old HTC G1?..
Anyways, I am trying to root my Legend to install CyanogenMod. I made a goldcard that I think works (how do you tell?). But when I run the r4-legend-root step1-windows.bat I get thrown:
Erasing 'cache'... FAILED (status malformed (1 bytes))
... FAILED (status malformed (1 bytes))
!
Click to expand...
Click to collapse
Are you 0.43.0001 or below (if there is such a bootloader)?
It says 43.00003, is that bad?..
Then you need to use another rooting process - downgrade first, then root...
Sent from my HTC Legend using XDA App
How do I go about downgrading?
Sent from my HTC Legend
bradtraver said:
How do I go about downgrading?
Sent from my HTC Legend
Click to expand...
Click to collapse
Try these:
http://forum.xda-developers.com/showthread.php?t=725430
http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
Thank you so much! Downgrade successful, just booting up now and then it's time to try the root again
Related
OK, so I was trying to flash the Minimal Matte theme onto my N1, and I seem to have bricked the phone.
The phone now just sticks at the "X" logo when trying to boot.
I cannot access recovery - I get the exclamation mark.
I've tried download the Nexus One FRG83 system image from HTC and put it on the SD card and renamed it passimg.zip to try and get it up and running again - it did the update on the bootloader screen, but it hasn't helped.
Any ideas?
If your getting the exclamation mark, I would say the recovery has been lost somehow, and its on standard again.
Try re flashing recovery via fastboot, amon ra or clockwork, which ever one. Then re flashing whatever rom
Rellikzephyr
Sent from my Nexus One using Tapatalk
OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.
tameracingdriver said:
OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.
Click to expand...
Click to collapse
Did you unlock the bootloader?
Also, have you tried:
Code:
fastboot boot recovery.img
Try the nandroid back up in the recovery.
I've just unlocked the bootloader, and ran the command again and I can now get into recovery, and am now trying the CM6 ROM... so we'll see what happens...
And that has worked
Thanks very much for your help
tameracingdriver said:
And that has worked
Thanks very much for your help
Click to expand...
Click to collapse
Glad it worked out for ya ^_^
What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.
Jack_R1 said:
What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.
Click to expand...
Click to collapse
It was about 80ish Mb IIRC.
Hmm.. FRG83 Passimg.. Could you share it or a link to it?
Jack_R1 said:
Hmm.. FRG83 Passimg.. Could you share it or a link to it?
Click to expand...
Click to collapse
http://developer.htc.com/ 2nd link...
http://dl3.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
That what you are looking for?
Yep Thanks. I'll try to see, why didn't this flash the system clean.
My Nexus 7 16GB 2012 has started to randomly reboot, it's running 4.4.2 and has been fine for months. This morning I switched it in, turned off the Airplane Mode and after 30 seconds or so it locked up, then reset. This happens every time I turn off Airplane Mode and switch on WiFi.
I'm wondering if there is some sort of corrupt RAM causing the issue? I've tried to do a Factory Reset, but this also fails and I end up back at square one. So I tried Nexus Root Tookit to go back to stock (all I've done previously is unlock the bootloader, no root). This also fails:
sending 'bootloader' (3911 KB)...
OKAY [ 0.516s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.745s
Any suggestions on what to try next?
This may of course be a hardware fault, the device was bought in Summer 2012 on release.
Hi, you need download image of 4.4 and flash it, because 4.4.2 image has corrupt bootloader. If not work try 4.2.2 image and update to kitkat OTA
Cheers, E11
estape11 said:
Hi, you need download image of 4.4 and flash it, because 4.4.2 image has corrupt bootloader. If not work try 4.2.2 image and update to kitkat OTA
Cheers, E11
Click to expand...
Click to collapse
Thanks for the tip, I'll give that a try.
I have been able to use the Nexus Toolkit to temporarily flash the TWRP. I test my hypothesis about an invalid file system and that fails:
/data/media/0/TWRP errno=30
Anyway, it's downloading the image now so lets see if that fixes the problem.
nigelw said:
Thanks for the tip, I'll give that a try.
I have been able to use the Nexus Toolkit to temporarily flash the TWRP. I test my hypothesis about an invalid file system and that fails:
/data/media/0/TWRP errno=30
Anyway, it's downloading the image now so lets see if that fixes the problem.
Click to expand...
Click to collapse
I'm trying KRT16S and the "Back to Stock" option. The Nexus goes to bootloader mode (so I have Android on back with open door). The flashstock.bat runs in a command tool and displays no errors, but nothing appears on the Nexus 7? The script completes, Nexus reboots and is in exactly the same state.
It doesn't seem to want to accept any kind of update.
nigelw said:
I'm trying KRT16S and the "Back to Stock" option. The Nexus goes to bootloader mode (so I have Android on back with open door). The flashstock.bat runs in a command tool and displays no errors, but nothing appears on the Nexus 7? The script completes, Nexus reboots and is in exactly the same state.
It doesn't seem to want to accept any kind of update.
Click to expand...
Click to collapse
Mmm try enter in recovery and do factory reset, if doesnt work, try image of 4.2.2 I'm sure that works
PD. And use Nexus toolkit
Enviado desde mi Xperia P mediante Tapatalk
lagoskon said:
Give a try with twrp 2.6.3.0.
Latest has issues with backups
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
From TWRP I'm able to Wipe and do Factory Reset. It says successful, but when I restart nothing has changed, still got 4.4.2 installed.
I also tried Back to stock with 4.2.2 JDQ39, device goes to Bootloader mode but fails with this error:
sending 'bootloader' (2096 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: ()
finished. total time: 0.873s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No such device or address))
finished. total time: 0.000s
i have one received from customer , when i power on just hang on start-up log
to fix that i need just unlock boot loader flash the phone (using Nexus Root Toolkit1.8.6 )
but this one , root is done phone habe unlocked boot loader , when i try to flash i get this error
archive does not contain 'boot.sig'
PHP:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
OKAY [ 0.318s]
finished. total time: 0.398s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'radio' (45537 KB)...
OKAY [ 1.503s]
writing 'radio'...
OKAY [ 2.578s]
finished. total time: 4.083s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
error: out of memory
any help ^
Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app
bojanz said:
Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
This ^ boot sig error is normal
Sent from my Nexus 5 using XDA Free mobile app
yes phone work with 4.2 as you say thx for help
but i have base band version unknown
hitibiti said:
yes phone work with 4.2 as you say thx for help
but i have base band version unknown
Click to expand...
Click to collapse
Fastboot flash the 4.2 cache image
Sent from my Nexus 5 using XDA Free mobile app
how can i do that ?
thx
hitibiti said:
how can i do that ?
thx
Click to expand...
Click to collapse
Download the factory image. Extract it. Inside is a zip, extract that too. In there you'll find the cache.img. boot into the bootloader and in a cmd window on the pc use
fastboot flash cache cache.img
If you don't have fastboot set up on the pc Google 15 second adb install xda
Sent from my Nexus 5 using XDA Free mobile app
Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks
scari said:
Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks
Click to expand...
Click to collapse
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.
foxob said:
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.
Click to expand...
Click to collapse
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you
scari said:
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you
Click to expand...
Click to collapse
so this doesn't work? too bad. that has helped me save my zte open a few times.
foxob said:
so this doesn't work? too bad. that has helped me save my zte open a few times.
Click to expand...
Click to collapse
no, that method doesn't work definitely...
:crying:
are you able to get into fastboot?
hecatae said:
are you able to get into fastboot?
Click to expand...
Click to collapse
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).
scari said:
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).
Click to expand...
Click to collapse
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.
Arrowblue said:
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.
Click to expand...
Click to collapse
when I flash the phone with windows this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
and when I try to flash with ADB under Mac Os this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
and I try to flash the original boot image and the modified one,
but without success...
So, I bricked my phone, iw won't boot into the bootloader is unlocked menu even though it is unlocked, when I install a recovery this is what appears
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 1.050s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.057s
can anyone help me with this? the 3 button method doesnt work, it always says software installation failed, I really need to restore my phone, any help would be appreciated
i have had the same problem some days ago.
Re unlock bootloader and re try
unloadedluck said:
So, I bricked my phone, iw won't boot into the bootloader is unlocked menu even though it is unlocked, when I install a recovery this is what appears
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 1.050s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.057s
can anyone help me with this? the 3 button method doesnt work, it always says software installation failed, I really need to restore my phone, any help would be appreciated
Click to expand...
Click to collapse
This thread may help you https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Neo Markson said:
This thread may help you https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Click to expand...
Click to collapse
okay, so, I fixed my phone and stuff, but there seems to be a problem, I can't force update my phone through the 3 button method, the zip I donwload aren't corrupted the version is compatible, it just says "Software install failed" is there a solution to this? I can only flash through twrp
to have b390 i do like this:
B160 -> B370(TWRP) -> B390 (Firmwre finder DNS method)
unloadedluck said:
okay, so, I fixed my phone and stuff, but there seems to be a problem, I can't force update my phone through the 3 button method, the zip I donwload aren't corrupted the version is compatible, it just says "Software install failed" is there a solution to this? I can only flash through twrp
Click to expand...
Click to collapse
You should try to nstall stock rom from your region. But NOTE: you shouldn't select that option on firmware finder(incase u use another phone) or you'll end up with test keys.