Develop Bugs

[Q] error trying to root

Hi all, i'm fairly new to android... and have followed instructions from:
network-13 . c o m /thread/3834-How-to-root-the-HTC-One-X
and i'm stuck trying to root / install the clockwork mod....
when i try and fastboot flash i get this error....
could someone offer any advice?
C:\android-sdk-windows\platform-tools>fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
sending 'recovery' (7122 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.074s
at this point the phone hangs... and i have to reboot by holding down the power button

echang01 said:
Hi all, i'm fairly new to android... and have followed instructions from:
network-13 . c o m /thread/3834-How-to-root-the-HTC-One-X
and i'm stuck trying to root / install the clockwork mod....
when i try and fastboot flash i get this error....
could someone offer any advice?
C:\android-sdk-windows\platform-tools>fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
sending 'recovery' (7122 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.074s
at this point the phone hangs... and i have to reboot by holding down the power button
Click to expand...
Click to collapse
Could be a bad download. Re download the img and try again,
TIP: Rename the img to something like "recovery.img". (A lot easier to type in cmd!!)

thanks for the reply... i've tried downloading multiple times and each time it doesn't work mmmm... just tried downloading again and still the same error

What do you mean 'the phone hangs'?
Have you booted into fastboot mode with the 'fastboot usb' showing in red?

Hi guys!
I FOUND THE SOLUTION! I plugged the phone into a different usb socket and it worked! Weird... i think it was the usb hub that was causing the issue.... possibly due to a faulty/lack of power port? not sure... but now i get
sending 'recovery' (5786 KB)...
OKAY [ 0.845s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.589s]
finished. total time: 1.436s
Thanks heaps guys
i hope this entry helps others in the same situation

echang01 said:
thanks for the reply... i've tried downloading multiple times and each time it doesn't work mmmm... just tried downloading again and still the same error
Click to expand...
Click to collapse
Sent from my HTC One X using xda app-developers app

HTC_Worldwide Stock Flash wildfire s without Using RUU.

Getting error on updating/downgrading your RUU.
Get back to official ROM,WITHOUT using any Running Any RUU.
No need to root for downgrading your ROM Any more.
And no need to Type any adb command.
Follow this 6 line tutorial.
1. Download this tool Flash Without RUU
2.Download Rom.zip No matter which location you belongs to.
3.Extract first folder,extract second folder.
4.Copy and paste the contents of second folder in First folder.
5.Connect your phone to Charge only mode with usb debbug on.(disable any antiviruse/and firewall if enabled).
6.RUN/Double click the "Run me flash.EXE"
If getting any connection error try using fastboot-usb mode.
Use Gold Card to bypass signature verification error or use area specific Rom.zip
Best of luck. (For those,who are getting signature error)
Remarks : Works with any wildfire s,no matter which Location device belongs to?(With Unlocked Bootloader or S-OFF)

do you know if this works on orange uk branded handset?
Answer, no.
< waiting for device >
erasing 'boot'... FAILED (remote: not allowed)
erasing 'recovery'... FAILED (remote: not allowed)
erasing 'system'... FAILED (remote: not allowed)
erasing 'userdata'... FAILED (remote: not allowed)
sending 'boot' (2582 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
sending 'recovery' (3180 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
sending 'system' (256876 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
flash finished ,now see your phone and find bootloaderú¼and then factory reset.
now wait for reboot
Press any key to continue . . .

technaudio said:
do you know if this works on orange uk branded handset?
Answer, no.
< waiting for device >
erasing 'boot'... FAILED (remote: not allowed)
erasing 'recovery'... FAILED (remote: not allowed)
erasing 'system'... FAILED (remote: not allowed)
erasing 'userdata'... FAILED (remote: not allowed)
sending 'boot' (2582 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
sending 'recovery' (3180 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
sending 'system' (256876 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
flash finished ,now see your phone and find bootloaderú¼and then factory reset.
now wait for reboot
Press any key to continue . . .
Click to expand...
Click to collapse
it ignores all the files excluding the highlighted Three (Boot.img,recovery.img and system.img).
it will not update your hboot,or radio.
but in your case i think
you are not bootloader unlocked or S-off.

technaudio said:
do you know if this works on orange uk branded handset?
Answer, no.
< waiting for device >
erasing 'boot'... FAILED (remote: not allowed)
erasing 'recovery'... FAILED (remote: not allowed)
erasing 'system'... FAILED (remote: not allowed)
erasing 'userdata'... FAILED (remote: not allowed)
sending 'boot' (2582 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
sending 'recovery' (3180 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
sending 'system' (256876 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
flash finished ,now see your phone and find bootloaderú¼and then factory reset.
now wait for reboot
Press any key to continue . . .
Click to expand...
Click to collapse
The signature verify fail error is because you flash a rom of a different region so it has a different cid. To overcome this you will have to make a gold card. Then you won't get that error.
Sent from my Wildfire S A510e using xda app-developers app

vbhtt said:
The signature verify fail error is because you flash a rom of a different region so it has a different cid. To overcome this you will have to make a gold card. Then you won't get that error.
Sent from my Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I forgot to mention that.

Also one of the main reasons is that you MUST be either bootloader unlocked or s-off.

I'm having a big issue here!!
I followed this guide,
my phone is gone into a loop with the htc quietly brilliant logo,
keeps reboting,
I tried to go back to the recovery to backup my sistem,
and the recovery is not there anymore,
what can I do now?
---------- Post added at 03:10 PM ---------- Previous post was at 02:59 PM ----------
Stupid_N00b said:
I'm having a big issue here!!
I followed this guide,
my phone is gone into a loop with the htc quietly brilliant logo,
keeps reboting,
I tried to go back to the recovery to backup my sistem,
and the recovery is not there anymore,
what can I do now?
Click to expand...
Click to collapse
UPDATE
just managed to reinstall custom recovery and backup my system
I think the issue was that I did not do a gold card?
Also could anyone post a link to make this gold card?

Stupid_N00b said:
I'm having a big issue here!!
I followed this guide,
my phone is gone into a loop with the htc quietly brilliant logo,
keeps reboting,
I tried to go back to the recovery to backup my sistem,
and the recovery is not there anymore,
what can I do now?
---------- Post added at 03:10 PM ---------- Previous post was at 02:59 PM ----------
UPDATE
just managed to reinstall custom recovery and backup my system
I think the issue was that I did not do a gold card?
Also could anyone post a link to make this gold card?
Click to expand...
Click to collapse
Download the Gold Card TOOL from here : -
Gold Card.exe
And Follow The steps ..
1.Run Gold card.exe (as administrator)
2.Change your phone to "USB Mass storage" and click refresh in Gold Card Tool until you see the drive letter assigned to the SD Card of your phone.
3.NOW select MMC1 in step3 and PRESS "get CID"copy it.
4.NOW go to step 4 and click on the link provided there.
5.paste the CID in Box "SD Card Serial (CID)" on that page.
6.do the further steps as guided on website.and download that .img file.
7.now return to the Goldcard.exe again and go to step 5 and browse the .img file obtained from The website.
DONE........................

is there any guide on how to use this exe?

Stupid_N00b said:
is there any guide on how to use this exe?
Click to expand...
Click to collapse
Ignore all and follow this simple tutorial.
I have updated it here for you..
Simple Tutorial for Creating GOLD card

rajanand said:
Ignore all and follow this simple tutorial.
I have updated it here for you..
Simple Tutorial for Creating GOLD card
Click to expand...
Click to collapse
sweet :good:

rezo609 said:
Also one of the main reasons is that you MUST be either bootloader unlocked or s-off.
Click to expand...
Click to collapse
Ah.
Sent from my LT26i using xda app-developers app

technaudio said:
Ah.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
So you Got your solution?

rajanand said:
Download the Gold Card TOOL from here : -
Gold Card.exe
And Follow The steps ..
1.Run Gold card.exe (as administrator)
2.Change your phone to "USB Mass storage" and click refresh in Gold Card Tool until you see the drive letter assigned to the SD Card of your phone.
3.NOW select MMC1 in step3 and PRESS "get CID"copy it.
4.NOW go to step 4 and click on the link provided there.
5.paste the CID in Box "SD Card Serial (CID)" on that page.
6.do the further steps as guided on website.and download that .img file.
7.now return to the Goldcard.exe again and go to step 5 and browse the .img file obtained from The website.
DONE........................
Click to expand...
Click to collapse
All right the program results in
Executing adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
Reading adb output
------------------------
* daemon not running. starting it now *
* daemon started successfully *
------------------------
Could not locate CID in output
Click to expand...
Click to collapse
on step 3, any suggestion?

Stupid_N00b said:
All right the program results in
on step 3, any suggestion?
Click to expand...
Click to collapse
if you are getting error in step 3.
after finishing format in step 1. > change the phone in charge only mode with debug on.
it will work now.
but again have to change your phone to "USB Mass storage" while patching the image file in step 5.
Best of luck.

rajanand said:
if you are getting error in step 3.
after finishing format in step 1. > change the phone in charge only mode with debug on.
it will work now.
but again have to change your phone to "USB Mass storage" while patching the image file in step 5.
Best of luck.
Click to expand...
Click to collapse
stuck again on step 5 it ask me to put the sd card back into computer
---------- Post added at 03:05 PM ---------- Previous post was at 02:54 PM ----------
so after making a goldcard I went through the same process for flashing system and all
I got the same result
htc logo looping
---------- Post added at 03:18 PM ---------- Previous post was at 03:05 PM ----------
Stupid_N00b said:
stuck again on step 5 it ask me to put the sd card back into computer
---------- Post added at 03:05 PM ---------- Previous post was at 02:54 PM ----------
so after making a goldcard I went through the same process for flashing system and all
I got the same result
htc logo looping
Click to expand...
Click to collapse
I also would like to get rid of this goldcard since it conflicts with the recovery system and
I can't find the clowork folder

Stupid_N00b said:
stuck again on step 5 it ask me to put the sd card back into computer
---------- Post added at 03:05 PM ---------- Previous post was at 02:54 PM ----------
so after making a goldcard I went through the same process for flashing system and all
I got the same result
htc logo looping
---------- Post added at 03:18 PM ---------- Previous post was at 03:05 PM ----------
I also would like to get rid of this goldcard since it conflicts with the recovery system and
I can't find the clowork folder
Click to expand...
Click to collapse
so many posts

rajanand said:
so many posts
Click to expand...
Click to collapse
Ok sorry, I'm gonna try to be more clear:
I patched the goldcard and repeated the process from top
still I got into the booting htc animation
which loops forever,
I wanted to go back to my back but I guess the goldcard won't let me do it since after backing up from clockwork recovery
the htc brillient loop comes back again instead of loading the cyanogen
can you help me?

Stupid_N00b said:
Ok sorry, I'm gonna try to be more clear:
I patched the goldcard and repeated the process from top
still I got into the booting htc animation
which loops forever,
I wanted to go back to my back but I guess the goldcard won't let me do it since after backing up from clockwork recovery
the htc brillient loop comes back again instead of loading the cyanogen
can you help me?
Click to expand...
Click to collapse
you have unlocked bootloader or you are using it in ***relocked***?

it is unlocked

[Q] Bootloader Not Unlocking?

I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating

Ditt0 - I have the same problem
Kittycatpenut said:
I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating
Click to expand...
Click to collapse
I'm experiencing the same thing. Can't flash recovery. Have followed instructions to Unlock bootloader through HTCdev and have gone through the process numerous times on different machines without any apparent error. Please help!
target reported max download size of 1830608896 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.479s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.093s

Dumb question #1
Have you tried different USB ports just to zero out all variables
---------- Post added at 07:07 AM ---------- Previous post was at 07:07 AM ----------
Either of you two
---------- Post added at 07:54 AM ---------- Previous post was at 07:07 AM ----------
@Kittycatpenut
@andersonwittekind
I would ask in the T-Mobile forum only cause you might find an answer faster
http://forum.xda-developers.com/showthread.php?t=2725099

[Q] fastbooot fails when flashing a recovery.img

Hi,
I have Hongmi Redmi1 WCDMA phone, which is in a softbrick boot-loop.
I can get into fastboot , from a Windows (8) comandprompt, so that does look promissing, however...
When I flash the (correct) recovery this is my output:
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (5462 KB)...
OKAY [ 0.181s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.189s
So the writing 'recovery' FAILED (remote: partition 'recovery' not support flash)
- It seems to me I am stuck...
- Is Fastboot the solution to my boot-loop problem?
- Should I try to get adb up and running, and then trying to push a complete ROM to the phone?
Do you have any suggestions?
Thanks in advance,
k03st

After running this command fastboot devices, I get
MTK0123456789ABCDEF fastboot
Does that help?

ko3st said:
Hi,
I have Hongmi Redmi1 WCDMA phone, which is in a softbrick boot-loop.
I can get into fastboot , from a Windows (8) comandprompt, so that does look promissing, however...
When I flash the (correct) recovery this is my output:
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (5462 KB)...
OKAY [ 0.181s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.189s
So the writing 'recovery' FAILED (remote: partition 'recovery' not support flash)
- It seems to me I am stuck...
- Is Fastboot the solution to my boot-loop problem?
- Should I try to get adb up and running, and then trying to push a complete ROM to the phone?
Do you have any suggestions?
Thanks in advance,
k03st
Click to expand...
Click to collapse
see Xiaomi hongmi / red rice by Urich24
All about Xiaomi RedMi 1S / Hongmi 1S by Tarun93
This thread will be moved to Redmi 1S Q&A, Help & Troubleshooting

too bad....
Thanks.
I was unable to get it working .:crying:
hence I have bought a new phone.
My old one is still rebooting, no matter what.....
Cheers,
ko3st

hey my friend!!!
try this:
root your device and install root explorer. go to /system/ and RENAME this file "recovery-from-boot.bak" to "recovery-from-boot.p"
edit:
ooohh sorry, your device have a bootloop :\

Swos said:
hey my friend!!!
try this:
root your device and install root explorer. go to /system/ and RENAME this file "recovery-from-boot.bak" to "recovery-from-boot.p"
edit:
ooohh sorry, your device have a bootloop :\
Click to expand...
Click to collapse
Hello, I have a similar problem, but in a xiaomi MI4, but i have problems to update, the rest is fine, do you think to this can help me solve the problem.

Bootloader unlocked, can't flash TWRP recovery

I've managed to unlock the bootloader on a friend's Zenfone 2 (Z00A); or, at least, I believe I have, because the boot splash screen has the inverted colors that most threads on BL unlocking mention. I used this method, inside a Windows XP VM.
The thing is, I can't flash TWRP. If I try, it tells me permission was denied.
Code:
[email protected]:~/dev/android/sdk/platform-tools$ sudo ./fastboot flash recovery /media/michael/2D66-7551/Zenfone\ 2\ ZE551ML/twrp-3.0.0-0-Z00A.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'recovery' (15674 KB)...
OKAY [ 0.967s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 1.123s
(The same thing happens if run from inside the XP VM.)
Could someone please steer me in the right direction?

Sorry i can't post any external link.
I had this kind of problem the first time, because you need to root the phone after you unlock the bootloader.
Follow this step : http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
then
Enter that in google : gurus wizard/2015/07/root-and-unlock-bootloader-on-asus-zenfone-2.html