Hello there!
I've tried now for a while and I'm getting realy pissed of to be honest.
I tried to root my legend which unfortunately has Android 2.2. By now, I managed to get the thing downgraded with the temproot with visionary+. I then inserted the goldcard and tried the r4-legend-root file. The first step produced an error message, but also the message "Step1 complete".
I then started the step2 procedure and got the error message "no devices found".
The same thing happened with Windows 7 and Linux Ubuntu 11.04.
What's wrong? Why wouldn't it work? Thanks in advance for helping me *sniff*
Sounds like you dont have adb drivers installed or adb installed
Oh and how I have. As I said, everything else worked fine, when I type adb devices in a shell, it displays my legend properly. But when I'm in Restore Mode it wouldn't recognize the device anywhere.
Hmm i didnt personally root using that method, What stage are you meant to be in for the bit where its stuck? Fastboot?HBOOT? Recovery?? Im thinking it is a driver issue.Have you installed the right HTC Sync?
As I wrote I'm in the stage of Recovery, where i should use the step2 of the r4-legend-root package.
I've tried it with linux and windows. On windows I had the right HTC Sync installed. And the drivers seam to work otherwise.
What bootloader do you have. (issue "adb reboot bootloader" and tell us the version of HBOOT)
When I start the phone with VolumeDown and the Powerbutton it displays, that I have HBOOT 1.01.0000.
I've done some research by the way, is it possible that it is a goldcard problem? And ist there any way to check out if my goldcard is valid or not?
Thanks in advance
please follow the steps.
i tried it on my legend and was successful in rooting my phone.
http://forum.xda-developers.com/showthread.php?t=725430
if you successfully downgraded your phone ( check if your in 2.1) your goldcard is useless now.
try again R4 step1 and 2 with a new empty SD or format your goldcard if you got only one SD.
[email protected]:~/android/r4-legend-root$ ./step1-linux.sh
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
[sudo] password for sirtobey:
erasing 'cache'... OKAY
... OKAY
About to start flash...
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the
volume keys and power button to select the RECOVERY option.
[email protected]:~/android/r4-legend-root$ ./step2-linux.sh
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
[email protected]:~/android/r4-legend-root$ error: device not found
^C
[email protected]:~/android/r4-legend-root$
Click to expand...
Click to collapse
That's what I get with or without the goldcard mounted in the phone.
I've redone all of it, downgrading although it already was, etc.
I really really could use some help...
1 when you launched step2 you get the red triangle on your phone?
2 i get "device not found" one time when i have an USB brick, is your phone recognized your SD?
Whenever I have had a device not found error in recovery it's because HTC sync was not installed even though the USB drivers has been installed from the android SDK
This post has a link to the version you should use.
http://forum.xda-developers.com/showthread.php?t=894465
Yes I have the red triangle on the Phone. How do you mean exactly with the SD Card?
On Windows I have this Version. Obviously I don't have one on Linux...
When I have my Legend plugged in on Windows 7 and at recovery I see in device manager.
My HTC under Android Devices using driver 2.0.7.1 provided by HTC.
Hmm, I guess no, I don't see it. Neither do I when I type adb devices in the console...
Any unknown devices?
I'll check it out with windows and let you know!
Ok, I checked it out, no unknown devices. When I connect the phone, it is recognized as USB mass storage device.
I tried fullfilling step2 while installing the correct htc sync but I still get the same error message.
:-(
Hooray!
Followed this Tutorial now step by step: http://forum.xda-developers.com/showthread.php?t=894465
Much better than theunlockr! Not so incomplete.
Seemed to be a problem with the goldcard...
not work for me too,
step 1, windows find driver "htc bootloader"
step 2, windwos find driver "My HTC", and i see - device not found =(
Related
Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
sguy156 said:
Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Click to expand...
Click to collapse
Hold vol down as it goes through the next loop, and it will put you in bootloader. From there, you can go to fastboot mode and flash custom recovery. Then adb sideload, adb push a ROM, or load a ROM to the removable SD if you have a card reader you can connect to your computer. Then boot custom recovery and flash the ROM.
sguy156 said:
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
Click to expand...
Click to collapse
It means you are trying to run the RUU for another carrier version. What version do you have (this section is for AT&T) and what RUU are you trying to run?
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
sguy156 said:
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
Click to expand...
Click to collapse
Yes if your S-OFF you can put recovery on your sdcard
http://forum.xda-developers.com/showthread.php?t=2951030
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
I thought you had S-OFF so no you can't load a custom recovery to your sdcard.
---------- Post added at 08:45 AM ---------- Previous post was at 08:36 AM ----------
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
Try the universal drivers from the link below.
http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/#asus
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
sguy156 said:
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Click to expand...
Click to collapse
The PC can see the phone, otherwise you wouldn't get the Model ID error message you indicated in the first post.
So no response if you type the following in command prompt?: fastboot devices
Fastboot and/or adb connectivity issues are rather common.
Another trick you can try, is to uninstall all HTC software (Sync and drivers) from your PC. Then connect the phone. DO NOT accept any prompts to automatically install drivers or Sync. Go to Device Manager, find the device, and pick the option to manually select the drivers, and pick the generic Android MTP device drivers.
Also try different USB ports. IN particular, if the ports are USB 3.0, that is known to cause issues (you may be able to disable the 3.0 drivers).
And if your PC is Win8.1, that is also known to be problematic.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
sguy156 said:
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
Click to expand...
Click to collapse
fastboot erase cache
fastboot flash recovery filename.img
(where filename.img above is replaced with the actual name of the desired recovery file)
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
sguy156 said:
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
Click to expand...
Click to collapse
Fastboot and adb connectivity issues are almost always a problem on the PC's side (ports, Win version, drivers, USB 3.0). Warranty replacement isn't going to help you.
I've given you a few suggestions on addressing the connectivity issues. You haven't indicated whether you have tried them yet, or not.
i tried your sugestions phone is showing up as HTC andriod device and running adb devices doesn't show anything. Not sure what else I can try , I am trying this on a windows 7 PC as windows 8 gave me so many issues .
@sguy156
So your running adb commands from c:\user .
I think your not navigating to adb properly.
I go to where adb and fastboot lives and Shift+right-click so I can open the cmd there
Thats what i did ran it from the location where adb and fastboot are installed same issues .
I hate to ask but do you have usb debugging on wile trying to use adb ?
Please keep an open mind as I'm trying to help ?
---------- Post added at 08:57 AM ---------- Previous post was at 08:30 AM ----------
Try this out if you can't get anything going.order the cable and use a second rooted Android device (no drivers needed at a all)
http://forum.xda-developers.com/att...c-fastboot-t2965030/post57315448#post57315448
USB debugging was on when phone was rooted not sure if its on ss I
Cannt check it now ..
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
sguy156 said:
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
Click to expand...
Click to collapse
I'm not trying to be rude but now that you have fastboot figured out I suggest you put the phone down in another room and start reading on what procedures to take next.
You learn the hard way by not looking in the "General section" where all the information is posted.
Yes you need the bootloader unlocked to push a custom recovery.
Thanks for your help , I found the other steps on other section . Hit post too quickly ..... Learning experience ..
sguy156 said:
Thanks for your help , I found the other steps on other section . Hit post too quickly .....
Click to expand...
Click to collapse
I like shortcuts when I drive ,I just don't advise taking them with the hacking of my devices.
If you use the "Tapatalk app" or the "XDA app" the forum is easier to read through
About 2 days back i received new android update from google. My phone was already rooted.
After installing new software phone was not starting.
When click poer button i launch on screen with options as Normal Powerup, Recovery, Factory etc..
I tried to recover but nothing happens when i click on recover.
Select Normal Powerup then also nothing happens.
Select Factory nothing happens. I am stuck on same page when starting phone.
I try to flash and install again using steps mentioned on xda but receive error when below command is entered:
mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.095s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.266s
On mobile i see below messages:
cmd: getvar:max-download-size
cmd: download:0008000
cmd: flash: partition
hab check failed for primary_gpt
Failed to verify hab image primary.gpt
I am stuck and unable to start my phone (moto e 2).
Help Help !!
I am not sure if I have posted on correct forum..
Did you unlock the bootloader of your phone before trying to flash something?
Or
You were on the stock ROM and they shipped you a update, and it upgraded, but the update failed to work?
i can fix this error
hi guys if any one facing this error message me ill help you :good:
bodboy8042 said:
hi guys if any one facing this error message me ill help you :good:
Click to expand...
Click to collapse
dude if u can that would be amazing. Please respond as soon as possible
Help brick moto e 2015
bodboy8042 said:
hi guys if any one facing this error message me ill help you :good:
Click to expand...
Click to collapse
I have the same problem with my XT1527 , if anyone knows unlock the bootloader would be grateful ...
Hello All.
Apologies if I am missing something obvious, but I am experiencing an issue with my US VZW XT912. Over a year ago, the phone bricked itself seemingly out of nowhere, only booting up into the "Encryption Failed" state. I went ahead and put it into AP fastboot and grabbed a copy of Matt's droid razr utility. I installed the motorola drivers and fired up the utility, then tried to flash the factory JB image to it WITH data wipe (option 1 on the utility). The process started, but right after "sending 'mbm' (512 KB)... OKAY [ 0.092s]" I got the message in the title of this post: "writing 'mbm'... FAILED (remote: )".
No matter how many different USB cables I tried, or how many different USB ports I used on several different computers and Operating Systems, I always got the same result; "writing 'mbm'... FAILED (remote: )".
I've gone as far as using ADB by hand and going through the flash instructions from an XML file step by step, but that fails in the same spot as well. RSDlite also failed.
My suspicions here are either A) The partition table is messed up somehow (which I unfortunately do not know how to fix) or B) The flash memory is actually just bad on the phone, which would obviously suck.
Now, most of my troubleshooting took place a year or so ago, so I've included a screenshot of Matt's utility that I just ran this morning. imgur<dot>com / QHsJbtO (sorry about the link; new user)
Any input is most appreciated.
Regards,
Steve P
physicsmaster131 said:
Hello All.
Apologies if I am missing something obvious, but I am experiencing an issue with my US VZW XT912. Over a year ago, the phone bricked itself seemingly out of nowhere, only booting up into the "Encryption Failed" state. I went ahead and put it into AP fastboot and grabbed a copy of Matt's droid razr utility. I installed the motorola drivers and fired up the utility, then tried to flash the factory JB image to it WITH data wipe (option 1 on the utility). The process started, but right after "sending 'mbm' (512 KB)... OKAY [ 0.092s]" I got the message in the title of this post: "writing 'mbm'... FAILED (remote: )".
No matter how many different USB cables I tried, or how many different USB ports I used on several different computers and Operating Systems, I always got the same result; "writing 'mbm'... FAILED (remote: )".
I've gone as far as using ADB by hand and going through the flash instructions from an XML file step by step, but that fails in the same spot as well. RSDlite also failed.
My suspicions here are either A) The partition table is messed up somehow (which I unfortunately do not know how to fix) or B) The flash memory is actually just bad on the phone, which would obviously suck.
Now, most of my troubleshooting took place a year or so ago, so I've included a screenshot of Matt's utility that I just ran this morning. imgur<dot>com / QHsJbtO (sorry about the link; new user)
Any input is most appreciated.
Regards,
Steve P
Click to expand...
Click to collapse
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Sent from my XT1060 using XDA Labs
sd_shadow said:
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Click to expand...
Click to collapse
Couldn't find a version number in the batch file of Matt's utility, but the created date on the file is August 26, 2014.
RSDLite 6.1.4
Was running stock JB when it bricked but I believe the phone shipped with ICS. I never loaded any custom ROMS, though.
"
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
"
Some (relatively poor) pictures of the AP screen: imgur<dot>com / a / mEFxz
sd_shadow said:
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
This is probably a dead thread, but I've been troubleshooting this issue on/off for over a year and still haven't managed to make any headway. Any other thoughts?
physicsmaster131 said:
This is probably a dead thread, but I've been troubleshooting this issue on/off for over a year and still haven't managed to make any headway. Any other thoughts?
Click to expand...
Click to collapse
What's the bootloader saying?
Sent from my sailfish using XDA Labs
sd_shadow said:
What's the bootloader saying?
Click to expand...
Click to collapse
Everything looks pretty normal on the bootloader. Trying to attach images but I keep getting an error so I'll type it out:
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To Return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
Some additional info:
When I try to boot normally I always get the "encryption failed" screen, and the reset button doesn't do anything.
When I try to boot into recovery, the android logo comes up, but I am never able to make it into the actual recovery menu.
Hi there. A couple of weeks ago my phone just restarted while writing an e-mail. First I didn't bother, but since then it keeps restarting.
As soon as Android is booted up (at the lockscreen) I got like 2-90 seconds (random), before the phone reboots itself. It does not matter whether I do any type of input or do nothing with it. It just restarts.
Starting the bootloader / recovery does not lead to a restart, the phone keeps active for hours without restarting.
Since the phone has never been modded / rooted / unlocked it is still as it left the factory: Locked Bootloader, S-On, Stock android, no root.
So far, so good, here are three ways with which I tried to make my phone reusable:
Number 1: Flashing RUU via fastboot.
What I did: starting Bootloader -> Fastboot -> Smartphone via USB connected to PC -> starting cmd -> "fastboot oem rebootRUU"
Normally, as far as I know, the phone should restart into the bootloader, what it is NOT doing. It just restarts to the OS. So I restarted it into the bootloader, retyped the fastbood command and kept holding vol- to make sure it is re-entering the bootloader this time. worked BUT without the cmd-notification.
fastboot flash zip firmware.zip (using matching RUU for my branding)
Follwed by this output:
E:\Program Files\ADB>fastboot flash zip firmware.zip
target reported max download size of 1542111232 bytes
sending 'zip' (1294516 KB)...
OKAY [ 42.641s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 144.410s
I tried several times, does not change. I also tried other and older zips from htcdev, didn't change a thing.
Number 2: Firmware-Upgrade w/o PC via 0P6BIMG.zip
Following a HowTo flash a RUU without a PC, I renamed the above mentioned zip to 0P6BIMG.zip and stored it on my external sd card, put it in my phone and started the bootload, which should result in automatically flashing the zip.
The result was:
SD Checking...
Not gift file...
Loading [0P6BIMG.zip]
No image !
Loading...[0P6BIMG.nbh]
No image or wrong image !
Loading... [0P6BIMG.zip]
No image or wrong image !
Of course, I also tried the above mentioned diffenrent zip files, all leading to the same result.
Number 3: Factory Reset.
Ok, after the two solutions above didn't work anyhow, I just tried to do a usual factory reset from the stock recovery.
Bootloader -> recovery -> wipe data/factory reset -> yes, erase all -> done.
Did this two times (just to ensure its wiped) and wiped the cache afterwards. When restarting back to the OS everything was still as I left it, the wipe didn't work...
All my trials let me think about a malfuntioning internal storage? Or what do you guys think I could try before dumping the phone into the trash?
Regards
As I tried nearly everything I will send my One Max to HTC for repair.
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
BoFar said:
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
Click to expand...
Click to collapse
FYI,
now i can get into bootloader but without a recovery...
with the already downloaded stock rom i'd extracted all IMG files from the UPDATE.APP.
the step where i'm stucking is that flashing system with fastboot gives this :
target reported max download size of 266338304 bytes
erasing 'system'...
OKAY [ 1.094s]
sending sparse 'system' (259466 KB)...
OKAY [ 17.422s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.547s
the system.img is 2.39 Go.
same things and messages happens with recovery & boot files [ FAILED (remote: size too large) ]
I thank you advising how to resolve this
[SOLVED]
Here's steps that I made (after a long search with Dr. GOOGLE ):
1- Download & install the Android Studio and its SDK tools (that include fastboot and adb latest version). when having the famous message of FAILED (....TOO LARGE) use the -S switch and be patient with SYSTEM.IMG since file size is big (first tries gave me the error message but after many try it works),
2- Download the official stock ROM from Huawei webpage,
3- Download Huawei Update extractor,
4- Extract BOOT.IMG & RECOVERY.IMG & SYSTEM.IMG from the UPDATE.APP extracted file,
5- flash sequentially : RECOVERY then BOOT then SYSTEM (Remember the reboot after each flash),
That's all...Folks