Related
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
jcr67 said:
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
Click to expand...
Click to collapse
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED?
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
tpbklake said:
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED? .
Click to expand...
Click to collapse
yep
tpbklake said:
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
Click to expand...
Click to collapse
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
jcr67 said:
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
Click to expand...
Click to collapse
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
jcr67 said:
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
Click to expand...
Click to collapse
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Drugzy said:
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Click to expand...
Click to collapse
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s
jcr67 said:
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s
Click to expand...
Click to collapse
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
tpbklake said:
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
Click to expand...
Click to collapse
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s
HBOOT now says:
*** RELOCKED ***
*** Security Warning ***
jcr67 said:
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s
Click to expand...
Click to collapse
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Reinstall the HTC ruu
Sent from my HTC Raider X710e using xda app-developers app
tpbklake said:
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Click to expand...
Click to collapse
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
jcr67 said:
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
Click to expand...
Click to collapse
Yes you should be ok.
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
yep he will be , during my downgrade i had to relock with security warning and ruu fixed it all
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
Thanks very much. The stock ICS RUU has now installed successfully. I guess when I originally tried to reinstall it, I had left out the 'RELOCK' step, which is why it failed.
So now I am back to the start (stock ICS + HBOOT 2.02 S-ON), and want to get S-OFF and install your ROM zip. ,What I originally intended to do to get S-OFF was:
1) Unlock the bootloader, flash CWM Recovery, flash SU
2) Run downgrade GB RUU
3) S-off with Revolutionary
4) Install Blackrose HBOOT
5) Install your vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But step 2) failed with an unknown error. (I then tried to install your zip, and the rest is the sad history.....).
So what caused step 2 to fail? Did I need to relock the bootloader first?
Many thanks for your help, tpbklake
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly.
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly. p
Click to expand...
Click to collapse
That's it. HBOOT is remaining at 2.02.0002 after runme.cmd
Is the device rooted?
y OR n:y
Waiting for device to connect
Device found
Pushing misc_version
2455 KB/s (367096 bytes in 0.146s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Cleaning temp files
Any ideas anyone?
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Click to expand...
Click to collapse
No, I'm unlocked and rooted
Does the stock ruu have superuser installed? If it does I'm outta ideas.
Sent from my HTC Incredible S using xda app-developers app
---------- Post added at 07:58 PM ---------- Previous post was at 07:40 PM ----------
One more thing, I would try flashing another ROM, i came from Niks Sense 4a rom, and the script worked with no issues.
Remember you will need to manually flash the boot.img of the rom as you are S-ON.
jcr67 said:
No, I'm unlocked and rooted
Click to expand...
Click to collapse
Open a command window and then type in the command:
adb shell
If you get a # prompt then your ROM is rooted correctly and the script should run. If it doesn't then the ROM isn't properly rooted and the script will fail.
For this quick how-to I will be using the file name Rom.zip as default for the Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM-1.zip firmware download available from
O.M.J. here (use ENCRYPTED version)
http://forum.xda-developers.com/showthread.php?p=40712553
From fastboot you need to first re-lock your bootloader
fastboot oem lock
Once locked it will boot back into bootloader
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
Make sure device is still in ruu mode(black HTC screen). If not rerun
fastboot oem rebootRUU
now simply reflash the rom.zip
fastboot flash zip Rom.zip
Let it run and it should finish this time
It will reboot to a fully stock build.
just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
The most common error is typically
(Error 155)
You did not re lock your bootloader first
-go relock and flash again
Thanks for the quick how-to. I've done plenty of similar things on all of my old Sammy devices with Odin, but this is my first HTC handset (so glad I made the switch).
bricked my phone, trying to flash it back to stock, hopefully you can help
i can get to bootloader, and can get to fastboot how do i relock bootloader?
fastboot oem lock - what does this mean?
Once locked it will boot back into bootloader
fastboot rebootRUU - is this an option i will see? how will i get the phone to reboot RUU?
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder. How can i get the rom.zip to my adb/fastboot folder
- my phone won't boot it hangs at the green htc screen. I can't mount the phone to add files to it.
thanks in advance
gu12u7 said:
bricked my phone, trying to flash it back to stock, hopefully you can help
i can get to bootloader, and can get to fastboot how do i relock bootloader?
fastboot oem lock - what does this mean?
Once locked it will boot back into bootloader
fastboot rebootRUU - is this an option i will see? how will i get the phone to reboot RUU?
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder. How can i get the rom.zip to my adb/fastboot folder
- my phone won't boot it hangs at the green htc screen. I can't mount the phone to add files to it.
thanks in advance
Click to expand...
Click to collapse
fastboot oem lock <---- this is the cmd u type, u need sdk tools installed
fastboot rebootRUU <----- another cmd u need to type
if u dont have sdk, just grab hasoons all in one toolkit, it will be much easier....another option is to run the RUU from windows (see 2nd link)
http://forum.xda-developers.com/showthread.php?t=2236814
http://forum.xda-developers.com/showpost.php?p=40737373&postcount=18
Hey kids, it's fastboot oem rebootRUU nice tutorial!
Sent from my HTCONE using Tapatalk 2
I get this error
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
any idea?
thanks!
Your either not using the correct Rom.zip for your device or your using one that has been decrypted. It has to be a untouched, encrypted Rom.zip.
Thank you all this info is good for when I root it.
Sent from my HTCONE using xda app-developers app
help with error
is there any way to skip the main version check. I've pasted my command prompt message below.
help and advice would be greatly appreciated
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
I can s-off, and set the bootloader to relocked... Would it work that way?
Sent from my HTC One using xda premium
mathrania said:
I can s-off, and set the bootloader to relocked... Would it work that way?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
no way to S-off htc rhyme :'(
i try to do this but i keep get failed eror 90
i try it twice and more
what can i do?
Q
Hey .. I use a HTC One M7 from USA T Mobile... I currently have an unlocked bootloader and s off
I'm currently using custom mid and cid of Europe flashed by exe RUU
So my question is can I flash d zip by relocking bootloader... And change the mid and cid as my desire ..(HTC__038 India)
And continue with your method?? ... Plzz reply asap
tomer861 said:
i try to do this but i keep get failed eror 90
i try it twice and more
what can i do?
Click to expand...
Click to collapse
Error 90 is a version error I believe. The Rom.zip you are trying to flash is a older firmware than what you are currently using on your device. It could also be a cid/mid mismatch. More info on your device and the firmware your trying to flash is needed to really do anything more than just speculate.
Do you have to relock first if you are s off and unlocked with revone? If so, can you relock using the revone method again?
Also, do you have to extract a separate file inside the ruu zip itself to flash?
Thanks
Sent from my HTCONE using xda premium
arcs_porwal said:
Hey .. I use a HTC One M7 from USA T Mobile... I currently have an unlocked bootloader and s off
I'm currently using custom mid and cid of Europe flashed by exe RUU
So my question is can I flash d zip by relocking bootloader... And change the mid and cid as my desire ..(HTC__038 India)
And continue with your method?? ... Plzz reply asap
Click to expand...
Click to collapse
The RUU changes your CID. You'd have to change it after the RUU. But why not leave it as Super CID? What's the point?
18th.abn said:
Error 90 is a version error I believe. The Rom.zip you are trying to flash is a older firmware than what you are currently using on your device. It could also be a cid/mid mismatch. More info on your device and the firmware your trying to flash is needed to really do anything more than just speculate.
Click to expand...
Click to collapse
I've flashed older firmware so I don't think that is it. Also, the CID gets changed so it doesn't have to match. He/She should copy/paste where the error occurs for us to have some context.
jacobspecht said:
Do you have to relock first if you are s off and unlocked with revone? If so, can you relock using the revone method again?
Also, do you have to extract a separate file inside the ruu zip itself to flash?
Thanks
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
You should be able to relock in Fastboot using 'fastboot oem lock'
is there a work around for this version yet 1.31.651.2
18th.abn said:
For this quick how-to I will be using the file name Rom.zip as default for the Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM-1.zip firmware download available from
O.M.J. here (use ENCRYPTED version)
http://forum.xda-developers.com/showthread.php?p=40712553
From fastboot you need to first re-lock your bootloader
fastboot oem lock
Once locked it will boot back into bootloader
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
Make sure device is still in ruu mode(black HTC screen). If not rerun
fastboot oem rebootRUU
now simply reflash the rom.zip
fastboot flash zip Rom.zip
Let it run and it should finish this time
It will reboot to a fully stock build.
just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
The most common error is typically
(Error 155)
You did not re lock your bootloader first
-go relock and flash again
Click to expand...
Click to collapse
i was getting this C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
then did the encripted file and now im getting
<remote: 43 main version check fail.
i think i flashed the international revolution ROM and my image version now is 1.31.651.2
how can u tell if ur using the correct rom?
evoshift617 said:
how can u tell if ur using the correct rom?
Click to expand...
Click to collapse
there is no Ruu for .31
fastboot boot recovery and then do this:
adb shell
echo 1.29.00 | dd if=/dev/block/mmcblk0p19 bs=1 skip=160
and then just fastboot oem lock and run the RUU
I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.
Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.
Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]
So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
virusdunil said:
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
Click to expand...
Click to collapse
I can have the phone in fastboot and run adb reboot bootloader and it says no devices found although the huawei HiSuite can detect the device being plugged in as it loads up when I plug the phone in
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
virusdunil said:
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
Click to expand...
Click to collapse
Not going to lie I am slightly out of my depth here, could you explain that further? I'm assuming I need to download an update.app but I have no idea where from or extracting the kernel from it
thanks
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
virusdunil said:
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
Click to expand...
Click to collapse
That Didn't work i just got:
C:\Users\jamie\Desktop\platform-tools>fastboot flash recovery KERNEL.img
target reported max download size of 471859200 bytes
sending 'recovery' (24576 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.537s
im assuming its due to the bootloader not being unlocked. and in the meantime im running a deepscan on my hard drive to see if I can recover my unlock code which was lost when cloning to a new ssd. It has a few hour left though
you have it wrong...
its fastboot flash kernel KERNEL.img
virusdunil said:
you have it wrong...
its fastboot flash kernel KERNEL.img
Click to expand...
Click to collapse
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
virusdunil said:
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
Click to expand...
Click to collapse
I have android studio, how do I flash the img with it?
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
virusdunil said:
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
Click to expand...
Click to collapse
exactly the same :
C:\Users\jamie\AppData\Local\Android\Sdk\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.533s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.542s
Is it maybe worth seeing if I can get the serial number product emei and product id without the os?
Jyndon said:
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
Click to expand...
Click to collapse
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
kwaichang said:
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
Click to expand...
Click to collapse
I don't know that I do have access though as the device doesn't appear in adb devices list and the bootlaoder is locked.
Although I think I may have found a way of flashing a new bios without bootloader by using the huawei recovery installation.
The default one that uses wifi obviously doent work because its crap but while the device is off I can hold vol+ vol- and power and it loads into an installation screen that shows installation failed but i found that it maybe possible to flash the bios this way by putting the update.app onto the sd card. However the problem I'm having is that windows says the file is too big to copy and unzipping it inside of the sd card doesnt work either. Any ideas as to how I might be able to do it like this? (similar to this: https://android.stackexchange.com/q...are-installation-failed-error-when-booting-up and this too https://forum.xda-developers.com/p9-plus/help/software-install-failed-updating-p9-t3587676)
SOLVED
I managed to get most of the information to unlock the bootloader from the box which I luckily kept, then for the product ID I used https://imei24.com/warranty_info/Huawei/865545034273084/ and it worked perfectly!
Bootloader unlocked and then I used the common HWOTA to rebrand it back to its original firmware.
Thanks to those who helped.
Jyndon said:
So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Click to expand...
Click to collapse
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
I know this is late but none the less, using the emei code I was able to request my code to unlock the bootloader through hwota. You cannot request this code anymore a way so you have to pay for dc unlocker which can rip the unlock code from the device.
petr.hybler said:
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
Click to expand...
Click to collapse
Is your bootloader unlocked?
If not you have your bootloader unlock code?
If not then you will need to pay for some software to get that code.
From there you can unlock the bootloader and use adb/fastboot again
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b