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?
Related
I selected to install 4.4 from my OTA notification and after it restarted my phone and then had the animation of an Android working it then went to the black screen with the white "Google" and it has been stuck there ever since. I held down the power key for ten seconds and it restarted and seems to be stuck in a bootloop. I tried entering recovery but i get a broken android animation saying i believe "no command"
So what can I do?
My phone was stock, so this should have been a simple update right?
I am pretty much a noobie.
I followed a step by step set of instructions for sideloading the update via a zip file, but when I get to the point I need to enter recovery mode nothing happens, i cant get to where i need to be. And my computer doesnt see my phone anymore when I plug it in via USB
Any advice would be greatly appreciated
thanks
Sideload the flashable zip of stock rom or any rom with the same android version in recovery ( guide )
Then flash back stock factory images (optional) ( guide ).
You can also refer this thread here.
Good luck.
I'm having a problem getting into my recovery. I have the D800. It started out I sideloaded cwr thru twrp. And it said it flashed fine. I selected to reboot back into recovery and got a fastboot error. So i tried just rebooting and couldnt get passed the splash image. So I did the whole flash stock firmware. And after i got done with that, I think I did the ota update, And I got my phone rerooted. But still no recovery, it loads to a black screen and my pc says I have to format drives from like u-z but one has a folder titled image with these files. I've tried adb pusing and flashy and nothin,.Please help
never mind I got it fixed I think. Please delete post
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Skroutz said:
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Click to expand...
Click to collapse
are u stuck in cmw recovery??
Stock recovery.... :/
Sent from my GT-I9100 using XDA Free mobile app
Same Problem here! Exact Same
Also having this issue, stuck in the secure boot loop, can't get to download mode.
Im exactly the same - im stuck in TWRP and cant boot into Download mode at all - just get the LG Bootscreen then straight into TWRP Recovery no matter what i do
Did we all except some kind of update from LG........ i wonder if this the link here and is now a common problem?
Mine was this and i thought it was just an app update for the stock apps and now im stuck big time
Any luck guys or solutions then please post here so we can keep it together and help each other!
Yeah I got an OTA update for my D803-Bell model, upon restart entered the secure boot error loop.
Sounds like, via this thread that it's commonly happening to people who had TWRP or CWM (or even aborted / possibly never completed installs like me) got nailed.
As per that thread, and everything else, I've tried every option possible -- no download mode. Recovery mode doesn't restore anything, just resterts to lg logo -> secure boot error -> black screen. Shows as QSHSUSB_BULK in windows/linux, and I can see those 25 partitions in linux (but reflashing openrecoverytwrp__.img over the recovery partition didn't help. I'm waiting to find out how I can make my own copies of those various partitions listed, from another D803-Bell model I have access to. All the D803 .img files on those links in that thread, appear to not contain D803 Bell stuff, just Telus, Rogers, etc... so I'll likely have to source my own.
I just took a shot in the dark recommended by a friend -- and fixed my phone.
I zeroed out the 'fota' partition on the phone. As seen in this thread ; http://forum.xda-developers.com/showthread.php?t=2451696
Just did a dd if=/dev/zero overtop of the fota partition, which was 25 for me from my linux box. One quick power cycle later, and I'm fully functional again, and the OTA update that killed me is still showing as available again.
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.
Ok- I need some help. If anyone cares to comment or point me in any direction it would be greatly appreciated.
TL;DR - tried to flash stock image and it still doesn't work.
My phone basically committed suicide last week for no apparent reason. No physical damage with the device that I am aware of so I presume it is just soft bricked. I attempted the usual clear/wipe cache and the stock recovery factory reset to no avail.
After turning it on it will just be stuck at the red Motorola "M" logo. Right before it got put in this boot loop a few system apps crashed so I rebooted (Google Play, Google Chrome), and the phone never came back up.
I do not have root, nor an unlocked boot loader, which seems to be why I can't load any custom recovery stuff (tried fastbooting the Clockwork Recovery image).
I've attempted to flash the stock image (VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF.xml.zip) from sd_shadow's stickied post[1]. According to RSD lite the flash is successful, but its still stuck in the boot loop
One thing I noticed is that the AP Fastboot screen doesn't actually print out anything other than "usb connected" during/after flashing. I would think it should print some diagnostics, or at least a success message. I'm suspicious because the AP Fastboot screen will print security or sizing error messages when it fails.
flashboot screen reads:
PHP:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 06:20:44)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
1 - http://forum.xda-developers.com/droid-razr-m/general/how-to-flash-firmware-rsd-lite-to-t3184005
pclose said:
Ok- I need some help. If anyone cares to comment or point me in any direction it would be greatly appreciated.
TL;DR - tried to flash stock image and it still doesn't work.
My phone basically committed suicide last week for no apparent reason. No physical damage with the device that I am aware of so I presume it is just soft bricked. I attempted the usual clear/wipe cache and the stock recovery factory reset to no avail.
After turning it on it will just be stuck at the red Motorola "M" logo. Right before it got put in this boot loop a few system apps crashed so I rebooted (Google Play, Google Chrome), and the phone never came back up.
I do not have root, nor an unlocked boot loader, which seems to be why I can't load any custom recovery stuff (tried fastbooting the Clockwork Recovery image).
I've attempted to flash the stock image (VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF.xml.zip) from sd_shadow's stickied post[1]. According to RSD lite the flash is successful, but its still stuck in the boot loop
One thing I noticed is that the AP Fastboot screen doesn't actually print out anything other than "usb connected" during/after flashing. I would think it should print some diagnostics, or at least a success message. I'm suspicious because the AP Fastboot screen will print security or sizing error messages when it fails.
flashboot screen reads:
PHP:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 06:20:44)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
1 - http://forum.xda-developers.com/droid-razr-m/general/how-to-flash-firmware-rsd-lite-to-t3184005
Click to expand...
Click to collapse
Same issue. Did you find any way to fix it ?
Hnk1 said:
Same issue. Did you find any way to fix it ?
Click to expand...
Click to collapse
Nope, and my guess is I would need the bootloader unlocked to get any further. The Razr M doesn't show up on this list so I'm not even going to bother
pclose said:
Nope, and my guess is I would need the bootloader unlocked to get any further. The Razr M doesn't show up on this list so I'm not even going to bother
Click to expand...
Click to collapse
any Motorola with Droid in the name, and Verizon on it, will not have an official unlock option
Sent from my XT1080 using XDA Labs