[Q] Moto e stuck in bootloop(?) - Moto E Q&A, Help & Troubleshooting

Guys I am a noob so be as detailed as possible
I have moto e xt1022, on lollipop 5.0.2, and my phone will just not work.
Here is what i did :
unlocked bootloader
flashed cwm recovery
installed superSU zip
changed boot logo
The phone was working fine up till this point.
Then i flashed twrp.
now the phone vibrates at first, shows the motorola animation, reaches the blue logo point and then is stuck at that point
i cant reach the bootloader. i switch off the phone, and if i attempt to go into the bootloader , it starts normal boot and again gets stuck.
Is my phone bricked?
What do i do?
Can i clear cache or do a reset without going to bootloader?

Random_Tag said:
Guys I am a noob so be as detailed as possible
I have moto e xt1022, on lollipop 5.0.2, and my phone will just not work.
Here is what i did :
unlocked bootloader
flashed cwm recovery
installed superSU zip
changed boot logo
The phone was working fine up till this point.
Then i flashed twrp.
now the phone vibrates at first, shows the motorola animation, reaches the blue logo point and then is stuck at that point
i cant reach the bootloader. i switch off the phone, and if i attempt to go into the bootloader , it starts normal boot and again gets stuck.
Is my phone bricked?
What do i do?
Can i clear cache or do a reset without going to bootloader?
Click to expand...
Click to collapse
The way you enter to the Bootloader (which is a different thing from Recovery) on Lollipop is pressing power + volume down for at least 10 seconds. Try that.
If you succeed, then use mfastboot to flash stock again.
If you need more instructions, let me know.

No idea what to do.
SirRhor said:
The way you enter to the Bootloader (which is a different thing from Recovery) on Lollipop is pressing power + volume down for at least 10 seconds. Try that.
If you succeed, then use mfastboot to flash stock again.
If you need more instructions, let me know.
Click to expand...
Click to collapse
Well I figured out how to get into fastboot, just pressing volume down does the trick.
One point I missed was i accidentally wiped everything in the phone.
In twrp, in the wipe section, instead of just data reset or cache, I removed everything. now it shows no os installed whenever i try to reboot via twrp. What do I do?
Also I cant find any link to my version of android as a whole, only updates to existing os.
Here's my os info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar ro.build.version.full
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.36.condor_reta
(bootloader) ro.build.version.full[1]: ildsds.retaildsdsall.en.03
ro.build.version.full: Done
I wanted to install MIUI instead of stock lollipop. Can that be done directly?
Sorry for the huge post, but Im freaking out here.

Random_Tag said:
Well I figured out how to get into fastboot, just pressing volume down does the trick.
One point I missed was i accidentally wiped everything in the phone.
In twrp, in the wipe section, instead of just data reset or cache, I removed everything. now it shows no os installed whenever i try to reboot via twrp. What do I do?
Also I cant find any link to my version of android as a whole, only updates to existing os.
Here's my os info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar ro.build.version.full
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.36.condor_reta
(bootloader) ro.build.version.full[1]: ildsds.retaildsdsall.en.03
ro.build.version.full: Done
I wanted to install MIUI instead of stock lollipop. Can that be done directly?
Sorry for the huge post, but Im freaking out here.
Click to expand...
Click to collapse
I am assuming you can enter to TWRP normally, if so, go to the following thread, read the whole first post and try that:
http://forum.xda-developers.com/moto-e/development/flashable-zip-stock-deodexed-rom-moto-e-t2823368

THANK YOU!!!
It worked. Thank you so much.

Related

Cannot boot into Recovery

I upgraded my OnePlus X today with the community build OxygenOS 3.1.0 using TWRP. There was an error saying that my device was not "OnePlus" but "ONE". So I edited the updater-script and replaced the word "OnePlus" by "ONE" in getprop line and successfully installed the ROM.
Then I connected my phone to PC, enabled OEM unlock and USB debugging, booted into fastboot and typed -
Code:
fastboot oem unlock
It said Okay, done...but there was not action on the phone screen. It stayed in Fastboot mode. I rebooted the phone and it was the same as before. I thought it was okay and continued with the process by booting into fastboot again and flashing TWRP with the command -
Code:
fastboot flash recovery twrp-3.0.2-0-onyx.img
It was successful. Then something weird happened when I typed -
Code:
fastboot boot twrp-3.0.2-0-onyx.img
The output was downloading image, okay. Then booting and the error FAILED(remote: dtb not found).
I tried manually entering the recovery mode, first by volume down + power button and then by advanced reboot menu -> recovery. All that happens is that it stays stuck in Oneplus Logo screen with powered by android written at bottom. I am able to boot into the OS.
I am sure that the image file is not corrupted as I have used the same before a couple of times. Still I tried flashing Stock recovery and a few other image files of the same version of TWRP. The same error comes up every time. Flashing is successful but booting is not. What should I do?
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is my recovery or bootloader corrupt?
I tried this code -
Code:
fastboot oem device-info
Output was -
...
(bootloader) Device tampered : false
(bootloader) Device unlocked : true
(bootloader) Charger screen enabled : false
(bootloader) Display panel :
(bootloader) console_enabled : 0
(bootloader) exec_console_unconsole : 0
OKAY [0.017s]
finished. total time : 0.018s
The problem is when I type -
Code:
fastboot oem unlock
Nothing pops up on my phone.
Maybe the reason is that I had a rooted version of OxygenOS 2.2.2 with TWRP but when I flashed the community build of OxygenOS 3.1.0 somehow TWRP was missing...
What should I do now? I am back at 2.2.2 now as the beta build didn't suit me. This error still persists. The first link above was stock recovery which did work. But I need TWRP back...
....................
Sorry to bother. Issue solved. It was already unlocked and this time flashing and booting in the image worked idk why...
arunmohan16 said:
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Thank you dude, i have been looking for this all day
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
tirlibibi said:
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
Click to expand...
Click to collapse
This guide will help you. http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 Use this mini tool, http://forum.xda-developers.com/showpost.php?p=64344611&postcount=4

CanĀ“t enter TWRP recovery on LG G5

Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
trash195 said:
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
Click to expand...
Click to collapse
Start your phone in fastboot mode, flash TWRP, disconnect and reconnect the battery.
Now hold volume down + power until you see the LG logo, keep holding volume down and let go of the power button for a moment and then hold the power button again while still holding the volume down button.
You will now see a prompt asking if you'd like to factory reset, press yes to both prompts.
You will now be inside TWRP.
Which variant you are using.
mass/cls/ said:
Start your phone in fastboot mode, flash TWRP, disconnect and reconnect the battery.
Now hold volume down + power until you see the LG logo, keep holding volume down and let go of the power button for a moment and then hold the power button again while still holding the volume down button.
You will now see a prompt asking if you'd like to factory reset, press yes to both prompts.
You will now be inside TWRP.
Click to expand...
Click to collapse
I've tried this process myself and I get the same result. Reply Yes, Yes to factory reset and it *should* then start TWRP but it doesn't. You end up with a wiped phone and have to start all over again. Tried process a few times and never works.
lywyn said:
I've tried this process myself and I get the same result. Reply Yes, Yes to factory reset and it *should* then start TWRP but it doesn't. You end up with a wiped phone and have to start all over again. Tried process a few times and never works.
Click to expand...
Click to collapse
The only reason it wouldn't work is if you did not flash TWRP correctly, make sure flashing TWRP with fastboot was successful before disconnecting the battery and entering the factory reset prompt.
mass/cls/ said:
The only reason it wouldn't work is if you did not flash TWRP correctly, make sure flashing TWRP with fastboot was successful before disconnecting the battery and entering the factory reset prompt.
Click to expand...
Click to collapse
It is successful, and I pull the battery and go straight into recovery as recommended. Used latest version.
lywyn said:
It is successful, and I pull the battery and go straight into recovery as recommended. Used latest version.
Click to expand...
Click to collapse
This is not something I've ever had a problem with, every time I've wiped my phone and installed a new version this has worked.
Flash the latest version of android with LGUP and try again.
mass/cls/ said:
This is not something I've ever had a problem with, every time I've wiped my phone and installed a new version this has worked.
Flash the latest version of android with LGUP and try again.
Click to expand...
Click to collapse
On V20a-234-30. I have flashed TWRP successfully in the past. Might try LGUP to V20D and then try, but if it factory resets I waste hours while phone goes through setup to try again
lywyn said:
On V20a-234-30. I have flashed TWRP successfully in the past. Might try LGUP to V20D and then try, but if it factory resets I waste hours while phone goes through setup to try again
Click to expand...
Click to collapse
Yes I know it is very annoying when that happens, you should definitely flash the latest version regardless, I'm sure you won't have the problem after flashing :good:.
trash195 said:
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
Click to expand...
Click to collapse
Found it! After you install twrp, you just execute 2 more commands:
fastboot format userdata
fastboot format cache
Don't reboot, just turn it off.
Works like a charm!

Bootloop after simple power off, oem unlock not working

Okay guys, I'm in full panic mode. I was just getting ready to reinstall my X with Lineage OS. I had CM 13.0 up until now. I've backuped everything, then powered off my phone (simple, normal power down).
After that I was trying to get into TWRP (I had 2.x.x.x installed), but VolDown+Power got me in a boot loop. The OnePlus Logo flashes, phone vibrates short then reset and it flashes/vibrates again. I tried booting normally, that doesn't work either.
The only thing I can do is get into fastboot, but I can't flash anything! The phone says it's locked (though I unlocked it before I put CM 13.0 on it)
Code:
c:\Android>fastboot flash recovery twrp-3.1.1-1-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (16002 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.509s
c:\Android>fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
c:\Android>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
Help! I can't boot my phone and I can't flash anything either. Is there anything I can do or missed?
After 2 hours of trying everything I found I'm now at a point where I could install the original (?) recovery via the MSM DownloadTool 2.0.2. Now I have a recovery which looks like stock... I can "Install from local" and "Install from USB". Tried the latter and I get the "adb sideload" mode. Tried to upload the latest Lineage OS Nightly through this sideload, but it fails after 47%.
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
intoxicated.mad said:
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
Click to expand...
Click to collapse
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Anyway you got out of trouble ??
I have the exact same problem, only I am running Sultan's ROM. Unfortunately, my phone is not backed up, because I wasn't going to install a new rom or anything. Is there any way to restore my phone without losing data. I downloaded the MsmDownloadTool V2.0, and am wondering if I could replace the stock recovery.img in there with the one for my ROM, or would this not work?
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
drunken_m said:
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Click to expand...
Click to collapse
I also faced that issue too and it happens when you have installed custom rom or recovery without first unlocking the bootloader. Do It Now If you haven't
Actually the bootloader was already unlocked (I needed that to install CM in the first place), but I think I accidentally re-locked it when I tried to remove root (to install a banking app).
As I wrote I already fixed the issue by installing the original bootloader/recovery and OOS over a serial link, then unlocked the bootloader again and installed the latest TWRP And Lineage. So all is fine now.
adamantiumXT said:
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
Click to expand...
Click to collapse
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
drunken_m said:
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
Click to expand...
Click to collapse
I have to agree, but I wasn't flashing when the phone decided to brick itself , so I didn't have a recent backup. In the bricked state I could only access fastboot mode, not recovery . I ended up copying what I could from the internal storage partition (which basically had everything I needed anyway), then clean installing a new ROM, and restoring my files.
For anyone else who gets into the same situation, I recommend that you make sure to not turn on WiFi or mobile data after you dirty flash OxygenOS, and remove your Google account. This will mean that Google's backup of your phone and apps (if you turned that feature on) will be of your working setup. As I tried to use Google Play in the messed up system, Google decided to replace my backup with the bad config so I couldn't restore in the new ROM - although looking at the Google Drive app now, the good setup is backed up, only I have no way to restore it
Maybe I have the same problem, not sure. I can't boot the phone. Holding vol down + power only makes the phone reboot over and over until I let go. It turns off afterwards, never enters recovery mode. I can access fastboot mode, but my bootloader is locked so I can't flash anything. Any suggestions?

Does boot normal instead of TWRP Recovery

Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
orthen2112 said:
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
Click to expand...
Click to collapse
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
trax7 said:
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
Click to expand...
Click to collapse
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
orthen2112 said:
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
Click to expand...
Click to collapse
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
trax7 said:
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
Click to expand...
Click to collapse
I have to admit I didn't understand very much in those to sentences.
trax7 said:
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Click to expand...
Click to collapse
Any ideas where else I can look
trax7 said:
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
Click to expand...
Click to collapse
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
orthen2112 said:
I have to admit I didn't understand very much in those to sentences.
Any ideas where else I can look
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
Click to expand...
Click to collapse
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
trax7 said:
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
Click to expand...
Click to collapse
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
orthen2112 said:
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
Click to expand...
Click to collapse
Glad I helped! The mods can close the thread now, I guess.
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
fetchaspade said:
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
trax7 said:
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
Click to expand...
Click to collapse
Thank you for your answer, sorry I did not notice.
My bootloader was indeed unlocked and I had adb + fastboot (on a linux distribution, never had to fetch specific drivers). In the end I tried to use flashtool to flash the stock Android L rom I had used for the downgrade (to backup the TA with the DRM keys before unlocking bootloader) which worked (I could not flash only the kernel image on boot). Then I tried again to boot on TWRP directly from fastboot mode without flashing anything: same error. I then downloaded a few recent stock Android N roms from xperifirm which flashtool could not unzip for some reason, then I found an Australian image elsewhere, and this time flashtool would accept it. So, back to Android N, I tried to flash TWRP again and it worked at last. I'm now running on the Lineage14.1+microG rom (so much better than stock roms I still can't believe it).
I guess TWRP, including old versions I tried, would not boot along the stock Android L rom that was currently flashed so I had to upgrade beforehand. I hope this will help people in the future.
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
elfae said:
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
Click to expand...
Click to collapse
Ofc that the latest recovery wont work for an Android version it wasn't made for (it would probably work on Marshmallow but Lollipop is too old). A different recovery would work there, the old zxz recovery if i remember correctly.
Also you can fastboot boot the recovery image directly.
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
elfae said:
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
Click to expand...
Click to collapse
You dont *have to* backup TA... It's only to preserve your original keys if you want. All of the custom kernels here emulate them anyway if you dont have the backup and LOS doesn't benefit from them at all.

Can't install recovery on slot A

EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.

Categories

Resources