Hi all,
I hope someone can guide me through. My MI A1 device has suddenly stopped booting for no reason. To fix up I tried many thing but with no luck.
here is link to one of the thread I have followed
Reddit thread
This guy exactly had the same issue as mine but on different model and I followed all the instruction as in this thread.
Summary of things I tried so far (Including instructions from the thread I mentioned) :
- Try mi flash tool to flash stock rom (Which succeeds and nothing actually works )
- Tried my luck with lineage os 17 and GPAPPS but no luck. (Interestingly, when I Install LOS and I the reboot device, it boots in LOS recovery fine but when I try to boot system it just keep rebooting and then finally stops at charging screen.)
PS. One more observation, when I flash it with MIflash tool with stock rom and it boots up for the first time, an intermediate screen with circle logo and erasing text appears just like when we get update screen not sure why!
Guys, this is my last bet on XDA. I almost wasted my whole day searching for solution on #Youtube and other forums, nearly read a ton of things but still no luck!
Please Help!
UPDATE :
Here is a little more progress,
So, I tried flashing the original stock rom boot image with fastboot
Code:
fastboot flash boot boot.img
and as usual first it just got rebooted with no luck but later somehow booted the device. I tried the same with recursion OS ROM and then again flashed boot image and just like prev attempt it rebooted first & then booted normally.
Also, when device was booted normally, I received a call and when I tried to pick it, It just got rebooted and I am where I started!
I really don't get the point why it boot when I manually boot it with fastboot and its not able to boot itself.
Anyone knows, why this is happening? Is there a way to clean whole and then install? am I doing something wrong here?
Update :
Yes, confirmed when I flash the boot image from fastboot it does boots up. the only problem is after a few seconds/minutes it just reboot and goes back to problematic state.
This thing is really pissing me off! Can someone help?
Update:
After a few more attempts now, it seems like the device is completely broken! It only boots up in fastboot and does not even boot in recovery ( Volume up + Power)
I also tried with pushing twrp recovery image with fastboot but even though the command succeeds the device just reboots with MI logo continuously.
Related
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.
Yesterday I tried to get rid of the ugly green UI on the TicWatch E following https://forum.xda-developers.com/smartwatch/other-smartwatches/ticwatch-e-chinese-version-ticwear-t3781183 . It worked, and my watch looked beautiful. But Bluetooth didn't work correctly. This wasn't a new issue, as the very first day I got the watch, I had the same issue. I tried to reboot, and many other solutions but had to reset like the first time. This time, it booted into TWRP as I had rooted my watch. I proceeded as normal, wiping the user data partition and cache, and rebooting. This time, the watch didn't reboot but went into TWRP instantly. I tried to reboot a couple of times, but ended up in TWRP every time. So I decide to do the most idiotic thing: try to reset again. This time, the watch simply shut off and dint respond to pressing the button. No sound, no vibration, nothing. Thankfully, it showed up in Mediatek flashing tool, so I followed https://forum.xda-developers.com/smartwatch/other-smartwatches/ticwatch-e-chinese-version-ticwear-t3781183 and got it to boot up. I messed up in flashing the userdata.img as well, but I doubt itll have any consequences as I then erased that partition using fast boot. Now, it has been showing the weird circle-throwing-ball animation for the last 4 hours.
For anyone finding this thread, this 7z worked for me
mega.nz/#!tw4hEZyA!xZD7RkSvnuXKcOayeHSvU3DMUat_NGLi0WI3nwIGU1A
Model WF12066
AutismicPootatoe said:
Yesterday I tried to ...
Click to expand...
Click to collapse
drive.google.com/open?id=1cLp_ALZhG-xdqd3fSj5xD7xj5UWfz95p
To explain more, that previous link was for android 5. It got the watch up and booting again. I found an Android 7 ROM on XDA, spliced in the img files and that booted too. Managed to get into TWRP and load my backups. Rerooted and enabled the black menus.
Above is a dump from my ticwatch e after all is said and done (except for userdata, that's still from the same link from above). The recovery is TWRP, system and boot are my restores from TWRP (running oreo), oem is preserved (to keep my oem.prop changes). The rest of the img files are from that mega link above (filename TicwearToAndroidWear.7z). Note: I haven't tested it, but if my SP Flash reading skills need some work, you should be able to replicate my steps ( download TicwearToAndroidWear.7z, replace recovery with TWRP, splice in the boot, system, userdata from forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3786600, then find a TWRP backup to restore from. I can probably provide my boot and system WIN files if my img files don't work.
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
iamleobn said:
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
Click to expand...
Click to collapse
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
EDG_ said:
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
Click to expand...
Click to collapse
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
iamleobn said:
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
Click to expand...
Click to collapse
Update to stock Pie before trying to reinstall LOS again. Hope this time works.
AA
You should install 1.0.8.0firmware first before install 9 ROM!?
Hello,
First to get this out of the way i have searched the topic and there were several "solutions" none worked for me.
How it started, I downloaded the latest LieneageOS update as always, set the phone to do it's thing, came back and the phone was stucked on OP log, tried a little reboot, nothing.
No access to recovery or fastboot.
computer wouldn't recognize device even after installing drivers, this guide helped me a little https://forums.oneplus.com/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
found tools got fastboot back and original recovery.
via fastboot attempted to installed TWRP
fastboot flash recovery twrp****.img
and then tried to boot into recovery
fastboot boot twrp****.img
Not able to boot into twrp
after all that my phone still stucked on the boot OP logo
any help would be greatly appreciated.
Anyone has any idea, sorry I have been scouring and reading everywhere, but I can't find a solution.
Thank you
So i have been trying many things and finally getting somewhere. I apologize for the long post, but i have been trying so many things to get this device back to speed.
So flashing TWRP newer version for some reason is not letting me boot into recovery.
I have flashed twrp-2.8.7.0 and i am able to boot into recovery, however when trying to install the ROM (LineageOS 16) i get error E3004.
Searching the web i find that the correction is to that error is to update TWRP, thus i have tried flashing
twrp-3.2.1-0 and twrp-3.1.1-0 and once installed i am not able to boot into recovery again.
I flashed 2.8.7.0 and i was able to get in, thus from inside TWRP i did an image install of twrp-3.1.1-0 and rebooted, recovery won't load. I proceeded to repeat this until i get a result.
I flashed twrp-3.0.2-0 and be able to boot. However still not able to install LOS.
Once i tried flashing twrp-3.0.2-1, recovery won't load.
For sake of argument i flashed twrp-3.0.2-0 and attempted a image install for twrp-3.0.2-1, but the system still won't boot to recovery.
I have completely formatted the phone.
I hope someone could give me a little advice . Thank you.
Please HELP
I am writing here the whole story.
I unlocked the bootloader of my Asus zenfone max m1 (3/32GB) using the unlock tool which I downloaded from Asus's website.
Then, I went to fastboot mode and flashed TWRP recovery and then tried booting into it through the cmd screen using fastboot boot twrp.img command and it worked.
Then I followed a really good tutorial and flashed the pie firmware, Pixel Experience and magisk and ZIPs in order.
And it showed no error, everything was fine and then I clicked on the reboot system button, it rebooted the system but the phone was stuck at the google logo with a loading bar and didn't go beyond that even when left for 30 mins and I tried rebooting the phone multiple times and that did not help. the phone was stuck at the google logo every time.
Then I turned off the phone and tried going to TWRP to flash the pixel rom again but the phone only went into fastboot mode, it never booted into recovery even though I tried multiple times(I was trying to boot into the recovery through the volume and power buttons, not through fastboot mode).
I flashed the phone's recovery multiple times and also the boot image (I even tried flashing the stock recovery) but the problem is that everything goes fine in the terminal, it shows that it flashed the img file successfully and it is finished but the commands like fastboot reboot recovery don't work at all, they all just reboot the phone normally and the phone just shows the ASUS logo for few secs and then turns off.
Note: I used fastboot erase commands to remove the pixel experience rom and now I'm only left with a phone which boots only into fastboot with no rom and I don't know about the recovery because it shows that it flashed but it never opens.
Hi
I am having a similar problem in that I can oly get into recovery mode with adb reboot recovery. I researched and tried all possibilities with the phone key but I can only go into bootloader mode.
After flashing recovery successfully (?) I can only boot the phone normally and that seems to reinstall the default recovery manager.
While researching I found that there are some discrepancies with the ID out there. While my phone is a Zenfone Max (M1) with the ID X00PD some places (TWRP) confirm that but others refer to Z555KL.
Did you get any further?