Related
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
EDIT: Sorry, I post on the wrong section. If someone can move this post on the right section ...
gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
try to use QPST (Qfil) method. This is final method can bring back your phone. If fail, congratulation ! :silly:
I success with QFIL Zui works but it's awful
Unfortunately, I try to install stock cos but I have the same issue.... Bootloop after "App update message".
I don't know why
Try flashing Cyanogen Os using fastboot
I did that...
I flash with the tool via fastboot. But bootloop result...
I also tried to flash CM13 via TWRP but I have an error message...
Do you have any other solutions?
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Here u go, QFIL CM 12 ROM: https://mega.nz/#!RFUw2CbZ!GXS6KeOy_8n2y_rOBJUS5WJSP5kchODcGUF0U1TxYO8
So with the ham version is the same as the QFIL version?
gaara19 said:
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Click to expand...
Click to collapse
READ THIS( use google translate)
BTW, what are the fastboot commands that you are using?
Hello everyone, I have the problem, that my 3T boots to recovery every time I boot. The system is no more booting. What I did was, "updating" in the CM about/update menu (from unofficial cm14.1 13.12. to 14.12. ).
So maybe an open recovery script was created and booted to bootloader. Update failed but I did it manually.
From now on the phone does just only boot twrp recovery (or is it a boot loop ?). I tried to restore a backup and install the oxygen os via zip and wiped all partitions (except internal storage) but nothing helps. Does anyone know this and can give me advice ? Thank a lot in advance.
Edit:
For the OnePlus One if found an error report which look a little bit my error:
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
Click to expand...
Click to collapse
But the partition layout on the 3T seems to be different, I can see only partitions like sda etc ...
same here
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
Thank you!
Enviado do meu ONEPLUS A3003 através de Tapatalk
Thnaks so much
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
:good:
I follow your recommendation thanks for your assistance I fixed my OP3T,
What a mess ... after all this I wanted to install my CM backups again, but TWRP refused to boot. I had only a black screen with a white LED when going to recovery. But now after some hours I have a solution to this. You need to update Oxygen OS before going on !!
Make a full system update or flash this update via TWRP: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.3/
After this TWRP is booting as expected.
Now I'll enjoy a beer or two or ....
Good luck to all others. If anybody needs assistance ... contact me.
never had a issue
Please help!!!! I tried flashing the update for the latest OTA, I had the full zip. I have unlocked bootloader, twrp, phh supersu, magisk and xposed. I did a nandroid backup and then clicked Wipe- Dalvik and Cache. I then flashed the zip. For 20 mins the boot logo was spinning around, so I rebooted into twrp to see what was going on. Now I can't reboot and it shows no data, it says my device is encrypted and I can't see any files. What can I do??
Was your internal storage encrypted before ?
TWRP doesn't show your internal storage and didn't ask for a password ?
fix bootloop
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
I solved the problem
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
RE
TOMASITO95 said:
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
Click to expand...
Click to collapse
how ? can you please teach me ( my op3t didn`t go to system is says " md5 checksum failed , recovery failed , boot failed , system failed , boot_aging failed , dsp failed , modem failed please help me (
Change USB port
Try a different USB port. I flashed it through a 2.0 USB port instead of the 3.0 and no checksum error!
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
just calm down and try to unlock bootloader again by (miflash_unlock) then install in computer (adb-setup-1.4.3) then keep press on power and volume down button for fastboat then open miflash (version=2017.4.25.0) and connect your phone and press refresh to see your phone on list then download India Stable Firmwares version in same thread you mention and unzip the file and unzip the result file then you will see 12 file (images/ flash_all.bat .....) and in miflash choose the file and press flash and wait... when its done your phone will work but will give account is locked just connect with wifi and write your micloud password and done .
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
Miflash only works on an unlocked bootloader. It appears that you have a Chinese Model and you just did what was supposed to be avoided. You should get accustomed to Miflash moving forward. Never use Flash_All_Lock while cross flashing China/Global roms. You'll have to wait to unlock your Bootloader now and post that flash the China rom to get back. If any time you wish to move to the India rom, either use a twrp recovery or just use Flash_All while using the fastboot image which should eventually avoid locking the bootloader
Sent from my Redmi K20 Pro using Tapatalk
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
1. if you can still enter fastboot mode, there is a possibility that you can do TWRP flashing again (the TWRP version must be correct so that the data on the cellphone can be read properly) / Flashing from the PC (if you are lucky, the flashing will work properly without any problem or you can bypass the bootloader locked using software or something else). [make sure ROM version must be appropriate because this is very crucial]
2. You can try using the test point method (EDL / Emergency Download Mode) [This method is usually used if your K20Pro is constrained by Hardbrick due to ARB4] , but this method requires you to open the case / body behind your K20Pro. and I cannot guarantee that the flashing process will succeed easily because in some cases if the K20Pro is detected damage / error due to ARB4, then you are required to have an Authorized Mi Account. I might be able to help you remotely, if you agree with the risks & requirements in the flashing process (I can lend my account, but it's not free).
Hi All, I did the same thing - whoever build the UI for MiFlash should be shot - why default that selection to something that will be undesirable!!?
Anyway, i tried to flash indian rom and forgot to set to Clean All, it locked the bootloader.
So i now have redmi recovery and Fastboot options only on phone.
Have tried fastboot + miflash but all options (now with Chinese rom) - says Erase Boot Error.
Tried MiAssistant + Mi PC Suite - it is not detecting the phone in either MiAssistant recovery mode nor Fastboot mode. what is weird is the phone and connector animation on phone is correctly depicting when it is plugged in/unplugged. But the PC suite isnt detecting the device.
Soft bricked - *sigh.... any help will be greatly appreciated from the community
BTW i am more worried that the phone will run out of battery and never wake up once battery drains completely as it is in bootloop into Redmi recovery and can't be turned off (someone tell me how!?) - I don't see the phone respond to charging in any state... : (
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
hippo2s said:
Hi All, I did the same thing - whoever build the UI for MiFlash should be shot - why default that selection to something that will be undesirable!!?
Anyway, i tried to flash indian rom and forgot to set to Clean All, it locked the bootloader.
So i now have redmi recovery and Fastboot options only on phone.
Have tried fastboot + miflash but all options (now with Chinese rom) - says Erase Boot Error.
Tried MiAssistant + Mi PC Suite - it is not detecting the phone in either MiAssistant recovery mode nor Fastboot mode. what is weird is the phone and connector animation on phone is correctly depicting when it is plugged in/unplugged. But the PC suite isnt detecting the device.
Soft bricked - *sigh.... any help will be greatly appreciated from the community
BTW i am more worried that the phone will run out of battery and never wake up once battery drains completely as it is in bootloop into Redmi recovery and can't be turned off (someone tell me how!?) - I don't see the phone respond to charging in any state... : (
Click to expand...
Click to collapse
Read this https://forum.xda-developers.com/k20-pro/help/destroyed-error-fastboot-locked-t3946012
And this
https://forum.xda-developers.com/k20-pro/help/k20-pro-bricked-t3951531
You're probably going to have to open up the phone and pay $20 for someone to use their authorised account to flash an official ROM whilst remoting in to your PC.
322Reznov said:
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
Click to expand...
Click to collapse
Some great ideas - Just tried to unlock bootloader - This device came pre-unlocked so the device is tied to the seller's account.
I have unlock permission - but unlocker say device is not bound to my account matching my assumptions - anyone know what's the best way to re-claim ownership? Especially when I can't get into ROM at all?
hippo2s said:
Some great ideas - Just tried to unlock bootloader - This device came pre-unlocked so the device is tied to the seller's account.
I have unlock permission - but unlocker say device is not bound to my account matching my assumptions - anyone know what's the best way to re-claim ownership? Especially when I can't get into ROM at all?
Click to expand...
Click to collapse
My comment was meant for OP but I hoped it would help you as well! I am personally not well informed about the Xiaomi / Redmi ownership situation when the seller unlocked the phone.. maybe you can contact them and get a corresponding password to the account, it has been the solution I have seen offered here. Maybe the emergency flash solution from Robbo.5000 works?
I just got this phone a week now and was only able to unlock and flash yesterday, I was aware of the ownership problem thanks to this forum so I bought the sealed CN version. Hope you figure it out!
Thanks guys. I am going for the Test Point solution - have made contact with the Russian tech the others did and made an appointment. I just have to pretend to be Jerry Rig before then and open her up! Fingers crossed!
322Reznov said:
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
Click to expand...
Click to collapse
You need yo flash magisk after you flash twrp if you want to run regular miui, to prevent it from overwriting the recovery. Its the same on poco and all xiaomi phones
Mooatreides said:
You need yo flash magisk after you flash twrp if you want to run regular miui, to prevent it from overwriting the recovery. Its the same on poco and all xiaomi phones
Click to expand...
Click to collapse
Ah alright thank you for the info! This is my first ever Xiaomi / Redmi phone haha
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
Did you flash the global rom on an existing running Chinese rom or on an empty device (formatted)? Just for myself cuz I'm not sure whether to unlock and then unable to relock. Thanks.
pungky771 said:
1. if you can still enter fastboot mode, there is a possibility that you can do TWRP flashing again (the TWRP version must be correct so that the data on the cellphone can be read properly) / Flashing from the PC (if you are lucky, the flashing will work properly without any problem or you can bypass the bootloader locked using software or something else). [make sure ROM version must be appropriate because this is very crucial]
2. You can try using the test point method (EDL / Emergency Download Mode) [This method is usually used if your K20Pro is constrained by Hardbrick due to ARB4] , but this method requires you to open the case / body behind your K20Pro. and I cannot guarantee that the flashing process will succeed easily because in some cases if the K20Pro is detected damage / error due to ARB4, then you are required to have an Authorized Mi Account. I might be able to help you remotely, if you agree with the risks & requirements in the flashing process (I can lend my account, but it's not free).
Click to expand...
Click to collapse
My k20 pro is hard bricked and i cant get fast boot or any thing it wont even come on. Assistance please
hippo2s said:
Thanks guys. I am going for the Test Point solution - have made contact with the Russian tech the others did and made an appointment. I just have to pretend to be Jerry Rig before then and open her up! Fingers crossed!
Click to expand...
Click to collapse
Could you please point me to the person you have contacted?
I'm in EDL for about two weeks now, unable to solve it by different means (seller sais 'send it back', which I'm not goong to do; S-unlock has the service unavailable, even though I've paid them and the guy I contacted there tried through TW to no avail, waiting for a 'money back' now)..
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
sabbath88 said:
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
Click to expand...
Click to collapse
Just flash a custom recovery, the device even had the offical twrp. So?? Just not into fastboot and then flash the recovery by the -- command
fastboot flash recovery recovery.img
(You have to rename the twrp file to recovery or whatever, just write the image file name instead of recovery in the second one. Ex fastboot flash recovery 123.img)
Then command
Fastboot reboot
(Hold the power up button for booting into twrp before hitting enter)
Download a miui recovery rom for your device from anywhere, I don't know I'm lazy.
And before flashing, go into mount select vendor and system if not selected.
And then select wipe
Advanced wipe
Select vendor system data cache.
Swipe to clean
Move the rom to your device
(If your device does not show up in your pc, then go into mount (twrp) select enable MTP if it's disabled, if it shows disabled then enable it again)
After that just flash your rom and then a permissive patch you can ask anyone. Or just flash pitchblack recovery. Fixed my problem of not not booting.
Sorry for the wrong format, wrote it on mobile, as I am a lazy bum.
Wut bruh.
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
ChakibDEV said:
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
Click to expand...
Click to collapse
thanks so much, that helped
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not