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
Related
ok i'm trying to flash .img through fastboot as tutorial says...
-fastboot flash recovery (filename.img)
but here is the problem according to cmd it sends okay but when it trys to write the .img it says: writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verify fail>
i checked if the .img was corrupted so i tried different one but same story
what can i do to make this work as it should?
checked forums and google but couldn't find a solution
grafitin
grafitin said:
ok i'm trying to flash .img through fastboot as tutorial says...
-fastboot flash recovery (filename.img)
but here is the problem according to cmd it sends okay but when it trys to write the .img it says: writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verify fail>
i checked if the .img was corrupted so i tried different one but same story
what can i do to make this work as it should?
checked forums and google but couldn't find a solution
grafitin
Click to expand...
Click to collapse
simple do it with unrevoked connect your phone choose custom image option.
but check for HBOT drivers,adb drivers.
very easy method.
grafitin said:
ok i'm trying to flash .img through fastboot as tutorial says...
-fastboot flash recovery (filename.img)
but here is the problem according to cmd it sends okay but when it trys to write the .img it says: writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verify fail>
i checked if the .img was corrupted so i tried different one but same story
what can i do to make this work as it should?
checked forums and google but couldn't find a solution
grafitin
Click to expand...
Click to collapse
This only applies if you're S-OFF
I have I bought Droid Incredible ( Refurbished ) from ebay.com
when system start run Its turn off , sometime turn off befor system start
I have change many root but still problem
I have two phones same problem
How can fix it ? Plz help me
Check through the recent boot loop/hboot threads about how to run an ruu using a PB31IMG.zip.
Sent from my Galaxy Nexus using Tapatalk 2
I did with this one ( mediafire.com/?uvha2u2pv3xp8d5[/url] )
But same problem
Can give me link for another to try plz
Pvillecomp.com. it should have all but the newer files. Try the froyo or gingerbread ruu there and read the help on the site. If you're still confused you can come back and ask questions. Also please report on your progress if you hit any issues or are successful.
Sent from my Galaxy Nexus using Tapatalk 2
I did with froyo and gingerbread , but problem still :crying:
copy of screen in attach
apas100 said:
I did with froyo and gingerbread , but problem still :crying:
copy of screen in attach
Click to expand...
Click to collapse
Try this ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
I did but same problem
I think is some wrong with me ,S still on , need I make it off ?
After i do it i got this message "No image or wrong image!"
Plz check photos in attachments
apas100 said:
I did but same problem
I think is some wrong with me ,S still on , need I make it off ?
After i do it i got this message "No image or wrong image!"
Plz check photos in attachments
Click to expand...
Click to collapse
Try reformating your sdcard fat32 with a pc. Then place only the ruu on the sdcard and try again. Sometimes that gets it to work.
My sdcard is FAT32 , I'm tired with it
When I try do it with android-sdk I get "FAILED (remote: not allowed)"
apas100 said:
My sdcard is FAT32 , I'm tired with it
When I try do it with android-sdk I get "FAILED (remote: not allowed)"
Click to expand...
Click to collapse
Even though its already fat32, sometimes reformating it gets it to work.
If your getting the remote not allowed message, it means the bootloader is still locked.
cmlusco said:
Even though its already fat32, sometimes reformating it gets it to work.
If your getting the remote not allowed message, it means the bootloader is still locked.
Click to expand...
Click to collapse
I have unlock bootloader by htcdev.com , It's unlock now , u can see photos in attachments
Is there other reason !
apas100 said:
I have unlock bootloader by htcdev.com , It's unlock now , u can see photos in attachments
Is there other reason !
Click to expand...
Click to collapse
Thats strange, with the bootloader unlocked you should have no issues fastboot flashing cwm recovery. Download this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it on your pc in the same folder as fastboot.exe. Open a cmd prompt with the phone connected. The phone should be in hboot and say fastboot usb plug in red at the top. Type " fastboot flash recovery recovery.img ".
It's working fine with recovery
----------------------------------------
sending 'recovery' (3064 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.994s]
finished. total time: 1.534s
-----------------------------------------
But with ruu isn't work
----------------------------------------
sending 'zip' (126494 KB)...
OKAY [ 19.493s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 19.517s
-----------------------------------------
apas100 said:
It's working fine with recovery
----------------------------------------
sending 'recovery' (3064 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 0.994s]
finished. total time: 1.534s
-----------------------------------------
But with ruu isn't work
----------------------------------------
sending 'zip' (126494 KB)...
OKAY [ 19.493s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 19.517s
-----------------------------------------
Click to expand...
Click to collapse
Try this one line at a time:
fastboot erase cache
fastboot oem rebootRUU
Wait for hboot to load.
fastboot flash zip PB31IMG.zip
hisnededsp
This what i got
sending 'zip' (185063 KB)...
OKAY [ 27.941s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 31.433s
apas100 said:
This what i got
sending 'zip' (185063 KB)...
OKAY [ 27.941s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 31.433s
Click to expand...
Click to collapse
That sounds like a bad download/corruption of the PB file, or the version of ruu you are trying to flash is older than the version on the phone. Try this one http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
Wait i forgot what are we trying to acomplish here lol. Are you just trying to go back to stock, downgrade, flash a rom ...?
This what I got
sending 'zip' (185063 KB)...
OKAY [ 27.777s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 31.250s
up
In short, I'm trying to factory reset the phone to it's default settings, but every attempt is met with a failed attempt. Here's the specs
HTC Incredible
Android 2.2
Locked
S-ON
Hboot 1.02.000
Software: 3.26.605.1
Baseband: 2.15.00.07.28
Upgrading using the RUU file, PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, does nothing because even when it says it succeeds, the software version is the same. Tried the PB31IMG.zip method doesn't work because I get the error, "Main version is older". Going into recovery mode and resetting from there does nothing either because that fails.
The closest method I've seen which resembles mine is from this thread, but because the phone is deactivated I can't access the market to download and install rom manager to fix what could be a corrupted recovery? On top of that, I spent over an hour working with SDK, and came to the conclusion that I'm out of my depth. If anyone could point me in the right directions.
Edit: Figured out I had the wrong zip file so when I finally got it to update to 4.08.605.2 image, the boot screen is stuck at "HTC Incredible" splash screen, so I'm to assume I bricked it?
S_K_I said:
In short, I'm trying to factory reset the phone to it's default settings, but every attempt is met with a failed attempt. Here's the specs
HTC Incredible
Android 2.2
Locked
S-ON
Hboot 1.02.000
Software: 3.26.605.1
Baseband: 2.15.00.07.28
Upgrading using the RUU file, PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, does nothing because even when it says it succeeds, the software version is the same. Tried the PB31IMG.zip method doesn't work because I get the error, "Main version is older". Going into recovery mode and resetting from there does nothing either because that fails.
The closest method I've seen which resembles mine is from this thread, but because the phone is deactivated I can't access the market to download and install rom manager to fix what could be a corrupted recovery? On top of that, I spent over an hour working with SDK, and came to the conclusion that I'm out of my depth. If anyone could point me in the right directions.
Edit: Figured out I had the wrong zip file so when I finally got it to update to 4.08.605.2 image, the boot screen is stuck at "HTC Incredible" splash screen, so I'm to assume I bricked it?
Click to expand...
Click to collapse
If you can get to hboot, its not bricked. Have you tried a factory reset from hboot since doing the update?
cmlusco said:
If you can get to hboot, its not bricked. Have you tried a factory reset from hboot since doing the update?
Click to expand...
Click to collapse
Yes, I can get to hboot, and unfortunately doing a factory reset from there didn't work either? What are my options now you think, since I ran out of ideas a while ago.
S_K_I said:
Yes, I can get to hboot, and unfortunately doing a factory reset from there didn't work either? What are my options now you think, since I ran out of ideas a while ago.
Click to expand...
Click to collapse
So am I out of options at this point, because I've exhausted every resource I could find.
S_K_I said:
So am I out of options at this point, because I've exhausted every resource I could find.
Click to expand...
Click to collapse
Try this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip. If that dosent work i would unlock your bootloader with http://htcdev.com/bootloader. Then flash a custom recovery. Then from recovery try to do a full wipe and a flash of a rom.
How do I get access to the sim card from my computer and install the zip if the phone won't boat? Or is there a way I can still do this through hboot?
S_K_I said:
How do I get access to the sim card from my computer and install the zip if the phone won't boat? Or is there a way I can still do this through hboot?
Click to expand...
Click to collapse
Well to put the PB file on the sdcard you would need to remove it from the phone, and then use a pc to put the file on there. You would most likley need an adapter, as most card readers dont do micro sd. However you can use fastboot to flash a pb file. Place the PB file on your pc in the same folder as fastboot.exe. Then type the folowing one at a time.
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip PB31IMG.zip
Also unlocking the bootloader, and flashing a recovery only requires the use of fastboot.
EDIT: I guess i should have asked first if you have fastboot adb and their drivers setup on your pc? And if you know how to use them?
Sorry bout not mentioning I'm still a noob at this but for the most part I'm pretty tech savvy (just with iphones shhhh), I was in the middle of updating my progress, and I just finished installing SDK and recovery-clockwork-5.0.2.0-vivo.img, so now after installing the PB zip udate I got this message, "Failed (remote: 99 unknown fail)". What version of PB is this anyways?
S_K_I said:
Sorry bout not mentioning I'm still a noob at this but for the most part I'm pretty tech savvy (just with iphones shhhh), I was in the middle of updating my progress, and I just finished installing SDK and recovery-clockwork-5.0.2.0-vivo.img, so now after installing the PB zip udate I got this message, "Failed (remote: 99 unknown fail)". What version of PB is this anyways?
Click to expand...
Click to collapse
The latest 4.08.605.15. Wait that is not a correct recovery for this phone. So you are unlocked now? If so that is why the fastboot ruu failed, the bootloader must be locked.
Yea I googled it not too long ago and figured that out. So what's the right version then?
S_K_I said:
Yea I googled it not too long ago and figured that out. So what's the right version then?
Click to expand...
Click to collapse
CWM - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/
Or
TWRP - http://dinc.does-it.net/Recoveries/TWRP_2.4.4.0/
I need to do some errands but I"ll be back in 30 minutes, Just letting you know in case you're waiting on me, but irregardless thanks for the help so far and I apologize having to put up with me. Bueno, ttys..
OK, I think I just made things worse. First off, I didn't know I shouldn't of unlocked it because now I instead of getting that error 99 when trying to mount the PB, I get the message saying, "bootloader err command error !!!" after I enter "fastboot oem rebootruu". And trying to mount it while it's unlocked I get the message, "FAILED (remote: not allowed)". Sad face all around. Also, those 2 links you gave me are broken or just aren't working for me, so I'll try to find other links in the mean time. But as far as re-locking the phone, I still get the same messages as above.
S_K_I said:
OK, I think I just made things worse. First off, I didn't know I shouldn't of unlocked it because now I instead of getting that error 99 when trying to mount the PB, I get the message saying, "bootloader err command error !!!" after I enter "fastboot oem rebootruu". And trying to mount it while it's unlocked I get the message, "FAILED (remote: not allowed)". Sad face all around. Also, those 2 links you gave me are broken or just aren't working for me, so I'll try to find other links in the mean time. But as far as re-locking the phone, I still get the same messages as above.
Click to expand...
Click to collapse
You can relock by typing in fastboot
Code:
fastboot oem lock
Or your saying you already tried that and it have an error?
The links should be working again.
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Wait, does your hboot still have the same info you posted earlier as far as software version and baseband? In othet words are you still on android 2.2? And do you have a working recovery now?
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
S_K_I said:
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
Click to expand...
Click to collapse
The RUU has to be capital letters in that first command. (fastboot rebootRUU)
Try with this one http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip, i forgot that last one was built and not official.
S_K_I said:
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
Click to expand...
Click to collapse
I got 4.08.605.2 installed, with radio 2.15.10.12.20. And if I understand you correctly regarding the recovery, I got clockwork installed and working.
S_K_I said:
I got 4.08.605.2 installed, with radio 2.15.10.12.20. And if I understand you correctly regarding the recovery, I got clockwork installed and working.
Click to expand...
Click to collapse
Well you could try thay ruu in the post above, or go to recovery, do a wipe, and flash a rom.
EDIT: To flash a rom thru recovery you would need to unlock again with the bin file.
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Lol we kind of have two different things going here, and they kind of conflict. So either stay locked and try that othet ruu, or unlock again and wipe and flash a rom with cwm.
Ok, it succesfully mounted that last image you linked to me. Only thing now after it finished on the command prompt, looking at the phone now and it's sitting there with the HTC logo, a black background, and a finished green bar. Should I just reboot it or keep waiting?
S_K_I said:
Ok, it succesfully mounted that last image you linked to me. Only thing now after it finished on the command prompt, looking at the phone now and it's sitting there with the HTC logo, a black background, and a finished green bar. Should I just reboot it or keep waiting?
Click to expand...
Click to collapse
Keep waiting, mabey for 10 15 min. It may take awile and reboot a few times.
Hello everyone, I started to play around with all the diff things you can do with a rooted phone had plans for getting a custom ROM for my phone. Let me stat by saying that I am very new to all this.
I day ago i was getting ready to install the custom ROM for viper (ViperOneM8_1.7.1) reason being is coming from a htc one m7 with sense i wanted to get back to sense from my stock GPe m8.
I was able to unlock my bootloader and get my phone rooted I fallowed this video (How to Root your HTC One M8 - Full Guide) From Sakitech... or least I think im rooted still... I'll come back to you as to why I say "I think I'm rooted".
I thought it would be very simple just fire up the custom recovery and flash the ROM and sit back while it flashed, well everything went down hill from this point. Let me tell you what i did.
First i got to the custom recovery and I did a wipe I did advanced wipe and checked the boxes this is where I think I deleted the OS(after this I could not get back on the phone to do anything only will boot to recovery and it say no OS installed then asks if I want to get SuperSU installed this is where I already thought I was rooted but maybe on not??? I'm very confused about that
Then I used the sideload method to push the rom zip and try to flash the rom at this point I cant get it to flash. First I was getting the MD5 error I checked that off now it will just fail either saying error executing the binary from the zip or that zip is corrupted. (I tried re-downloading the ROM even from mirror link)
At this point I am very frustrated and feel helpless. I tried my best to keep from posting this and try to research to see if i can find the solution myself but I'm having no luck I have my days off from work to get my phone up and running or ill just have to go but another phone. At this point I really need some help. All I want is a working phone if i can get back to GPe stock that would be fine or make the ViperOne work.
Attempts to solve my problem: I tried flashing GPE4.4.3_m8.zip and other stock GPe ROMs nothing works
Thanks for reading and all your help I will sit nest to my comp and answer anything to try make everything as clear as possible. Thank you again
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Demonwarrior said:
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Click to expand...
Click to collapse
no offense, buy you need to read before you continue anything else.
rbouza1 said:
no offense, buy you need to read before you continue anything else.
Click to expand...
Click to collapse
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Demonwarrior said:
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Click to expand...
Click to collapse
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Mr Hofs said:
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Click to expand...
Click to collapse
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
fastboot flash img boot.img
---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------
try that command, and what model did you have originally and did you convert to gpe or flash a gpe ROM.
gave me an error
Code:
FAILED (remote: signature verify fail)
Its a stock Google play edition I bought from the Google paly store, I didnt flash any other rom the ViperOne rom was going to be the first flash on the phone
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
iHagbani said:
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
Click to expand...
Click to collapse
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
ckpv5 said:
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Demonwarrior said:
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Click to expand...
Click to collapse
I know, but I told you this way in case that the adb didn't flash the whole zip file!
Demonwarrior said:
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Click to expand...
Click to collapse
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
j to the 4n said:
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
Click to expand...
Click to collapse
I tried the instruction on the thread it didnt work... I think its because i have s-on
Code:
C:\Users\owner\Desktop\htc one\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.058s]
finished. total time: 0.061s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.483s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.846s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.484s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.665s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.479s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.662s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.478s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.661s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.458s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.641s
C:\Users\owner\Desktop\htc one\platform-tools>
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.470s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.650s
C:\Users\owner\Desktop\htc one\platform-tools>
The post says to try it a few times but still giving me the say error
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