Related
Info :
Greetings and Welcome. Here's the latest firmware update for Sony Z2(D6503) Build23.5.A.1.291_R4D with (Recovery + Root)
Enjoy!
How To Flash :
Method 1 Clean Flash :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Do A Full Wipe Except the storage partition where u put Prerooted Rom + Bootloop Fix,
4. Flash Prerooted Rom and then Bootloop Fix
5. Reboot.
Method 2 Dirty Flash Over Previous Build Of Android MM :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Flash Prerooted Rom and then Bootloop Fix,
4. Wipe Cache And Dalvik/Art
5. Reboot.
6. After Finishing booting process wait a few mins,
7. Now go to app drawer and check if supersu is there or not, If not then simply download it from google play store and install it and open it and select SU Binary install normal & Click Reboot,
8. Enjoy!
Stuff Used to Create This Pre-rooted Room :
D6503_Customized AU_1281-9715_23.5.A.1.291_R4D
PRFCreator_v1.3
UPDATE-SuperSU-v2.76-SYSTEMMODE
RecRootV4_combined
My Dell Laptop,
A Keyboard + Mouse,
My Experiences With This Build Of Android MM :
Now We can transfer apps to "EXTSDCARD" using "Transfer data to SD card"
STAMINA mode is back
Multi Tasking Is better than Previous Build Of Course XD
Significantly faster & smoother than previous build (23.5.A.0.575)
Screen Recording Error still exist
Anything Else? :good:
Download Links :
Rom : Click On ME
Bootloop Fix : Click On ME
Screenshots :
http://imgur.com/a/i7icA
Instead of Typing Thanks, You can simply press on it :good:, Try not to spam this thread, If u have any Question regarding my upload Ask here.
First Comment
Keep Up Bro (Y)
Thank you. ?
Thanks!
I'll try to build the same file but for Customized FR (my country) !
Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk
itsnie said:
Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Because that's a life saver for Z2 with Prerooted rom. That's the only bootloop fix exist here on xda for now. Can you try flashing without it at see if it boots? And report back here! Unless u wanna waste some times on re-flashing LP rom and rooting it again to get back on a rooted mm rom
Will previous D6502 patches work?
RICdefeat & byeselinux
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you
supercfc said:
Will previous D6502 patches work?
Click to expand...
Click to collapse
Can't say since I don't have a D6502 Model. Try and let me know if it works
LunaFree said:
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you
Click to expand...
Click to collapse
"RecRootV4_combined" Include all of those stuff as well as recovery
@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post
Thank you so much!!!!
So I finally made the same thing for the french firmware !
https://www.wetransfer.com/downloads/9d69b9f8a30da16970abc3f5655fa01720160804144653/d99f41
Dilesh Perera said:
@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post
Click to expand...
Click to collapse
As I already said "RecRootV4_combined" Includes Root + Recovery. So u don't need anything else. Except Bootloop Fix
rakeshbro said:
"RecRootV4_combined" Include all of those stuff as well as recovery
Click to expand...
Click to collapse
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:
LunaFree said:
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:
Click to expand...
Click to collapse
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!
Yeah you need bootloop fix. The same thing happened to me but I just pressed volume button during the bootloop, I entered TWRP, connected to USB, copied bootloop fix and flashed it without reinstalling everything
rakeshbro said:
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!
Click to expand...
Click to collapse
I think we have do the same, but i dont use the bootloop fix...
I will flash recroot v4 next time without bootloop fix and i tell you. Thank you!!
Thanks for your work
flashing without a probleme
Hi guys,
First, English isn't my first language so, sorry if it hurts your eyes :/
Second, I'm new to TWRP / root etc... (since yesterday) and I don't fully understand the exact meening of all words like flash / rom etc...
So: I'm actually blocked in the "Your device can't be checked for corruption. Please lock the bootloader". Apparently it's a normal screen now, when we boot we always see this. OK ( at least that's what I read)
My volume keys aren't doing anything and I can't access my phone anymore.
I can access TWRP if I want.
Thx for responding :good:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
coremania said:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
Click to expand...
Click to collapse
How can I know if ADB recognize my phone?
I can access TWRP so I don't need to flash it again ? Is there a difference between just flash TWRP and flash TWRP with fastboot ?
Sry, my bad, i miss read that you can access twrp, sry, I thought you can't, what happens if you flash a rom, which twrp is installed, what were your steps that you end stuck on bootloader message ?
Edit: if your issue is that you don't know how to start flashing, read the Los thread and follow the op.
Instructions:
1. Install the Universal bootloader and your model specific modem.Failure to do so will not allow flashing the ROM!
2. Update recovery [Recommended -> Official TWRP for Axon7
3. Factory reset if coming from another ROM.
4. Install ROM
5. Install GApps (optionally) [Recommended -> Open GApps (arm64) (7.1) 2017-02-01 or Newer
Download all files from the thread and put them on to your microsdcard, if your twrp is up to date you don't have to do this again. Flash the zip files in the order of the instructions, just press install at twrp and choose the zips, you can add multiple and flash them together.
Man, trust me, I'm not a lazy man and all I want is to have my phone back even if it's stock
I don't understand what you're trying to make me do, sincerely
If you can give me a link where I can have a guide steps by steps or make this guide for me that would be the best thing of my day...
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
I really don't know your issue, except you seem not to read enough. What guide you want ? How I flash a custom rom to my phone ? How to use twrp ?Why you unlocked your bootloader ? How did you manage to have the stock recovery back ?
I have to guess what you want and what you already did . If you need a guide, here are severals in the guide section.
https://forum.xda-developers.com/axon-7/how-to
TheGreatNarchy said:
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
Click to expand...
Click to collapse
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
JTruj1ll0923 said:
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
Click to expand...
Click to collapse
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Choose an username... said:
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Click to expand...
Click to collapse
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
JTruj1ll0923 said:
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
Click to expand...
Click to collapse
The thing is, after you flash the universal bootloader, the TWRP on the sd gets replaced. but the TWRP that you are using is loaded in RAM. So even if you install a TWRP version you'll stay in the version you flashed before until you reboot. If you install the universal bootloader and then install the TWRP img you'll keep everything as-is on the next reboot. I discourage rebooting without a system especially on a G because any interruption might lock the phone in DFU. On an a2017U that wouldn't be a problem because the phone boots into edl if any software error is present
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
You can request unlock .img again
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
ShaktiSW said:
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
Click to expand...
Click to collapse
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
satyen_ said:
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
Click to expand...
Click to collapse
I never needed to. And AEX 6.0 run pretty much smooth without blue screen issue. I just followed the above mentioned procedures.
Deleted.
senthamizhan said:
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
Click to expand...
Click to collapse
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
renatohm said:
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
Click to expand...
Click to collapse
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
senthamizhan said:
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
Click to expand...
Click to collapse
Thanks for your kindness!
Alright then, I'm next on line to test! I'll just backup (it sucks...) then I'll flash!
Out of luck, flashing via Mi Tool now...
renatohm said:
Out of luck, flashing via Mi Tool now...
Click to expand...
Click to collapse
What happened
senthamizhan said:
What happened
Click to expand...
Click to collapse
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
renatohm said:
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
Click to expand...
Click to collapse
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
satyen_ said:
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
Click to expand...
Click to collapse
Yes, that's the reason I tried this in the first place, but it didn't work for me.
Qfil did work, and I'm now on Bootleggers.
sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
Bro,if u had used your email address try checking in your inbox again for image, just search bootloader .
I've changed my mail with a Gmail one and it work. Now I've my unl files
Inviato dal mio Z2 Plus utilizzando Tapatalk
flash vendor to factory ( if you already flashed factory to vendor ) "
explain this line
In these forums there was a file for updating baseband to 1.70. I flashed it promptly and my phone also went into soft brick. Because accidentally my bootloader got locked and got revised also. By using certain key combinations I succeeded in again unlocking my bootloader without formatting my inner storage . now I am able to flash 4.4 ROMs. Without going through all the hassles of backup, formatting and again flashing twrp.
Your guide didn't work for me (but step 2 using your file didn't lock my bootloader). It would be nice if you gave direct link to items in your steps (for i.e factory to vendor.zip, twrp...). I guess I'll try using qfil unless someone has some tips... BTW I can't find a good qfil guide for 4.4 kernel roms, could anyone give me a link to a helpful thread for it if I can't get it working using this method?
Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)
I am not expert on that field but from my knowledge try booting twrp and copy all your files to your pc or laptop (the one you need at least for saving some photos or videos ) then flash a fastboot ROM
And as I said from my knowledge not sure there might be other ways
testemailmailx said:
Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)
Click to expand...
Click to collapse
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...
Micdu70 said:
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...
Click to expand...
Click to collapse
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)
testemailmailx said:
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)
Click to expand...
Click to collapse
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo
batman957 said:
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo
Click to expand...
Click to collapse
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?
testemailmailx said:
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?
Click to expand...
Click to collapse
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )
batman957 said:
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )
Click to expand...
Click to collapse
I could make it work easily, but I want keep that step as final step cuz will wipe everything
testemailmailx said:
I could make it work easily, but I want keep that step as final step cuz will wipe everything
Click to expand...
Click to collapse
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) ? then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode
batman957 said:
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode
Click to expand...
Click to collapse
God bless us
I’m not using custom rom at all
BTW is there any way to delete twrp recovery without delete system ?
Did you by any chance flashed with the greek TWRP? I got the same bootloop so I get back to miui 10 official global version (the one I updated from) and it booted alright without wipe needed...
I'll try other TWRP versions as well though but right now I don't think I wanna update :|
Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3
sijav said:
Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3
Click to expand...
Click to collapse
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?
m-Khadem said:
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?
Click to expand...
Click to collapse
Here is patched vbmeta for davinci (K20/Mi 9T) => https://drive.google.com/file/d/1IC78J20ovcZudWYlijgSGdjeP6D3hx2V/view?usp=sharing
hello everybody
I was on the Android version 10 global version 11.0.4 ,I decided to download ExtendedUI OFFICIAL ROM, the bootloader was unlocked, then I Installaled the recovery , so i waiped system ,chash and date
by mistake i restart my phone , when i did that every thing is gone and the only thing that works is fastboot .
i tried everything nothing is worked .
please guys help me what should i do?:crying:
abood.mhd said:
hello everybody
I was on the Android version 10 global version 11.0.4 ,I decided to download ExtendedUI OFFICIAL ROM, the bootloader was unlocked, then I Installaled the recovery , so i waiped system ,chash and date
by mistake i restart my phone , when i did that every thing is gone and the only thing that works is fastboot .
i tried everything nothing is worked .
please guys help me what should i do?:crying:
Click to expand...
Click to collapse
Reflash the official twrp and flash the extended ui ROM. It isn't bricked
This happenned to me too.
If you can't boot or flash twrp via fastboot in this state (It wouldn't work for me), download and flash the fastboot ROM for your device and use the flash_all script (careful NOT to use flash_all_lock!!!!!). It'll go back to stock and keep the bootloader unlocked so you can flash TWRP and start over.
Benfatica said:
Reflash the official twrp and flash the extended ui ROM. It isn't bricked
Click to expand...
Click to collapse
how can i do that?
ShiningScias said:
This happenned to me too.
If you can't boot or flash twrp via fastboot in this state (It wouldn't work for me), download and flash the fastboot ROM for your device and use the flash_all script (careful NOT to use flash_all_lock!!!!!). It'll go back to stock and keep the bootloader unlocked so you can flash TWRP and start over.
Click to expand...
Click to collapse
can you please tell me exactly how to do this ? whech app is that?
thank you guys i did it lol