Related
Hi Experts,
I've flashed TWRP and the stock rom posted into XDA with GAPPS included , everything is fine and working.
Now I want to disable TWRP and deploy the stock recovery image bacause I need to sell the phone and after an factory reset TWRP comes up, to me it's acceptable but for an simple user this can be annoying.
I was not able to find the factory recovery.img for Nubia Z17 to flash it. Do someone knows if it's possible ?
This can cause problems ? I don't want to lock the phone again I just want to deploy the stock recovery and let the phone with the actual ROM.
Any help will be appreciated.
recovery.img
fabianomira said:
Hi Experts,
I've flashed TWRP and the stock rom posted into XDA with GAPPS included , everything is fine and working.
Now I want to disable TWRP and deploy the stock recovery image bacause I need to sell the phone and after an factory reset TWRP comes up, to me it's acceptable but for an simple user this can be annoying.
I was not able to find the factory recovery.img for Nubia Z17 to flash it. Do someone knows if it's possible ?
This can cause problems ? I don't want to lock the phone again I just want to deploy the stock recovery and let the phone with the actual ROM.
Any help will be appreciated.
Click to expand...
Click to collapse
I think you need to flash the "recovery.img" from the stock ROM to the phone.
And befor that flash the stock ROM
And I have to admit that I have not tried this but have also thought of doing it.
Let us know what happens.
Thomas
Understood. So I need to flash the Chinese stock ROM without GAPPS and other stuffs.
I think maybe just flashing the Chinese stock ROM it will replace TWRP.
BUT in order to install GAPPS I MUST have TWRP right?
What I want is to flash everything to have the phone functional to sell to an simple end user, this means with PlayStore, GAPPs and without TWRP.
well flashing the chinese ROM will NOT replace TWRP. I believe I tried this once.
I would do the following:
0. keep TWRP
1. Flash the chinese stock ROM
2. Flash GAPPS depening on your customer
3. as a last thing flash the stock recovery image
tsiebold said:
well flashing the chinese ROM will NOT replace TWRP. I believe I tried this once.
I would do the following:
0. keep TWRP
1. Flash the chinese stock ROM
2. Flash GAPPS depening on your customer
3. as a last thing flash the stock recovery image
Click to expand...
Click to collapse
understood, but how do I get the stock recovery image?
Take the Chinese Rom and open it with WINRAR or winzig.
At the top Level you'll find a recovery.img about 18mb in size.
I believe this is it.
Flash it with fastboot utility.
Cheers Thomas
winzig should be WINZIP
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
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Baron Zemo said:
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Click to expand...
Click to collapse
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
levone1 said:
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
Click to expand...
Click to collapse
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Baron Zemo said:
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Click to expand...
Click to collapse
Yes, flash 118 fw. If you want to save data, back it up first.
levone1 said:
Yes, flash 118 fw. If you want to save data, back it up first.
Click to expand...
Click to collapse
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Baron Zemo said:
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Click to expand...
Click to collapse
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
levone1 said:
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
Click to expand...
Click to collapse
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Baron Zemo said:
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Click to expand...
Click to collapse
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
levone1 said:
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
Click to expand...
Click to collapse
There's why it's so odd to me. Not the 1st time i'm doing this too. I would have waited even longer if it was stuck, but it was looping continuously back to the start.
I suspect could simply be a hardware fault developed. Anyway, i've given up. Probably best excuse to get a new phone
Many thanks for trying to help :good:
I haven't been able to get mine to reboot to recovery either, so i just boot recovery.img from fastboot anytime I want to mod. Kinda annoying but I haven't figured a way around it.
Hello everyone i am in desparate need of some guidance where i unfortunately Hard bricked my Mi9t while trying to flash the new Mokee Rom.
Where i think i went wrong was wiping the system option in twrp. After reboot i was stuck on flashboot and unable to get back into twrp recovery.
I then proceeded to flashboot twrp, also used multiple versions of twrp, again to hopefully be able to get into twrp recovery with no prevail.
Also tried to fastboot via Miflash tool with all latest fastboot roms available currently but kept getting a anti-rollback error.
So then i searched a way to install recovery or stock rom manually via flashboot commands. This caused me to end up where im at, no fastboot, no recovery, no logo at all. I connect the usb and the phone wont turn on at all, just a dead phone. Power button completely unresponsive now, Vol-Up/Vol-Down + Power and nothing.
I worked on it for countless hours trying to simply get into fastboot now with huge anxiety thinking i killed my phone.
I left my phone to charge all night and woke up this morning trying to get into fastboot again and nothing again.
Can someone please lead me in the right direction???
Everywhere i look the info seems to be outdated. At this point i am willing to send it in for repairs but i live in Indiana, US and there isnt a Xiaomi Service location anywhere in site.
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
When i 1st attempted to recover twrp i used TWRP 3.1.1-2 fixed from 4PDA. Ran the .exe file and the prompt said both fires installed successfully, but when i did a reboot it wouldnt go into twrp anymore, just stuck in logo so i would end up back in bootloader.
ttp://en.miui.com/thread-942449-1-1.html
This is exactly the instructions i tried to use before i lost fastboot.
At one point while entering the commands, it froze then my phone completely died and could never make it do anything else.
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
fabsen said:
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
Click to expand...
Click to collapse
I kno bro i felt like shyt believe me. Literally all day in panic and anxiety that i just wasnt thinking straight and using any kind of guide i can find and ended up here.
Made some progress today tho.
Since my device manager or MiFlash tool wasnt recognizing my device even when i installed Qualcom drivers and pushing all sorts of buttons lol,
I have now opened her up for some surgery and using the Test-Point EDL method.
https://i.postimg.cc/HWJGWHRw/test-point-redmi-k20-mi-9t.png
While USB connected and shorted these 2 pins my computer finally recognized my device in MiFlash Tool and Device Manager again as Qualcomm HS-USB QDLoader 9008 (COM3)!!!
Now the next problem is the MiFlash tool. I tried to flash rom and status states cannot receive hello packet. From what i understand, i need an authorized account.
Only thing i could find to bypass this was this but currently not yet working. - https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Any ideas where to go from here?
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
fabsen said:
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
Click to expand...
Click to collapse
Already ran into those sites and actually am currently trying out S-Unlock service to bypass Authorized Account with there XiaomiTool v0.01, and unfortunately again with no prevail.
https://imgur.com/gallery/WMt968b
As you can see i got passed Hello packet, but now it doesn't go passed this message or looks like it didnt do anything.
https://imgur.com/gallery/hHApyJL
Already contacted S-Unlock Admin and now waiting for response. Im assuming im using the right Flashboot Roms. Tried latest flashboot roms from here available. https://xiaomifirmwareupdater.com/miui/davinci/
I also emailed unbrick.ru if they support K20/Mi9T variant and waiting for there reply.
Firmware on your page is not up to date. Use https://mifirm.net/
What device do you have? EEA/Global/CN? And what flashfiles did you use? I'm asking this because the only way I know to brick your device is to flash global/eea-rom on chinese device and lock the bootloader.
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Waidowai said:
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Click to expand...
Click to collapse
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
fabsen said:
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
Click to expand...
Click to collapse
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Waidowai said:
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Click to expand...
Click to collapse
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
fabsen said:
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
Click to expand...
Click to collapse
If i download the xiamitool v2 and choose my device is bricked it says feature is not available yet.
/edit
If I choose mod the phone it says my phone serial and all the 3 other things are unknown.
if I select my phone my phone reboots and says waiting for debugging mode....
Then if I delete the ARB lines and try to flash via MiFlash it says error error no such file found
Can someone pls give me some clearer instructions.
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
/edit
alright who gives a dang I just flashed the eu rom to be safe with updates..
anyhow is it normal that my devices says Redmi by Xiaomi now?
Prior on my stock rom it said MI by mi.com or something
Waidowai said:
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
Click to expand...
Click to collapse
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
fabsen said:
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Click to expand...
Click to collapse
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
mauriciocardoso said:
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
Click to expand...
Click to collapse
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
just like me , for the anti roll issue u need to flash newers rom like from latest u flash on ur device before (recommend V10.3.11.0.PFJMIXM) u can get on mifirm.net . after download rom extract the file into fastboot tools then copy all .img file into fastboot tools . after that open the fastboot mode on ur phone and tools on pc
then flash this file
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
then try reboot phone into recovery
if work let me know . im trying make this method because before this i got this problem to after flashing paranoid rom without format data .
Waidowai said:
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
Click to expand...
Click to collapse
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
fabsen said:
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
Click to expand...
Click to collapse
I mean yeah that's what i thought just flash a official rom like any stock rom. Or rather if you change roms cuz if you update existing roms you don't really need to wipe anything anymore.
But apperently it busted my whole phone. It was a weird brick. My phone wasn't recognized as a phone anymore in fastboot. But it was recognized normal in adb. So I needed to change windows drivers to make my phone recognize.
And after that nothing booted but stock recovery and even then it said I don't have debugging enabled. Eventho I was connected to adb??
Anyhow I think the flash messed up the whole system partition. So what I did is in short formate the whole drive and start with a clean slate.. anyhow don't need to repeat all that.
But yeah I'm with you with the take on costume roms. I don't see the need anymore since most stock roms are decent nowadays and costume roms especially are most likely buggy somehow. Good thing is that most stuff I need in my phone is working on the eu rom. Like I said only thing that I could find not working are themes. But thats ok.
I don't know what that widevine L1 thing is. So I prolly don't need it. But maybe u can explain it to me Always up to learn new things.
Well for now I stick with the costume rom since it's basically no different to me. And the chance of bricking again like that with a costume rom are slim to none. If the phone brick it's most likely just a simple brick that can be fixed with twrp. and if that doesn't work by booting into twrp from adb.
Btw that didn't work on my weird brick either. I couldn't boot anything from adb. It gave me a black screen when trying to boot something.
Anyhow I'm glad I've got it running again. But somehow I'm not that surprised. Most times when I brick phones I can fix it when I'm at the point where I wanna throw the phone away. Cuz then I'm just flashing everything I can to make it work xD.
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