Related
Team Win Recovery Project
for Huawei Mediapad s7-301u
What's new in 2.8.4.0:
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
SS:
Download
https://drive.google.com/file/d/0B-JwjbrlsO9CbUpyOHQtSGs4ak0/view?usp=sharing
Installation :
It's automatic
- Be sure that you have checked this points :
- on you computer : install huawei usb driver
- on your phone : enabled USB Debuging in
- Settings-Developer options-USB debugging on your tablet
credit : Dees_Troy, TheMasterMindGT
Hello,
Unfortunatelly the google drive link in the OP does not appear to work for me. It reports 404 error to me.
pvdeejay said:
Hello,
Unfortunatelly the google drive link in the OP does not appear to work for me. It reports 404 error to me.
Click to expand...
Click to collapse
Done, Link Update
ary12282 said:
Done, Link Update
Click to expand...
Click to collapse
Someone has tested the Huawei Mediapad S7-302u
TheMasterMindGT said:
Someone has tested the Huawei Mediapad S7-302u
Click to expand...
Click to collapse
according to this http://forum.xda-developers.com/showthread.php?t=1743025, there is no difference between those two versions, except the radio freq, so i think you can safely flash the recovery
Hello,
I have flashed this hoping I will be finally able to control TWRP using commandline. That's a new feature added in TWRP 2.8. However most likelly because of the core MTP support ADB is not turned on as this version of TWRP boots up.
I am unable to use TWRP GUI because I'm blind, so I had to revert back to TWRP 2.7.1 in order to get ADB functional in the recovery by default.
This is my strange use case only I think you will have no issues with this. You should safelly flash this using fastboot or flashify if you have got rooted your tablet.
install this recovery to Huawei MediaPad 7 S7-302u but shows no navigation buttons, so it does not work for the model Huawei MediaPad 7 S7-302u.
ary12282 said:
Done, Link Update
Click to expand...
Click to collapse
Hi @ary12282,
I this TWRP still available? Seems the link to google drive requires permission?
Thank you!
Edit:
Hi @pvdeejay and @TheMasterMindGT,
any chance one of you still have a copy of the TWRP 2.8.4.0 for the S7-301u on hand, which you can share?
Thank you!
[Guide] How to install TWRP & root Lenovo Vibe B A2016A40 (single & dual SIM version)
Here's how I rooted my phone. This assumes some previous knowledge of using ADB and TWRP. If you need to, I strongly recommend SIM-unlocking your phone BEFORE you do this - I used this ebay service which cost £1.99 and I received the codes 36 hours later.
Please note that although this worked on my phone, I accept no responsibility if you brick your phone doing this
1. Update your ROM to the latest version, open Settings -> About and tap on Build Number seven times to enable Developer options then check USB debugging & OEM unlocking of the bootloader.
2. Connect your phone to your PC, start ADB and type adb devices - this will bring up a prompt on your phone that you need to respond to. Type adb reboot-bootloader
3. Once in bootloader mode, type fastboot oem unlock. Hit the Volume Up key to confirm.
4. Disconnect the phone from the PC and pull the battery for at least 3 seconds.
5. Download the SuperSU flashable zip https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and copy it to a microSD card and insert it in the phone.
6. Download TWRP recovery to your PC http://www.mediafire.com/file/4hb66m26kfkw9qt/twrp.img and copy it to the same folder as your ADB (I use Minimal ADB & Fastboot https://androidmtk.com/download-minimal-adb-and-fastboot-tool ).
7. Start the phone in bootloader mode by holding the Power and Volume Up buttons together until you see white text on the screen. Use the Volume Up button to navigate to Fastboot then select it by pressing Volume Down. Connect the phone to your PC.
8. Type fastboot flash recovery twrp.img
9. Disconnect the phone from the PC and pull the battery for at least 3 seconds.
10. Start the phone in Recovery mode by holding the Power and Volume Up buttons together until you see white text on the screen. Use the Volume Up button to navigate to Recovery then select it by pressing Volume Down.
11. You should then see TWRP starting. Tick the box to agree then swipe the blue button to the right.
12. Tap on Wipe then Format Data. Do not miss out this step or TWRP won't be able to mount the /data partition.
13. Tap the Back button then Factory Reset and swipe the blue button to start.
14. Tap the back button then Install then Select Storage -> microsd card then your SuperSU file then swipe the blue button to the right to flash it.
15. Tap on Reboot System and your phone should boot to your newly rooted OS! Don't panic if the first boot takes 5 or 10 minutes. If it gets stuck, pull the battery & try again.
16. Make sure you disable System Updates as they will no longer work with the non-stock recovery. Hopefully it shouldn't be too long until there's an AOSP or LineageOS ROM for this phone
Thank you
This worked like a charm - although I was hesitant knowing there would be no way back, would it?
It *should* be possible to extract the stock recovery from a recent stock firmware - I just haven't found any (my phone came with S219, and was upgraded to S235 prior to rooting). That in theory would open the path to a stock upgrade, if one would like to have it.
Re LineageOS: There's an unofficial build for a codename 'al732row' but I'm in doubt this would match a dual-sim A2016a40. I'll wait for another update or two (three releases within 72 hours, then 2 weeks silence?).
For now I won't complain: this was a bargain even without LinOS - those dirt cheap devices often get stuck with Lollipop.
Another edit: The Nougat LineageOS ROM by CarlosArriagaCM (http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/) seems to be limited to the LATAM version of the B (aka A2016b30). For A2016a40 (EMEA version) no cigar
steve8x8 said:
This worked like a charm - although I was hesitant knowing there would be no way back, would it?
It *should* be possible to extract the stock recovery from a recent stock firmware - I just haven't found any (my phone came with S219, and was upgraded to S235 prior to rooting). That in theory would open the path to a stock upgrade, if one would like to have it.
Re LineageOS: There's an unofficial build for a codename 'al732row' but I'm in doubt this would match a dual-sim A2016a40. I'll wait for another update or two (three releases within 72 hours, then 2 weeks silence?).
For now I won't complain: this was a bargain even without LinOS - those dirt cheap devices often get stuck with Lollipop.
Another edit: The Nougat LineageOS ROM by CarlosArriagaCM (http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/) seems to be limited to the LATAM version of the B (aka A2016b30). For A2016a40 (EMEA version) no cigar
Click to expand...
Click to collapse
You can flash the dual-SIM stock ROM using SP Flash Tools so you're never going to end up with a bricked device
Thank you much. I rooted, installed twrp and i updated TWRP to 3.1.0-0
https://forum.xda-developers.com/android/development/recovery-3-1-0-0-lenovo-vibe-b-t3603304
Any custom rom available for Lenovo Vibe B (A2016A40 version)?
Best Regards,
Vlad
@dwl99 ?
Vlad Paul said:
Thank you much. I rooted, installed twrp and i updated TWRP to 3.1.0-0
https://forum.xda-developers.com/android/development/recovery-3-1-0-0-lenovo-vibe-b-t3603304
Any custom rom available for Lenovo Vibe B (A2016A40 version)?
Best Regards,
Vlad
@dwl99 ?
Click to expand...
Click to collapse
Not that I can find. There is one for the a2016b30 but the camera doesn't work.
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
Hi! Do you have a2016a40 model? Wich TWRP you have installed, 3. 1.0-0 ? Not working latest rom build?
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
@Carlos Arriaga replied me will release a new fixed build soon. I hope will working on our model of phone a2016a40.
Look his reply here:
https://forum.xda-developers.com/showthread.php?p=72692660
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
New build release on 19.06. 2017. Working on model a2016a40?
Short answer: No, no change between 0614 and 0619.
Long answer: You may check this yourself: Open the ZIP file in your favourite archiver tool, and extract the file META-INF/com/google/android/updater-script, then inspect the first line (assert()) for A2016a40.
Disclaimer: Even if the new ROM would be accepted by an A2016a40 I couldn't test it right away (no access to the device anymore / yet again).
steve8x8 said:
Short answer: No, no change between 0614 and 0619.
Long answer: You may check this yourself: Open the ZIP file in your favourite archiver tool, and extract the file META-INF/com/google/android/updater-script, then inspect the first line (assert()) for A2016a40.
Disclaimer: Even if the new ROM would be accepted by an A2016a40 I couldn't test it right away (no access to the device anymore / yet again).
Click to expand...
Click to collapse
Thank you for reply @steve8x8 . No luck for a2016a40 users
assert(getprop("ro.product.device") == "al732row" || getprop("ro.build.product") == "al732row" || getprop("ro.product.device") == "A2016b30" || getprop("ro.build.product") == "A2016b30" || abort("E3004: This package is for device: al732row,A2016b30; this device is " + getprop("ro.product.device")
Click to expand...
Click to collapse
I hope to help us @Carlos Arriaga
I'm somewhat afraid there'll be only one way to get @CarlosArriaga to support the a40 variant: purchase one (70€), send it to him (almost same amount). Any volunteers?
steve8x8 said:
I'm somewhat afraid there'll be only one way to get @CarlosArriaga to support the a40 variant: purchase one (70€), send it to him (almost same amount). Any volunteers?
Click to expand...
Click to collapse
Sorry, im homeless, i don't have 1 dolar to eat something.
I found a comparison of the two sub-models: http://www.phonemore.com/compare/phones/lenovo-vibe-b-a2016b30-vs-lenovo-b-a2016b40/4710928 - most prominent difference is 3G and LTE bands, but I'd presume this would be handled by the modem part of the firmware (which isn't part of LineageOS).
If I could get my hands on FCC documents (although I'm in doubt that a40 and b30 would have separate ones) I'd have a closer look.
Any pointers to stock firmware are welcome (but if that comes in MTK format I'm lost I'm afraid).
If I were @CarlosArriaga I'd check too for the model of phone I know, even with a disclaimer in 96pt.
But: nobody stops you from modifying the updater script to include the other model (and as the OP said, with MTK flash tools recovery from a bad flash would be easy - if you got the stock firmware, that is).
Due to lack of the actual hardware (for yet a few months) I'm limited to speculating and using a magnifying glass on the code itself - if time permits.
Does the ZTE Blade A510 look very similar to the Vibe B? Almost identical characteristics, same CPU type? There are rumours about LineageOS support planned for the Blade.
Answering myself: an A510 scatter file I came across shows more partitions than the Vibe has, so this may be close but not close enough.
ZTE has a device called A2016 though. Coincidence?
steve8x8 said:
Does the ZTE Blade A510 look very similar to the Vibe B? Almost identical characteristics, same CPU type? There are rumours about LineageOS support planned for the Blade.
Answering myself: an A510 scatter file I came across shows more partitions than the Vibe has, so this may be close but not close enough.
ZTE has a device called A2016 though. Coincidence?
Click to expand...
Click to collapse
Nothing new for our model a40? No chance to develop @Carlos Arriaga a LineageOS build for this model? The developer is very quiet.
Hello,
Sorry my english I use a translator.
TWRP & root Lenovo Vibe B A2016A40, instructions very good.
But there is no unofficial Android 7 for Lenovo Vibe B A2016A40?
For Lenovo Vibe B A2016A30 gives Android 7. I know that.
Unfortunately, my smartphone Lenovo Vibe B A2016A40 does not.
Twrp error reports installation. Error 7.
TWRP (3.1.0-0 at least, I didn't upgrade to 3.1.1) installed properly on the A2016a40. The check for the model in the updater script is what gives you an error (is there a translation table to lookup the value of 7 you got?).
As had been said before, it's possible to change the updater script to skip the check and repackage the zip, but nobody knows yet what will happen to your phone, and whether it can be restored using SP Flash Tool. We all are keen to learn about this...
(reply removed)
Hi guys,
Hope it's ok if I start this thread, I just wanted to give new users some feedback before/ after unlocking and flashing an India ROM on my sealed China ROM K20 Pro (8/256). It might be useful to some, or maybe even help others. Thanks a lot to Robbo.5000, Madsponge and Hursty UK (hope I got it right?) among others for their help and advice.
- [BUYING PROCESS] My trip with the K20 Pro started here: https://forum.xda-developers.com/k2...ice-to-buy-t3939616/post79918346#post79918346 (about 18 days to get it from China during high season, not too bad I guess). (FYI, the real Global version will come out in Europe in a few weeks but the 8/256 won't be available here.)
- [UNLOCKING PROCESS] I then started the "infamous" unlocking process which triggered the even more "infamous" unlocking wait time. Why did Xiaomi choose to do that? Pretty strange if you ask me. Why should you wait 5 days or more? Anyways, in my case it was almost 6 days. That part of the process went smoothly (I run a kinda old Windows 7 PC). I rebooted the phone and it was unlocked indeed. Then started the stressful process: flashing a +400 euros phone without knowing if it would actually work. Kinda reminded of the time when we "backuped" PS1 (PSX) games, haha.
- [FLASHING PROCESS] I used the official MiFlash tool, with the official India ROM (fastboot file, .TGZ extension). First problem : MiFlash couldn't install the drivers because a /log/ folder was missing, which I had to create manually (didn't see that mentioned on the forum, but might be my OS? Oh well). The rest was OK until I launched the flashing process and hit the "clean all" button (I carefully didn't choose the clean all and lock which would have bricked the phone).
>> Link to the official India ROM Fastboot .TGZ -> http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
>> Link to the official MiFlash tool I used -> https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
>> Use the official Xiaomi USB-C cable - do not try another USB cable
>> Important reminder: please change the default option in the flashing tool and DO NOT choose "clean all and lock". Change it to "clean all" only (you don't want to lock it as you might brick it - see posts below about this)
- [STRESSFUL REBOOT] The flashing process ran for about 10 minutes, said "error: Not catch checkpoint (\$fastboot -s .*lock)". Needless to say I was very stressed out at that point, especially with the not cool red message "error" on the right of the tool, in the column "result". I thought the phone was bricked...but no, it just rebooted normally with the India ROM on it. Honestly I don't know what happened, if it was normal or something but I didn't see anyone mentioning this.
Some feedback post flash: everything is fine, the phone seems even faster than on China ROM but it might be just an impression. I do not like the POCO launcher at all, when you're used for 4 years with the classic MIUI launcher it's honestly a pain, I like to see all installed apps on the home and next screens. I had an issue with my Mi Cloud backup (home screen): Mi Cloud said there was no backup even though I did one just before flashing. The rest of the sync process (except home screen - maybe because of POCO launcher?) was fine though: pics, notes, calls, messages, etc. Too bad we're missing NFC but it feels good to be back on "Global" (was coming from a Mi 8 Global phone). Oh yeah, missing the multiple shots option from the China ROM (where you can choose the "best" shot), but it will come to Global one day I guess.
- [MI CLOUD BACKUPS] I can confirm the Mi Cloud home screen backup issue described above is indeed because of the POCO launcher: my previous backups didn't have it (Mi 8 Global, K20 Pro China) and so Mi Cloud couldn't restore from those backups. I now have a POCO launcher backup (daily in Mi Cloud) and I can restore from those. So keep that in mind: if you come from non POCO you won't be able to restore home screen, but same thing if you move from POCO to a non POCO launcher. If you're not familiar with those backups, it's very practical (usually...) when you change phone because you just have to restore it and you'll have all your icons, apps and stuff like before.
[UPDATE] As you might know, a European Global version will be released in a few weeks, let's see if it has the POCO launcher or not.
Thanks again all for the help and let me know if you have more feedback.
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
You need to fully unpack the ROM. It requires unzipping twice. You now need to extract everything from the tar file. After extracting the tar file you should have a folder with all the ROM image files and some .bat files. Point the Mi Flash Tool to this folder.
The phone needs to be booted into fastboot mode. The PC should recognise the phone automatically if it has all the correct drivers installed.
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
i failed multiple times to flash the global india rom before(using winzip to extract). and I tried again extract the files using winrar and it succeed. i'ved been using it almost 2 weeks now. the issue that i am facing is i cant use earphone mic on discord and whatsapp call. the rest is fine. for the updates, i get it from system app updater in settings.
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
I forgot to mention it, yes you do have to extract it (using WinRAR or similar) until you get an actual folder like Robbo.5000 said. I then renamed the rom's parent folder as "raphaelin" because another user mentioned we could have issues if the folder's name was too long.
About the USB connection i didnt change anything, i left it by default.
hippo2s said:
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
Click to expand...
Click to collapse
I'm guessing your phone is already in fastboot mode (with the little Mi cartoon guy)?
I installed ADB minimal, the MiFlash drivers but also ADB Lite drivers (mentioned in the big Madsponge thread where you can find the links). That might help.
In MiFlash when i hit Refresh it saw the phone as some ID like 1d23456 or something.
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
piqiee said:
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
Click to expand...
Click to collapse
I dont think there is an update since 10.3.3.0 but i guess we'll find out with the next OTA update. I read somewhere an automatic update might lock the phone back (and brick it) so i disabled them for now, until we know more...
Of course Chinese OTA was fine on the China ROM.
hippo2s said:
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
Click to expand...
Click to collapse
In fastboot mode you cant change it on the phone if i remember, and its set automatically in file transfer mode i think.
Yes I installed those drivers too. I might try a different laptop and usb cable tonight.
Thank you so far for your help.
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
DontDamnMe said:
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
Click to expand...
Click to collapse
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
theincognito said:
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
Click to expand...
Click to collapse
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
DontDamnMe said:
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
Click to expand...
Click to collapse
Thanks mate. Just one more thing. Could you play "Test Patterns" - S1:E1 video, zoomed out for 2 mins, in Netflix app?
It will initially show "960x540" (right top corner of the screen in zoomed out mode), but after 2 mins, does it change to "1280x720" or still stays at "960x540"??
Again, thanks in advance!
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
I think its only "soft bricked". Another user had a similar issue and created a thread below. Experts here will be able to help you for sure. If its locked i believe you have to reinstall the China stock ROM.
About Netflix it stays on 960, so no HD i guess...
hippo2s said:
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
Click to expand...
Click to collapse
Just download the china latest stock rom or china latest dev rom (recovery rom will be enough), no need of mi flash.
Then go to this link and follow the instructions. Since you can access the recovery, you are fine mate.
PS: Use the latest official Mi Assistant app from the MIUI site, not the one given in the link above. But the steps are the same.
Thanks guys I will try. Really worried that phone doesn’t shut down it keeps going into recovery (doesn’t power off) and charging doesn’t seem to work in all these conditions.
Will work quickly
---------- Post added at 12:15 PM ---------- Previous post was at 12:04 PM ----------
err... thats not the Mi PC Suite is it? when i google miphone assistant thats what comes up...
Err...not detecting my phone so the PC Suite can't find the device
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Didn't work for me, I tried with the AOSP_super.tar, which succeeded, but got a boot loop.
I tried with the AP_AOSP_.., but it fails, I got "Only official released binaries are allowed to be flashed (SUPER)". The same occurs with Havoc tar.
When I tried the AOSP_super.tar again, I got the same message, instead of a boot loop.
Steps:
Unlock bootloader (OEM unlock is also permanently triggered in developer settings)
Power off phone
Download mode (volume up + power on) and connect USB
Load tar file in AP slot (other slots are empty)
Factory reset and clear cache
Flashing back the stock rom still works. Stock rom: A217FXXU5BUB4
Any ideas?
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Is there a way to install Havoc OS prerooted?
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Yeah I think I know why, There's a filesystem problem, the UUID and filesystem has to be the same as the system.img of OneUI
The UUID depends in the device binary that you have (in the firmware)
I'd help you but, all my steps just led to a dead end sadly
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Hi i flash havocos but not reboot in rom reboot in download mode help please
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Can you make a unrooted gsi? If you could please use dot os 5.2 it would mean world for me. The community also i think.
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
EatABRick said:
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
Click to expand...
Click to collapse
It worked, but with older version of OneUI installed. I don't have this phone anymore but maybe i can help
So, have anyone tried Android 12 on haydn?
Note : Works with K40 Pro as well thanks to @makiothekid
Refer second post
Here are the bugs from Xiaomi Global Community
Mi 11i/Mi 11X Pro:
1."Earphone" icon doesn't show in status bar when earphone is inserted.
2.Unable to find TV device in Cast.
3.There may be crashes after making an emergency call and checking the call records.
(source)
--------------------------------------------------------------
Wanna try it?
Here's Android 12 (AOSP)
Here's the guide from XDA Developers
UNLOCK YOUR BOOTLOADER
MIGHT BRICK YOUR PHONE SO DO IT AT YOUR OWN RISK
How to flash Android 12 betaThe Android 12 beta ROM comes in the form of a .tgz extension, commonly referred to as a Fastboot ROM. To flash this ROM, you also need to have a Windows PC and phone with an unlocked bootloader. Instructions to unlock the bootloader of your phone can be found on your device’s subforums on XDA.
To flash the downloaded file, follow the instructions below:
Download the MiFlash Tool on your PC that can be found here. After downloading, extract the tool and install it. It is also advised to have ADB and Fastboot installed.
Reboot your phone into Download mode by powering it off and then pressing both the Power and Volume Down buttons together.
Connect your phone to the computer using the USB cable.
Download the Fastboot ROM .tgz file and extract it and make sure you remember the extract location, as you will need to paste the address into MiFlash Tool. Make sure there are no spaces in the extract location path.
Run MiFlash Tool on your PC and in the address bar within the tool, paste the extract location from Step 4.
Click “Refresh” within MiFlash and the app should automatically recognize your device.
Click “Run” within MiFlash to flash the ROM file to the device.
The progress bar within MiFlash will turn green, which indicates that the ROM was successfully installed. Your device should boot automatically to the new version.
------------------------------------------
Can i flash it on my K40 Pro?
Edit1: Just flash it on K40 Pro/Mi 11i. Lack of features compare official Pixel Devices.
No new quick setting menu, can't change accent colors, icon shape and fonts. Change can't screen framerate to 122hz. But it's a clean firmware compare with MIUI.
I can recommend this for people refer stock firmware over MIUI or want to review and send it to google.
I can't not recommend to flash in this stage, if it's your main devices. Nothing happen to my device though, just a precaution
Edit2: Successfully rooted without any problem.
Edit3: Magisk can be install but not work yet. Battery seem to be way better than Stock MIUI
makiothekid said:
Can i flash it on my K40 Pro?
Edit1: Just flash it on K40 Pro/Mi 11i. Lack of features compare official Pixel Devices.
No new quick setting menu, can't change accent colors, icon shape and fonts. Change can't screen framerate to 122hz. But it's a clean firmware compare with MIUI.
I can recommend this for people refer stock firmware over MIUI or want to review and send it to google.
I can't not recommend to flash in this stage, if it's your main devices. Nothing happen to my device though, just a precaution
Edit2: Successfully rooted without any problem.
Edit3: Magisk can be install but not work yet. Battery seem to be way better than Stock MIUI
Click to expand...
Click to collapse
For your 1st point, it's just Android 12 rom for our device in order to test the compatibility, don't expect it will have Pixel's exclusive features. #3 surprise me, and Xiaomi should feel embarrassing about that.
khanhdx said:
For your 1st point, it's just Android 12 rom for our device in order to test the compatibility, don't expect it will have Pixel's exclusive features. #3 surprise me, and Xiaomi should feel embarrassing about that.
Click to expand...
Click to collapse
About #3 12 hours at work and i still have 68% of juice left.
note about battery life.. I'm seeing about the same longevity compared to MIUI with MIUI optimisations turned off. couldn't quite understand why it drained so quickly with optimisations on
bit disappointed we're not seeing the fancy new ui in this version of the beta for the 11i