Database Users

Root: stopped at step1.. help!

I've tryed to root my NoBrand Legend fw1.31 BL0.43 with No Succes!!
I did the step1 but after this I cannot enter in recovery mode from bootloader. It appairs a black warning screen and the Mac does'nt found the device so I cannot start the step2!
Once I restarted the phone I've the previous setting but in setting/software information I got a ROM no-sign.
Help me!

FAILED (remote: 42 custom id check fail)
I guess this is the problem! But how solve it????
From cmd:
C:\r3-legend-root>step1-windows.bat
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
< waiting for device >
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.
C:\r3-legend-root>step2-windows.bat
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* 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.
error: device not found
C:\r3-legend-root>

Don't forget to remove the "goldcard"
Modaco's tutorial say :
When this step has completed, REMOVE THE GOLDCARD and either format it and replace, or replace with a different (non goldcard) microSD.
Click to expand...
Click to collapse

I removed it!
I put also in recovery mode like a friend suggest:
Originally Posted by iziy
Don't restart phone on red exclamation screen push power + VOL up button at the same time and u will enter on recovery menu
Ok I did it! Now I've the blue recovery screen but in the bottom of the screen there is written in yellow:
E:Can't open /cache/recovery/command.
So I've the same problem that the PC doen't find the device when I lunch the step2!

before step1 you must be in fastboot ( phone off , push power + vol down ) select fastboot with power button and when you see FASBOOT in red case launch step1.bat
after step1 , you probably return on first screen , select, with VOL button , RECOVERY, you will see a black screen with a phone inside and a red ! symbol, launch step2
Make your microSD card into a goldcard by following these instructions (it's a good idea to back up the contents of your card first!).
Unzip the file you downloaded to a directory, then open a command prompt / terminal window at that directory.
Turn off your HTC Legend, then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box. Connect the phone to the computer.
In the terminal window, enter either 'step1-windows.bat', './step1-mac.sh' or './step1-linux.sh' as appropriate.
When this step has completed, REMOVE THE GOLDCARD and either format it and replace, or replace with a different (non goldcard) microSD.
Navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select.
In the terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate.
When this has completed, your device should be at the 'recovery' screen ( this recovery menu is green ). Select the 'wipe' option, then select the option to apply an update zip from sdcard, and select 'rootedupdate.zip'. This will take a little while, so go make a nice cup of tea. When the flash has finished, reboot, and you are DONE!
Click to expand...
Click to collapse
pls read all explanation on original Paul O Brien post before doing anything and claiming that does not work...

ilos said:
before step1 you must be in fastboot ( phone off , push power + vol down ) select fastboot with power button and when you see FASBOOT in red case launch step1.bat
after step1 , you probably return on first screen , select, with VOL button , RECOVERY, you will see a black screen with a phone inside and a red ! symbol, launch step2
pls read all explanation on original Paul O Brien post before doing anything and claiming that does not work...
Click to expand...
Click to collapse
I read very well and followed the guide step by step!
All points followed very closely.
Created Goldcard, fastboot, launched the step1 and then the screen with the "!" .
I've also launched the step2 but unfortunately either the PC than the Mac cannot find the device!
I said nothing against Paul just wondering if anyone can solve this problem.
I'm not a newbie in the world of phones and I had WindowsMobile phone, iPhone, Palm Prè and Android, all hacked before this!
Thanks

When it says:
FAILED (remote: 42 custom id check fail)
I'm pretty sure your goldcard isn't working. Try again with another microSD and make it a gold card. Follow the instructions carefull.
Best Regards - Liquid211

Thanks! Ok, I'll do another GoldCard SD.
Anyway, my Legend is a NO Brand htc, is so important to have a GoldCard?

SOLVED!!!
Finally I've root it!
Run all the processes from a lite version of Windows XP!
The difficult part was to configure the drivers of Legend for adb, fastboot and bootloader mode: http://www.mail-archive.com/[email protected]/msg90765.html
After that another possible variant for my success may have been the change of the microSD which I created the Goldcard.
So, from windows, step1 did not give me more the error 42 and was able to load all necessary files on the device, consequently, has also completed the step2!
P.S. single bug found ... greater instability in wifi!

I have a unbranded legend. Do i have to make a goldcard? I am going to try rooting my legend on a other laptop today. Maybe it works on xp instead of Windows 7.
-------------------------------------
Sent via the XDA Tapatalk App

Yes, even for No Brand Legend you need GoldCard!
Sent from my Nexus One using Tapatalk

my legend lost its adb/usb function...

Hard time rooting, don't know what else to do...
Hi,
I'm trying to root my new HTC legend, I got it from eBay and it came with 1.32.161.4 and bootloader 0.43.0001.
I've tried to make a goldcard using two different microSD, 2GB kingstone and a 4GB "nokia". Both of them I'm able to mount without reformatting after making them as goldcard. I tried three different methods to create the goldcard, manually from windows xp, manually from Linux (Debian) and with GoldCard Tool from windows xp.
When trying to downgrade to 1.23 I get the bootloader version error and when trying step1 from rooting guide I get "remote: 43 main version check fail" so step2 fails too...
I have the feeling that my goldcard is not working properly but don't know other way of verifying it than just check if my OSes mount it without asking to reformat it.
Don't really know what else to do...any help would be much appreciated, would like to get root on my legend and get all the juice from it
Thanks.

The firmware 1.32 cannot be rooted yet!
Sent from my HTC Legend using Tapatalk

Pirreballo said:
The firmware 1.32 cannot be rooted yet!
Sent from my HTC Legend using Tapatalk
Click to expand...
Click to collapse
Ok, thank you.
Any work in progress?? any place where I could come by to check and also might offer for testing?
Regards.

tripledes said:
Hi,
I'm trying to root my new HTC legend, I got it from eBay and it came with 1.32.161.4 and bootloader 0.43.0001.
I've tried to make a goldcard using two different microSD, 2GB kingstone and a 4GB "nokia". Both of them I'm able to mount without reformatting after making them as goldcard. I tried three different methods to create the goldcard, manually from windows xp, manually from Linux (Debian) and with GoldCard Tool from windows xp.
When trying to downgrade to 1.23 I get the bootloader version error and when trying step1 from rooting guide I get "remote: 43 main version check fail" so step2 fails too...
I have the feeling that my goldcard is not working properly but don't know other way of verifying it than just check if my OSes mount it without asking to reformat it.
Don't really know what else to do...any help would be much appreciated, would like to get root on my legend and get all the juice from it
Thanks.
Click to expand...
Click to collapse
i have the same issue with 1.35.405.4 (i tried through windows and through lsh). Same problem in two ways
Any idea?
Thx

Step 1 and Step 2 problems with HTC Desire
Anyone please help...I have a HTC Desire (branded Telstra) and i am having the following issue when trying to perfom a root. I have a 2gb Kingston Goldcard and i have gone step for step (i think). Look forward to any help on this
C:\Desire_Root\r5-desire-root>step1-windows.bat
Desire Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
< waiting for device >
sending 'zip' (137446 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
sending 'zip' (137446 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model 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.
C:\Desire_Root\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* 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.
error: device not found

vord_ said:
i have the same issue with 1.35.405.4 (i tried through windows and through lsh). Same problem in two ways
Any idea?
Thx
Click to expand...
Click to collapse
We're doomed for now mate, I'm trying to get a 1.32 WWE ROM base to see if I could reproduce what Paul has achieved with 1.31...I think it shouldn't be too hard to copy Paul's work but don't really know till I can get one...
I'm pretty sure Paul's got better connections than me and he will get one before I do
Till then, we'll have to wait.

help
i did step 2 after i saw the red sign
step2-windows.bat
Legend Root Step 2
Pushing required files to device...
errorrotocol fault <no status>
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
-exec '/system/bin/sh' failed: No such file or directory <2> -
Pushing update file to device sdcard - this may take a few minutes...
-exec '/system/bin/sh' failed: No such file or directory <2> -
920 KB/s <110689022 bytes in 117.404s>
now wipe and apply rootedupdate.zip from the recovery image menu.
-exec '/system/bin/sh' failed: No such file or directory <2> -
c:\documents\root\r4-legendroot>
it says it should be at recovery screen after it but i can still see the red sign on my phone. how long does it take to go back to recovery or did i brick my phone =(..

nevermind i figured it out. after replacing the goldcarded sd with a different sd. you're suppose to press vol down and power button to go into recovery mode. and then do step 2. =)

[GUIDE] How To Root HBOOT 1.02/1.07 and gain S-OFF

I am in no way responsible if you turn your phone into an expensive brick. Unlocking bootloaders is technical, and can be hazardous to your devices health if you don’t understand what you are doing.
REQUIRED: ADB, fastboot, and all related drivers setup and working on your pc. If you do not have adb setup download this http://dinc.does-it.net/Guide_Root_New_Hboot/adb_fastboot.zip, and extract the files to some place like C:\adb and also download these required drivers http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install.
1. Head over to HTC Dev http://www.htcdev.com/bootloader/.
2. Create a account or sign in (you must use your real email address).
3. Go to unlock bootloader.
4. Select “HTC DROID INCREDIBLE*”.
5. Follow the directions and install all the software provided and you will end up with a unlocked bootloader with s-on. Save a copy of the unlock_code.bin to your pc, so you have it after dooing the froyo ruu.
6. Enter FASTBOOT again on your phone.
7.Open the command prompt again on your pc to where adb.exe is. (ie. C:\android-sdk\platform-tools or C:\adb
8. Download this - CWM recovery 5.0.2.0 http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it in the same folder as fastboot (where you put unlock_code.bin ie. C:\adb).
9. For simplicity’s sake rename the above file to recovery.img if it doesn’t already save it as recovery.img.
10. In your command prompt navigate to the folder containing your fastboot files and recovery.img
11. Enter the following in the command prompt:
Code:
fastboot flash recovery recovery.img
Code:
12. Once that completes navigate to recovery on your phone and press power to select it.
13. Once CWM recovery boots on your phone use the volume up and down to pick "Mounts and storage" press the trackball to select it.
14. Select "Mount usb storage".
15. Take this zip and drag it to the root of your SD card http://dinc.does-it.net/Guide_Root_New_Hboot/su.zip
16. On your phone press the trackball to unmount your usb storage.
17. Select go back.
18. Select install zip from SD card.
19. Choose zip from sd card.
20. Select the su.zip file we just downloaded and press the trackball to flash.
21. Reboot the phone.
22. Once your phone is booted go to the market and search "superuser".
23. Download and install superuser.
24. Search "busybox".
25. Use one of the busybox installers and install busybox (hit allow on the su notification).
26. Enter superuser app, press the menu button on your phone, select preferences, then scroll down to su-binary.
27. Hit update, and allow the prompt, if all the output is in green then you have full root congrats!!!.
For Those who wish to take it one step further and achieve s-off with unrevoked.
This process will format your phone I recommend making a nandroid, and running a program like Titanium Backup along with MyBackup to backup all your apps/data, and sync your contacts to google before you go any further.
28. Reboot your phone, and enable usb debugging.
29. Place these 2 files, unzipped on the root of your SD card. Do not put them in a folder, just drop the files right to your card. http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip
30. Set your phone to charge only.
31. Open the command prompt on your PC and navigate to the same folder as your fastboot files in the step above for example: cd c:\android-sdk\platform-tools\ or C:\adb
32. Type the following into the command prompt pressing the enter key at the end of each line:
Code:
adb shell
You should get a dollar sign $
Code:
su
You should now get a pound sign #
Code:
cat /sdcard/flash_image > /data/flash_image
Code:
chmod 755 /data/flash_image
Code:
/data/flash_image misc /sdcard/mtd0.img
33. Now set your phone to disk drive mode and place this zip on the root of your SD card (do not unzip) http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip
34. Rename the above file to PB31IMG
35. Set your phone to charge only
36. At this step you have 2 options you can pull the battery of your phone and put it back in then hold volume down and pres power to enter the bootloader or you can go back to your command prompt and type the following:
Code:
exit
Code:
adb reboot bootloader
37. When your bootloader is done loading press volume up to flash the PB31IMG.zip
38. Your phone will reboot the bootloader once during this process, don’t be alarmed just wait for it to finish, when done it will ask you to press volume up to restart the phone
39. When done remove the PB31IMG file from your sd card
40. Congratulations you are now back to stock 2.2 froyo
41. Put the unlock_code.bin file in the same folder with the fastboote.exe file if its not already there. Go to fastboot on the phone. Open a commant prompt to the folder where the files are.
42. Type the folowing:
Code:
fastboot flash unlocktoken unlock_code.bin
Code:
43. Fastboot flash cwm recovery.img again.
Code:
fastboot flash recovery recovery.img
Code.
44. Flash the su.zip file thru recovery.
45. Flash the unrevoked forever s-off patch thru recovery http://dinc.does-it.net/Guide_Root_New_Hboot/unrevoked-forever.zip
You should now be rooted and s-off.

Reserved

do you know if this method enables fastboot? I never could get fastboot working on my slcd Inc and I don't know if there is an eng hboot that works for it.
Sent from my Galaxy Nexus using Tapatalk

tiny4579 said:
do you know if this method enables fastboot? I never could get fastboot working on my slcd Inc and I don't know if there is an eng hboot that works for it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?

cmlusco said:
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?
Click to expand...
Click to collapse
is there a reason why update hboot? any thing good come with it?

synisterwolf said:
is there a reason why update hboot? any thing good come with it?
Click to expand...
Click to collapse
No reason to update and is reccomended that you dont. This is just for people who got an inc recently that came with the new hboot.

cmlusco said:
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?
Click to expand...
Click to collapse
I can use fastboot but I mean commands like fastboot flash and fastboot boot never worked for me. They should as I'm s-off but my conclusion is that the current boot loader doesn't allow fastboot to flash to a device.
I want it mainly to boot a boot.img without having to flash to the boot partition. Good for testing purposes.
Sent from my Galaxy Nexus using Tapatalk

cmlusco said:
No reason to update and is reccomended that you dont. This is just for people who got an inc recently that came with the new hboot.
Click to expand...
Click to collapse
thank you.

tiny4579 said:
I can use fastboot but I mean commands like fastboot flash and fastboot boot never worked for me. They should as I'm s-off but my conclusion is that the current boot loader doesn't allow fastboot to flash to a device.
I want it mainly to boot a boot.img without having to flash to the boot partition. Good for testing purposes.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I know the fastboot flash works for recovery and misc img, not sure about boot. I wrote this thread after helping my cousin root his inc with the new hboot that was ***locked*** (oow) s-on. After doing htc dev unlock, it did allow us to use fasboot to flash the cwm recovery img and the misc partition, and allow him to downgrade to 2.2. Then used unrevoked like normal to get s-off. He is now true s-off while still being on the new hboot. Now it says ***unlocked*** (oow) s-off.

cmlusco said:
I know the fastboot flash works for recovery and misc img, not sure about boot. I wrote this thread after helping my cousin root his inc with the new hboot that was ***locked*** (oow) s-on. After doing htc dev unlock, it did allow us to use fasboot to flash the cwm recovery img and the misc partition, and allow him to downgrade to 2.2. Then used unrevoked like normal to get s-off. He is now true s-off while still being on the new hboot. Now it says ***unlocked*** (oow) s-off.
Click to expand...
Click to collapse
To test you can dump the current boot.img or pull one from a nandroid to your pc and do fastboot flash boot boot.img. I'm just curious if that works for you as I couldn't do it but I might try again this evening.
Sent from my Galaxy Nexus using Tapatalk
Edit: Here is what I tried and it shows that fastboot boot fails for me:
Code:
D:\Users\Andrew\Desktop\droid>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.470s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.480s
D:\Users\Andrew\Desktop\droid>fastboot flash boot boot.img
sending 'boot' (3072 KB)...
OKAY [ 0.470s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.470s
D:\Users\Andrew\Desktop\droid>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)...
OKAY [ 0.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.700s

tiny4579 said:
To test you can dump the current boot.img or pull one from a nandroid to your pc and do fastboot flash boot boot.img. I'm just curious if that works for you as I couldn't do it but I might try again this evening.
Sent from my Galaxy Nexus using Tapatalk
Edit: Here is what I tried and it shows that fastboot boot fails for me:
Code:
D:\Users\Andrew\Desktop\droid>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.470s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.480s
D:\Users\Andrew\Desktop\droid>fastboot flash boot boot.img
sending 'boot' (3072 KB)...
OKAY [ 0.470s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.470s
D:\Users\Andrew\Desktop\droid>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)...
OKAY [ 0.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.700s
Click to expand...
Click to collapse
Yeah it does the same thing on mine 0.92 remote not allowed. I will check on my cousins phone next time i see him, and see if the new hboot can do it.

congrats on making it to the portal
http://www.xda-developers.com/android/root-and-s-off-for-the-htc-incredible-with-hboot-1-02-0000/

synisterwolf said:
congrats on making it to the portal
http://www.xda-developers.com/android/root-and-s-off-for-the-htc-incredible-with-hboot-1-02-0000/
Click to expand...
Click to collapse
Holy crap lol. I had no idea, thanks for telling me.

cmlusco said:
Holy crap lol. I had no idea, thanks for telling me.
Click to expand...
Click to collapse
your welcome.

When I try to run unrevoked for root and s-off it fails with Internal error: failed to unlock NAND flash?
I have no idea where to go from here anyone have advice?
Edit: I have run everything else in the guide successfully. I am downgraded to 2.2.

warpurlgis said:
When I try to run unrevoked for root and s-off it fails with Internal error: failed to unlock NAND flash?
I have no idea where to go from here anyone have advice?
Edit: I have run everything else in the guide successfully. I am downgraded to 2.2.
Click to expand...
Click to collapse
What version of unrevoked did you use 3.32, you should use version 3.22 http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe. Also make sure to go to the unrevoked menu and select custom recovery, and use this cwm img http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img before starting the process.

I did use 3.32 first. Then I decided to try 3.22.
I just read your post about using to custom recovery image and I just tried that with 3.22 unsuccessfully with a Failed to flash recovery image.

Can you access recovery, and when booted do you have root?

I can access the HTC recovery if that is what you mean. I lost root when I did the downgrade from 2.3.4 to 2.2

warpurlgis said:
I can access the HTC recovery if that is what you mean. I lost root when I did the downgrade from 2.3.4 to 2.2
Click to expand...
Click to collapse
Try flashing cwm with fastboot like in step 11. Then if you can access it flash the su binary, boot, install su app and busybox, and then try unrevoked again.

Root, Downgrade and install TWRP

For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin

Oisins said:
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Click to expand...
Click to collapse
In order to boot in twrp recovery you should first remove your usb cable,once is done,press and hold volume up and power button,once you see huawei logo,release power button but keep press on volume up,about firmware witch build number do you have on your phone,share more info if you want a quick help

"No app can detect root"
TWRP isn't root
"fastboot flash recovery recovery.img"
Any error?
"....(remote: Command not allowed)"
i think you have to unlock bootloader

Thank you for you quick response!
Running "fastboot flash recovery recovery.img" returns
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.880s]
writing 'recovery'...
OKAY [ 2.084s]
finished. total time: 2.967s
I checked if the bootloader is unlocked with "fastboot oem get-bootinfo"
Code:
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
I also tried booting into recovery without the cable plugged it, but it still just booted into "eRocovery"
More info
Product: ALE-L21
Serial: W3D4C16916992523
Build: ALE-L21C432BB574

just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery

ItalianWolf said:
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
Click to expand...
Click to collapse
The phone reboots, shows the HUAWEI logo and then turn off again.

Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320

ItalianWolf said:
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
Click to expand...
Click to collapse
It worked! Thank you very very much! I spend sooo much time on this... wow thanks!

Softbrick - Can't do anything execpt booting into fastboot - P9 Lite VNS-L21

Hello guys!
I recently wanted to upgrade to Nougat but now my P9 Lite seems softbricked. I own the version VNS-L21 but installed the oeminfo from an dual-sim VNS-L31, this worked for me under MM.
But now I can't boot into system or recovery. The only thing I can do is boot into fastboot. From there I can only flash boot.img or recovery(2).img. I'm unable to flash system.img, fastboot says the following:
Code:
\path\to\rom>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (430553 KB)...
OKAY [ 11.231s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 11.255s
I've tried both VNS-L31(tried B100) and VNS-L21 (tried B151) and B336 system.img files, all fail with the same message. When I flash a recovery.img file and try to boot into it my phone just stucks at the "Your device is unlocked and can't be trusted..." screen.
What can I do? Can someone help me to get at least the recovery working again? I've already tried meticulu's TWRP (V1 and V2) and BadWolfYe's Revolution (b. 9).
Regards,
- 4240Benny

Are you sure to have pressed the right buttons? It's Volume Up+Power button.
Try also to boot into recovery directly from fastboot:
fastboot boot twrpname.img
Click to expand...
Click to collapse

Potato997 said:
Are you sure to have pressed the right buttons? It's Volume Up+Power button.
Try also to boot into recovery directly from fastboot:
Click to expand...
Click to collapse
Yes, I've used Vol + and Power for booting into recovery. When I try to boot directly into recovery using the command you've posted I get the following message:
Code:
\path\to\recovery>fastboot boot recovery_twrp.img
downloading 'boot.img'...
OKAY [ 0.800s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.808s

Can be try toolkit 0008 twrp

Chisetdel31260 said:
Can be try toolkit 0008 twrp
Click to expand...
Click to collapse
Could you send me a link plese? There are many toolkits out there...
EDIT: Foud it

Chisetdel31260 said:
Can be try toolkit 0008 twrp
Click to expand...
Click to collapse
Ok, so I've tried flashing TWRP with the toolkit, it finishes successful but I still can't boot into recovery (Using Power, Vol+ and Vol-), i'm still stuck. (see Screenshot below)

4240Benny said:
Ok, so I've tried flashing TWRP with the toolkit, it finishes successful but I still can't boot into recovery (Using Power, Vol+ and Vol-), i'm still stuck. (see Screenshot below)
Click to expand...
Click to collapse
revolution recovery nougatb9 badwolfye Since you have flash nougat
https://mega.nz/#!JNtWRRbb!b2Nor1CXgLsgkYyu8ixfPY4DMi0Ay4nIX01KCGSGiVI
Plug, cable.
Volume - and power.
Flash fastboot flash recovery recovery.img
Remove the cable, pressed volume + and power, when logo huawei lache power. It will happen twrpnougatb9
Sorry, if its not working

4240Benny said:
Ok, so I've tried flashing TWRP with the toolkit, it finishes successful but I still can't boot into recovery (Using Power, Vol+ and Vol-), i'm still stuck. (see Screenshot below)
Click to expand...
Click to collapse
Hi. i have a bit the same problem here. I tried to instal emui 5 like you but i forgot to install the both zips.Well try like this.Pres volume up+power button and hold it. you will get that message like in the photo "Your device is booting now..",when you get this message keep holding the bottons until you get in erecovery,but hold and wait..From there you will have 3 options:1)Connect to wi-fi and recover.2)Reboot and 3)shotdown(or something like that).You will press on the 2,Reboot.Now your device will rebot and you will get a message like this:"For erecovery pres vol up for 3 seconds" and "To continue press power boton for 5 seconds" You will press power or you will wait couple of seconds and then the phone will start booting.

Try to do what helped me. 1-flash twrp for nougat (it should work) 2-copy MM APP file to dload folder 3-flash l21 oeminfo via adb sideload 4-reboot to bootloader and flash boot, system and recovery from b329 app file 5-power on phone holding vol+and vol- buttons

My mate 9 has become a hard brick and I want to help for recovery.

My mate 9 has become a hard brick and I want to help for recovery.
I am Japanese and I am not good at English.
I apologize for being a difficult to read sentence
I purchased MATE 9(MHA-AL00 6GB/128GB).
However, the firmware was MHA-L29C636B183 from the beginning.
I tried updating to Android 8 but I failed.
Currently, it is in the following state.
1. When turn on the power,Huawei logo is not displayed
2. The screen is black and does not react even if the power button is pressed for a long time.
3. use Vol-Up + Power , Vol-Down + Power,3 Button does not respond.
4. However, when I run fastboot devices, The following is returned.
=====
C:\>fastboot devices
N8K021xxxxxxxxxx fastboot
=====
5. fastboot reboot-bootloader respond. but there is no change in the display.
=====
C:\>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.025s
=====
When Oreo update failed and turned on,
"ERROR 10 Boot.img" displayed on the screen where the droid doll is displayed,
and it can not start up.
I tried to recover with the following procedure No.1-4, but it got even worse.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Currently, fastboot may be usable. I installed TWRP but I can not use it.
eRecovery also does not work.
I am thinking that I can recover using FASTBOOT FLASH XXXX.IMG.
But I do not know which partition and how to update.
Please tell me about how to recover and related sites.
Thank you

have you tried turning it off and on?

;74563891 said:
My mate 9 has become a hard brick and I want to help for recovery.
I am Japanese and I am not good at English.
I apologize for being a difficult to read sentence
I purchased MATE 9(MHA-AL00 6GB/128GB).
However, the firmware was MHA-L29C636B183 from the beginning.
I tried updating to Android 8 but I failed.
Currently, it is in the following state.
1. When turn on the power,Huawei logo is not displayed
2. The screen is black and does not react even if the power button is pressed for a long time.
3. use Vol-Up + Power , Vol-Down + Power,3 Button does not respond.
4. However, when I run fastboot devices, The following is returned.
=====
C:\>fastboot devices
N8K021xxxxxxxxxx fastboot
=====
5. fastboot reboot-bootloader respond. but there is no change in the display.
=====
C:\>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.025s
=====
When Oreo update failed and turned on,
"ERROR 10 Boot.img" displayed on the screen where the droid doll is displayed,
and it can not start up.
I tried to recover with the following procedure No.1-4, but it got even worse.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Currently, fastboot may be usable. I installed TWRP but I can not use it.
eRecovery also does not work.
I am thinking that I can recover using FASTBOOT FLASH XXXX.IMG.
But I do not know which partition and how to update.
Please tell me about how to recover and related sites.
Thank you
Click to expand...
Click to collapse
Is Erecovery working?

what command that you use to flash twrp ??

le grande magnetto said:
have you tried turning it off and on?
Click to expand...
Click to collapse
wmfreak said:
Is Erecovery working?
Click to expand...
Click to collapse
Thank you for your reply.
I turned off the power, but it looks like the power is turned on automatically.
There is no screen display, but confirmed with fastboot devices.
I can not enter eRecovery screen.

superseventh said:
what command that you use to flash twrp ??
Click to expand...
Click to collapse
fastboot flash recovery TWRP8_3.0.3.img

;74565458 said:
fastboot flash recovery TWRP8_3.0.3.img
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
this link will guide you how to HWOTA to update ROM when you already have Oreo update.zip, update_data_public.zip, and update_all_hw.zip put these 3 files in to update folder
if this HWOTA that you download not work try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
it is HWOTA8 to update to Oreo
if twrp won't work try this https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622

superseventh said:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
this link will guide you how to HWOTA to update ROM when you already have Oreo update.zip, update_data_public.zip, and update_all_hw.zip put these 3 files in to update folder
if this HWOTA that you download not work try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
it is HWOTA8 to update to Oreo
if twrp won't work try this https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622
Click to expand...
Click to collapse
Thank you for showing me three ways. Since I am going to work from now I will try after going home.
After that, as a result of investigation, I found out that the FRP is locked.
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
I am looking for a way to unlock this using FASTBOOT.
If I erase a partition somewhere, will it be unlockd ?

;74570405 said:
Thank you for showing me three ways. Since I am going to work from now I will try after going home.
After that, as a result of investigation, I found out that the FRP is locked.
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
I am looking for a way to unlock this using FASTBOOT.
If I erase a partition somewhere, will it be unlockd ?
Click to expand...
Click to collapse
when you rebrand and install ROM with dload and then sign in to Google account the FRP Locked will be dissappear
this following method be the same that you use it before
now try this
1- Unlock bootloader
2- install twrp,
3-do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with Oeminfo Al00 : https://www.mediafire.com/download/37n3jqv23j6erq5
Once replaced, put this folder on ur sd card and boot to twrp recovery than restore it.
4- download C00 offline firmware from third post here https://forum.xda-developers.com/ma...o-bootloop-t3534594/post70937310#post70937310 , Download B115 then extract the rar and copy dload folder to external sd card,turn off ur phone than press 3 buttons combination,power volume up and down till the update start.
5- when finished unlock bootloader again
6-install twrp again
7- flash hw_data for C00 in twrp http://update.hicloud.com:8180/TDS/.../v65567/f2/full/all/cn/update_full_all_cn.zip it will give an error, don't worry.
8-flash c00 offline firmware again to have locked bootloader and get rid of the warning message lol
9 factory rest from settings.
10-use system update to get the latest firmware, sometimes you need sim card inserted,and using the download latest package option.
11 done.

Currently, only FASTBOOT can be used,
FRP is preventing the overwriting of the partition,
so I can not try the suggested method.
I studied variously, but I can not find a good solution.
I am planning to use DC-Phoenix (paid service) in a few days.
It seems to be able to update ROM from FASTBOOT even when FRP is locked.

I tried DC-Phoenix, but as a result it failed. The FAST BOOT which I was able to use until now can not be used and the power can not be turned on.
I am disappointed that the method of recovery is gone.
Thank you for your support.

Bricked
GreenOcean said:
I tried DC-Phoenix, but as a result it failed. The FAST BOOT which I was able to use until now can not be used and the power can not be turned on.
I am disappointed that the method of recovery is gone.
Thank you for your support.
Click to expand...
Click to collapse
Well, with fastboot, adb, bootloader mode, and eRecovery gone there is not really a lot you can do short of returning the device to Huawei (hopefully you still have warranty) for a replacement. Just tell them your phone died.