So while i was trying to flash my k5 with twrp i accidently broke my recovery mode and didnt able to turn it back and after that i tried to flash my phone with adb but a message saying "failed:need unlock blabla" and then i opened my oem but it didnt work too (Debug already opened) so i was desperetaly searching for a solution then i saw a option in twrp app saying like allow flashing to boot partition so i checked it and flashed it after that i tried to restart my phone but it started to close and open again and again. The only thing i could do was going in bootloader but even adb cant do anything in there(i still dont know why). In the end i only have a phone that restarts again and again cant even open and i need help. If hope there is a way to fix or format or reflash
Related
Hello guys,
I tried to update my phone to marshmellow, it got stuck at 95% and after it it entered a bootloop, I thought on just installing a custom recovery and take it from there but when I use fastboot it gives me a Remote: command not allowed error, I have my bootloader unlocked, I am thinking this has to do with not having USB debugging enabled, I can´t access the phone to activate it though. I have also tried to flash lots of stock roms through sd putting them on dload folder on Sds root but it fails right away at 5% it says update install failed, at this point Im not sure what to do... Any ideas?
thanks
Hello guys,
i wanted to upgrade my Ressurection Remix ROM and managed to softbrick my phone. While flashing the software (Flashing system partition unconditionally) TWRP got stuck.
My phone got an unlocked bootloader and i already tried to flash the global MIUI ROM via EDL and also fastboot. The flashing process is successfull but after i restart my phone i'm stuck at the MI Logo with the moving Android Circles for loading.
I let this run for ~6 hours, no progress at all.
I also tried flashing the Global DEV Rom, same as above.
Factory Reset via Recovery Mode (with MI Suite) also didn't do the trick.
I think something with the bootloader went wrong. Any ideas to unbrick it?
I can access Fastboot and EDL Mode, unlocked Bootloader. I also got a TWRP backup with System and Data Partition, but currently only the original Revocery is installed.
Any help is very much appreciated, thank you.
Did you tried using this guide to flash stock firmware/recovery?
http://en.miui.com/a-234.html
Yes, the problem is not to flash the Fastboot ROM, but after successfully flashing the ROM i got stuck at the MI Logo with the loading Android dots
That's weird.. this bootloop usually happens when you flash stock MIUI and still have TWRP installed, can you check if you have stock recovery after fastboot flash?
After i flashed the global DEV ROM i got the stock recovery where i can choose between Wiping Data, switch to MI Suite etc.
Edit: Its not really an bootloop, it just gets stuck there without doing anything
Update: Got TWRP back, now if i want to flash any ROM (doesn't matter if stock/custom) i'm stuck at TWRP saying: "Patching system unconditionally..." it stays there for hours.
Any advice in this case?
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
tandob said:
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
Click to expand...
Click to collapse
That has absolutely nothing to do with the problem mentioned above.
So, I have quite a problem, and having a country-native device isn't really helping.
I have a Cherry Mobile J2s in 6.0 with bootloader access allowed.
I seemed to have failed in rooting my phone by doing 'fastboot recovery twrp-3.2.1-0-cherry.img' it seemed to have been added properly but it said something like 'recovery' partition successfully made. I'm not sure if that's something wrong but I placed it in just in case. Because of this, my phone showed the Encryption Unsuccessful.
Here's the bad part. It doesn't seem to be able to reset itself. It just stays on the opening screen that says Flare J2s. It doesn't seem to open up the reset screen which I see from other tutorials. I believe it's because I failed to install the recovery img correctly, most especially since I had nothing like a boot img to use. I have tried opening recovery mode but to no avail. I seem to not have a way with connecting my phone to my pc so I can't use adb to fix itself.
Does anyone know how to fix this problem? Thanks in advance. ^^
Pink Panther Bumps
Bu-bump. Bu-bump.
Bu-buh, bu-buh, bu-buh, bu-buh-
Bu-buuuuuump. Bu-bu-bu-bump.
thatguy396 said:
So, I have quite a problem, and having a country-native device isn't really helping.
I have a Cherry Mobile J2s in 6.0 with bootloader access allowed.
I seemed to have failed in rooting my phone by doing 'fastboot recovery twrp-3.2.1-0-cherry.img' it seemed to have been added properly but it said something like 'recovery' partition successfully made. I'm not sure if that's something wrong but I placed it in just in case. Because of this, my phone showed the Encryption Unsuccessful.
Here's the bad part. It doesn't seem to be able to reset itself. It just stays on the opening screen that says Flare J2s. It doesn't seem to open up the reset screen which I see from other tutorials. I believe it's because I failed to install the recovery img correctly, most especially since I had nothing like a boot img to use. I have tried opening recovery mode but to no avail. I seem to not have a way with connecting my phone to my pc so I can't use adb to fix itself.
Does anyone know how to fix this problem? Thanks in advance. ^^
Click to expand...
Click to collapse
The proper command should have been fastboot flash recovery twrp-3.2.1-0-cherry.img . I am not to familiar with the device you are using, but can you put it in download mode? If that's an option, try to reflash the same firmware you are using to recover your phone.
Bump
Bump.
I think first you need to unlock bootloader before flashing that custom recovery .
Similar problem and Fix you can find here:
https://forum.xda-developers.com/showthread.php?t=2453849
Good Luck .
i managed to delete twrp and when i did then it shows that the system has been destroyed and after restart it is stuck on
fastboot windows. i tried to connect it with my pc so i could install flash rom but it doesnt show up on pc after connecting to usb.
i dont understand what to do next... helppppppppppppppppppppppppp
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
twistyplain said:
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
Click to expand...
Click to collapse
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
AjTheKiller1 said:
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
Click to expand...
Click to collapse
Have you ever had your phone detected by your pc in fastboot mode? And if you connect it to the pc, does the computer play the hardware detected sound?
You need to rule out a driver issue. I'm not the only other person to get the "system has been destroyed" message and people usually get out of it. I don't know why yours is so problematic.
Had you successfully unlocked bootloader?
The Good old "System has been destroyed" Message. Well, This is terrible This should not happen in the first place. I assume it happened Because you wiped data and then deleted twrp. But If you want help you have to specify how exactly did you " Delete TWRP" What steps did you follow to Delete it. None the less the best bet on getting your device back would be to go to the nearest service center. Pretend you did nothing and maybe they will say you got a bad update.
So I tried installing custom rom lineage os 19.1 . Everything was going flawlessly like from unlocking to installing GApps . Then when I tried to reboot system i was stuck at at lineage logo booting . I stays stuck for like 5 minutes then again reboots. I tried the whole process again and again and again (wiping the cache,system etc. to installing GApps) and all the 3 times it installs without any error but at the time i try to reboot system its the same old story. It gets stuck for 5mins and then again reboot and again gets stuck for 5min and again the same thing. So I thought about flashing through mi flash tool and idiot me pulled of the usb cable at the middle of flashing thinking it ended (Wasnt showing success in result) so it booted but right after setting up pops out, the phone again reboots . So I again went on trying to flash the device through mi flash tool and now it shows "Error writing in partition ; Critical Partition Flashing is not allowed" . Then I tried to unlock via cmd as i cant access to mi unlock (I had to login via QR code when i was unlocking and i had to the same so i couldnt), so as i try to unlock via cmd it says "token verify failed" . I cant even go to EDL mode . I dont mind on losing data I just want to keep it alive somehow. Any helps would be appreciated TIA !
I also tried different flash tool (older ones) but it didnt work
Roudero said:
So I tried installing custom rom lineage os 19.1 . Everything was going flawlessly like from unlocking to installing GApps . Then when I tried to reboot system i was stuck at at lineage logo booting . I stays stuck for like 5 minutes then again reboots. I tried the whole process again and again and again (wiping the cache,system etc. to installing GApps) and all the 3 times it installs without any error but at the time i try to reboot system its the same old story. It gets stuck for 5mins and then again reboot and again gets stuck for 5min and again the same thing. So I thought about flashing through mi flash tool and idiot me pulled of the usb cable at the middle of flashing thinking it ended (Wasnt showing success in result) so it booted but right after setting up pops out, the phone again reboots . So I again went on trying to flash the device through mi flash tool and now it shows "Error writing in partition ; Critical Partition Flashing is not allowed" . Then I tried to unlock via cmd as i cant access to mi unlock (I had to login via QR code when i was unlocking and i had to the same so i couldnt), so as i try to unlock via cmd it says "token verify failed" . I cant even go to EDL mode . I dont mind on losing data I just want to keep it alive somehow. Any helps would be appreciated TIA !
I also tried different flash tool (older ones) but it didnt work
Click to expand...
Click to collapse
Yeah, same story for me. Looking for an answer too
I was facing same problem. so i gave it to local phone repair shop. they solved it perfectly.
angshuman_sarkar said:
I was facing same problem. so i gave it to local phone repair shop. they solved it perfectly.
Click to expand...
Click to collapse
can you tell us what local repair shop done with phone? i also gave to local repair shop they said it cant be repaired!
Roudero said:
So I tried installing custom rom lineage os 19.1 . Everything was going flawlessly like from unlocking to installing GApps . Then when I tried to reboot system i was stuck at at lineage logo booting . I stays stuck for like 5 minutes then again reboots. I tried the whole process again and again and again (wiping the cache,system etc. to installing GApps) and all the 3 times it installs without any error but at the time i try to reboot system its the same old story. It gets stuck for 5mins and then again reboot and again gets stuck for 5min and again the same thing. So I thought about flashing through mi flash tool and idiot me pulled of the usb cable at the middle of flashing thinking it ended (Wasnt showing success in result) so it booted but right after setting up pops out, the phone again reboots . So I again went on trying to flash the device through mi flash tool and now it shows "Error writing in partition ; Critical Partition Flashing is not allowed" . Then I tried to unlock via cmd as i cant access to mi unlock (I had to login via QR code when i was unlocking and i had to the same so i couldnt), so as i try to unlock via cmd it says "token verify failed" . I cant even go to EDL mode . I dont mind on losing data I just want to keep it alive somehow. Any helps would be appreciated TIA !
I also tried different flash tool (older ones) but it didnt work
Click to expand...
Click to collapse
same thing hapannig with me . is it your issue fixed if tell me how ?