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.
Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
axel_johnson said:
Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
Click to expand...
Click to collapse
1. This should not be in the development section......
2. Boot to bootloader.
3. Does it say Locked, Relocked, or Unlocked?
4. Does it say S-On or S-Off?
5. Do you have v1.83 or 1.85 bootloader?
6. Select Recovery, what happens?
1. This should not be in the development section......
2. Boot to bootloader.
yes boot with volumen - and power
3. Does it say Locked, Relocked, or Unlocked?
Unlocked, i try locked again but nothing the phone still stuck, running the command fastboot oem lock.
4. Does it say S-On or S-Off?
s-off along a few months with the method juonot... with wire.
5. Do you have v1.83 or 1.85 bootloader?
show the version 1.85
6.- recovery
don't work when selected the option recovery the phone show the screen logo along 1 second and back to screen boot.
Next step would be fast boot flashing a custom recovery. I recommend wcx or twrp. Once youve done that, youll be set to properly wipe and flash the ROM of your choice
wcxjb hello and try but I can not, I get the following error.
C: \ Useful HTC One X \ WCXJB_ROOT_PACK \ WCXJB_ROOT_PACK> fastboot flash zip jb_hboot.
zip
******** sending 'zip' (379 KB) ... OKAY [0.318s]
***************** writing 'zip' ... FAILED (remote: not allowed)
finished. total time: 0.642s
please what else I can do ... I need to operate this phone.
Extract the wcxrecovery.IMG from the zip..
Fastboot flash recovery wcxrecovery.IMG
You can't fastboot flash a zip
I tried to do that and I get the following error.
C:\Utiles HTC One X\WCXJB_ROOT_PACK\WCXJB_ROOT_PACK>fastboot flash recovery wcxr
ecovery.img
sending 'recovery' (6996 KB)... OKAY [ 1.720s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 3.178s
please help me.
Is your Boot loader unlocked?
yes the bootloader is unlocked, i try locked o relocked but not possibly, the phone was stuck.
please help what steps should I follow ... I want to retrieve the phone.
axel_johnson said:
please help what steps should I follow ... I want to retrieve the phone.
Click to expand...
Click to collapse
The only things I can think of that would cause this "writing 'recovery'... FAILED (remote: image update error)" would be:
1. You got a bad download
2. Bootloader is not properly unlocked
3. Your recovery partition got borked somehow
Things I would try next:
1. Redownload the recovery image and try again
2. fastboot oem lock to lock the bootloader, then go through the unlock process again
3. fastboot oem lock, run your carrier's RUU, reunlock bootloader, fastboot flash recovery wcxrecovery.img, fastboot flash boot boot.img (from ROM), boot to recovery, wipe data, system, dalvik, and cache, and flash ROM
pleas help me my htc rider
My phone refuse to boot up to normal background it is stuck on the htc logo hv tried factry reset bt still no progress it was caused by an apps I installed phone name htc rider vrsn 4.0 pls help me
I'm on the T-Mobile variant and have followed the steps on the motorola website to unlock the bootloader. When I boot into fastboot, it says the device is unlocked with at status code 3. When I run 'fastboot flash recovery recovery.img' everything seems to run fine:
fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.930sWhen I try to reboot into recovery mode it just shows me the warning that my bootloader is unlocked, then boots as normal. I don't know what to do. I've tried both the twrp and cwm recovery images. Any help?
what recovery did you flash?
waiflih said:
what recovery did you flash?
Click to expand...
Click to collapse
I've tried both the twrp and cwm recoveries that are available in the android development section.
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
mentose457 said:
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
Click to expand...
Click to collapse
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
elijahah said:
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
Click to expand...
Click to collapse
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
jayboyyyy said:
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
I'm already on 4.2.2. I'm guessing you mean to undo the recent OTA? How would I do that without a custom recovery or root?
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
flashallthetime said:
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
Click to expand...
Click to collapse
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
mentose457 said:
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
Click to expand...
Click to collapse
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
phositadc said:
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
Click to expand...
Click to collapse
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Thanks for all your help though guys.
Click to expand...
Click to collapse
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
mentose457 said:
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
Click to expand...
Click to collapse
I get this:
fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.071s
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
Excellent. Glad you got it working.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
PS you had recovery the first time you hit the up volume and it sent you to a screen that said "no command" from that screen if you press the up volume and power button together it sends you to the recovery screen. It may be down volume and power together to get passed that "no command" screen but its one of the two. I saw people having that same problem in the forum about maintaining root through the OTA.
phositadc said:
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
Click to expand...
Click to collapse
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
leonardoafa said:
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
Click to expand...
Click to collapse
Will charge up a bit over 50% and see. I still get permission denied. Plus when I try to get into recovery, I can't. The Motorola log shows up for a while, then restarts and boots normally into Android.
Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.
ergosteur said:
Just got my One back from warranty repair. Looks like they either gave me a new main board or updated my device, I'm on the latest Bell 4.19.666.8 with hboot 1.56.
I figured I would get a full nandroid backup of the phone at stock 4.4.2, but I can't seem to get fastboot boot to work. Don't want to flash the recovery as I want to get a backup of the stock one.
with the phone in FASTBOOT USB, I ran
$ fastboot boot openrecovery-twrp-2.7.0.0-m7.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.311s]
booting...
OKAY [ 0.000s]
finished. total time: 1.311s
But the device just sits at the fastboot screen and does nothing. It doesn't even respond to fastboot commands anymore so I have to force power off and reboot.
I saw on the Nexus 4 forum that on that phone you now have to specify a kernel command line with fastboot boot - something like
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Is this true for the One too? If so, what is the command line? I'm guessing lge.kcal is specific to LG devices.
Click to expand...
Click to collapse
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.
nkk71 said:
"fastboot boot ..." only worked on hboot 1.44.
and I can't answer about the N4 method if that would work or not; but I kinda doubt it.
Click to expand...
Click to collapse
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.
ergosteur said:
OK, thanks. Should I even bother trying to back up the stock recovery or just go ahead and flash a custom one? Would there be any way to do it without hboot 1.44? I see that temproot doesn't work on stock 4.4.2.
Click to expand...
Click to collapse
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?
nkk71 said:
Couldn't find stock recovery 4.19.666.8, but if it's for future OTAs then any stock recovery 4.19.xxx.x should work (maybe even 3.xx.666.x)
This is a good source for stock recoveries [Recovery]Collection of Stock Recovery
If you're using a stock recovery that is not a 100% match, then the OTA would just hang, and you have to manually reboot for it to continue.... you can check my guide under CWM method about info on that.
There's also @SaHiLzZ guide for Canadian users: http://forum.xda-developers.com/showthread.php?t=2529225
Or do you need it for some other reason?
Click to expand...
Click to collapse
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.
ergosteur said:
I was thinking more for archival purposes- Just in case. I restored my phone back to stock twice for warranty, your guide was very helpful.
I think I'll just go ahead and flash CWM/TWRP, my warranty is done anyway.
Click to expand...
Click to collapse
do go back to warranty you need to set phone to LOCKED, which is only possible with S-Off.
the fastboot oem lock command will set your bootloader to RELOCKED, so they would know you've unlocked it.... so stock recovery is the least of your worries if you want to ever go 100% back to stock.
stick with TWRP 2.6.3.3 or higher, but not 2.7.0.0 which seems to have problems with adb (and if i remember correctly charging when phone is off... though it could be a different one)
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
or 2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
EDIT: forgot to tell you why TWRP: it's compatible with 4.4 ROMs, CWM doesn't seem fully updated yet
Happy flashing :laugh:
Hi!
I am trying to root my Mi A2 without unlocking the bootloader. I have tried:
C:\Users\Dell\Desktop\root>fastboot boot TWRP.img
downloading 'TWRP.img'...
OKAY [ 1.025s]
booting...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 1.183s
I wasn't trying to flash, I was going to boot from the TWRP image. Theoretically I could boot to TWRP temporarily and then flash magisk or something.
I have considered using another thread's guide to unlocking the bootloader without the data wipe. The only thing is, I don't want a wipe operation still pending in recovery so if I ever decided to boot to recovery it would delete my data. I don't know if when I hold the volume button it will go back to fastboot mode and I know that I can temporarily boot to TWRP and flash, but still.
Help???
I think its not possible, you need to unlock the bootloader to root the device
vmf9911833 said:
I think its not possible, you need to unlock the bootloader to root the device
Click to expand...
Click to collapse
You cannot flash unsigned software without unlocking LE bootloader.
oem unlock, retry. I can fastboot boot official twrp, but it bootloops afterwards.