My watch suddenly restart and stuck in logo lg screen... I can't make it go further.
I tried get into recovery through fastboot and seems (i don't know for sure) system in unmounted but i can not mount it or write in system (i can not flash)
Can someone explain me step by step for dummies how to solve it?
Thanks in advance
Enviado desde mi Nexus 5 mediante Tapatalk
Upp still stuck
Enviado desde mi Nexus 5 mediante Tapatalk
mmc_meneses said:
Upp still stuck
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
Just factory reset it should work after that if no then reinstall system here
Still stuck, the problem i see is when i try from fastboot to erase data I receive a FAILED remote: partition table doesn't exist
Whatever i try to flash i go into the LG bootscreen bootloop
Any ideas?
Also when I try from fastboot a format data I receive a "formatting is not supported for filesystem with type ' ' .
I ll try a little bit more, if not i ll use lg warranty... How should i send back the watch, i mean bootloader locked (that let me change through fastboot...)
Enviado desde mi Nexus 5 mediante Tapatalk
To lock the bootloader type this from fastboot:
fastboot oem lock
Try flash stock system(complete package - system, boot and recovery) in fastboot and if you will get bootloop, boot into twrp ("fastboot boot YourTwrpName.img") and make factory reset. After that boot to system. It may help.
The problem seems I can't write in the watch partitions...like fastboot boot works but fasboot flash doesn't make any changes...Maybe partitions are corrupt or something..., I think I am going to try to use the warranty
Did you try "fastboot format system" command or format option in TWRP? It looks like damaged partition/ partition table but if format doesn't work I don't know how to fix it.
Re-install your device drivers from here
by this I mean go into device manager find the device right click uninstall then reboot then install the drivers again from the link
koszanty said:
Did you try "fastboot format system" command or format option in TWRP? It looks like damaged partition/ partition table but if format doesn't work I don't know how to fix it.
Click to expand...
Click to collapse
Yes I tried it and get back a "formatting is not supported for filesystem with type ' ' .
Anyway I already send it back to LG, let's see if the warranty covers it (I hope so)
Related
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk
I think the title speaks for itself but here's the story
I recently flashed the Oreo kdz on my h850, so I lost TWRP and Magisk, but I cannot live without root access. Since my phone's volume down button is not working, is there any way I can install TWRP? Using adb and fastboot commands I can flash it, but if I boot into the system the recovery will be overwritten, so I really have to boot to the recovery.
Any ideas?
(EDIT: nevermind, I forgot that recovery is overwritten first boot without root. How about "fastboot boot recovery xxxx.img"?
This will boot temporarily into twrp where you can root device and flash twrp permanently )
Enable adb in developer option, and using a computer type
"adb reboot bootloader"
And then flash twrp
"fastboot flash recovery xxxxx.img"
Then boot into the os and type "adb reboot recovery" to enter twrp
Enviado desde mi LG-H850 mediante Tapatalk
jaggyjags said:
(EDIT: nevermind, I forgot that recovery is overwritten first boot without root. How about "fastboot boot recovery xxxx.img"?
This will boot temporarily into twrp where you can root device and flash twrp permanently )
Enable adb in developer option, and using a computer type
"adb reboot bootloader"
And then flash twrp
"fastboot flash recovery xxxxx.img"
Then boot into the os and type "adb reboot recovery" to enter twrp
Enviado desde mi LG-H850 mediante Tapatalk
Click to expand...
Click to collapse
I guess it's worth the try
But how can I permanently flash it?
leonardovallem said:
I guess it's worth the try
But how can I permanently flash it?
Click to expand...
Click to collapse
Twrp can flash .img files
Enviado desde mi LG-H850 mediante Tapatalk
jaggyjags said:
Twrp can flash .img files
Enviado desde mi LG-H850 mediante Tapatalk
Click to expand...
Click to collapse
yeah you're right!! totally forgot about that!! thank you so much, I'll try it out, hopefully it'll work. Thanks again!!!
Need help.. cant turn on my Phone.. always stuck at android one Logo and fastboot (when i try hold volume up and power )
i rooted phone (adb,twrp,magisk) . Everything well good, but WIFI didn't work. Then i get in TWRP and maybe deleted partition A and B( ) i can't get through the Fastboot.
my mi a3 is V10.3.6.0.PFQMIXM version-- and cant Flash it with miflash tool, it says error : can not found file flash_all_lock.bat
now i cant find my device with Adb devices (its says List of devices attached)
pls help :/ thank you.
Go to nearest service centre
Going to a service center probably isn't a wise idea. You've rooted your phone - your warranty is gone.
I guess you don't have the right drivers installed OR, the stock rom you were trying to flash had some issues with the flash script. You might want to take a look at this post
Download the correct stock ROM for your device, the .tgz version & flash it with miflash tool. It's important to note that some versions of miflash tool don't work with Mi A series phones for unknown reasons.
Alternatively, if your recovery is working, then you can flash the recovery version of stock rom. It's all available on this forum.
evanB70 said:
Going to a service center probably isn't a wise idea. You've rooted your phone - your warranty is gone.
I guess you don't have the right drivers installed OR, the stock rom you were trying flash had some issues with the flash script. You might want to take a look at this post
Download the correct stock ROM for your device, the .tgz version & flash it with miflash tool. It's important to note that some versions of miflash tool don't work with Mi A series phones for unknown reasons.
Alternatively, if your recovery is working, then you can flash the recovery version of stock rom. It's all available on this forum.
Click to expand...
Click to collapse
thx m8
I flashed with Miflash( and writed flash_all_lock.bat), used version V10.3.4.0. and it worked.. wifi working. (my build number say it is V10.3.6) ?
ticmali said:
thx m8
I flashed with Miflash( and writed flash_all_lock.bat), used version V10.3.4.0. and it worked.. wifi working. (my build number say it is V10.3.6) ?
Click to expand...
Click to collapse
Glad to hear you're phone is working fine now :highfive: :highfive:
I think you somehow had your wifi / mobile data on & the phone downloaded the OTA & auto updated itself to the latest firmware, that is V10.3.6.0.
evanB70 said:
Glad to hear you're phone is working fine now :highfive: :highfive:
I think you somehow had your wifi / mobile data on & the phone downloaded the OTA & auto updated itself to the latest firmware, that is V10.3.6.0.
Click to expand...
Click to collapse
yes, I had mobile data on. thanks
hello,
i was trying to install havoc on mi fresh new mi a3 i got stocked in fastboot. tried everthing but it give a status as "pause" in miflash or bat command.. what to do?
error message in bat command for V10.3.4.0.PFQMIXM_20190815 as in https://drive.google.com/open?id=1oLmwpDsd8ICUPsty46osBReJdcckqvPE please hekp
Underraino said:
hello,
i was trying to install havoc on mi fresh new mi a3 i got stocked in fastboot. tried everthing but it give a status as "pause" in miflash or bat command.. what to do?
error message in bat command for V10.3.4.0.PFQMIXM_20190815 as in https://drive.google.com/open?id=1oLmwpDsd8ICUPsty46osBReJdcckqvPE please hekp
Click to expand...
Click to collapse
Set active slot to a first before flashing in MiFlash using command - "fastboot set_active a" (without quotations) in adb command.
Underraino said:
hello,
i was trying to install havoc on mi fresh new mi a3 i got stocked in fastboot. tried everthing but it give a status as "pause" in miflash or bat command.. what to do?
error message in bat command for V10.3.4.0.PFQMIXM_20190815 as in https://drive.google.com/open?id=1oLmwpDsd8ICUPsty46osBReJdcckqvPE please hekp
Click to expand...
Click to collapse
Try my Procedere,i try it Yesterday and works:
-set SLOT B and install twrp
-then boot to TWRP recovery and Flash TWRP.zip again
-reboot to twrp recovery (Check If you on SLOT B ...)
-wipe Cache,system,Data
-flash Rom HAVOC
-flash TWRP
-reboot in TWRP again,then...
Set SLOT A!
-flash Gapps
-flash FDE
-Format Data
-Reboot to to System and wait when HAVOC done
Reboot to TWRP then Flash and root Magisk 20.2 in SLOT A, Reboot...
Done!
tried flashing my mi a3 to stock now stuck in fastboot mode
I finally got miflash to recognize my phone by adding a new folder and naming it "log" and i tried flashing "laurel_sprout_global_images_V10.3.8.0.PFQMIXM_20191012.0000.00_9.0_d099f2839b" ; it said it was flashing and had green progress bar, but it went all the way to 100% after about 600 seconds and i just gave up after 1200 seconds. what am I missing?
mewcatchew said:
I finally got miflash to recognize my phone by adding a new folder and naming it "log" and i tried flashing "laurel_sprout_global_images_V10.3.8.0.PFQMIXM_20191012.0000.00_9.0_d099f2839b" ; it said it was flashing and had green progress bar, but it went all the way to 100% after about 600 seconds and i just gave up after 1200 seconds. what am I missing?
Click to expand...
Click to collapse
Just reboot your device when it finishes after 600 seconds. Miflash doesn't tell you that it successfully flashed it it just goes on forever. So just reboot and it will work.
Negative. still stuck in fastboot mode
mewcatchew said:
Negative. still stuck in fastboot mode
Click to expand...
Click to collapse
Change the active slot to 'a' and reboot.
garylawwd said:
Just reboot your device when it finishes after 600 seconds. Miflash doesn't tell you that it successfully flashed it it just goes on forever. So just reboot and it will work.
Click to expand...
Click to collapse
msatyanarayana said:
Change the active slot to 'a' and reboot.
Click to expand...
Click to collapse
it's unable as its in a locked state: 'FAILED (remote: 'Slot Change is not allowed in Lock State
I believe I need to get it into EDL mode. I have no problem taking off the back glass and shorting the pins to do so, but not sure what to do after that point... Set slot to active "a", flash it with miflash with a fastboot stock ROM? Also from what ive read, you can only put thw phone into edl mode once so it's a one shot deal.
mewcatchew said:
it's unable as its in a locked state: 'FAILED (remote: 'Slot Change is not allowed in Lock State
I believe I need to get it into EDL mode. I have no problem taking off the back glass and shorting the pins to do so, but not sure what to do after that point... Set slot to active "a", flash it with miflash with a fastboot stock ROM? Also from what ive read, you can only put thw phone into edl mode once so it's a one shot deal.
Click to expand...
Click to collapse
Try to unlock bootloader once again through fastboot and after that you can change the slot.
MarcusMario0605 said:
Set active slot to a first before flashing in MiFlash using command - "fastboot set_active a" (without quotations) in adb command.
Click to expand...
Click to collapse
this command is not working for me it is giving error of unknown command
msatyanarayana said:
Try to unlock bootloader once again through fastboot and after that you can change the slot.
Click to expand...
Click to collapse
it wont allow me to< says phone is in locked state
123123123...123 said:
this command is not working for me it is giving error of unknown command
Click to expand...
Click to collapse
C:\adb\fastboot.exe: unknown option -- set-active=a
how to solve this?
:crying:
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
MarcusMario0605 said:
Set active slot to a first before flashing in MiFlash using command - "fastboot set_active a" (without quotations) in adb command.
Click to expand...
Click to collapse
on entering this command i am getting a whole lot of command suggestion as this command not working for me. can you tell me what i am doing wrong and what should i do to make it correct.
123123123...123 said:
C:\adb\fastboot.exe: unknown option -- set-active=a
how to solve this?
:crying:
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
on entering this command i am getting a whole lot of command suggestion as this command not working for me. can you tell me what i am doing wrong and what should i do to make it correct.
Click to expand...
Click to collapse
managed to get into EDL mode by shorting the pinouts, but still cant flash stock ROM cuz apparently xiaomi has to authorize it (ie i dont have permission to unbrick it). This is the first and last xiaomi phone I'll ever buy - never had a phone where there was no option i had to unbrick it. going to ****in smash it to peices!
I felt sorry that no one did help these people,
go to fastboot and run windows commands in twrp folder and type as following :
- option one:
fastboot devices
./fastboot set_active b
./fastboot erase boot
./fastboot set_active a
./fastboot erase boot
fastboot flashing unlock (optional)
fastboot Flash boot [put twrp name].img or go to mi flash to install stock rom. or unzip the stock rom from bat file run it
or try the second option:
https://ibb.co/w6bcG5g
islam=salam=peace=paix
Hey, i was trying to install pixel experience, and when it didnt boot i tried to go back to stock with mi flash, when it was going to boot it says "The system is destroyed" Is there anyway to fix it ? i tried mi flash again and it doesnt work
ManuMan99 said:
Hey, i was trying to install pixel experience, and when it didnt boot i tried to go back to stock with mi flash, when it was going to boot it says "The system is destroyed" Is there anyway to fix it ? i tried mi flash again and it doesnt work
Click to expand...
Click to collapse
Try booting to fastboot and then enter the command "fastboot --set-active=a". For some reason they forgot to add this command in the flash scripts.
I was using Corvus OS (Android 10). After updating few apps on play store, one of them was maybe android framework related my phone stopped responding and got black screen errors. (I think a system UI crash). So i tried rebooting, got stuck on boot animation. when i went back to orangefox recovery, the phone was simply not responding to any touch even though i could see the files on my phone (orange fox homescreen). Please help ASAP. Thank You.
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Sp_3ctr_3 said:
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Click to expand...
Click to collapse
Did you format the data partition?
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
#To format system partition
fastboot format system
#To format boot partition
fastboot format boot
#To format cache partition
fastboot format cache
#To format user data partition
fastboot format userdata
#To format recovery partition
fastboot format recovery
did all of these. thanks for responding almost lost all hopes.
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Sp_3ctr_3 said:
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Click to expand...
Click to collapse
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en_IN
I think this was the app that i update and later caused the crashes.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Alright, i will try that and respond. thanks for the reply.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Did this, succesfully flashed with Bootloader intact. Still touch is not responsive, all i can see is a black screen with "This Device is Locked, for security reasons you need to enter the password to verify the device" but i cant select any option since it wont respond to touch.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Sp_3ctr_3 said:
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Click to expand...
Click to collapse
It is good that you have your device back! With regard to the bootloader, you can always go through the unlock procedure again.
PS: updating something from the Play Store should not cause a problem like this. It looks like corruption of the firmware, and/or the persist partition. Flashing a fastboot ROM via Mi Flash (the "flash all" option) should have solved the problem completely. If it didn't, then this might actually be a sign of impending hardware failure, rather than a mere corruption of partitions.
Which version of MIUI did you install?