I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
did you make a back up?
I didn't unfortunately, I can get into recovery and as long as I leave it as 'Read-Only' it seems to mount everything. I think I need to get a stock image.
Resolved - used a Toolkit to go completely back to stock, kind of scared to try again now.
Follow directions and that won't happen again. Make sure you are on the correct version MDB08K BEFORE you start (you have the OTA), format not wipe in TWRP and you won't get caught in the boot loop.
Failing to do those two things will put you in a boot loop.
What toolkit did you use because i myself have this issue with my nexus 6p
Swatto86 said:
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
Click to expand...
Click to collapse
That warning is normal, and should be ignored if you want unlocked bootloader, custom ROMs, etc.
Here TWRP couldn't mount because you forgot to decrypt after flashing the modified boot.img.
If you have further issues, let me know.
A quick advise - Avoid toolkits. They are handy and easy, but if something goes wrong, it will be hard to track down the cause. On the contrary, doing thing manually, will not only make it easy, but will also help you learn more about your Android, and how it works.
Related
I really hope someone can help me out. I think I bricked my phone.
I tried to recover my phone back to stock with stock recovery so I can send it in for repair. When I installed 2.3.4 OTA update through zip, I accidentally clicked yes for updating 2.3.6. I didn't know, went to washroom and my phone won't boot. I thought no worries I'll install the zip again. Going into recovery, there's an android picture with an exclamation mark. I can't boot into phone and cannot load recovery. Someone please help >_<
download CWM and try to flash it through fastboot, and use that to flash a new img. im assuming you've done this before, having a custom recovery before now. if not, make sure you have fastboot setup, and if you don't go look through a rooting guide how to set it up then once you have it set up, move the new recovery you downloaded to the same folder as fastboot, then type
fastboot flash recovery name_of_recovery
of course replace the name_of_recovery with the exact filename of the recovery you downloaded. you can get the ClockworkMod recovery I think at www.clockworkmod.com
then boot into the new recovery and go to Mounts and Storage and Mount USB, and take the update.zip that you have and load it onto your SD Card, then go into the recovery and do as you would to flash the zip
Problem is, I don't think usb debugged was enabled. I tried to lock bootloader so I can just take it back to my carrier and say phone is screwed up, but when I tried, it said device not found.
The only way I think is using odin.
So I was trying to install the new Oreo beta, and couldn't get into TWRP, and couldn't get it to flash it either. So I tried to reinstall the stock recovery by using flashall, but during the process I accidentally disconnected my phone. For a while I was stuck in a bootloop, but I've gotten it to the point where I actually get in. But it still says my device is corrupted and cannot be trusted and may not work properly. Does anyone know how to fix this? The phone is functional, but I worry that it will fail to boot when I'm not near a computer.
Edit: Problem solved, realized I needed to flash the full stock.
that message comes up when bootloader is unlocked
For that specific boot message (I believe it's a red screen) you have to use invisiblek's boot fix.
Look at his page https://mata.readthedocs.io/en/latest/ at the very bottom and follow the instructions.
Quick Question
Ellises said:
For that specific boot message (I believe it's a red screen) you have to use invisiblek's boot fix.
Look at his page https://mata.readthedocs.io/en/latest/ at the very bottom and follow the instructions.
Click to expand...
Click to collapse
Do I fastboot flash this boot image then the stock boot image or just over top of the stock boot image? Also the boot fix image is only ~26mb while the stock boot image is ~65mb?
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
abstractartemis said:
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
Click to expand...
Click to collapse
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
ashyx said:
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
Click to expand...
Click to collapse
So just keep flashing it until i can boot to twrp recovery basically?
abstractartemis said:
So just keep flashing it until i can boot to twrp recovery basically?
Click to expand...
Click to collapse
What's stopping you boot to Download mode?
ashyx said:
What's stopping you boot to Download mode?
Click to expand...
Click to collapse
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
abstractartemis said:
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
Click to expand...
Click to collapse
If you can flash twrp then not booting to twrp must be pilot error.
It MUST be done immediately after flashing in odin.
I had already installed TWRP and decided to wipe the whole data from my phone, thinking that it's going to be the same as a factory reset because I want to reset my phone. Phone startup went well, no hiccups or anything. Then I decided to flash TWRP again. But I never managed to actually install it. I follow the manuals from here and here, but I somehow always can't boot into the recovery. I use the same ADB and fastboot I used to install TWRP from before. Flashed .img, reboot, can't enter the recovery, starts over again, and this goes on and on. Until now, whenever I want to boot normally, I keep getting stuck at the "Zenfone" logo screen. The only different thing that I could think of that caused this is when I decided to use Universal ADB Helper, because maybe it'll work there i thought, and I flash the twrp.img using the "Flash Recovery via fastboot" command. If there's anything that could help me, even if it meant resetting the phone again, I'd very much appreciate it.