Related
I have serious trouble.
I tried unroot my phone but when I tried to install original ROM, I got message about fail. I rebooted the phone into recovery and restored nand backup.
I tried newer ROM. This rans longer, updated HBOOT from 1.09 to 1.13 and removed root (now I have S-ON) but then I got error "Main Version is older!" Now I can boot only info boorloader. When I use ROM in file PG32IMG.zip I got error message again.
Can anybody help me? I don't need S-OFF but I need working phone
HTC Incredible S, previous ROM was CyanogenMod 7.1 nightly, HBOOT was 1.09 but now is 1.13.
Then I try use alpharev I have no connection to phone. Driver manager says that device is working properly but then I got message that it was not recognized.
I really need drivers to connect phone un fastboot and made S-OFF again or install stock ROM (this rather). How I can recognize the right ROM?
Thanks!
P.S. I looked into forum but all solutions are for dirrerent phones
Your going to have to remove your sd card and load it into your computer with another device and replace the pg32img.zip file with another Rom.... I think.
itsbeertimenow said:
Your going to have to remove your sd card and load it into your computer with another device and replace the pg32img.zip file with another Rom.... I think.
Click to expand...
Click to collapse
I tried this but I don't know which ROM is correct for me. I tried three ROMs and every ends with error or with no message but also no effect
I want to help dude but I've never heard of this. Are you flashing a froyo or gingerbread Rom?
libb said:
I have serious trouble.
I tried unroot my phone but when I tried to install original ROM, I got message about fail. I rebooted the phone into recovery and restored nand backup.
I tried newer ROM. This rans longer, updated HBOOT from 1.09 to 1.13 and removed root (now I have S-ON) but then I got error "Main Version is older!" Now I can boot only info boorloader. When I use ROM in file PG32IMG.zip I got error message again.
Can anybody help me? I don't need S-OFF but I need working phone
HTC Incredible S, previous ROM was CyanogenMod 7.1 nightly, HBOOT was 1.09 but now is 1.13.
Then I try use alpharev I have no connection to phone. Driver manager says that device is working properly but then I got message that it was not recognized.
I really need drivers to connect phone un fastboot and made S-OFF again or install stock ROM (this rather). How I can recognize the right ROM?
Thanks!
P.S. I looked into forum but all solutions are for dirrerent phones
Click to expand...
Click to collapse
dude are you stuck at security warning bootloader???
Sent from my HTC Incredible S using xda premium
santhoshpirate said:
dude are you stuck at security warning bootloader???
Click to expand...
Click to collapse
Yes
I can run fastboot and bootloader. But I cannot connect to phone from Windows.
itsbeertimenow said:
I want to help dude but I've never heard of this. Are you flashing a froyo or gingerbread Rom?
Click to expand...
Click to collapse
I flashed Gingerbread.
I tried this ROMS in this order:
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.0225_2_NV_VZW1.92_release_181303_signed.exe (cleared CM7.1 but not recovery)
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe (cleared recovery and S-OFF, Error message)
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe (nothing, load, check then nothing - try to flash from card)
libb said:
Yes
I can run fastboot and bootloader. But I cannot connect to phone from Windows.
Click to expand...
Click to collapse
read the post carefully!
http://forum.xda-developers.com/showpost.php?p=18706124&postcount=6
santhoshpirate said:
read the post carefully!
http://forum.xda-developers.com/showpost.php?p=18706124&postcount=6
Click to expand...
Click to collapse
I read it twice.
Now I can connect via fastboot.exe but I have problem with versions.
Whe I try flash ROM, I got this:
Code:
sending 'zip' (293453 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
or this
Code:
sending 'zip' (262360 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)
fastboot getvar all returns:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3805.06.03.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.32.1010.1
INFOserialno: HT12WTD01939
INFOimei: 355301040865167
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4010mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
I desperated because I flashed before latest radio and I'm afraid that the mainver is too high. Can you please advice me which ROM I could use?
On display I see:
*** Security Warning ***
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.06.03.03_M
eMMC-boot
Apt 1 2011, 18:34:39
use "fast boot getvar all" to get the mainver is. And than go to "h ttp://goo-inside.me/ruu/vivo" to download a new PG32IMG.zip
Delete the space between h and t.
---------- Post added at 10:01 AM ---------- Previous post was at 09:55 AM ----------
1.go to "goo-inside.me/ruu/vivo/full" and download "PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip"
2.Flash it
3.revolutionary S-OFF
4.use adb and misc_version to write a new version that you are pending to flash.
5.reboot to Bootloader
6.Make a cup of coffee
7.OK
keroro430 said:
download "PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip"
2.Flash it
Click to expand...
Click to collapse
Code:
c:\SDK_15\platform-tools>fastboot flash zip PG32IMG_Vivo_Gingerbread_S_KT_KR_2.3
2.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
sending 'zip' (262360 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
What could be wrong?
P.S. I have removed SIM and also microSD card, i't ok?
When I flash it via RUU, I got:
Code:
c:\SDK_15\platform-tools>fastboot reboot
rebooting...
c:\SDK_15\platform-tools>fastboot erase cache
erasing 'cache'... OKAY
c:\SDK_15\platform-tools>fastboot oem rebootRUU
... OKAY
c:\SDK_15\platform-tools>fastboot flash zip PG32IMG_Vivo_Gingerbread_S_KT_KR_2.3
2.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
sending 'zip' (262360 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)
Okay this is really old and from the evo xda threads but check it out it describes unbricking evo phones that were bricked by installing old ruu's. I'm not saying to follow this at all but it might lead you to try a different method of flashing I dunno
h ttp://forum.xda-developers.com/showthread.php?t=654119
Your going to have to mess around til you get it. Just don't let your battery get too low. Also make sure the radio isn't in the packaged zip your flashing, its not vital.
Create a goldcard, and copy the PG32IMG.zip to the root of sdcard(goldcard),enter the hboot and flash it.
Hi All,
I am trying to get my phone back to stock and trying to flash RUU zip via fastboot, however i am getting the below error, could you please help me understand what the error means :
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fastboot flash zip rom.
zip
sending 'zip' (1029979 KB)...
OKAY [ 59.742s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 186.470s
Thanks a lot
Could anyone please help me with this?
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
well so i guess there is no way currently to go back to stock with 1.544 hboot. I checked the RUU has my model id but i am s-on , so i guess i have nothing left but to sulk
gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
Do you know if there is anyway for me to go 100% stock with a 4.1.2 RUU , when i am on 4.2.2 with 1.544 hboot with s-on?
No not possible.
I just spent way too much time trying to figure this out. Today the mic on my one shat the bed, so I was attempting to return to stock to get a replacement. I am running the 1.31 software and foolishly tried to run back to 1.29. I am relocked, I have access to fastboot but nothing pass security verification. I've tried recoveries, my unlock time bin, and anything else I could throw at it. Nothing works. I always get the FAILED message. I am S ON, and security warning at the header of my boot loader screen. I can't get it to be recognized be adb either. Man would I love some advice to get past this. Please.
Sent from my Nexus 7 using xda app-developers app
Your good don't worry. Download a recovery from the dev section. Rename it something easy like recovery.img and place it in the same folder as your ADB (if you don't have ADB keep reading down to the bottom then come back and flash your recovery). Open a command prompt on your computer and cd to your adb dir. Connect phone in fastboot to computer and type fastboot flash recovery recovery.img (or whatever you named it. Then from recovery follow the guide for 1.31 RUU which I will link below.
Now to RUU follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
You will see this message (failed) ignore it and flash the RUU anyway.
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
It was lots of fun typing all of this on my phone.
Sent from my HTCONE using xda app-developers app
I can't get anything including recovery to flash. It all says Failed. Here's a pic of ,e trying to fastboot flash TWRP.
Sent from my Nexus 7 using xda app-developers app
ajd88 said:
I can't get anything including recovery to flash. It all says Failed. Here's a pic of ,e trying to fastboot flash TWRP.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Check PM
I think I got it. I had to re unlock the boot loader with a new token. I was trying to unlock with my old bin file. Thank you for helping me out much appreciated. Wasted way to many hours on this.
Sent from my Nexus 7 using xda app-developers app
Hit me up if you need anything else
ajd88 said:
I think I got it. I had to re unlock the boot loader with a new token. I was trying to unlock with my old bin file. Thank you for helping me out much appreciated. Wasted way to many hours on this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No worries, hope you get it sorted.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
It was lots of fun typing all of this on my phone.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I bet it was!! I wouldn't have tried that. More power to ya!! You are PRO!
Still getting
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
Im not stuck like I was I can get into recovery and boot, but everytime I try to Ruu I get this crap. I am Soff and have oem relocked everytime before attempting RUU. This sucks.
ajd88 said:
Still getting
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
Im not stuck like I was I can get into recovery and boot, but everytime I try to Ruu I get this crap. I am Soff and have oem relocked everytime before attempting RUU. This sucks.
Click to expand...
Click to collapse
Every time I got that message it was due to a bad or wrong choice in RUU files. I would try fastboot flashing this RUU.zip. Hopefully that will work for you. I have written up all the steps to follow that work for most people here. You are already past the tricky part.
Good luck.
MrFixit007 said:
Every time I got that message it was due to a bad or wrong choice in RUU files. I would try fastboot flashing this RUU.zip. Hopefully that will work for you. I have written up all the steps to follow that work for most people here. You are already past the tricky part.
Good luck.
Click to expand...
Click to collapse
That Zip file got me a little farther, still stuck though.
sending 'zip' (1029700 KB)...
OKAY [ 48.045s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 54.880s
Are you running the RUU from your PC?
bigdaddy619 said:
Are you running the RUU from your PC?
Click to expand...
Click to collapse
Yes I am. Running windows 8. I have never had issues before doing stuff like this. I'm stumped.
Edit: Think I'm good now.
ajd88 said:
That Zip file got me a little farther, still stuck though.
sending 'zip' (1029700 KB)...
OKAY [ 48.045s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 54.880s
Click to expand...
Click to collapse
When you get the please flush message you IMMEDIATELY run the exact same command again!!
Everything will work fine after that.
MrFixit007 said:
When you get the please flush message you IMMEDIATELY run the exact same command again!!
Everything will work fine after that.[/
Your right thats what I did. All good now. Thank you.
Click to expand...
Click to collapse
Hello all,
I am having trouble trying to restore my AT&T HTC One M7 back to being functional again. The phone was soft-bricked "somehow" by my ex-wife and have been trying to restore it for the past few months. I have done alot of searching and tried many options but nothing is working so far.
The phone had never been rooted and has no custom roms on it. After it was soft-bricked, I was able to get it unlocked at one point, but stupidly enough I followed some wrong advice on how to proceed from there and relocked the phone. Now I cannot unlock it again in order to try to put TWRP or recovery on the phone to get it working again.
So far I have tried the following approaches to this issue:
1)I tried going through the HTC dev site steps to get a unlock code, but nothing happens on the phone screen even after getting a successful notice in CMD screen. (I tried both the original code and getting a new code)
2)Every time I try to flash it on there also I get signature failures in CMD and nothing happens on the phone.
3)I also tried running a stock RUU app, but after the process beings the final update, I get a usb cable error saying it is unplugged when it is not.
Thanks in advance for any suggestions.
To me that sounds like it might be a corrupt boot loader. You could also try to gain s-off and flash a recovery that way. Rumrunner works well: http://rumrunner.us
If you can s-off it then you can flash an hboot image which should fix the issue. Just go to the hboot section on the rumrunner website. Then install TWRP etc....
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
MarkBell said:
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
Click to expand...
Click to collapse
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
I love Xda, and plan to become more involved. My thinking is he is likely flashing the wrong RUU. If there is a mistake to be made, I've made it.
---------- Post added at 07:47 PM ---------- Previous post was at 07:37 PM ----------
And sorry about screwing up that Fastboot command. Lol. Posting too early in the day I guess. Lol. It is indeed Fastboot oem lock. I skimmed over the fact he can't unlock the bootloader. Sorry.
clsA said:
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
Click to expand...
Click to collapse
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
You can flash just the firmware zip
It's on my android file host
I'll post the link when I get to my PC
MarkBell said:
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Click to expand...
Click to collapse
I tried again using different USB ports and different cables with the same error result. Both cables that I used are stock HTC One cables that came with this problem phone and my newer M8 version.
The RUU I have been trying is:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
MarkBell said:
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
Click to expand...
Click to collapse
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Squirrelsquisher said:
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Click to expand...
Click to collapse
MarkBell said:
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Click to expand...
Click to collapse
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
http://www.androidfilehost.com/?fid=23329332407580581
I meant that download specifically thinking along the lines of a bad file/download. clsA is very good and I recommend following any advice he gives.
clsA said:
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
Squirrelsquisher said:
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
nkk71 said:
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
Click to expand...
Click to collapse
I attached a screenshot of the getvar results before attempting those steps you posted.
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
oh crap, just saw your screenshot
are you using a USB3 port?
nkk71 said:
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
oh crap, just saw your screenshot
are you using a USB3 port?
Click to expand...
Click to collapse
My PC does not have USB3 ports, only USB2. I don't see how the speed of the transfer would affect the process though?
Hello Guys,
Sorry to bother again but I think I messed up bad, I accidently did this some how,(attached file) can you help me with it ?
todorov.drago1 said:
Hello Guys,
Sorry to bother again but I think I messed up bad, I accidently did this some how,(attached file) can you help me with it ?
Click to expand...
Click to collapse
That used to happen to me with some versions of TWRP. Which one do you have?
donkeykong1 said:
That used to happen to me with some versions of TWRP. Which one do you have?
Click to expand...
Click to collapse
TWRP v2.8.7.0.. is it because of that, that I cannot flash the RUU.zip from fastboot ?
When I try to flash it a second time it just stays there for 2 hours and nothing.
todorov.drago1 said:
TWRP v2.8.7.0.. is it because of that, that I cannot flash the RUU.zip from fastboot ?
When I try to flash it a second time it just stays there for 2 hours and nothing.
Click to expand...
Click to collapse
2.8.7.0 works fine for me. Can you go to bootloader menu and do factory reset from there? Then go to recovery and try again
donkeykong1 said:
2.8.7.0 works fine for me. Can you go to bootloader menu and do factory reset from there? Then go to recovery and try again
Click to expand...
Click to collapse
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
todorov.drago1 said:
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
Click to expand...
Click to collapse
Why not just flash the RUU that @alray mentioned in your other thread. I think your initial flash problem was because you didn't use htc-fastboot. The download link is in the "How to flash" instructions for the Lolipop ruu collection in the general thread.
mb_guy said:
Why not just flash the RUU that @alray mentioned in your other thread. I think your initial flash problem was because you didn't use htc-fastboot. The download link is in the "How to flash" instructions for the Lolipop ruu collection in the general thread.
Click to expand...
Click to collapse
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
todorov.drago1 said:
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
Click to expand...
Click to collapse
That's recovery. I ment bootloader. Press power+vol down, and you will get in bootloader menu. From there make a factory reset
todorov.drago1 said:
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
Click to expand...
Click to collapse
I think when others have seen this @alray and others suggest it could be adb drivers (make sure you have most current) and tray another usb cable and \or port. I know it worked the first time, sort of as it usully restarts automatically. But worth a try.
donkeykong1 said:
That's recovery. I ment bootloader. Press power+vol down, and you will get in bootloader menu. From there make a factory reset
Click to expand...
Click to collapse
Well, when I go to the bootloader and press factory reset I sends me to the recovery. I think that was normal. Is it not ?
mb_guy said:
I think when others have seen this @alray and others suggest it could be adb drivers (make sure you have most current) and tray another usb cable and \or port. I know it worked the first time, sort of as it usully restarts automatically. But worth a try.
Click to expand...
Click to collapse
I'll try with a different usb cable and different port, and ill get back to you. Thanks for the help fellas.
todorov.drago1 said:
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
Click to expand...
Click to collapse
Wait just a moment. I didn't see this post of yours. When fastboot prompts you to "flush image again immediately" what steps exactly do you do? Please describe it in your own words. I think I know what the problem is [emoji6]
todorov.drago1 said:
I'll try with a different usb cable and different port, and ill get back to you. Thanks for the help fellas.
Click to expand...
Click to collapse
Do you have HTCsync installed on your pc? If so uninstall it. Leaving only the HTC drivers installed. Reboot your pc and flash the RUU again.
HTCsync can cause ruu's to stall like that :good:
Sent from my SM-T230 using Tapatalk
donkeykong1 said:
Wait just a moment. I didn't see this post of yours. When fastboot prompts you to "flush image again immediately" what steps exactly do you do? Please describe it in your own words. I think I know what the problem is [emoji6]
Click to expand...
Click to collapse
Thanks mate for the help, i flashed it correctly. I just switched the usb's and it went on with the install.
And now can i ask you somethink else, after the install my phone says there is no IMEI num and doesnt exept my sim card can this be fix or is it hardware problem, it worked before tho?
todorov.drago1 said:
Thanks mate for the help, i flashed it correctly. I just switched the usb's and it went on with the install.
And now can i ask you somethink else, after the install my phone says there is no IMEI num and doesnt exept my sim card can this be fix or is it hardware problem, it worked before tho?
Click to expand...
Click to collapse
Sorry mate, I really can't help you with that. I never encountered that issue, so everything I say would be guessing, and potenetial fixes might ruin your phone. Sorry again [emoji20]
donkeykong1 said:
Sorry mate, I really can't help you with that. I never encountered that issue, so everything I say would be guessing, and potenetial fixes might ruin your phone. Sorry again [emoji20]
Click to expand...
Click to collapse
Nah Dude you did alot for me for it im am thankful alot. ill just have to take it to a GSM service to fix it then :angel:
todorov.drago1 said:
Nah Dude you did alot for me for it im am thankful alot. ill just have to take it to a GSM service to fix it then :angel:
Click to expand...
Click to collapse
Check your baseband as well. Unknown IMEI and baseband is a known issue. Unfortunately if flashing the ruu doesn't help its most probably a hardware problem. ?
Sent from my HTC One using Tapatalk
?
I'm trying to flash recovery.img with fastboot and it is downloaded, but when it starts to write
it says Failed (remote not allowed.) Any hints? Thanks
halloj said:
I'm trying to flash recovery.img with fastboot and it is downloaded, but when it starts to write
it says Failed (remote not allowed.) Any hints? Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?