Develop Bugs

Can't find anything like it anywhere else (bootloop)

So I made a post in the general help thread and nobody has replied (although I've only waited a few days so I could probably wait a bit longer) but still I feel like my phone's issues are "unique" compared to other bootloops, I can't find anyone else having the same symptoms on their phone. I'll repost what I said in the general help thread and then give a brief overview of everything because I simply cannot comprehend why I'm unable to get out of bootloop with this damn phone.
So I just recently picked up an old Zenfone 2 (ZE500CL) off of my father who didn't really need it anymore and it was an upgrade from my old ****ty phone, so of course I wanted to root it and after using it for a few hours I wanted to install a custom rom by unlocking the bootloader. Well, I tried that, and something must have gone wrong because I got a bootloop and was only really able to boot into recovery mode.
Now, I didn't backup because I'm dumb for one and two I generally have a good idea of where to start if something does go wrong. The thing is, the methods I've looked up and tried have all failed. First, reflashing the stock rom of my ZE500CL (I've tried four different firmwares from the official website, and I know it's ZE500CL because that's what recovery mode is telling me) does not work. Adb hits 47% in the command prompt, the phone stays at 25% until then, and it goes:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Not sure why it doesn't work, I looked it up and tried various things and it just isn't resolving itself.
So I tried simply running commands like the following:
fastboot flash recovery recovery.img
Using files from the stock firmwares themselves, and that gives me a flash_cmds error. I've tried deleting all of the userdata, the system, the cache, and a factory reset through recovery mode but none of that works. I'd really appreciate any help anyone could offer, this is a pickle and I'd really like to get this phone back up so that I can just run it as a rooted phone.
Click to expand...
Click to collapse
Now, I'll go over the issues quickly:
I'm stuck in bootloop but I can get into recovery mode
Trying to flash any rom, including multiple stock roms from the asus website, results in an installation aborted message at 47% in either ADB or microSD attempt at flashing the rom.
Attempting to run commands like fastboot flash recovery recovery.img ends up giving me a flash_cmds error which I cannot find anywhere else for the Zenfone 2e
Deleting the cache, userdata, system, or factory resetting the phone does not remove the bootloop
Unlocking and relocking the bootloader does nothing
I would really appreciate any help, feels like my phone is a lost cause even when it's not hard bricked.

Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...

ponnuvelpandian said:
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
Click to expand...
Click to collapse
Thanks, I haven't seen this. I've got the Intel and xFSTK drivers all up and running but my phone isn't being recognized constantly by my computer under Intel Soc in my Driver Manager, and it's not being recognized as MOOREFIELD but rather as CLOVERVIEW PLUS, and only for a second in-between boots on my phone. Can't get the files to be downloaded through xFSTK, so I've hit a snag here unless someone knows the solution to this.
I'll try just running the flash tool and using a raw firmware, then, since I can't do any of the other stuff.
EDIT: Looks like the issue I was having before is stopping me from running the tool, seems that the computer needs to recognize my phone through the Intel drivers at all time (which it doesn't) in order to run the tool. Also I can't get the tool to view the raw file, it only seems to read zip files (so I put the raw into an empty zip, thinking that could maybe work but I don't know for sure). Damnit, I don't know why this is so difficult.
EDIT 2: All right! Looks like I got it working. The process was relatively simple, actually. It involved booting into TWRP but I wasn't able to most of the time for some reason, it would just never do it. But, I was able to using the CWM Zenfone 2 bat file located here: http://forum.xda-developers.com/zenfone2/help/ze500cl-rooting-related-stuff-t3163528/
Then, I needed the stock rom for my ZE550CL placed onto an external sd card which can be found here: http://forum.xda-developers.com/zenfone2/help/ze550cl-factory-reset-return-to-stock-t3141513
So I would download the CWM Zenfone 2, replace the recovery file as the post states, then run the file. After that, I would run T4 since T1 and T2 didn't work (never tried T3), only T4 would seem to boot me into TWRP. From there, I went to Install, left Zip Verification unchecked, and let the damn thing run. It was the only thing that would run for me, even when doing it with ADB it wouldn't work with the stock rom. Then, I just rebooted and now I'm back on my phone. Hopefully this helps anyone else having this troubling issue, it was terrible!

5x Hard Bricked??

I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.

I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul

pgoelz said:
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
Click to expand...
Click to collapse
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!

ItsMason said:
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
Click to expand...
Click to collapse
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.

exige34 said:
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
Click to expand...
Click to collapse
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.

ItsMason said:
I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
Click to expand...
Click to collapse
Do you use 3.02.1. Twrp

Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Code:
adb push "/path/to/rom.zip" /data/media

ItsMason said:
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
Click to expand...
Click to collapse
Good. I see you mention flashing system, boot, recovery, cache(?), data(?) and radio. What do you mean by flash cache&data? You mean you've cleaned it? Formatting data is not usually a thing you have to do to recover from a bootloop.
What ROM have you flashed? Are you flashing stock? It's important you give more details so I can help you.
Have you flashed vendor.img? If you have been on a ROM that had it's own vendor.img and you went back to stock, then the vendor.imgs are different enough to cause a bootloop.
If all and all fails, we just want to see your system running so I'd recommend drop everything you are doing and follow these steps:
1. Access recovery (make sure you're using v 3.0.2.2)
2. Tap Wipe - > Advanced Wipe - > And check:
Dalvik / ART Cache
System
Internal Storage
Cache
3. Go to -> Pixel ROM (7.1.1) Get V 3.0 which was just uploaded recently. Please note it comes preconfigured with Gapps so no need to get that
4. You have to unzip the archive and you will see all the necessary img files (includes boot/vendor which are critical for boot). I strongly recommend manually flashing them. You can open the flash-all.bat file with a .txt editor and just follow the steps there.
After you have finished these steps, you should be free of a bootloop. From there, it is your decision where you. Either stay on a stock ROM or flash safely and always remember that you can make a backup and flash that backup in case you bootloop.
Good luck.
EDIT
Decay3 said:
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Click to expand...
Click to collapse
I think his problem is deeper than a /system error. I'm guessing the wrong boot/vendor is flashed for the ROM he is trying to install and trying to guess which ROM would work on his current config would take more time than just starting from a clean flash.

Thanks for the help guys, but I gave up. I contacted Google and they sent me a replacement. Sorry for kind of wasting time.

I think I bricked my ZE551ML_Z00A

Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.

Yuno17 said:
Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Click to expand...
Click to collapse
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?

Yuno17 said:
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Click to expand...
Click to collapse
very first of all uninstall everything especially i soc drivers and xFSTK. then disable driver signature enforcement. and go to thread above posted and do step by step.
how to disable signature enforcement and install driver on win 10 see in thread above

My Honor 7x BND-L21 is quite broken, need help

Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors

Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.

sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks

Quite an experience. All the best. ?

Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?

Note 8 pro bricked

Today i installed LR recovery and rooted my phone then i installed Viper 4 android... everything went well.. at last i uninstalled xiamo sim activation apk because it bothered me every time i reboot my phone... but after uninstalling that my phone is no longer booting up.. it boots to fastboot mode only.. I can manually boot to twrp but my files are also corrupted...
anyway to recover my data? MIUI 11 indonesian rom

You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.

wang1chung said:
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
Click to expand...
Click to collapse
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks

n70shan said:
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.

antony.ps said:
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
Click to expand...
Click to collapse
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.7 and it opens now, will see what it does

n70shan said:
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.4 , and the problem is it opens and closes immediately.. what should i do now?
Click to expand...
Click to collapse
I'm using Linux right now, and it only runs on Java 11, maybe it's java version problem? Try to use Oracle Java 11 if Redhat or other OpenJDK distribution doesn't work.

n70shan said:
.......
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.

wang1chung said:
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
Click to expand...
Click to collapse
Oh my bad i forget that.. been out of Android from months..
Anyways issues are resolved now with data lost ?
Thanks
Moderators can close the thread