Related
I updated to beta Nougat using a non-official-beta method and am somehow stuck with NRD90M test keys as my build number. The rom works ok for the most part, the only thing which doesn't seem to work properly is Themes.
Would now like to know what the appropriate process is to go to the new and official stock Nougat for EVA-L19. Thanks community!
So was I and I posted about it here and got the right advice to roll back:
forum.xda-developers.com/p9/help/nougat-update-borked-p9-2-imeis-t3534530#post70475746
thank you zemblance! so it would appear that i would have to rollback to stock then only update to official nougat using the built-in updater huh?
Which recovery did u use ? I got that same problem when I flashed with 3.0.0.0 instead of 3.0.2.0
Edit: here's the one http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331/page13
z4d02 said:
Which recovery did u use ? I got that same problem when I flashed with 3.0.0.0 instead of 3.0.2.0
Edit: here's the one http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331/page13
Click to expand...
Click to collapse
not sure which TWRP i used but its fixed now. i did the rollback to lollipop. now on B190 but now Themes is being wonky and I have no magazine unlock. :/
Flash 136 again, there should be two folders hw and dt that need to be in the dload folder too.
If they aren't there you could try flashing the l09 136 first then the l19 one straight after.
Sent from my EVA-L09 using Tapatalk
Ya tone obnaveli eto rom no skajite pojalusta kak vernutsya moy zovoskoy emui 4.1 honor 6x
So I managed to get myself into this bind as well back in January, but I just didn't have the stamina to fight it and I've been running that crap ever since. Now I thought it time to take care of it.
This is the scenario. I got an unlocked EVA-L09 with TWRP 3.0.2.0 running build NRD90M test-keys and I want to "fix it" and update it to the latest version.
What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
And I can as well ask if the Huawei builds are preferable or perhaps there's some other ROM/mod out there worth using instead? I was on CM for years before I got the P9, though such a ROM is of course unlikely to ever be made for the P9, maybe there's a good mod..?
Farmfield said:
What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
And I can as well ask if the Huawei builds are preferable or perhaps there's some other ROM/mod out there worth using instead? I was on CM for years before I got the P9, though such a ROM is of course unlikely to ever be made for the P9, maybe there's a good mod..?
Click to expand...
Click to collapse
You need to download and flash the appropriate hw data update zip for the ROM that you installed.
And if you check out this forum you will see there is both Lineage OS (aka CM) and CM13 ROMs for the P9 :good:
Peace.
chris5s said:
You need to download and flash the appropriate hw data update zip for the ROM that you installed.
And if you check out this forum you will see there is both Lineage OS (aka CM) and CM13 ROMs for the P9 :good:
Peace.
Click to expand...
Click to collapse
Eh, yeah, that I know, but I'm not going to try to figure this out myself again as last time I did, I spent two days trying to get my phone to boot at all - and that's a first since I started messing with ROM's back in the HTC Hero days.
And I thought the undocumented SoC made "real" custom ROM's on P9 impossible - or did Huawei release the doc's?
Farmfield said:
Eh, yeah, that I know, but I'm not going to try to figure this out myself again as last time I did, I spent two days trying to get my phone to boot at all - and that's a first since I started messing with ROM's back in the HTC Hero days.
And I thought the undocumented SoC made "real" custom ROM's on P9 impossible - or did Huawei release the doc's?
Click to expand...
Click to collapse
Ok, so get the 2 files for the ROM you want, and flash update zip then hw data update zip next.
It worked in either TWRP or dload method for me. Of course, for dload method you need to unzip and flash each zip in turn, or TWRP can flash one after the other. Flashing will relock your bootloader...
Well, if you note my post count and alike, I'm not really a newbie here, I got 10 years experience messing about with custom Android ROM's and about the same experience of general Linux experience on top of that, so when I don't wanna do this without some trustworthy information on the workflow, etc, you should get there's good reason. So posting replies like -Oh, just flash something, it'll work out!, that looks a lot to me you just having been really lucky not getting into the situation I did.
So I will repost the question I posed and hopefully someone with that know how will reply.
I got an unlocked EVA-L09 with TWRP 3.0.2.0 running build NRD90M test-keys and I want to "fix it" and update it to the latest version. What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
Just to clarify....
I had an unlocked EVA-L09 with TWRP, running build NRD90M test-keys, and I wanted to fix it....
So, I downloaded update.zip and update_data_full_hw_eu.zip and flashed them one after the other using dload method. It worked. That was my workflow.
Just trying to help out, don't get shirty about it....or you can wait for someone who's been on the forum longer than me, or who has a higher post count than me. Btw, I've received help before from folks with very low post count and I know it's no indication or predictor of noob-ness.
Peace out...
*I* did the exact same thing and then spent the following 30 hours trying to get it to even boot.
And I really didn't want to be rude, but if I got that kinda post number, I'm not likely to ask for help with something like this unless I really needed it. As I said, I have a lot of experience of this stuff and I still messed up immensely trying this the first time, so I'm not even going to try before I have someone who really knows what *NOT* to do give me some hints on how to avoid getting into the same spot - because I'm not doing another 30h trying to save this phone if I mess up again, I'll just smash it and buy something else, like a used Nokia 3310, because it's just not worth the stress.
Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?
Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.
aurismat, and what version of twrp do you use ?
I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.
Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.
Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.
@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)
@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.
well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"
Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!
That would be great man, thanks !!
Hello,
As a preface I have to say I'm less than a newbie in this matter.
My Huawei P8 Lite 2017 (PRA-LX1) had problems with lack of internal memory, so I decided to find a solution.
Following suggestions coming from some forums, I decided to root the phone to move the apps to an external microSD card and free the internal memory.
I got the unlock code and I used Multi-Tool for Huawei v.8.0.7.1 to root the phone.
After rooting I found in my phone only few apps and even Google App Store and keyboard were missing. To fix this last problem I downloaded and installed Gboard apk and then Firefox (no browser ar all in the phone).
Nevertheless, I can't even setup the Google account in the phone because in account settings is not available any Google option.
I'd like to setup the phone to install the apps and then change partitions and move the apps to the external SD card.
These are the installations I applied via the Multi-Tool:
- TWRP-3.1.1-2_by_greatslon.zip
- SR1-SuperSU-v2.82.zip
Please, could you help me on try to fix this issue?
I'm available even to do everything from the beginning if better, but I need to fix this issue.
Thank you very much in advance for any help.
Bets regards,
GP
Hi,
You need to format data using eRecovery. Flash it back if you have twrp, format user data then flash twrp and root etc..
Cosmox_ said:
Hi,
You need to format data using eRecovery. Flash it back if you have twrp, format user data then flash twrp and root etc..
Click to expand...
Click to collapse
Could you write me the link to the original firmware ROM? If needed, how can I get the IMEI number for my phone from the TWRP? Is it possible? I think is needed to identify the single/dual sim model, is it right?
At the moment, after trying to restore the phone, I can only get access to the TWRP. The phone is bricked :'-(
Thanks,
GP
granpinguino said:
Could you write me the link to the original firmware ROM? If needed, how can I get the IMEI number for my phone from the TWRP? Is it possible? I think is needed to identify the single/dual sim model, is it right?
At the moment, after trying to restore the phone, I can only get access to the TWRP. The phone is bricked :'-(
Thanks,
GP
Click to expand...
Click to collapse
Hello,
is there anyone who can help me on restoring my phone?
At the moment I can only use the TWRP to try to fix it.
Might you write me the link to the stock firmware ROM and a step by step procedure to restore it?
I thank you in advance for any help you would give me.
GP
I recommend you to look at htc mania for a ROM (you can find the phone there as Huawei P9Lite 2017, altough I can't say for sure that the phones are exactly identical so I don't know if it will work for you but gsm arena says that they are the same phones with different names). I'm on mobile right now, sorry can't give you the link.
I need to ask you (unrelated to your problem), what command did you use when installing TWRP?
Jhon_Locke said:
I recommend you to look at htc mania for a ROM (you can find the phone there as Huawei P9Lite 2017, altough I can't say for sure that the phones are exactly identical so I don't know if it will work for you but gsm arena says that they are the same phones with different names). I'm on mobile right now, sorry can't give you the link.
I need to ask you (unrelated to your problem), what command did you use when installing TWRP?
Click to expand...
Click to collapse
Hello Jhon_Locke,
first of all, thank you very much for your answer to my message. I'm going to check htc mania to try to fix my issue.
About TWRP installation, I used Multi-Tool for Huawei and Honor v. 8 to install TWRP in my phone, so I didn't use a direct command.
Thank you very much again!
GP
So I have a Moto E5 Plus (hannah) XT1924-8
and I'm in a jam.
I'm new to moto phones I just moved over to this phone 4 days ago from my HTC M9 yeah I have been a HTC guy for a long time.
My stock rom is fubar, when it boots up I get that encrypt storage thing & reset phone etc.... (no password box) but reset phone is not fixing it.
The boot loader is unlocked
& my twrp is on twrp-3.2.3-0-hannah.img got it from twrp.me
So my problem is that I want to re-flash my stock rom but "Lenovo Moto Smart Assistant" witch did worked 4 times this week but now does not want to work anymore.
It comes back at me with "this device is not supported" & that is not true.
So Now I can't get back to stock & I have not been able to get any custom rom to work me as well.
So my ?s to all of you:
Is there some kind of fix for the "Lenovo Moto Smart Assistant"?
and if not then where do I get a copy of the stock rom & some info on how I should go about installing it
and yes I have the newest adb all installed & I think I have the right driver installed "Motorola_Mobile_Drivers_64bit_v6.4.0.msi" Motorola ADB Interface 7/7/2013 v2.0.2.0
Any help will be much appreciated
Also is the phone default encryption getting in the way of me installing Lineage 15.1 or Bootleggers ??
When ever I try to installing a custom rom I get the dreaded 'To Start Android, Enter Password'
also in twrp /data does not mount when ever I booted into twrp, I had to change the format from ext4 to exfat & then change it back to ext4, from that point on it mounts no problem.
My HTC m9 phone did not have encryption on so I'm not use to working around it.
Well I'm going to return this thing & stay with my HTC m9 with only a 10% working battery.
It seems that no one is going to help me.??
there might be reasons why people wouldn't respond
1. this board isn't active like you'd expect it to be
2. there's already threads out there to save yourself from this
anyway, on twrp, you'd need to FORMAT data to have it de-encrypted... and you'd need to flash a certain boot image that prevents it from auto-encrypting, which is in one of the threads. you'd also never would want to use the smart assistant, because as you can see, it won't work. i don't know if there's a stock rom for your variant, so i can't really link you to yours, but getting it from the moto assistant isn't ideal, it's better to get it from here on the forums or something.
so, in order to install a custom rom, flash the boot.img that doesn't have encrypt, and then flash the gsi system image, and then flash magisk in twrp.
There should already be a thread with the xt1924-8 stock firmware in here somewhere just gotta search. If not I'd suggest trying to re-flash the stock recovery and boot images if you have those and then just try to do a recovery from within.
well I already returned it.
I did read many many many guides on here & on other websites before asking for help.
most of them did not say anything about the book.img to turn off the auto-encrypting.
again I never had to work around auto-encrypt before.
Also @wihzard
I did look for a stock rom for (hannah) XT1924-8 but did not find it.
anyways I returned it & now I'm looking for a unused M9 to replace my old one,
I will end up putting LineageOS 16.0 on it.
Thanks for replying
my moto e5 plus is bricked im pretty sure ...any help anyone?
E-TARD_The_LifeCaster said:
well I already returned it.
I did read many many many guides on here & on other websites before asking for help.
most of them did not say anything about the book.img to turn off the auto-encrypting.
again I never had to work around auto-encrypt before.
Also @wihzard
I did look for a stock rom for (hannah) XT1924-8 but did not find it.
anyways I returned it & now I'm looking for a unused M9 to replace my old one,
I will end up putting LineageOS 16.0 on it.
Thanks for replying
Click to expand...
Click to collapse
………………………………………….
I need help as well haven't had much time to get on here and try to get help. I have the XT1924-7 varriant. I had discovered a hidden network that was placed on there by an ex to track me. So I factory reset I had AEX pie installed on it. Come to find out factory reset didn't even get ride of had to follow some extra steps to erase partitions that weren't wiped during the reset with TWRP. So my problem is once booted and going through setup process these pop up start popping up(screen shots below)the first is the modem keeps stopping. I get that about 25 times of hitting ok then I get one last one stating internal error need to factory reset. IVE DONE THAT COMPLETELY DELETED IT ALL RESTORED ALL. I've flashed NON-HLOS alone withe the erase modem 1&2. And still I've done diffent methods of trying to restore and get nowhere. Any help would be appreciated
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Edit 3: Okay so new issue, everything is all good TWRP is installed phone is rooted, but im trying to update to the latest MIUI 10 version (on MIUI 9 atm) and i can't install it? It downloads fine but it wont install? Do i have to flash the update file since it wont update through the updater?
JasonBjorn said:
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Click to expand...
Click to collapse
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Robbo.5000 said:
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Click to expand...
Click to collapse
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
JasonBjorn said:
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
Click to expand...
Click to collapse
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Robbo.5000 said:
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Click to expand...
Click to collapse
well heres the weird thing, i bought the EU version of the phone, which i know is supposed to be the 9t pro, but not only did the site call it the K20 pro, but in the settings its model number is also the K20 pro. I got everything working fine.