Error : 43, while restoring RUU from zip - One (M7) Q&A, Help & Troubleshooting

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.

Related

[Q] Unsuccessfuly unroot - Main Version is older!

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.

[Q] Rooted - Update firmware and ROM?

I'm rooted, on stock, with a custom ROM installed. I'm trying to update to the latest software, and found a thread with the new stock ROM, rooted, and an altered firmware update, with hboot, boot, and recovery removed:
http://forum.xda-developers.com/showthread.php?t=2766604
My plan was: update firmware in fastboot, then flash the ROM in recovery (I'm assuming only cache wipe is needed, since it's stock).
I tried to start by updating the firmware, using the instructions in the thread, but am getting the error message:
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 2.751s
I can't figure out how to get past this, and the thread is locked, so I can't ask there. Any help in updating ROM/firmware would be greatly appreciated.
Edit... is it because I'm S-On?
Yes it's because you are s-on.

[Q] No Red Text Firmware 7.17.1540.7 Solved

Has anyone done a no red text version of the firmware for 7.17.1540.7? This is from the current dev edition release of lollipop. At this point I can't seem to find it if someone has done one already.
I have done one, but not tested it yet. If you want to test it, go ahead but I'm not responsible if this brick your phone.
If you want to test it, report if its working fine, then I'll upload it to my thread and give you credit for testing it. You can compare the origianl hboot with this one with an hex editing tool to double check if you want.
Edit:
7.17.1540.7 no red text hboot available here: http://forum.xda-developers.com/htc-one/general/stock-rom-reset-developer-edition-t2915170
Thanks! I tested and it works. I did verify it against my copy of the clean hboot here and it checked out and based on instruction I saw elsewhere looked fine so I took a try. Here is the zip pack I used. It only updates the hboot (I've seen others doing a full pack) so it is best run on top after already having firmware 7.17.1540.7.
Please note it may appear to get stuck at about 75%. As long as it says OKAY at the end and does not indicate it failed then it should be ok to reboot. It got stuck for me on my screen so I had to fastboot reboot-bootloader after. From my understanding that last 25% is actually the reboot stage which doesn't happen automatically so here you do get a chance to check the result before rebooting manually.
For those that do download from this post...
If it says FAILED at the end DO NOT reboot the device. Instead try to flash again or flash a stock hboot. If you reboot at this point there is a very high chance it will not boot and become a lightweight doorstop. Let's not have that happen ok?
Trial run (serial is censored):
Code:
C:\Users\User\Desktop>fastboot flash zip 7.17.1540.7_no_red.zip
target reported max download size of 1514139648 bytes
sending 'zip' (603 KB)...
OKAY [ 0.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.211s]
finished. total time: 2.461s
C:\Users\User\Desktop>fastboot devices
HT42CW000000 fastboot
C:\Users\User\Desktop>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s
signes or unsigned firmware?
Hi,
I'm sorry for the noob question but what's the difference of a signed and unsigned firmware?
shinji257 said:
Thanks! I tested and it works. I did verify it against my copy of the clean hboot here and it checked out and based on instruction I saw elsewhere looked fine so I took a try. Here is the zip pack I used. It only updates the hboot (I've seen others doing a full pack) so it is best run on top after already having firmware 7.17.1540.7.
Please note it may appear to get stuck at about 75%. As long as it says OKAY at the end and does not indicate it failed then it should be ok to reboot. It got stuck for me on my screen so I had to fastboot reboot-bootloader after. From my understanding that last 25% is actually the reboot stage which doesn't happen automatically so here you do get a chance to check the result before rebooting manually.
For those that do download from this post...
If it says FAILED at the end DO NOT reboot the device. Instead try to flash again or flash a stock hboot. If you reboot at this point there is a very high chance it will not boot and become a lightweight doorstop. Let's not have that happen ok?
Trial run (serial is censored):
Click to expand...
Click to collapse
Thanks for reporting, will remove the file from this thread and post it I'm my collection thread and also in a firmware.zip
RucaNebas said:
Hi,
I'm sorry for the noob question but what's the difference of a signed and unsigned firmware?
Click to expand...
Click to collapse
Signed firmware is official HTC firmware signed with their private (encrypted) key. S-ON phones can only flash signed firmware. Firmware to flash must be the same version or newer (higher) than whats already running on the phone and bootloader must be locked/relocked.
S-OFF phone can flash unsigned firmware package, like this one, with a modded bootloader (hboot), no matters what the version is can be done with an locked/unlocked/relocked bootloader.

[Q] How to unroot S-on, hboot 1.61.0000 ?

I want to unroot to get the Google drive offer for HTC One.
My phone info:
Code:
It is HTC One M7, SIM Free international,
M7_UL,
CID: HTC__102,
model id:PN0710000
HBOOT-1.61.0000
os-7.19.401.30
OpenDSP-v35.120.274.0718
RADIO-4T.35.3218.16
s-on,
TWRP,
unlocked.
rooted.
I have the OTA zip files for the latest update, and also the nandroid backups of my phone.
What I have tried so far:
I know that I need s-off for unrooting, but I read in forum that if I have the firmware for exact same CID and modelID of my phone, I can unroot with s-on. So I extracted the firmware.zip from the latest OTA that I received from carrier. And I assume that it has the same CID and modelID for me.
1. I booted into bootloader, fast boot and run "fastboot oem lock"
It worked fine, phone restarted in the bootloader and it said "re-blocked"
2. I ran the command "fastboot oem rebootRUU "
It took some time, but eventually, the phone restarted automatically. It showed a bootloader screen with no option, just showing phone infor and the word RUU in the middle.
3. Then I ran the command "fastboot flash zip firmware.zip", I get the following result in the command terminal:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (44368 KB)...
OKAY [ 2.737s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(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: 8.585s
and in the phone screen it says:
Code:
"Main version is older!
Update Fail"
What should I do to unroot hboot 1.61, s-on ?

And again Help Needed.

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?

Categories

Resources