Hello,
I have some problem on my phone (AOSP 9) but I didn't know why (I didn't download any new apps, last thing was Magisk update). Now more than the half of the apps don't work, battery drain very fast and I can't restart and shutdown the phone (or I need to do soft reset).
I tried to do a factory reset directly from Android but it doesn't work.
I tried to flash TWRP and and I got this message.
Code:
Y:\Download>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15864 KB) OKAY [ 0.512s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.204s]
Finished. Total time: 0.919s
According to other subjects it's not a big deal so I decided to restart in bootloader but now I'm stuck on TWRP logo. I waited more than 1h30 and nothing happens.
Have you got an idea ?
Thank you
Do a clean flash of the stock ROM.
Thank you, it works, and I was able to reinstall AOSP.
Thank you again
Related
Bought Japan Variant HTC 10,
S-off, Bootloader Unlocked.
[flashed TWRP once and did Backup.]<-yeah i did
Changed CID to US Unlocked one and RUUed Android 7.0
All went great at this point.
Then I tried to flash TWRP again and now i just can't boot into it.
flashing went smoothly, at leat log says;
fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (21992 KB)...
OKAY [ 1.717s]
writing 'recovery'...
(bootloader) HOSD CL#831921
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.529s]
finished. total time: 4.249s
fastboot reboot-bootloader
AAAAAAAAAAAAAAAND I just can't boot into TWRP.
Phone just showing htc logo for a while and reboot to ROM.
So i tried fastboot boot twrp.img method, still not working.
download mode screen
Am I missing sth? like key combo to show twrp or bug at twrp 3.0.2.6?
I had the exact same problem, I solved it by flasing the twrp 3.0.3-0 unofficial version that you can find on the twrp recovery's thread
Edit: I don't know if this is the right way to do it, it worked for me but I'm new in the modding world and I'm not sure it will work for you too or if it's safe. Maybe is better to wait for someone that knows more than me.
solved
Since I did OTA from 2.28.617.8 to 2.38.617.6,
I googled and RUUed 2.38.617.6, not 2.28.617.8 from official HTC US hp.
and I flashed twrp 3.0.3.0 unofficial, instead of 3.0.2.6 official.
I don't know which one was critical, but everything went fluently.
Seems like 3.0.3.0 was the critical one.
Thx @fratorga100, for the reply.
I recently got a replacement HTC 10 unit from HTC. I am attempting to install TWRP on it, but am unable to.
I did the standard unlock method from HTCdev.com. Everything there worked fine and the device is unlocked.
I have downloaded multiple versions of the twrp.img but am having the same issue across the board. I can't figure out what is wrong, as I had no issues on my previous HTC 10 unit.
C:\HTC>fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (47708 KB)...
OKAY [ 2.668s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.074s]
finished. total time: 5.773s
Everything seems like it's fine, but when I try to boot into bootloader and then recovery it gives me the htc, this build is intended for develpment purposes... screen and then goes directly into the rom never loading TWRP.
I can't figure this out, as I never had any issue before. My device is updated with the latest US version.
Can anyone help?
Thanks
I was having the exact same issue and was literally typing the same post as you when I saw yours.
I found this link with the unofficial TWRP builds and flashed 3.0.3.3. That finally got me into TWRP. You'll still see the gray HTC letters with the red disclaimer, but wait a few seconds and it should boot into recovery.
Hopefully that helps.
yoderz said:
I was having the exact same issue and was literally typing the same post as you when I saw yours.
I found this link with the unofficial TWRP builds and flashed 3.0.3.3. That finally got me into TWRP. You'll still see the gray HTC letters with the red disclaimer, but wait a few seconds and it should boot into recovery.
Hopefully that helps.
Click to expand...
Click to collapse
That worked!
Thanks!
I have searched and searched but cannot find anywhere that tells me what these messages mean in fastboot.
Example:
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Please help.
Thank you.
Did you do something before this happened?
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
myjess said:
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
Click to expand...
Click to collapse
probably u just delete system image file
Is ok, got it all working again.
Thanks.
I took the Dec 2019 OTA, by uninstalling Magisk, took the OTA ( did not reboot) and where I think i went wrong was when re-patching the boot.img i choose to install on inactive slot.
I have since tried many other things to recover from this. Is it possible to fix it without wiping and losing my data?
I have myself at No vaild slot to boot
EDIT: No I am on Enter Reason: error boot prepare
=========================================
After 10hrs of throwing crap at the wall and having nothing stuck. I just started over with the Dec 2019 factory image.
Androider4Life said:
I took the Dec 2019 OTA, by uninstalling Magisk, took the OTA ( did not reboot) and where I think i went wrong was when re-patching the boot.img i choose to install on inactive slot.
I have since tried many other things to recover from this. Is it possible to fix it without wiping and losing my data?
I have myself at No vaild slot to boot. EDIT: No I am on Enter Reason: error boot prepare
Click to expand...
Click to collapse
What happens when you flash the stock boot.img? Have you tried fastboot flashing the full image (not OTA) removing the wipe flag (-w) from the flash-all.bat? If that doesn't work, your data may already be gone or corrupt. Next step, flash full image and allowing data wipe.
v12xke said:
What happens when you flash the stock boot.img? Have you tried fastboot flashing the full image (not OTA) removing the wipe flag (-w) from the flash-all.bat? If that doesn't work, your data may already be gone or corrupt. Next step, flash full image and allowing data wipe.
Click to expand...
Click to collapse
============================================================
boot.img flash, Phone reboots to White G Screen and sits there. If I hold the power button till it reboots it goes back to the White G Screen and sits there.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.835s]
Writing 'boot_a' OKAY [ 0.595s]
Finished. Total time: 3.705s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.045s]
Finished. Total time: 0.052s
Androider4Life said:
============================================================
boot.img flash, Phone reboots to White G Screen and sits there. If I hold the power button till it reboots it goes back to the White G Screen and sits there.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.835s]
Writing 'boot_a' OKAY [ 0.595s]
Finished. Total time: 3.705s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.045s]
Finished. Total time: 0.052s
Click to expand...
Click to collapse
Assuming that was the stock boot.img extracted from the Google image, you could also try flashing the same to both slots before trying flashing the full factory image, removing the wipe flag first. Some people like to update using OTA's. I ALWAYS flash the full image every month on my Pixel devices and have never had an issue.
v12xke said:
Assuming that was the stock boot.img extracted from the Google image, you could also try flashing the same to both slots before trying flashing the full factory image, removing the wipe flag first. Some people like to update using OTA's. I ALWAYS flash the full image every month on my Pixel devices and have never had an issue.
Click to expand...
Click to collapse
======================================================================================
Back to setting on the White G screen.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot --slot all boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.635s]
Writing 'boot_a' OKAY [ 0.623s]
Sending 'boot_b' (65536 KB) OKAY [ 3.126s]
Writing 'boot_b' OKAY [ 0.618s]
Finished. Total time: 7.624s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.033s]
Finished. Total time: 0.071s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>
Flashing the December Full image (removing the -w) I am back to the Error Reason: no valid slot to boot. I have attached the log
See my thread a couple of posts down about the December update for the fix.
DOMF said:
See my thread a couple of posts down about the December update for the fix.
Click to expand...
Click to collapse
I have read thru it and tried somethings with no luck..which part fixed it for you?
If I could just get to a point that I can access my internal storage to back up some stuff, I'd be ok full wiping after that.
After 10hrs of throwing crap at the wall and having nothing stuck. I just started over with the Dec 2019 factory image.
flash-all.sh without -w, adb rebbot bootloader, fastboot boot image-newpixel3xlRemove.img, adb reboot bootloader, fastboot flash boot magisk-patched.img
DOMF said:
flash-all.sh without -w, adb rebbot bootloader, fastboot boot image-newpixel3xlRemove.img, adb reboot bootloader, fastboot flash boot magisk-patched.img
Click to expand...
Click to collapse
Having the same issue.
What is ''image-newpixel3xlRemove.img''
Hey guys, first time posting, hoping I can get some help with these very frustrating problems. My device is an XT1952-4 running Android 10 with bootloader unlocked. I'll break this in to two sections for simplicity:
Magisk
I got a stock firmware img from the Rescue and Smart Assistant. (I had to use it to save my device after almost ruining it on a prior attempt with an incorrect img.) I installed the latest Magisk Manager (8.0.4 (4768)), and got it read to install Magisk 20.4 (20400). I used this to patch the stock img. I grabbed the patched img off my phone and put it into my adb folder. I then rebooted into fastboot. Here's how the flash command line went:
fastboot flash boot_a magisk_patched_x2DRE.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (17629 KB) OKAY [ 0.423s]
Writing 'boot_a' (bootloader) Image signed with key
I then tried to reboot to recovery, which resulted in an android screen saying, "No command." I was able to subsequently get to the regular recovery menu by using power + volume up, but after rebooting again, Magisk still says, "Installed: N/A". I've tried this like a dozen times and can't get it to install.
TWRP
With this one, I've tried using two different TWRP builds. (Or at least I presume they're two different TWRP builds.) One is a 3.3.0-0 River custom for G7 Play, the other is from this thread: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
I used the DTBO from the above-listed thread.
I get the same result with trying to fastboot either TWRP img from my adb folder. I get the following command line:
fastboot flash dtbo dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (965 KB) OKAY [ 0.186s]
Writing 'dtbo_a' OKAY [ 0.054s]
Finished. Total time: 0.287s
fastboot boot recovery.img
Sending 'boot.img' (22156 KB) OKAY [ 0.486s]
Booting OKAY [ 0.163s]
Finished. Total time: 0.687s
After this, I get to the Team Win splash page showing the version of TWRP, but it hangs indefinitely on that screen. I am able to shutdown by holding the power button. Again, I've tried this about a dozen times with the same result.
I'd really appreciate any help with either of these issues, or even suggestions of other ways to root a G7 Play. Thanks!
TWRP I can't help you with as I haven't tried installing it.
Magisk is partially solved in the thread here.
Check the posts by myself and M47Z.
The short version is that the Moto boot image needs some, rather difficult, manual massaging before you can install Magisk to it.
Curmudge0n said:
Hey guys, first time posting, hoping I can get some help with these very frustrating problems. My device is an XT1952-4 running Android 10 with bootloader unlocked. I'll break this in to two sections for simplicity:
Magisk
I got a stock firmware img from the Rescue and Smart Assistant. (I had to use it to save my device after almost ruining it on a prior attempt with an incorrect img.) I installed the latest Magisk Manager (8.0.4 (4768)), and got it read to install Magisk 20.4 (20400). I used this to patch the stock img. I grabbed the patched img off my phone and put it into my adb folder. I then rebooted into fastboot. Here's how the flash command line went:
fastboot flash boot_a magisk_patched_x2DRE.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (17629 KB) OKAY [ 0.423s]
Writing 'boot_a' (bootloader) Image signed with key
I then tried to reboot to recovery, which resulted in an android screen saying, "No command." I was able to subsequently get to the regular recovery menu by using power + volume up, but after rebooting again, Magisk still says, "Installed: N/A". I've tried this like a dozen times and can't get it to install.
TWRP
With this one, I've tried using two different TWRP builds. (Or at least I presume they're two different TWRP builds.) One is a 3.3.0-0 River custom for G7 Play, the other is from this thread: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
I used the DTBO from the above-listed thread.
I get the same result with trying to fastboot either TWRP img from my adb folder. I get the following command line:
fastboot flash dtbo dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (965 KB) OKAY [ 0.186s]
Writing 'dtbo_a' OKAY [ 0.054s]
Finished. Total time: 0.287s
fastboot boot recovery.img
Sending 'boot.img' (22156 KB) OKAY [ 0.486s]
Booting OKAY [ 0.163s]
Finished. Total time: 0.687s
After this, I get to the Team Win splash page showing the version of TWRP, but it hangs indefinitely on that screen. I am able to shutdown by holding the power button. Again, I've tried this about a dozen times with the same result.
I'd really appreciate any help with either of these issues, or even suggestions of other ways to root a G7 Play. Thanks!
Click to expand...
Click to collapse
when TWRP hangs like that after booting i've found in my own experiences that is usually caused from the version of TWRP you are using. Or you could have just downloaded a bad file of TWRP if you didn't use the official website. I currently use twrp-3.5.1 for my g7 play xt1952-t channel. hope this helps a little.