Unfortunately, I have a problem. My phone was on the power cord overnight and pulled the latest update (EEA 12.5.5.0 Enhanced). It was then booted into OrangeFox (OrangeFox recovery with OTA support) and waited for my OK. I didn't think anything of it and didn't make a backup either, as I assumed that everything would go smoothly like the last update.
The update then went on, but there was probably an error, because now I have a bootloop (yellow Poco lettering for about 2 seconds). I can't use an old backup because I'm abroad right now and I don't want to lose the apps I've already set up (pandemic, tracking apps, certificates, ...).
Does anyone have a quick trick or the latest full ROM that I can just iron over or any other good quick idea? Change bootloader slot or other options? OrangeRecovery and Fastboot are still accessible. Now I only have ADB/Fastboot on my work laptop, but I still can't list the device with adb devices. I guess I still need to install the Xiaomi driver for it, but that should be the minor issue.
Update: I am currently downloading the different ROM versions (fastboot, recovery and incremental update), just in case they are needed.
OTA for the rom and using ofox? hmm it's not supported unless you will flash stock rom maybe. I don't know much more. Correct me if im wrong.
OTA works very well with orangefox and AICP 16.1...
Related
Does anyone know what changed regarding wifi in Android 8 or MIUI 10?
I was happily using LOS 14 for a while (after having officially unlocked my bootloader at some point in the past, but became curios and wanted to try out the new MIUI 10. While I could not find anything official, I did find this chinese dev ROM (I DO NOT RECOMMEND YOU FLASH THIS). I flashed it, wasn't that impressed and then decided to try LOS 15 based on Android 8.
That was a bit too unstable for me, so I tried reverting back to LOS 14.
I did so using a backup I made to my pc (I did `adb backup` while in TWRP and selected every partition I think). After booting into LOS14, things seemed to crash an awful lot.
At this point I realized wifi wasn't working. It showed a MAC Address of 02:00:00 I think, but no networks were found. I tried restoring my phone using MiFlash normally. I then tried restoring it using Qualcomm's download mode. Older MIUI versions would not boot anymore (although I did manage to boot an old version of TWRP made for the pre-Nougat bootloader). I tried LOS14 again, and attempted using fastboot to erase various partitions (such as the bluetooth and modem partition, and then manually flashed the image again. Still no wifi.
Does anyone know what could have happened? My bootloader is still unlocked, and even downgrading the device to an old version of MIUI using Qualcomm mode did not make it work again? How come LOS15 and MIUI 10 are able to use wifi without problems?
tl;dr WiFi stopped working on any rom other then Lineage OS 15 or MIUI 10.
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
MI MIX 3 8/256
Stable 10.3 Chinese ROM with twrp (10.2 before update, with root and twrp)
Had no root but unlocked bootloader
z1ldj1an said:
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
Click to expand...
Click to collapse
Back up, wipe, flash, restore
Ok. That was the one thing I tried to avoid, since my backup is 27G (nandroid) and internal storage is 133G..
Will try and feedback.
Hi all,
Got it back again, of course with all data and apps gone. I have done nandroid backups (since there is no other way of backing things up from TWRP, except copying everything) from recovery before starting the upper described process. I figure they are of no use to me now or are they?
Please advise
P.S. restoring from nandroids brought me back to square 1..
z1ldj1an said:
P.S. restoring from nandroids brought me back to square 1..
Click to expand...
Click to collapse
Something not right with your data so start over
Restarted, redone. Recovered only Data. Looks ok but works a little laggy..
Upd.: needed to set up the screen lock after had done that and a restart, all works like it was, except with a new OS version
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Isopropil said:
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Click to expand...
Click to collapse
I took it from twrp themselves, not bothering to search any forums. It's not like digging for gold or the like
Upd.:
I read that the official TWRP doesn't support some mounts migrating from EU to global or CN-->EU V Global. It was discovered that it has some bugs with mounting paths. People recommend the LR Team TWRP over the official because of that, besides it has more options under Advanced tab e.g.
Personally I prefer the one that does the job for the moment and is the latest, so it was an easy choice for me ? especially installing a fresh OS update.
Latest release
Built from whoshotjr2006/touchpro's sources with minimal changes. All credit to original devs.
I'm not going to commit to regular updates but I'll try to do occasional ones.
Recommend using this TWRP (also stolen from touchpro).
Installation:
Enable developer options in stock ROM (tap build number a bunch of times)
Enable 'Advanced Restart' in developer options
Hold power button, select restart, restart to bootloader
Use fastboot to unlock bootloader
Use fastboot to flash TWRP recovery
Reboot to recovery using fastboot command
Wipe everything in TWRP, format data, and factory reset
Push ROM to /sdcard/ and install
Optionally push Gapps and/or LineageSU and install
Boot and enjoy (first start might take a while)
Tested on a T-Mobile LG G Stylo, all seems well.
As far as I can tell, everything is working fine. You should be able to dirty flash if you are using another Lineage 14.1 build but I haven't tested it.
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
ItzBluestone said:
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
Click to expand...
Click to collapse
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
jsheradin said:
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
Click to expand...
Click to collapse
oh, well that's unfortunate...
So what is different? Just security updates?
This ROM breathed new life into my old MetroPC version of this phone (2GB/16GB)!
I bought this phone two years ago refurbished and carrier-unlocked (other than banned on MPC) off Amazon. Looked brand new. I just installed a new battery last month. Original battery wore out.
ROM works beautifully. Nice to be free of the factory cruft. Also, the TWRP from your OP works much better than the one I had been running. (Neither TWRP reads the current time/date through.)
I had been rooted with SuperSU, now I'm rooted with Magisk. I flashed mini Gapps 7.1.
I have not tested NFC yet.
Thank you for this ROM and your post!
My TMo h631 will not take the image. During the install it will kernel panic and throw an error.
I do factory reset, wipes, formats but still no go.
Anyone knows how I can fix it?
Will this work fine on the LGM631?
Hello! I have had my One plus 7 pro international running for months now, rooted, following this guide https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368. I had the OTA update notification for quite some time now, but I ignored it because I was lazy. A few weeks ago my phone must have auto updated however, as I started noticing banner ads again that adaway usually blocked, and I have had a few other minor issues like GPS taking longer to connect or find where I am, wifi disconnects, and google not understanding what it usually does. Phone still works just fine, just minor issues I didn't really experience before.
I would like to completely reset the phone to clean it up, and re root and setup TWRP again, but im not sure how to safely do that since my phone was updated improperly (automatically). I have magisk still installed, but the modules dont seem to be working properly. Rebooting to recovery will reboot me to one plus recovery instead of twrp. When I restart is still says my boot loader is unlocked, and some apps (like chase mobile app) still say my phone is rooted. Oxygen updater says im up to date on OxygenOS 10.0.3.gm21aa.
What would be the best option for me to clean everything up, get my root modules working again, and have the phone fully up to date and stable? Any information would be greatly appreciated.
follow the same steps you followed first time. Boot to TWRP flash magisk, No need to factory reset. Flash twrp again if you want and reboot to system
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?