I tried to flash Pixel Experience, activate USB debugging and OEM unlocking, start TWRP, clean System, Data and Dalvik, flashed the ROM and restart, but when I started it asked for a password for encryption, I placed it but mentioned that the files were damaged and it went into reboot, and so on. So I went to the CMD terminal to flash the stock ROM, but I was not allowed to flash the boot.img, so I rebooted from CMD to the bootloader with "fastboot reboot-bootloader" and it was turned off to not turn on. I already managed to revive it using the Test Point method, but at the moment of starting it now it enters Bootloop, it is on for 30 seconds and it turns off again ... Is there anything I can do to remove the bootloop?
Related
hey anything please i wiped everything and installed zip"rom" from sd and installed secussful and then i clicked reboot and it just stays on the motorola screen with unlocked in the corner and is stuck there what am i not doing or doing wrong its rooted and unlocked
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
clod007 said:
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
Click to expand...
Click to collapse
i made a back up with titanium and android recovery....
i pulled the battery installed it 2 or 3 times and same thing
what exactly do i type in my cmd prompt on fastboot
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
clod007 said:
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
Click to expand...
Click to collapse
i dont know how to reinstall it but i made back ups of everything
Enter in Android recovery mod
Backup
Chose restore
Atrix - "CM7"
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
android-DEP said:
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
Click to expand...
Click to collapse
ok it rebooted and went off the screen now its in a boot loop and flashes the motorola sign then shuts down and keeps going
ok, so the issue was partly the cache not being wiped prior the rom being installed and something went wrong with the installation of the kernel. That happens if the boot.img didnt properly extract and write to partition or its just incompatible with the rom\device.
Visit faux123's thread with kernels for ATT froyo, GB, CM7 & CM9
download the kernel that's compatible for your rom(froyo, gb, cm7 or cm9). Once you download the zip, go in there and pull out the "boot.img" file and put it into the same folder you have fastboot.exe in and boot into fastboot again.
quickly check connectivity with "fastboot devices" to verify and if that checks out, use this command.
"fastboot flash boot boot.img"
it takes like 3 seconds or something to complete so its an easy fix, after its done just do the "fastboot reboot" command.
i had this same exact issue last week plus my recovery was being erased along with this problem so i keep boot.img & recovery.img just sitting inside the fastboot folder just in case
atrix reboot project - it has every single file thats for the atrix and copies of systems, roms, tools, recovery files, mods, tweaks
Try this:
Pull battery
Replace battery while holding volume down until you see fastboot
Tap volume down to until you see android recovery, then press volume up to enter recovery
First try wiping cache/dalvik, if that doesn't work restore nandroid backup, if that doesn't work reflash rom
I rooted my oneplus 2 some time ago to install the Screencast.app that there was on the oneplus one. I then after a while noticed that it started to perform worse than before i rooted it, so i decided to try to unroot it to fix the performance. But when i rebooted to fastboot and tried to flash the stock recovery, it said that the bootloader was locked. I then tried doing the unlock command (fastboot oem unlock), and it seemed to work (although - it didnt - in cmd it said finish but when i booted into bootloader again it was still locked) but when my phone tried to reboot, there was i quick flash of the oneplus logo and then the screen went blank. When i tried turning it off, i just rebooted and did the same thing. I could not boot into recovery either. The only thing i could do was booting into fastboot and from there i managed to use the command fastboot continue and restart my phone properly. So now i cant use my recovery to factory reset, i cant install a new recovery because the bootloader is locked, and now every time my phones powers off, i have to do the same thing with booting into fastboot and do the fastboot continue command to start it.
Can anyone tell me what the issues is here and how i can solve it?
I have the same problem, but once I got the phone to boot, I did a factory reset. Now I'm unable to even boot, literally the only thing that works is fastboot.
Hi guys, I tried flashing stock rom and re-locking the bootloader so that I could have the phone completely stock. However, after re-locking the bootloader, I seem to have bricked the phone. I've scoured the forum for fixes, tried tenfar's tool, and nothing has worked yet. Hopefully someone has come across this situation before and can advise me on how to get my phone working again.
So how I got to this point.
-Originally the phone was on stock rom, rooted, with official TWRP recovery.
-Booted into TWRP, wiped cache, dalvik, data.
-Flashed ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip.
-Flashed ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip.
-Rebooted phone, went through initial setup, then turned on Allow OEM Unlocking in Dev Options.
-Rebooted back into TWRP, used Minimal ADB to fastboot oem lock.
So the phone rebooted twice from there, and seemed like it was going to boot properly, but the first screen that appeared was a lock screen asking for the password. I didn't set any passwords, and couldn't find any default factory passwords even looking through the zteusa forums on posts for similar situations. Then I tried rebooting into the bootloader to factory reset the phone, but trying to boot into the bootloader only leads to a black screen after the ZTE boot logo. That's where I'm currently stuck. No matter what I try, be it tenfar's tool, I can't get into anything but the black screen or the password-locked screen.
Using tenfar's tool, after I issue the axon7root.exe -p 3 command, it shows the next two lines, up to Version 1.10, then does nothing else. I'm not sure if this is because I flashed B29, and the tool only goes up to B27.
Any advice would be greatly appreciated!
Tennear's tool for flashing a boot and recovery image seems the most promising I think, but I don't quite understand how to use it.
-Rebooted back into TWRP, used Minimal ADB to fastboot oem lock.
Click to expand...
Click to collapse
First, you shouldn't (can't?) relock the bootloader while you're using a custom recovery. Additionally, I don't think you can issue fastboot commands to recovery.
Boot into TWRP and do a factory reset from there.
If not, flash the ZTE B29 image either via stock recovery (flashed via TWRP/tenfar's tool), or edit the install script to make it flashable via TWRP.
Hello, the problem started today after going from pixel experience to the stock room, I went to miflash and flashed the last update, after doing that the phone started to restart itself and in the Mi Flash program it marked the command "fastboot reboot" so I decided to enter in the fastboot mode and the phone restarted, the problem persists, it keeps restarting without being able to enter the system, I made a wipe from the original recovery, since I can not enter twrp since in minimal adb fastboot it says me that the phone is not found with the oem enabled, and if I try to put the command "fastboot oem unlock" it tells me that the oem is not enabled the same, I would appreciate your help, thanks.
AgustinPatatas said:
Hello, the problem started today after going from pixel experience to the stock room, I went to miflash and flashed the last update, after doing that the phone started to restart itself and in the Mi Flash program it marked the command "fastboot reboot" so I decided to enter in the fastboot mode and the phone restarted, the problem persists, it keeps restarting without being able to enter the system, I made a wipe from the original recovery, since I can not enter twrp since in minimal adb fastboot it says me that the phone is not found with the oem enabled, and if I try to put the command "fastboot oem unlock" it tells me that the oem is not enabled the same, I would appreciate your help, thanks.
Click to expand...
Click to collapse
You should've let the mi flash do it's thing. Don't touch the phone, but since the damage has already been done, you have to flash rom via edl mode.
WhatzIt2Ya said:
You should've let the mi flash do it's thing. Don't touch the phone, but since the damage has already been done, you have to flash rom via edl mode.
Click to expand...
Click to collapse
Thanks, I have managed to get into the system, however at the time I receive an update of the December patch I update it and at the end of the update and give it to restart so that it is installed it stays in a restart loop, it reaches the screen android one and it reboots, any solution?
P.S: In the ROM that worked for me, it was the "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" however does not recognize the sim
AgustinPatatas said:
Thanks, I have managed to get into the system, however at the time I receive an update of the December patch I update it and at the end of the update and give it to restart so that it is installed it stays in a restart loop, it reaches the screen android one and it reboots, any solution?
P.S: In the ROM that worked for me, it was the "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" however does not recognize the sim
Click to expand...
Click to collapse
When I updated it. I uninstalled magisk, relock the bootloader, and reboot the phone a couple of times (to chack for corruption and stuff). Then I installed the update. Try flash pie rom with mi flash tool.
Hi guys,
I'm really desperate for a solution. I was on OOS 11.1.1. and installed an OTA update the usual way like I did 5-6 times before, including the update to OOS 11 which was the last update I did.
Magisk -> Restore Images
Install OTA and don't reboot
Magisk -> Install to inactive slot (after OTA)
but after rebooting, the phone keeps going into this semi recovery screen, where I cant to anything but to
a. reboot to recovery which brings me back to this screen
b. reboot to fastboot which is working
c. wipe cache, dalvik, user data where i already tried the first 2 with no success.
Now here is where it gets tricky: I don't have USB Debugging enabled for some reason. This means my phone doesn't appear on any recovery tools (like msm) and also adb and fastboot commands don't find it (it keeps waiting for any device), no matter if I'm in this semi recovery screen or in fastboot mode. My device was previously rooted and of course bootloader is unlocked.
ADB and drivers are installed.
Anyone got an idea what I could try here?
There is no need of "usb debugging" for msm tool to work. Msm tool work in EDL mode.
Make sure you have propper adb drivers installed for fastboot to work.
Morever for msm tool Just turn off your phone and then connect it to your PC while holding both Volume keys. By doing so the OnePlus 6T will enter EDL mode