Hi everyone,
When trying to update from LOS 18.1 for microG to 19.1 for microG today, something went terribly wrong.
The recovery flashing for LOS 19.1 went ok, but when i tried start the bootloader i got an ugly "Waiting for flashing full ramdump" message. I managed to reboot pressing the three physical buttons, and i even managed to start the 18.1 recovery mode. Assuming the recovery didn't get properly flashed, i flashed it again and the operation seemed successful.
But when i tried to boot the device again, i realised i was stuck in the fastboot mode, whatever key combination i would press. If connected to the computer or the power, the device wouldn't even turn off, it would boot into fastboot again.
Before flashing the device i spent a lot of time trying to properly install the ADB USB drivers, but it would always return me a "Code 10" error message. I tried it on 4 different computers. But when booting in fastboot, the drivers seemed to be properly installed (no "!" in the device manager).
When i first installed LOS, i first installed LOS 18.1 and then decided to switch the LOS 18.1 for microG, but i did not flash the LOS 18.1 for microG recovery. Could it be part of the problem ?
I don't mind formatting everything, as i wanted make a new clean install.
Your help would be really appreciated as i am totally lost as a real noob. I'm afraid that i bricked my phone.
Thanks.
Problem solved.
I used the script mentioned here.
Related
Hello, everyone!
The problem is that when booted, the phone only vibrates and turns off immediately. The screen never enables, LED for charging never enables. When connected to a charger, just vibrates. Tried to follow the steps here : installed the Soc driver, plugged the phone, tried to power it off - device manager recognized the phone for a couple of seconds and then it's gone.
Long story short: I tried to install official firmware upgrade using TWRP > Install > .zip. The installation was going on for a couple of minutes and then the screen blacked out. Since then, the phone does not boot.
So, I got bored of my Android 5 and decided to install a custom ROM, but I had to upgrade official firmware before that.
At first, I dove into how to install custom ROM tutorials, so I did the rooting first:
I downloaded a BootLoaderUnlocker program from the official Asus website and unlocked the BL. Then, I followed a tutorial for one-click-root, and succeded. Then I installed TWRP and flashed the Recovery to the latest available img for my phone and tried to install the Lineage OS 14.1 but got status 7 error, meaning something is incompatible.
This post states, that in order to install Lineage OS 14.1 I have to have a firmware at least MM 4.21.40.xx which is Android 6, so I went to the official Asus website and downloaded the Firmware upgrade. Since, I probably had the wrong BL at that point, I flashed the bootloader with TWRP for Z00A (Lollipop) 2.8.7.3 from here, which is the same website from which the post suggest to download a BL for MM (Android 6). I thought, since I currently have the Lolipop, should install the BL for that, just to be sure. Then I started the firmware upgrade, which rebooted the phone into the BL, I didn't think, and just pressed Normal Boot and the phone booted as usual in the old Android. Then I tried to initiate the instalation again but couldn't (it's supposed to auto-detect the file in the storage root), so I got an idea to just boot the Recovery, maybe it will continue. So, I did that, and the TWRP showed up (I forgot about it already and thought that the instalation would just continue), so I just pressed Install and chose the firmware upgrade zip manualy. The installation was going on for a couple of minutes and then the screen blacked out.
Since then, the phone does not boot. If I try to, it vibrates like it is going to boot, but then nothing happens (not even a logo).
I even tried to disconnect the battery: removed all the screws, removed the back panel and manually disconnected it. When I put it back the phone vibrated like it was going to boot, but nothing happened again.
P.S. I tried to boot into the Recovery, but that just does not work, and even did not work before the firmware upgrade (I googled, that I must press power and volume up and hold until the logo appears, but that doesn't happen).
upd: plugged into the charger, periodically shows the battery icon on the screen.
upd: I went to a service and the dude said I might have screwed up the `preLoader`, so some might say it's a disastah
https://forum.xda-developers.com/showthread.php?t=3452785
Sent from my ASUS_Z00AD using Tapatalk
Resolved
So, I went to a service and turns out I messed up the PreLoader, that boots the BootLoader. Sometimes this cannot be restored and costs a bunch of money to replace the memory block, but I got lucky and got the phone repaired.
P.S. Do not install official firmware with programs like TWRP, use only your manufacturer's SoftWare
So yesterday I decided to install Magisk, I was on 10.0.3.0 Android Pie stock image with TWRP installed. With the fastboot ROM in Xiaomi's web I created my own patched_boot.img for this version and then I rebooted into fastboot and used
Code:
fastboot boot patched_boot.img
after that, the phone stayed for 3-4 minutes in the fastboot screen and then rebooted. The booting process was superslow, it took almost 10 minutes and when it finally showed me the screen to put my pin, i wasn't able to write it at the moment, since the phone started to freeze. After several minutes of waiting I was able to unlock my device but navigating to the Magisk Manager app to install it directly was a pain in the ass, constant freezes, lots of lag... but with patience I was able eventually to install it. Pressed reboot and the same history, booting process i superslow, theres a lot of lag... Basically unusable at this point, so I decided to restore a backup that I did before installing Magisk and after finishing it, the problem was still there. I was only able to get rid of the lag by flashing the stock ROM again with MiFlash without deleting data. I've also tried upgrading to 10.0.4.0 but it happens the same. Why could it be that booting into the patched_boot.img makes my phone unusable until I reflash it? How can I install Magisk and not getting all of this lag?
Not my phone, but a friend that rooted their friend's phone.
Goal: Unlock the bootloader and root the Redmi Note 8 Pro (Global)
Steps:
- Unlocked bootloader.
- Flashed TWRP. (it worked & booted)
- Installed Magisk (worked, phone booted with Magisk)
- Update Magisk through the Magisk Manager
This is where the problem occured:
The moment they clicked on Update in Magisk Manager, before the update process could even begin, before the update file would be downloaded, the phone rebooted (vibrated as if it was force rebooted) and the display never came back on.
This makes me believe it was a coincidence and the phone just rebooted on its own anyway.
The phone seemingly appeared to not work, as the display was off and would not turn on, but the phone does actually boot into MIUI and vibrations can be made using the screen.
The phone is detected in ADB according to my friend.
I am unsure whether fastboot or recovery works, but I would assume that if the system boots, fastboot would also work.
We tried looking this up online and we get all sorts of stuff about bricks and whatnot, but nothing about a display not working but the phone booted.
This isn't a brick, as the phone boots, but there is no visual output, not even the Mi logo on startup.
Anyone have a clue?
The user isn't comfortable with messing more with their phone to fix it, but they would like to charge my friend even if the repair ends up free. This is stupid.
Should try fastboot mode and flash the stock boot of the current rom
I was on AEX and tried a new roms (Pixys, Evolution, Pixel Experience etc) and none of them booted the android.
Tried to restore AEX and even that is not booting. Phone keeps rebooting in loop without booting to any os including the restored backup.
Evolution and pixel after a clean installation says "no os".
Phone stays in start mode and does not move beyond this point.
Phone boots to twrp recovery.
Any idea what is wrong? Have corrupted the phone that it can't be used?
Is there a way out?
Quick solution would be highly appreciated.
Thanks
Anyone has a solution/suggestion for this?Deperate now since there is no alternate phone.
Thanks again
The phone boots recovery and adb commands work whereas fastboot commands don't work. I am able to flash vendor2factory and rom successfully with no error but the phone still not boot android but vibrates and goes back start screen and if i don't press any keys it restarts again after showing the ZUK logo.
I hope i have been able to explain the situation. I am still not able to boot the android despite trying more than one rom.
Anyone has any clues? Thanks
ramadurair said:
I was on AEX and tried a new roms (Pixys, Evolution, Pixel Experience etc) and none of them booted the android.
Tried to restore AEX and even that is not booting. Phone keeps rebooting in loop without booting to any os including the restored backup.
Evolution and pixel after a clean installation says "no os".
Phone stays in start mode and does not move beyond this point.
Phone boots to twrp recovery.
Any idea what is wrong? Have corrupted the phone that it can't be used?
Is there a way out?
Quick solution would be highly appreciated.
Thanks
Click to expand...
Click to collapse
I am having the same problem. I was in pixel experience and i flashed latest pixel experiences august security patch, it showed no os but it booted. But there were several bugs in the rom, i thought it was roms problem and then i tried to flash evolution, it again showed no os after flashing and then i got stuck at evolution x boot logo. So, i tried to qfil zui but to no avail, the flashing process won't even start the qpst tool just freezes after pressing the download button. Then in the twrp i noticed that battery percentage is different at different times sometimes it shows correct value but somes it won't so i thought that the problem might be from twrp and then i flashed new twrp but again same problem. Then i flashed arrow os 10.0 without gapps, it booted successfully then i flashed gapps. After sometime i tried to flash evolution x but got stuck at boot logo again. Finally i flashed arrows os again it booted successfully (i flashed rom and gapps separetly)
So, FINALLY THE TEMPORARY SOLUTION IS TO FLASH ARROW OS IT WILL BOOT SUCCESSFULLY BUT THEN AGAIN OTHER ROMS WON'T BOOT. IF I FIND ANY SOLUTION I WILL POST HERE
muralee krishna said:
I am having the same problem. I was in pixel experience and i flashed latest pixel experiences august security patch, it showed no os but it booted. But there were several bugs in the rom, i thought it was roms problem and then i tried to flash evolution, it again showed no os after flashing and then i got stuck at evolution x boot logo. So, i tried to qfil zui but to no avail, the flashing process won't even start the qpst tool just freezes after pressing the download button. Then in the twrp i noticed that battery percentage is different at different times sometimes it shows correct value but somes it won't so i thought that the problem might be from twrp and then i flashed new twrp but again same problem. Then i flashed arrow os 10.0 without gapps, it booted successfully then i flashed gapps. After sometime i tried to flash evolution x but got stuck at boot logo again. Finally i flashed arrows os again it booted successfully (i flashed rom and gapps separetly)
So, FINALLY THE TEMPORARY SOLUTION IS TO FLASH ARROW OS IT WILL BOOT SUCCESSFULLY BUT THEN AGAIN OTHER ROMS WON'T BOOT. IF I FIND ANY SOLUTION I WILL POST HERE
Click to expand...
Click to collapse
Now the phone is not even booting into recovery after i did a qfil install on zui rom. Looping into start screen only.
ramadurair said:
Now the phone is not even booting into recovery after i did a qfil install on zui rom. Looping into start screen only.
Click to expand...
Click to collapse
When you qfil, the recovery will be lost i think. But since you cannot enable usb debugging i think you wont be able to flash twrp.
---------- Post added at 07:26 AM ---------- Previous post was at 07:19 AM ----------
ramadurair said:
Now the phone is not even booting into recovery after i did a qfil install on zui rom. Looping into start screen only.
Click to expand...
Click to collapse
I think the problem is our phone is not able to boot big rom i.e. roms of size close to 1gb or more than 1gb since arrow os without gapps is only 600mb my phone is able to boot. If you are able to find the solution or get your phone repaired at any cell repair centre please let me know
bro is your phone working now
Hi to all, I just want to ask for some advice or tips. The thing is:
I have one old Redmi 5A Riva. It was lying in the drawer some time, so I decided to try to unlock the bootloader and flash some custom ROM.
So, I unlocked the bootloader - OK
Then I flashed TWRP - OK
Then I decided to make root on stock firmware - OK
Then I tried to flash Lineage OS 17 - after flash it stopped booting.
So I tried to flash Lineage OS 18 - it started booting again but I found out that phone doesn´t detect an USB cable, so I wanted to flash some other ROM instead.
But after few moments TWRP suddenly disappeared (volume up + power on stopped working, only vol. down and power on worked to fastboot) - kinda weird, I said to myself Now I am f**ked up because Lineage 18 was not rooted, I wanted to do it later, so I couldn´t use TWRP app to reflash it.
But after few moments there appeared stock recovery menu, so I thought okay, maybe its not dead, so I try to flash just stock rom. I tried MIUI 10, but again - not booting.
So I did wipe again and tried MIUI 9 - flashing via fastboot and used flash_all.bat attached to rom - it booted up and worked, so I enabled USB debugging again and tried OMNI ROM. I flashed it, after flash it boots up, but after few second screen goes black and nothing else happens.
I am kinda annoyed with this , I flashed many phones, but only Xiaomi makes these weird problems.
Can someone help me to fix this?