This is a new GSI thread i found. It includes MIUI, OOS, HOS, ZenUI, and One UI. Now let us test this gsi and discuss our experience.
Here is the link:
https://forum.xda-developers.com/pr...vice-development/pie-erfan-gsi-ports-t3906486
I had some crazy problems. I flashed OOS. everything seemed fine. Boot took some time but ok. Eventually booted. Everything seemed to be working, even the fingerprint! After some time it just started to reboot again and again. Tried going back to stock rom with twrp: failed. Tried fastboot: failed. Even edl didnt work. Everytime i tried flashing it came up with a different error. I kept trying and after like 10 tries it finally worked. Got real worried there
What i want to say is: Be careful. As always you might run into some trouble.
Yes!! I saw this thread too and it seems to be very interesting
atengo said:
I had some crazy problems. I flashed OOS. everything seemed fine. Boot took some time but ok. Eventually booted. Everything seemed to be working, even the fingerprint! After some time it just started to reboot again and again. Tried going back to stock rom with twrp: failed. Tried fastboot: failed. Even edl didnt work. Everytime i tried flashing it came up with a different error. I kept trying and after like 10 tries it finally worked. Got real worried there
What i want to say is: Be careful. As always you might run into some trouble.
Click to expand...
Click to collapse
I tried OOS with 9.6.4.0 vendor it booted but im bugged in the notch cut out and i think its very unstable. Also the wifi isnt working but i havent tried installing custom kernel. What did vendor did you tried?
Related
Brief back story goes like this. Working TF300T running JB, was running slow and laggy so it seems a good time to flash something new. I'm no android/linux pro but I have a good base knowledge (you may question this statement later) . Successfully unlocked and flashed CM12 and TWRP. Tablet ran ok, sometimes significant lag, updated to a few different nightlies, then eventually decided to go back to stock. This is where it all went wrong. I followed the instructions here on XDA by d_crossfader. The flash seemed to go as expected, wiped cache/dalvik, rebooted. Loaded up to stock JB but no wifi, rebooted, all went bad. Stuck at the silver ASUS with spinning dots screen.
here's what working at this point.
I can load to fastboot, recovery etc, and have re-installed TWRP, the latest 2.8.1 failed install, but 2.6 is working (since I've read that this rev has issues).
I went back to the CM12.1 ROM I had working and it seems to flash fine but GAPPS fails, gives 'E: error updating binary in zip' for /boot and /recovery.
I think I've exhausted my abilities so it's time to call in people with actual skills.
What should my next move be? I'd be happy with stock or custom ROM's just like to get it back to functioning.
Thanks
Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.
I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.
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.
So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Blackest Pain said:
So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Click to expand...
Click to collapse
You can't use TWRP on OOS 12, though you might be able to install the OOS 12 zip using TWRP if you're on OOS 11.
Check your drivers if you can't connect to the phone in bootloader mode. You might need to simply reinstall it (I've had to do this a number of times).
You might be able to switch active partition it might save you I had something similar happen changing partion helped me get back into adroid
I recently installed lineageOS 18.1 on my Oneplus 8 (t-mobile) and everything worked just fine. Only problem I had was a slightly reduced signal strength and noticed I was often roaming with LOS while at work so I ended up using msm-tools to go back to stock and check a few things with the stock firmware near my work and noticed I was just always roaming out there so lineage was working just fine after all (OOS just didn't have the R above my signal like LOS). But when I tried reinstalling any other custom rom it now fails to write the modem or something. I get no errors until it boots up lineage and then suddenly CrashDumps after a minute or so. I have no sim detection or wifi. The msm tool will always bring me back to a fully functional stock image that works just fine but I cant get any custom rom working now. Has anybody else seen this issue before? I get no error reports other than modem failed to load on CrashDump. Followed the same instructions on lineageOS site and ran same exact files as before. I have tried running older versions of msm tools and still the same result. Same with crDroid. I tried installing through both TWRP and LineageRecovery.
Ok I think I figured it out. In case anyone else stumbles on this issue.. using the manual firmware upgrade on lineage site.. https://wiki.lineageos.org/devices/instantnoodle/fw_update fixed the problem. Just need to extract a payload from an official update from T-Mobile and flash every driver again.