Related
Blur_Version.1.11.0.ME525.ChinaRetail.en.CN
ME525-JDGC_U6_1.11.0_SIGNED_USAJRDNPRCB1B50AA02F.0R_JORDANGCCORE_P011_A030_HWp3_Service1FF
http://u.115.com/file/f24b620be5
password "bbs.dkdiy.net" without quotes.
original source bbs.dkdiy.net
and http://bbs.goapk.com/thread-952839-1-1.html
lower bl version than UK, OR 2.2 sbf.....
not confirmed, but it may damage mb525's flash light... proceed with care.
for mb525, you might wanna use the nandroid backup with boot_only sbf to try it... both can be found in this thread
update with sources in this thread...
nandroid: http://u.115.com/file/t1fd48f976
thanks to SteveChou "here it's my system backup base on 1.11.0（new CN 2.2）, if anyone need it
Last edited by SteveChou; 25th February 2011 at 03:38 AM."
boot_only+devtree: http://forum.xda-developers.com/attachment.php?attachmentid=528823&d=1298827699
thanks to ollienightly
let's wait for someone whose camera flash is already dead to experiment with this one.
Sent from my MB525 using Tapatalk
ME525? Will this rom kill the flashlight?
the reason why the flashlight didn't work is mostly because the dev tree was not flashed properly. it's not the rom that kills the flashlight...
i didn't flash, so i couldn't be sure though
shady_lanem said:
ME525? Will this rom kill the flashlight?
Click to expand...
Click to collapse
does it include full screen recorder and 720p playback?
I am up for it, where should I download it?
don't tell me I have to install bunch of trogen before I can download.
i think that's an encrypted link and password is required.
to provide more information about this one:
i created a system.img out of cg39.smg, flashed it and that's it. you dont need a devtree or boot if you are already on 3.4.x
everything works properly, including flash which did not work with 0.26.0
racca said:
i think that's an encrypted link and password is required.
to provide more information about this one:
i created a system.img out of cg39.smg, flashed it and that's it. you dont need a devtree or boot if you are already on 3.4.x
everything works properly, including flash which did not work with 0.26.0
Click to expand...
Click to collapse
can you tell me how to flash it, or give me the img file.
http://u.115.com/file/t355594b48
here is the link without extract code
hello738 said:
can you tell me how to flash it, or give me the img file.
Click to expand...
Click to collapse
removed since there's a proper nandroid a few lines down
and also, i think a zip version should work on all 3.4.x
Mybe this is the original link?
http://bbs.gfan.com/android-736967-1-1.html
The guy says:
Still VGA, no 720p recording.
Photo qaulity improved a lot.
Compass still difficult to calibrate.
............
http://bbs.gfan.com/android-739900-1-1.html
The last two lines:
Based on testers' feedback, do NOT flash this sbf if you have flashed UK2.2, T2.2, or Orange2.2 sbf before or your defy will get bricked!
However, you can unbrick it by flashing your original system back.
Jasper.tw said:
http://bbs.gfan.com/android-739900-1-1.html
The last two lines:
Based on testers' feedback, do NOT flash this sbf if you have flashed UK2.2, T2.2, or Orange2.2 sbf before or your defy will get bricked!
However, you can unbrick it by flashing your original system back.
Click to expand...
Click to collapse
So most people here will be unable to use it unless a nandroid backup and a boot only is made.
http://u.115.com/file/t1fd48f976
here it's my system backup base on 1.11.0（new CN 2.2）, if anyone need it
Updated to new CN 2.21- 1.11.
( from official T-mobile 2.1 to official CN 2.21-0.26 )
This is what I did...
1. wipe
2. reboot to bootloader
3. flash new sbf via 4.9 (OMAP 3630)
4. wipe again
5. install google-market package (tks to sorensiim : http://www.mediafire.com/?4tgq4cmmzm4dc5v )
6. wipe again
7. root
8. install recovery
9. install t-mobile radio via recovery ( tks to adlx.xda: http://www.mediafire.com/?a0aaezdhazl3557 )
10. wipe again.
11. skip Blur setting.
Went straight to camera, greenish flash still exist. ( but it is working, nevertheless ) Video recording still on VGA only.
Other than that, I havn't play with it long enough.....
( since it is official 2.21, I will stay with it )
***** If you guys want me to check on something, let me know. ( will run quadrant later )
no clue said:
Updated to new CN 2.21- 1.11.
( from official T-mobile 2.1 to official CN 2.21-0.26 )
This is what I did...
1. wipe
2. reboot to bootloader
3. flash new sbf via 4.9 (OMAP 3630)
4. wipe again
5. install google-market package (tks to sorensiim : http://www.mediafire.com/?4tgq4cmmzm4dc5v )
6. wipe again
7. root
8. install recovery
9. install t-mobile radio via recovery ( tks to adlx.xda: http://www.mediafire.com/?a0aaezdhazl3557 )
10. wipe again.
11. skip Blur setting.
Went straight to camera, greenish flash still exist. ( but it is working, nevertheless ) Video recording still on VGA only.
Other than that, I havn't play with it long enough.....
( since it is official 2.21, I will stay with it )
***** If you guys want me to check on something, let me know. ( will run quadrant later )
Click to expand...
Click to collapse
Your Defy is MB525 or ME525?
I have the problem of Flash does not work (or burnt) and I have some hope that the resurrected ROM
I can flash the ROM if I have Froyo Orange (PL)?
Sorry for my English.
THX.
Can anyone tell me the difference between MB525 and ME525?
AgentSmith said:
Can anyone tell me the difference between MB525 and ME525?
Click to expand...
Click to collapse
ME525 is the Chinese version. IIRC, come with 850/1900 3G radio.
Darkcaptain said:
Your Defy is MB525 or ME525?
I have the problem of Flash does not work (or burnt) and I have some hope that the resurrected ROM
I can flash the ROM if I have Froyo Orange (PL)?
Sorry for my English.
THX.
Click to expand...
Click to collapse
I am Originally from the U.S. T-mobile MB525.
There is a warning, you can't flash this from higher 2.3+, such as UK/Tmobile Froyo.
any changelog?
I tried to flash non-ruu roms, but it bricked my one x, saying "this build is for development purposes only" on both system boot screen and recovery. Then i flashed RUU and fixed this problem. So is there any chance that i can flash unofficial ROMs? My one x is rogers version, thanks!
aspirinmatt said:
I tried to flash non-ruu roms, but it bricked my one x, saying "this build is for development purposes only" on both system boot screen and recovery. Then i flashed RUU and fixed this problem. So is there any chance that i can flash unofficial ROMs? My one x is rogers version, thanks!
Click to expand...
Click to collapse
That message you are getting on the splash screen is normal (not bricked). There is no avoiding that notice right now. That has nothing to do with being able to flash ROMs. You need to unlock your bootloader and a custom recovery to flash roms
How do you know that your phone is bricked?
mikelebz said:
That message you are getting on the splash screen is normal (not bricked). There is no avoiding that notice right now. That has nothing to do with being able to flash ROMs. You need to unlock your bootloader and a custom recovery to flash roms
How do you know that your phone is bricked?
Click to expand...
Click to collapse
Yeah, I heard that message is "normal", but it's not normal for me XD cuz i can't get in to system and recovery. My phone just freeze there, so i thought that message is the problem, and my one x is bricked. (I already unlocked bootloader following the process provided by HTCdev )
aspirinmatt said:
I tried to flash non-ruu roms, but it bricked my one x, saying "this build is for development purposes only" on both system boot screen and recovery. Then i flashed RUU and fixed this problem. So is there any chance that i can flash unofficial ROMs? My one x is rogers version, thanks!
Click to expand...
Click to collapse
As pointed out that is not a brick notice. That will show up when you unlock your bootloader. Noting you can do about it. Just wait a moment for the ROM to load after you get that screen. If the ROMs aren't loading, make sure you are not flashing international One X ROMs which can actually hard brick your phone.
Edit: Did you just say you can't get into recovery? How about bootloader?
Edit 2: If you can run the RUU then you should be able to get in to bootloader. Are you using TWRP for recovery?
What ROM did you try to flash?
Butters619 said:
As pointed out that is not a brick notice. That will show up when you unlock your bootloader. Noting you can do about it. Just wait a moment for the ROM to load after you get that screen. If the ROMs aren't loading, make sure you are not flashing international One X ROMs which can actually hard brick your phone.
Edit: Did you just say you can't get into recovery? How about bootloader?
Edit 2: If you can run the RUU then you should be able to get in to bootloader. Are you using TWRP for recovery?
Click to expand...
Click to collapse
Yes i can get in to bootloader, as well as fastboot, just not recovery. I tried to flash in ClockworkMod, and recovery(just this name, the official one i guess?). Get confused by how to flash in 4EXT so i didn't try this one and the one you just told me. What do you mean by international One X ROMs? Like the ROMs made based on Taiwan kernel? I'm getting confused that which model my One is now cuz i notice that there is another twin model called "XL" XD, so i think the reason is that i flashed the wrong version of system, as well as recovery? And is there any way to recognize which model my One is? Thanks!
aspirinmatt said:
Yes i can get in to bootloader, as well as fastboot, just not recovery. I tried to flash in ClockworkMod, and recovery(just this name, the official one i guess?). Get confused by how to flash in 4EXT so i didn't try this one and the one you just told me. What do you mean by international One X ROMs? Like the ROMs made based on Taiwan kernel? I'm getting confused that which model my One is now cuz i notice that there is another twin model called "XL" XD, so i think the reason is that i flashed the wrong version of system, as well as recovery? And is there any way to recognize which model my One is? Thanks!
Click to expand...
Click to collapse
You said you had a Rogers One X, so you need to stay in this sub forum. This is for the Snapdragon/LTE version of the One X. The other forum is for the quad core One X. Stay away from that one.
For your phone you need to use TWRP recovery. Do a search in this forum for it and there are tons of threads on how to install it.
aspirinmatt said:
I tried to flash in ClockworkMod, and recovery(just this name, the official one i guess?).
Click to expand...
Click to collapse
You can't flash custom ROMs for recovery. Stock recovery is a picture of the phone with a green circle or red triangle. I think you're confusing ClockworkMod with the stock recovery.
aspirinmatt said:
Get confused by how to flash in 4EXT so i didn't try this one
Click to expand...
Click to collapse
That's good. Because there is no 4EXT recovery for our phone.
aspirinmatt said:
What do you mean by international One X ROMs? Like the ROMs made based on Taiwan kernel?
Click to expand...
Click to collapse
No, what is often called the "international" version of our phone is the Tegra3 quad core version of the One X, which has completely different hardware from our Snapdragon S4 dual core, called the One X in US and Canada, but the One XL elsewhere.
If you flashed a ROM for the "international" One X, you may have really screwed up your phone, as the memory partitions are different, and recovery may have been overwritten by the ROM flash. Although the fact you can get to bootloader and fastboot is a good sign.
Tell us EXACTLY what ROM you tried to flash and where you got it from.
---------- Post added at 03:24 PM ---------- Previous post was at 03:17 PM ----------
Agree that TWRP is the only recovery that should be used with our device. Clockworkmod does not really support our device, its just a port, and it has some known issues due to that.
Try installing TWRP using fastboot: http://www.teamw.in/project/twrp2/99
redpoint73 said:
You can't flash custom ROMs for recovery. Stock recovery is a picture of the phone with a green circle or red triangle. I think you're confusing ClockworkMod with the stock recovery.
That's good. Because there is no 4EXT recovery for our phone.
No, what is often called the "international" version of our phone is the Tegra3 quad core version of the One X, which has completely different hardware from our Snapdragon S4 dual core, called the One X in US and Canada, but the One XL elsewhere.
If you flashed a ROM for the "international" One X, you may have really screwed up your phone, as the memory partitions are different, and recovery may have been overwritten by the ROM flash. Although the fact you can get to bootloader and fastboot is a good sign.
Tell us EXACTLY what ROM you tried to flash and where you got it from.
Click to expand...
Click to collapse
Tnaks, you solved a lot of questions for me I got the roms from a Chinese website, they are all probably for international model! I saw a rom called Revolution HD, is this rom good on my One x? I think i mess up with recovery (i got recovery on that website as well).
Revolution HD is not for our phone. Flashing things for the international One X will not work, and may brick or otherwise damage your phone.
Where did you get Clockworkmod from?
Don't install things from random websites. It makes it really easy to flash the ROM for the "other" One X. Stick to our Development forum, everything here is meant for our phone: http://forum.xda-developers.com/forumdisplay.php?f=1538
If you want to see everything in an organized list, you will enjoy my index: http://forum.xda-developers.com/showthread.php?t=1671237
be nice for him to be able to remove the battery and read his model number =)
aspirinmatt, could you list your bootloader information?
DvineLord said:
be nice for him to be able to remove the battery and read his model number =)
Click to expand...
Click to collapse
He already said its the Rogers version.
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
This rom is compiled from source from cm-13 tree by me. https://github.com/LineageOS/android/tree/cm-13.0
This rom is built for BLU Life One X2 Mini (L0130UU)
This rom allows adb to run as root, but mounting system rw will cause kernel panic and forced shutdown.
I don't use any root other than adb root.
This rom is my daily driver, I have used Lineageos on my phone since my first build, I have no problems with rom, however your mileage may vary.
What works
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
known issue
FM radio doesn't work
ideals are welcome.
below are two roms, main difference is toolchain stock toolchain verses UBERTC toolchain, you decide which you prefer.
download rom
https://www.androidfilehost.com/?fid=889964283620760376
Current Rom
Rom is built using GCC: (UBERTC-4.9.x) toolchain
Kernel is built using (UBERTC-5.4.1) toolchain
Older rom version
this version using google stock toolchain
download rom
https://androidfilehost.com/?fid=889964283620759752
device tree
https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
vendor tree
https://github.com/vampirefo/android_vendor_blu_Life_One_X2_Mini
kernel source
works great so far - what version of gapps do you use?
I installed the arm64 6.0 micro version from http://opengapps.org/ and have been getting crashes now randomly thru-out on menu's in the settings and on the first app I installed "spotify" Have you had any better luck?
cyrusharding said:
works great so far - what version of gapps do you use?
Click to expand...
Click to collapse
open_gapps-arm64-6.0-nano-20171005.zip
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
When I install the ROM with gapps I get errors in the set up process - it says "google services stopped" and then when I try to install software from playstore it gives another error and the apps wont install.
I am using the upside down TWRP 3.1, it seems when I wipe and even format there is still data on the drive - any ideas, do you think its an error because I'm not doing it from adb sideload?
cyrusharding said:
When I install the ROM with gapps I get errors in the set up process - it says "google services stopped" and then when I try to install software from playstore it gives another error and the apps wont install.
I am using the upside down TWRP 3.1, it seems when I wipe and even format there is still data on the drive - any ideas, do you think its an error because I'm not doing it from adb sideload?
Click to expand...
Click to collapse
No ideal, might be wrong TWRP.
Sent from my Life One X2 Mini using Tapatalk
vampirefo said:
No ideal, might be wrong TWRP.
Sent from my Life One X2 Mini using Tapatalk
Click to expand...
Click to collapse
What process do you use for wiping / formatting prior to install?
cyrusharding said:
What process do you use for wiping / formatting prior to install?
Click to expand...
Click to collapse
My device isn't encrypted, I use fastboot to format data, system, cache the first time, then use TWRP from then on.
I use my own version of TWRP, I am not familiar with the version you use, from reading that is an earlier version later version are better.
Sent from my Life One X2 Mini using Tapatalk
vampirefo said:
My device isn't encrypted, I use fastboot to format data, system, cache the first time, then use TWRP from then on.
I use my own version of TWRP, I am not familiar with the version you use, from reading that is an earlier version later version are better.
Sent from my Life One X2 Mini using Tapatalk
Click to expand...
Click to collapse
what adb command do you use for format? thanks for following (updated to the newest recovery that is "right side up"
Edit: I am thinking my root is not working for some reason... Unsure how to fix. I flash magisk from TWRP but it doesnt look like it takes when I run a rootchecker
Looks very promising, I will attempt to flash this tonight. I ran the ported version of lineage OS for a good 6 months before it one day started boot looping (which others have reported as well for that version) . Been running the latest Drax for the mini since then (thank goodness for backups) but am starting to miss a lot of the features from Lineage. Have you had any luck getting the FM radio app to work? If not I would be happy to take a look at it when I flash it later on.
cyrusharding said:
what adb command do you use for format? thanks for following (updated to the newest recovery that is "right side up"
Edit: I am thinking my root is not working for some reason... Unsure how to fix. I flash magisk from TWRP but it doesnt look like it takes when I run a rootchecker
Click to expand...
Click to collapse
I only use SuperSU for root, no ideal about other root method.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
ieatgravity said:
Looks very promising, I will attempt to flash this tonight. I ran the ported version of lineage OS for a good 6 months before it one day started boot looping (which others have reported as well for that version) . Been running the latest Drax for the mini since then (thank goodness for backups) but am starting to miss a lot of the features from Lineage. Have you had any luck getting the FM radio app to work? If not I would be happy to take a look at it when I flash it later on.
Click to expand...
Click to collapse
I haven't looked at FM radio, I would say it doesn't work, On mtk devices source had to be patched for radio to work, I am using unpatched LineageOS source.
The source takes so long to download and sync, I won't patch it just for FM radio.
If you want to work on FM radio, that's up to you, just isn't important to me.
Anyway good luck.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
vampirefo said:
I only use SuperSU for root, no ideal about other root method.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
Click to expand...
Click to collapse
how do you do supersu for root instead of magisk?
cyrusharding said:
how do you do supersu for root instead of magisk?
Click to expand...
Click to collapse
i got it working, but had to install supersu instead of magisk from @ http://www.supersu.com/download
seems like quickcharge isnt working with my 2.0 adapter, otherwise running smoothly.
spotify install crashes and causes a boot loop....
anyway I can help with version testing of updates?
cyrusharding said:
anyway I can help with version testing of updates?
Click to expand...
Click to collapse
I ordered a different phone today, blue tank phone, water is killing my phones, plus the battery life isn't enough to last all day, I have no way to charge phone at work.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
Thanks for building this! Just wondering if builds are actively being maintained for Life One X2 Mini.
Also wondering if there are any plans to maintain this ROM? Thanks!!
Is it possible to post a link to the kernel sources you used?
Thanks
srgrusso said:
Is it possible to post a link to the kernel sources you used?
Thanks
Click to expand...
Click to collapse
The source is from Blu ftp server, I don't currently have the source as I removed it from my computer to make room for kernel source for tank, that's my current phone.
https://forum.xda-developers.com/showthread.php?t=3716454
Sent from my Tank Xtreme Pro using Tapatalk
Beta version is out for umi (and cmi) and appears to be completely stock Android, although very buggy, such as no fingerprint sensor amongst others.
As it's early Chinese beta there's no Google play installed.
fastboot version
http://106.7.64.1/bigota.d.miui.com...ive.user_20200614.0000.00_11.0_6c6b84e950.tgz
Not recommended just yet...
[Edit] removed first link as posted weekly a10 beta by mistake.
We should waiting for Beta 2...
fards said:
Beta version is out for umi (and cmi) and appears to be completely stock Android, although very buggy, such as no fingerprint sensor amongst others.
As it's early Chinese beta there's no Google play installed.
https://bigota.d.miui.com/20.6.15/miui_UMI_20.6.15_826e1ce00a_10.0.zip
And fastboot version
http://106.7.64.1/bigota.d.miui.com...ive.user_20200614.0000.00_11.0_6c6b84e950.tgz
Not recommended just yet...
Click to expand...
Click to collapse
I tried this rom and it turns out to be android 10 with miui 12 beta security update 6/1
tknguyencsu said:
I tried this rom and it turns out to be android 10 with miui 12 beta security update 6/1
Click to expand...
Click to collapse
Ah. Just noticed the first link was for the weekly beta.
The second link is for the Android 11 beta.
I'll remove the first link.
That's what you get for posting links while in the supermarket ?
There is no adaptation in the status bar, expecting the third-party ROM to arrive as
There is no adaptation in the status bar, expecting the third-party ROM to arrive as soon as possible
try to update gsi by DSU
http://bigota.d.miui.com/0.06.14.na....gl.user_20200615.0000.00_11.0_30884eb908.tgz
updated beta build, looks like a daily builds are on.
fards said:
http://bigota.d.miui.com/0.06.14.na....gl.user_20200615.0000.00_11.0_30884eb908.tgz
updated beta build, looks like a daily builds are on.
Click to expand...
Click to collapse
OTA support?
k1n9n0th1n9 said:
OTA support?
Click to expand...
Click to collapse
Unlikely
Version with miui12 is now out.
https://bigota.d.miui.com/20.6.28/miui_UMI_20.6.28_a5e0d69c19_11.0.zip
Lots of bugs though. (Google translate from Chinese)
1. The status bar shows some problems
2. The camera night view function cannot be used
3. Xiaomi classmates do not support voice wake-up
?? Assistant??
4. Temporarily does not support the long screenshot function
5. Temporarily does not support the Xiaomi mutual transmission function
6. Temporarily does not support one-key switch
7. The sun screen of some machines does not take effect ?? Daylight??
8. Probably failed to upgrade the application in the application store ?? some apps wont update??
It also might need stock recovery to flash it
There's another build dated 06.30.20 out as well.
https://hugeota.d.miui.com/20.6.30/miui_UMI_20.6.30_0d99b1b562_11.0.zip
I am in 20.06.17, how to install 20.06.30 via stock recovery?
https://hugeota.d.miui.com/20.7.2/miui_UMI_20.7.2_bb17565fc5_11.0.zip
letfly said:
I am in 20.06.17, how to install 20.06.30 via stock recovery?
Click to expand...
Click to collapse
Have you tried fastboot a normal build?
I've but used stock recovery so I don't know.
What is the error?
fards said:
Have you tried fastboot a normal build?
I've but used stock recovery so I don't know.
What is the error?
Click to expand...
Click to collapse
Fastboot a normal build? I dont understand so much. 2020.06.30 is zip file, so I think must use recovery, but twrp is not compatible. Can you tell me how can we fastboot this build? Just because I dont know that way.
letfly said:
Fastboot a normal build? I dont understand so much. 2020.06.30 is zip file, so I think must use recovery, but twrp is not compatible. Can you tell me how can we fastboot this build? Just because I dont know that way.
Click to expand...
Click to collapse
no.
Fastboot flash a standard non-beta build.. (don't let it relock the bootloader) using miflash with one of the fastboot roms.
https://c.mi.com/oc/miuidownload/detail?guide=2
That way you should hopefully get back to a stock working android 10 rom and stock recovery, from there if you want to flash another beta you can go through the process again.
Android 11 has changed something with the FBE and twrp doesn't decrypt properly.
fards said:
no.
Fastboot flash a standard non-beta build.. (don't let it relock the bootloader) using miflash with one of the fastboot roms.
https://c.mi.com/oc/miuidownload/detail?guide=2
That way you should hopefully get back to a stock working android 10 rom and stock recovery, from there if you want to flash another beta you can go through the process again.
Android 11 has changed something with the FBE and twrp doesn't decrypt properly.
Click to expand...
Click to collapse
No. I already did it. But when in Stock MIUI, stock recovery dont allow to update 20.06.30, it say need fastboot. But 20.06.30 dont have fastboot rom, only zip rom. so I dont know how to flash it.
letfly said:
No. I already did it. But when in Stock MIUI, stock recovery dont allow to update 20.06.30, it say need fastboot. But 20.06.30 dont have fastboot rom, only zip rom. so I dont know how to flash it.
Click to expand...
Click to collapse
Have you tried putting an older update-binary in the zip file?
That it supposed to work for twrp if you're on a normal stock rom.
fards said:
Have you tried putting an older update-binary in the zip file?
That it supposed to work for twrp if you're on a normal stock rom.
Click to expand...
Click to collapse
I will try it. Put older update-binary. Do we need to put older update-scripts?
letfly said:
I will try it. Put older update-binary. Do we need to put older update-scripts?
Click to expand...
Click to collapse
In the android 10 zip file there is a compatibility.zip which does not exist in the android 11 zip file. I think it might cause a problem if you put the older update-binary zip in the android 11 zip file.