Database Develop

HELP - Cant boot after updates

Hi, I have a MI5 with chinese ROM...
I've unlocked the bootloader, flashed TWRP rocovery and rooted it.
Problem start when i updated using the built in apps. And now i am in this MI logo screen with the 2 dots flashing... 20-30minutes.
I've tried wiping to factory reset, wipe dalvik > reboot ... no go
I've tried miflash the fastboot rom and Miflash showed "The operation completed successfully." > auto reboot ... now is 25 minutes into the boot.... still no go
I'm panicking now.... Please help

I forgot to mention, the file system is decrypted.
Now i cant go into twrp. there's a screen showing a phone with cable. I still can go fastboot though
Help please

Just to share, I'm able to get it boot again.
Instead of using "Flash All except Storage" in Miflash, I selected "Flash All".
After completion of the flashing, it took around 7-8 minutes for the first boot before system GUI came on.
I think it may be due to SuperSU that i have installed earlier.
But now i cannot boot into recovery, should i fastboot flash TWRP again or revert to stock recovery? Please help on how to do it.
Can i install SuperSU by using fastboot?

it makes more sense now.
After flashing of developer rom, the phone is encrypted again and recovery is reverted to stock which i think will only works with updater.

Help with flashing CM13 to Moto G 2014.

Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.

Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.

phoenix964 said:
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Click to expand...
Click to collapse
while @kushal_10 explained most of the things to do, i would like to remind you that CM13 has inbuilt Root. You just have to enable Developer options, then in Developer Options,under Root Access, choose Apps and ADB. Don't flash SuperSu
Hope I helped you.

kushal_10 said:
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
Click to expand...
Click to collapse
I read somewhere that wiping the system isn't advisory because in case something goes wrong, there will be no way to restore. Can you confirm this?

Rooting Problems Need Help

Hi I'm a new Android user and don't know much about it :'( I recently got my OnePlus 3T and I wanted to root it
so I followed a tutorial video from YouTube successfully unlocked bootloader and flashed twrp recovery then I tried to install SuperSU... well it installed but the device got soft bricked when I rebooted after finishing the installation and wiping cache/dalvik
then I format/factory reset everything using twrp recovery and it's working now but the device isn't rooted :'( tried to install SuperSU again and it got bricked again
Also I'm getting these messages on the startup screen-
1st one: Your device has been unlocked and can't be trusted. If you don't want to see this screen please lock your device by "fastboot oem lock" and erase user data.
2nd one: The dm-verity is not started in enforcing mode and may not work properly.
(My os version is 4.1.7)
device OP 3t A3010
plz help me :'(

The 1st and the 2nd msg that gets displayed is shown because the bootloader is unlocked..
Bootloops are common while flashing su...when I flashed super su for the first time, I got 3 or 4 random reboots and took almost 7 to 10 mins for the phone to boot up..

I would suggest using Magisk as a rooting method instead of SuperSU. If you use SuperSU then some apps can detect root and object to you being rooted and Google's SafetyNet gets triggered. Magisk solves this by trying to hide root from apps and Google so that you can use your device as if it wasnt rooted at all (but in fact is rooted). Go the the Magisk forum and download Magisk 13.3 zip from there.
I am assuming you are using OxygenOS (Oneplus's software) and not a custom ROM. Download the Open Beta or Stable build from here/
These steps will erase all the data on your phone permanently (including internal storage) so please backup anything in there.
To fix the DM verity error youll have to follow the steps outlined here
Once you have fixed that, flash oneplus recovery via fastboot which you can download here
To flash it go to fastboot mode, and cd into the folder where you downloaded it. Run the command 'fastboot flash recovery <RECOVERY_NAME>'.
Then run the command 'fastboot oem lock' to lock the bootloader. After you confirm the prompt on screen, the phone will boot into the recovery and youll see a progress bar. Once the progress completes and the screen turns off, be ready to immediately go back to fastboot mode by pressing volume up and power.
When you enter fastboot mode again, run the command 'fastboot oem unlock' and follow the same steps as before.
Once you are in fastboot mode, the phone is now in a clean state with no OS.
Follow the steps outlined on the oneplus website to flash a clean OxygenOS build (stable or open beta as per your taste)
Once the flashing is complete you have to let the phone boot up completely once. When you get to the setup screen, go through it and reach the launcher.
Now we flash TWRP recovery. Reboot to fastboot again. Flash TWRP recovery (I personally use blu_spark's twrp but you can use one of your choice). When it is done, boot into the recovery. Youll now be able to copy magisk zip into the internal sd. Do that, and flash it. Reboot.
Youll now be rooted. If you have any problems holla at me.

Stuck in fastboot

Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)

Slymi4n said:
Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)
Click to expand...
Click to collapse
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account

zgfg said:
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account
Click to expand...
Click to collapse
YES!! IT WORKED!!! Thank you so much

NV data is corrupted

Hello, I am using a Redmi 9 Global (64/4) lancelot device. Since yesterday I have been using the Pixel Experince Android 13 Vendor S ROM, anyway yesterday i was testing something on TWRP recovery and performed the following actions (to the best of my recollection):
I mounted almost all partitions, then, I went to Advanced > Addons and experimented with options like 'Enforce decrypt' (I'm not sure about the exact name), 'Primissive,' and another option that failed immediately upon running but it has almost same name.
Afterward, I wiped Dalvik/Art cache, system, data, internal storage and caches. I flashed the same ROM (Pixel Experience) again, but upon reboot, the device went back into recovery mode, regardless of how many times I rebooted.
Anyway, I tried that 'Enforce' option (i didn’t remember its exact name), and it allowed the system to boot. However, both Wi-Fi and hotspot functionality were not working but the SIM cards are functional, providing data, call services, and other features. However, I did not check if the IMEI 1 and 2 were still there or not.
In an attempt to resolve the issue, I flashed the official fastboot ROM using Mi Flash Tool. However, the device entered official recovery mode and displayed the error message 'NV data is corrupted'. I attempted to resolve the problem by flashing the official fastboot ROM using SP Flash Tool, i tried it 3 times using different optios such as 'download only' 'firmware upgrade' and 'format all + download' Unfortunately, the problem persisted.
Then I tried to reinstall TWRP and use a custom rom without WIFI to be able to use my phone until i can find a way to fix it but my bootloader was locked, and when I attempted to unlock it using the Mi Unlock Tool, I received a message stating that my phone did not have the permission. This was wierd because during my previous use of SP Flash Tool(few months ago), I was able to unlock the bootloader.
Currently, I have installed an engineering ROM. Here's the situation: Wi-Fi and both SIM cards are working fine, but I cannot see any IMEI numbers in the settings or using the *#06# code for any of the slots. I'm unsure if this is due to the engineering ROM or if the IMEI numbers were wiped.
Fortunately, I still have the box and that lable which IMEI is written on it. I am now seeking a solution to fix this issue. I know there is a tool that can help write my IMEI for slot 2, but I'm unsure if it will resolve the problem. I have seen some Youtube videos where people fixed this problem using Unlock tool, but I don't have it, and the cracked versions are all fake and viruses.
Anyway , I wonder if there is any way to install Gapps on my engineering ROM. I know it's not ideal, but I could use it for a while. If its possible to install Gapps on Engineering ROM using custom recovery then which recovery should i use? I mean my Eng ROM android is 10 so should i use a custom recovery that designed for Vendor Q and then how to install it while my bootloader is locked ? Or is there anyway to install Gapps using adb sideload?
I attached some screenshots below
Thanks for any help