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. =)

Need help, tried to flash and now NP stuck at Google boot screen with unlock icon

Hello,
I'll start off by apologizing for being a noob. I tried to follow the instructions found here but somehow I got stuck in a state where my NP won't boot up. It is stuck at the Google black screen with an unlock icon. I tried to flash the 2.1 Lollirock rom and now i'm stuck in this state.
I have the NP plugged in and can get to the bootloader screen but I can't seem to figure out how to fix this. I downloaded the boot.img and system.img files from the Lollirock XDA page.
Steps I did:
At the bootloader page -
1) fastboot oem unlock (twice)
2) the bootloader screen then said it was unlocked
3) flashboot boot boot.img
4) flashboot flash system system.img
5) flashboot -w
Everything was successful with no errors so I put enabled Normal Boot in the bootloader and it just sits at the Google screen for about a minute and loops.
I tried to download fugu-lmy48n-factory-3b9d8638.tgz from the nexus stock image page and tried flashboot flash system fugu-lmy48n-factory-3b9d8638.tgz and got the error:
< waiting for device >
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.223s]
sending 'system' (457721 KB)...
OKAY [ 16.014s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 18.417s
I unzipped the TGZ file and tried with the TAR file and got the same error.
Then I flashed CM Recovery and that worked and I can get into CM Recovery thinking I can just update with the CM12.1 rom. The problem is that I don't have the zip on the device's sd card so I had to push from ADB by doing -
ADB sideload cm-12.1-20150520-UNOFFICIAL-fugu.zip
and it starts and goes for about 46% and stops with CM Recovery stating:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I googled this and people said to turn off signature verification since most roms are signed but I can't find any instructions on how to do that....
I also found an OTA zip of 6.0 and when updating from CM via ADB sideload, it gives me the error:
E: Error in /sideload/package.zip
(Status 7)
So that's where I'm at....not sure what to do next so any help you guys can provide would GREATLY be apprciated. Thanks!!!

Disregard, I think I got it figured out. I guess I was in stock recover and not in CM Recovery. Flashed CM Recovery again and I was able to flash CM12.1. RIght now it's sitting at the loading screen with the happy blue android face.

Asus ZenFone 2 Laser 551KL Z00TD soft-bricked in bootloop

Hi XDA Community,
I'm in a bit of a pickle. Yesterday my Zenfone started to bootloop and I tried to reset to fabric settings in bootmode but it didn't do anything. Afterwards I put the stockrom (Lollipop) and the latest rom (Marshmallow) and installed them. No errors, but it is stuck in bootloop and I can only enter fastboot mode now and it gets stuck there.
Tried Intel SoC solution, no results and also QFil but it isn't shown under ports.
How can I unbrick it?
Thank you very much.

The way I did it
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.

utahja1 said:
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.
Click to expand...
Click to collapse
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s

So, I finally managed to install the latest version of TWRP and SuperSU (don't know which version, tried two of them and thee TWRP install and finally one of the stuck).
I tried back2stock with 1.14 and 1.17 firmware, but the same problem happened. Bootloop and bootloop, on and on and on. The curious thing is that I didn't encounter any error message during installations so what could be the problem. Is there a log I can see to disover what could be the solution.
Thank you.
adriantamas said:
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s
Click to expand...
Click to collapse

No OS - P9 Lite VNS-L31

(Premise: my primary language it's not english, sorry for mistakes)
Hi guys, some weekend's ago, i tried to relock bootloader (i followed a tutorial), here the problems started...
The bootloader was successful locked, but, i got this message error:
"Data partition damaged ... (i don't remember all)" i decided to unlock the bootloader, reinstall twrp and flash a stock ROM, but, when i try to flash, i got this message error in twrp:
"Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/product' (Invalid Argument) "
I tried to use the tool Huawei update extractor, but when i try to flash system i get:
"target reported max download size of 471859200 bytes
sending sparse 'system' (451240 KB)...
OKAY [ 18.046s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 18.077s"
Thanks in advance...

Did you 'format data' before flashing ?
You should try to install via fastboot the stock recovery then use the dload folder method. That may fixe your problem.

Nathoufresh said:
Did you 'format data' before flashing ?
You should try to install via fastboot the stock recovery then use the dload folder method. That may fixe your problem.
Click to expand...
Click to collapse
I tried to install the recovery stock, but, when i try to go in, he stuck in "Your Device is booting now".

Gianpi612 said:
I tried to install the recovery stock, but, when i try to go in, he stuck in "Your Device is booting now".
Click to expand...
Click to collapse
And Can you install TWRP instead offre stock?

Nathoufresh said:
And Can you install TWRP instead offre stock?
Click to expand...
Click to collapse
Yes

Is your device a VNS-L31 3Gb of RAM?

General Help - My Nothing is stuck in a boot loop after attempting to root it

I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?

Did you try this? https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/

@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?

nike1 said:
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
Click to expand...
Click to collapse
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant

itsTarec said:
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
Click to expand...
Click to collapse
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully

nike1 said:
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
Click to expand...
Click to collapse
Is your device rooted now? Or did you just fixed the issue?

nike1 said:
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Click to expand...
Click to collapse
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.

lucy1983 said:
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
Click to expand...
Click to collapse
Aha, I see. That wasn't clear to me. I thought i needed a full package and not just an incremental one, that's why I went for 1.1.7. I did patch it with Magisk though, just the wrong version i guess. But all is well now, the phone's fully working afaict. Thank you for clarifying what went wrong!