Related
My N7 is unlocked, I upgraded to 4.2.2 factory stock, rooted, and flashed ClockworkMod Recovery 6.0.2.3 touch recovery. I ran into a very strange issue; if I flash the custom recovery on the tablet, then the tablet boots into a screen that asks me to type my password to decrypt storage not allowing me to enter the homescreen until I do so. Later, I found out that flashing back to stock recovery fixes the problem and my N7 is functional again. I've tried everything while on the custom recovery: erasing, formatting, writing userdata to the device without success.
I'm not really sure what question you are asking. Also, I think you might be leaving something out which ought to be clarified, the way you describe things seems to have some pieces missing. (And, you really should not be starting yet another thread on this)
You shouldn't be able to flash custom ROMs with a stock recovery; so, are you saying that you:
- flash a ROM with a custom recovery
- try and boot it -- but it fails with the "enter password" prompt (you mention "won't let me enter the homescreen")
- flash the stock recovery into place
- perform a factory reset with the stock recovery
- now the ROM boots?
Also, do you get the same result with TWRP?
bftb0 said:
I'm not really sure what question you are asking. Also, I think you might be leaving something out which ought to be clarified, the way you describe things seems to have some pieces missing. (And, you really should not be starting yet another thread on this)
You shouldn't be able to flash custom ROMs with a stock recovery; so, are you saying that you:
- flash a ROM with a custom recovery
- try and boot it -- but it fails with the "enter password" prompt (you mention "won't let me enter the homescreen")
- flash the stock recovery into place
- perform a factory reset with the stock recovery
- now the ROM boots?
Also, do you get the same result with TWRP?
Click to expand...
Click to collapse
It's a help/troubleshooting post. I know it wasn't good to start another thread, but I felt that people that had already browsed my thread the first time wouldn't come back and now I found the reason behind my issue. I didn't flash a custom rom with stock recovery; I used fastboot on my pc to issue commands. My phone has the factory stock rom on it - then if I flash clockworkmod recovery, the next time I reboot, there's a screen that says I need to type a password to decrypt storage and I'm not able to access anything. If I go back into the bootloader and erase and write the stock recovery, I'm able to boot into the homescreen without the issue. Everything I've flashed to the tablet is done through my pc via fastboot. I never tried TWRP, but I don't like that recovery anyways.
UnlockedNand said:
It's a help/troubleshooting post. I know it wasn't good to start another thread, but I felt that people that had already browsed my thread the first time wouldn't come back and now I found the reason behind my issue. I didn't flash a custom rom with stock recovery; I used fastboot on my pc to issue commands. My phone has the factory stock rom on it - then if I flash clockworkmod recovery, the next time I reboot, there's a screen that says I need to type a password to decrypt storage and I'm not able to access anything. If I go back into the bootloader and erase and write the stock recovery, I'm able to boot into the homescreen without the issue. Everything I've flashed to the tablet is done through my pc via fastboot. I never tried TWRP, but I don't like that recovery anyways.
Click to expand...
Click to collapse
OK, read and understood. Very bizzare, however. Almost sounds more like something caused by the bootloader (during the fastboot write) rather than it mattering which custom recovery is sitting there (it's not clear from the above, but it almost sounds like it is not even necessary to have ever booted the custom recovery from the device's recovery partition for the problem to appear)
Are you also saying that you can not flash a custom ROM from the custom recovery without this "enter password" phenomenon happening, or is it only this combo of pure stock ROM + recovery flashed via fastboot that exhibits the problem?
I have a lightly-rooted JDQ39 Stock (4.2.2) ROM with a custom recovery - no such troubles. But mine was installed by using factory-via-fastboot of 4.2.1, followed by a manually-triggered OTA to JDQ39, and then followed in turn by a fastboot flash of the recovery partition (TWRP 2.4.1.0). That last flash was certainly performed by the 4.18 bootloader.
No troubles, but that is certainly a different installation path.
Two more small questions for clarification purposes: when you installed the factory 4.2.2 ROM via fastboot, did you follow the exact sequence of the install-all.sh script:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jdq39.zip
... or did you omit anything (e.g. one or more of the erases, the bootloader flashing, etc)?
Yeah, it's like the bootloader writes bad information to the userdata partition if the recovery isn't stock. I haven't flashed a custom rom from the custom recovery, but I'm assuming the type your password issue would appear again. Yes, it's a combo of pure stock rom + custom recovery when this problem occurs. No, when I installed the 4.2.2 factory stock rom, I unzipped all the image files and typed these commands.
Code:
fastboot oem lock
fastboot oem unlock
fastboot flash bootloader <bootloader name>.img
fastboot flash boot <boot name>.img
fastboot flash system <system name>.img
fastboot flash userdata <userdata name>.img
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
I've also gone back and manually erased, formatted, and wrote the userdata partition again. Maybe I should try downgrading the bootloader to 4.2.1, reflash userdata, and flash the custom recovery?
UnlockedNand said:
Yeah, it's like the bootloader writes bad information to the userdata partition if the recovery isn't stock. I haven't flashed a custom rom from the custom recovery, but I'm assuming the type your password issue would appear again. Yes, it's a combo of pure stock rom + custom recovery when this problem occurs. No, when I installed the 4.2.2 factory stock rom, I unzipped all the image files and typed these commands.
Code:
fastboot oem lock
fastboot oem unlock
fastboot flash bootloader <bootloader name>.img
fastboot flash boot <boot name>.img
fastboot flash system <system name>.img
fastboot flash userdata <userdata name>.img
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
I've also gone back and manually erased, formatted, and wrote the userdata partition again. Maybe I should try downgrading the bootloader to 4.2.1, reflash userdata, and flash the custom recovery?
Click to expand...
Click to collapse
Hmmm. Well, I can't say for sure, but I am willing to gamble that the bootloader relocates itself into a load-offset address so that it runs out of RAM rather than running directly out of Flash Memory. Much quicker that way. The implication of that is that once it is fully loaded into RAM and operational, you could actually erase the bootloader and suffer no ill effects - until you powered off the device. Then you would be in real trouble.
The point is, in the Google factory sequence, all of the partition flashing is done by the new bootloader (4.18), whereas in your case none of it is done that way - except for the custom recovery flash. Here's the Google sequence:
- erase all partitions using currently installed bootloader (4.13)
- flash new bootloader and boot into it ( 4.13 -> 4.18 )
- flash all 4.2.2 ROM partitions using new bootloader
whereas your sequence looks like:
- (no explicit erasures)
- flash partitions with old bootloader (4.13)
- reboot into new bootloader ( 4.13 -> 4.18 )
- erase cache
- flash recovery with new bootloader ( 4.18 )
very different!
Also, the "-w" switch used in the google sequence causes partition erasure and re-formatting (depending on partition type) prior to each partition's flashing.
Without going through the lock/unlock procedure, I suppose it would be possible to reflash all the partitions with 4.18 to see if the problem disappears. But, now that I said that, I realize my tab - which had an OTA upgrade - is sort of similar in that the partitions & files patched by the OTA were all initially flashed by 4.13 (by me), patched by the OTA, and then finally I flashed only the custom recovery with the 4.18 bootloader.
Doing further experimentation might mean attempting a bootloader rollback flash. I can't say that I've seen reports here of anybody trying it. And I can't say I blame them - there could be dragons hiding in that process.
Ah, I see. The sequence I followed flashing the partitions would erase and write the partitions automatically done by the fastboot script. The only instance where I erased, formatted, and flashed the partition was the userdata when I was troubleshooting. From reading other threads before, I believe people have done bootloader rollbacks without consequences to the rest of the partitions. The bootloader updates contain fixes, but aren't explicitly required for the rom to run, am I correct?
I used the WonderHowTo site incorrectly to flash a nexus 5 version of twrp unto my nexus 4.
My device at this point booted to a blank screen. It could still boot the boot loader at this point.
To "fix" this I found the correct version of twrp for my device and proceeded to flash that unto my device.
This has appeared to work since I can access twrp on my device but it is only thing I can access on the phone. When I attempt to boot to system through twrp I am sent back into twrp.
I have attempted to use the wugfresh root tool kit to unroot and return to stock using both soft bricked and phone is still working normally options with no success.
It can still boot to the boot loader currently.
I have logs from the toolkit if these can shed more light on my issue.
Is there anyway I can return my device to stock? Thanks for any response
Flash factory image
https://developers.google.com/android/nexus/images#occam
attempted
attempted to flash stock and got the following error message
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
codebam said:
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
Click to expand...
Click to collapse
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
MrTalk said:
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
Click to expand...
Click to collapse
Okay adb push a cyanogenmod zip from here and flash it in recovery. It should automatically install a working boot image. You should also flash the latest bootloader in the factory image with "fastboot flash bootloader bootloader.img" if you're using an outdated bootloader.
used the advice
I pushed the zip file using cmd and it appears to have been successful since I was given the summary of data transferred and how long it took once the process was finished.
I can't find the zip file in twrp to attempt to flash it.. Is there any reason the file name would change inside the device once it has been pushed?
Is there a way to flash the zip in question without pushing it unto the device?
Hi,
I have a Nexus 4 which was flashed with Lollipop 5.1.1.
My problem started when, after letting the battery completely drain and then trying to turn the phone on again, I got stuck on the message "Android is starting... optimizing apps" for days. I tried rebooting and factory format with no success.
I also tried formatting it through TWRP, but I got the message "Unable to mount /cache". After that, I tried flashing older factory images but only got my phone to work with the oldest version of jelly bean available by google developers page (4.2.2). After I got it to work, I tried to OTA update it to 4.3, but the same message "Android is starting ... optimizing apps" came back.
I had no other choice but to fastboot format it and flash it again with 4.2.2.
Any ideas on what could possibly be causing this? I thought it might be some problem in the cache partition but haven't found a way to fix it or if it's even possible to. Apparently everything's working with 4.2.2 but I'd love to go back to 5.1.1!
Thanks in advance!
dont dirty flash the factory image. make a clean factory image flash
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
audit13 said:
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Click to expand...
Click to collapse
Haven't tried that, I'll give it a go and post the results here!
I've also noticed the phone isn't receiving any signal and it doesn't display the IMEI anymore..
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
audit13 said:
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
Click to expand...
Click to collapse
Did a clean factory image flash of Lollipop 5.1.1, booted into twrp recovery (I'm not sure how to go back to stock recovery) to wipe the data and got the following message:
E: UnMount: Unable to find partition for path '/sdcard'
E: Mount: Unable to find partition for path '/sdcard'
Updating partition details...
E: Unable to mount '/cache'
...done
E: Unable to mount '/cache'
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Formatting Data using make_ext4fs function.
Ypu may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to mount '/cache'
...done
After that I rebooted the phone and it's been stuck on bootloop again since then.
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
audit13 said:
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
Click to expand...
Click to collapse
Yeah, I flashed the images for boot, recovery, system, userdata and cache separately. I'll look up how to get back into stock recovery now and I'll try what you've said!
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
audit13 said:
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
Click to expand...
Click to collapse
I tried it again, flashed everything including recovery, went into stock recovery mode and wiped the data. Apparently its back to being stuck on bootloop
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
audit13 said:
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
Click to expand...
Click to collapse
Did it, still stuck on bootloop... Not sure if it can be somehow related but I got this message when I booted into recovery
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
audit13 said:
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
Click to expand...
Click to collapse
Ah, thanks for the help, anyway!
If someone else knows what to do.. The phone is now back to the initial message "android is starting... optimizing apps". Kinda of losing hope now
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
playitlouder said:
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
Click to expand...
Click to collapse
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
thafuchs said:
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
Click to expand...
Click to collapse
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
playitlouder said:
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
Click to expand...
Click to collapse
Okay, got some errors on the way... trying to erase data failed (Remote: partition table doesnt exist), format data failed too (formatting is not supported for filesystem with type ' '.)
Also, on the last command:
.\fastboot -w update .\image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
[...]
checking version-bootloader
FAILED
Device version-bootloader is 'MAKOZ10o'
Update requires 'MAKOZ30f'
Rebooted and its now stuck on google logo
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
playitlouder said:
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
Click to expand...
Click to collapse
Okay, I've flashed bootloader, rebooted, flashed radio, rebooted, typed the update command but the checking of bootloader version failed again.. rebooted and its back to being stuck on google logo
When I try to flash TWRP (via "fastboot flash recovery twrp.img" then "fastboot boot twrp.img") I receive the following error:
Downloading 'boot.img'
OKAY [1.477s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.534s
I've tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
that link just saved me!
I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app
I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Spannaa said:
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Click to expand...
Click to collapse
That's exactly what I meant to convey.
Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
The bootloader (also called fastboot) comes with the original ROM. In your case you're already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
Also you can't run ROMs not compatible with this newer bootloader (which means pretty much any ROM that's not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.
Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.
That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.
Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.
thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse
Hi guys,
i was on Miui Global 10.xxxx (dont know exactly)
bootloader was unlocked.
Rollback protection target was 1
my recovery was Orangefox recovery (https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899)
I have made a full backup of all partitions before.
I wanted to flash Miui 11.0.4.0 global to flash a custom rom.
First i flashed recovery and installed the recovery.zip.
That worked fine.
Then i wanted to flash Miui 11.0.4.0 with this instructions for a clean flash:
1. If you're coming from another ROM or need to perform a clean flash:
Boot into Recovery
Wipe Data/Cache/System
Flash vendor/firmware (Global 11.0.4.0 recommended)
Flash ROM
(Optional) Flash Gapps (not included!)
(Optional) Flash the latest Magisk
Reboot
Enjoy
This instructions are from here: https://forum.xda-developers.com/mi-9t/development/rom-stagos-t4072637
So, i was in recovery, and deleted data, cache and system.
Then i restarted the phone to go to recovery, but that didnt work.
It stucked in bootloop.
I now reinstalled Adb and fastboot, and erased recovery and System partition.
There were much errors in time due old adb and fastboot version etc....
But now iam at this point here again.
wait for your answers how to continue.....
It looks like just flashing or booting recovery is not possible without system partition.
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
1. When you make format data, than reboot in twrp again
2.when boot second time, wipe data, dalvick, cache, system...and flash new rom.
If you wipe system partition and reboot in twrp again without system, you get fastboot.
zgfg said:
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
Click to expand...
Click to collapse
Sooo....after hours of reading with errors over errors and fixing, it still doesnt work.
First i tried to flash everything via mi flashtool.
There was an error: Antirollbackcheck Error.
https://www.reddit.com/r/Xiaomi/comments/d0xmbp/what_on_earth_is_miflash_antirollback_check_error/
https://xiaomi.eu/community/threads...nd-flashing-recovery-fails-please-help.51349/
To fix this i had to move the Tool and the rom into my C hard drive next to program etc folders...
Then i editet the flashall.bat file and removed the rollbackcheck lines.
Now after doing this, it flashed for 100 seconds, and then there was this error: Failed to flash dtbo.img
sooo....Then i tried to flash the dtbo.img and all the other ones via Minimal adb and fastboot.
https://forum.xda-developers.com/mi-9t/help/flash-stuck-fastboot-soft-brick-t3962662/page3
And this didnt work for me too. Everytime if i try to flash dtbo.img, this error comes:
target didnt report max-download-size
sending dtbo (32768KB)....
FAILED (command write failed (no error))
finished.
Now everything is like before....
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Kidence said:
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Click to expand...
Click to collapse
C:\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-12-davinci-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.914s]
writing 'recovery'...
OKAY [ 0.151s]
finished. total time: 2.065s
C:\Minimal ADB and Fastboot>fastboot boot recovery
error: cannot load 'recovery': No such file or directory
C:\Minimal ADB and Fastboot>fastboot boot twrp-3.3.1-12-davinci-mauronofrio.img
downloading 'boot.img'...
OKAY [ 1.891s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.900s
When you flash recovery, hold volume up and type in adb
fastboot reboot
After that, phone will be boot in twrp
Sent from my MI 9T using Tapatalk
FINALLY it worked YES
FIRST: The Story for everybody who has the same problem like me:
Device: Xiaomi Mi 9T
Firmware: MIUI 10 GLOBAL
Antirollbackprotectioncounter: 1
Bootloader: Unlocked
Story:
At the beginning, everything was working, but i wanted to install a custom rom (STAGOS)
For this step, i had to Update my Miui firmware on 11.0.4.0.
But this step didnt work so well via device OTA (error), then i decided to install it via custom recovery.
I still had the stock recovery on my device, so i went in fastboot mode, and installed Orangefox recovery via ADB and Fastboot on Windows. That worked without problems.
In Orangefox, i wiped as sayed in instructions data, cache and System. then i rebooted.
But before realised that was the wrong way, i stucked in fastboot.
No tools helped. ADB and Fastboot didnt work as seen in screenshots.
I tried everything via fastboot....
fastboot flash recovery XXX.img
fastboot boot XXXX.img
Fastboot format.....etc
But NOTHING worked. Everytime there were the following errors:
Target didnt report Max download size
Error: Cannot load recovery
No such file or directory
Error: Download size is higher that allowed
Failed to load boot image (Load error)
Command write failed (no error)
and some other ones too.....
It looked like, some flashes worked and some not. Sometimes it worked, sometimes not.
After some new tries it just showed via the command: Fastboot devices
????????? fastboot
That problem has been solved. Just unplug the device and wait for 10 minutes until it shuts down automatically.
If that doesnt work, you can try to replug it to pc some times again.
It looked like replugging and using different USB Port (one user solved the problem via USB 2.0) helps to get a better connection and prevent errors.
Then i tried some tools, for example android all in one tool, but no one worked.
After this, i reinstalled the driver and installed MI Flash tool (https://mi-globe.com/download-xiaomi-mi-flash-tool-all-versions/)
It looks like there are some mi flash tools around here which are not working right, but THIS one worked for me.
After installing, i connected my device, choosed the fastboot firmware (.tgz), unpacked it and choosed the right location in mi Flash tool.
Firmware files are find here: https://c.mi.com/oc/miuidownload/detail?guide=2
(You should check you Antirollback counter before to avoid a brick. Here you find some informations: https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/)
DONT FORGET TO CHOOSE IN THE RIGHT DOWN CORNER: CLEAN ALL !!! (normally, clean all and lock is choosen, but that bricks your device)
After doing this, i started flashing, but there was an error: Antirollbackcheck error.
I solved it via moving the mi flashtool directly into my C hard drive, and deleted some lines in the flashall.bat, as seen in post history here.
Then....it worked for some seconds longer, but than: Error: Failed to flash dtbo.img
So i tried it via ADB and Fastboot. But nothing changed.
Then i tried flashing via mi Flash tool again, and this time the following error comes: Failed to flash system.img.
After this is thought: hmmm....something is very wrong with this device....lets try again, after a device restart.
So i tried again, let it running for ~360 seconds, and IT WORKED!
At the End: there was the following error: Error: Not catch checkpoint.
But this error (you can also see in a screenshot) it not necessary.
This is the result of removing some lines in flashall.bat.
After this my phone successfully booted im Miui 11.