Related
So I searched and found a solution but I'm not exactly sure how to perform it. I'm not a complete noob but I am not very familiar with adb and using the cmd window.
The problem that I have is I tried to flash the stock kernel with the GUI app because I was experiencing a lot of random reboots with the kernel that I was using. After flashing the kernel I chose to reboot the phone and it gave me the black screen of death. I can reboot into hboot, so I did. I wiped everything multiple times and tried reflashing roms and kernels to no avail. I've only managed to get the phone to hang on the splash screen now.
This thread shows how others have resolved the issue but I need more specific instructions on how to use the commands.
Help! Stuck at boot loop evo 3d
I've been trying to troubleshoot this since 2am and it's 6:30 now. Thanks in advance.
gators2kt said:
So I searched and found a solution but I'm not exactly sure how to perform it. I'm not a complete noob but I am not very familiar with adb and using the cmd window.
The problem that I have is I tried to flash the stock kernel with the GUI app because I was experiencing a lot of random reboots with the kernel that I was using. After flashing the kernel I chose to reboot the phone and it gave me the black screen of death. I can reboot into hboot, so I did. I wiped everything multiple times and tried reflashing roms and kernels to no avail. I've only managed to get the phone to hang on the splash screen now.
This thread shows how others have resolved the issue but I need more specific instructions on how to use the commands.
Help! Stuck at boot loop evo 3d
I've been trying to troubleshoot this since 2am and it's 6:30 now. Thanks in advance.
Click to expand...
Click to collapse
Belongs in Q&A...
Edit: Have you tried flashing in recovery. If that didn't work try a different kernel. If that doesn't work then I would suggest trying a different ROM all 0together....though I doubt it's the ROM causing your issue. What ROM is it BTW?
I tried flashing in recovery by holding the vol down button while powering on the phone. I flashed 2 different roms and 3 different kernels and none of those worked. I am using the Infected Eternity rom and it ran perfect until I changed kernels... I switched to the anthrax a couple of weeks ago and it kept randomly rebooting. So I flashed the stock kernel and then this happened. In the other thread, the users were saying that flashing worked when you access fastboot through the command window. I don't know how to do that though.
Wait are you on hboot1.50? If so the flashing instructions are in the Eternity thread on how to do that. If not then you can still refer to that same post for how to get into fastboot. I think it's "adb reboot fastboot" but I'm not 100% sure. Just go there and look in the hboot 1.50 flash instructions. That should get you where need to be. Let us know if it works.
Edit: It should be in the first few post if I'm not mistaken. Check posts 1-3.
gators2kt said:
So I searched and found a solution but I'm not exactly sure how to perform it. I'm not a complete noob but I am not very familiar with adb and using the cmd window.
The problem that I have is I tried to flash the stock kernel with the GUI app because I was experiencing a lot of random reboots with the kernel that I was using. After flashing the kernel I chose to reboot the phone and it gave me the black screen of death. I can reboot into hboot, so I did. I wiped everything multiple times and tried reflashing roms and kernels to no avail. I've only managed to get the phone to hang on the splash screen now.
This thread shows how others have resolved the issue but I need more specific instructions on how to use the commands.
Help! Stuck at boot loop evo 3d
I've been trying to troubleshoot this since 2am and it's 6:30 now. Thanks in advance.
Click to expand...
Click to collapse
From what you are experiencing , i m guessing you are on hboot 1.50.
Now follow the below steps:
Download this =====> http://downloadandroidrom.com/file/HTCEvo3D/rooting/rootevo3dnew.zip
Download any ROM or use any ROM that you have.
Download a superwipe tool ( or you can manually wipe everything from recovery).
>extract the "rootevo3dnew.zip" you downloaded above in "C:\" drive.(So it should be like "c:\rootevo3dnew\*.* ")
> install "HTCDriver3.0.0.007.exe" from it.
> open the ROM.zip (that you want to flash) with winRAR/7z and copy the boot.img from it to the rootevo3dnew folder.
> open cmd prompt ( press the key between "alt and fn" and press "r" then type cmd and hit enter)
> navigate to fastboot folder ( command : "cd c:\rootevo3dnew")
> boot phone in bootloader
> select fastboot
> connect to PC (phone should say fastboot-usb)
> type command "fastboot flash boot boot.img"
> now type "fastboot boot cwm-4.0.1.4-shooter.img"
> Phone should boot into recovery ( make sure the red LED is lit up)
> now flash the superwipe tool.zip(or wipe everything manually from wipe menu in recovery)
> and then flash the same ROM from which you pulled the boot.img.......
Hope this helps...........
Awesome! Thank you very much. Now I just need to restore my phone and everything else on it. Again, thank you.
its all ok!
My friend. Hopefully, I can help you. First off, download the android sdk from here:
http://developer.android.com/sdk/index.html
While that is downloading, on your laptop or pc, locate the ROM you are trying to flash and drag it to the desktop. Should be a zip file. From there double click the rom and you should see a file named "boot.img." Drag it onto the desktop.
OK, back to our download, open it up and extract it to the desktop as well.
Boot into fastboot on your device. Then, hook it up to a USB cable and you should see "fastboot usb" from there put your phone down.
Open a command prompt on your computer and type:
cd Desktop( hit enter)
fastboot flash boot boot.img(enter) it should reflash your boot partition. Let it do its thing and when completed boot into recovery. Flash the ROM that you extracted the boot image from. Bada Bang.
If this doesnt help you, PM me.
Thank you jsufx. I already fixed it thanks to mnomaanw. Phone is back to normal and I'm just going to stick with the stock kernel for now.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
New AT&T HTC One 64M S-ON
Did the following (after trying the all-in-one toolkit and not being able to boot into recovery)
> fastboot flash boot boot.img
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img
> fastboot erase cache
This got the recovery working. I installed supersu.zip from recovery. Verified root using root checker.
Tried to download and install a couple programs. Installing MyBackupPro and gave me an error relating to being unable to install.
Rebooted a couple of times and reset the phone to factory using the OS settings. At that point, wifi would not turn on. Says "turning on", and eventually says "error".
Any suggestions? I'm concerned that the boot.img was incorrect--for the international model? It was the one "made by Paul O'Brien"?
I am able to install and run both TWRP and CWM.
I've subsequently redone as follows:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Everything works except wifi. Could it be just a hardware failure? I don't believe the failure was triggered immediately after any of my changes, but only after the "factory reset".
I have also tried disabling su from its settings menu.
Application installation error
This must be related? When I try to install My Backup Pro (I can download over 4G), I get the error "couldn't install on USB storage or SD card".
This is after a fresh factory "reset", including all user data.
You could install Android revolution from the Standard One Development section. Thats what im running. Works great. Remember to flash the kernel...http://forum.xda-developers.com/showthread.php?t=2183023
.
If you install Mikes Rom i linked above and the boot.img that goes with it you'll be fine. Right now you have a kernel from a different Firmware package so it isnt compatible.
This happened on one of my One's tonight as well. Turns out it was the boot.img that is most likely from the International One and a different version than what our stock AT&T Rom is (1.26 vs 1.27/8/9). I pulled the boot.img from my other One's nandroid and flashed it via fastboot and wifi was back.
I've posted it here.
Oh man, Thanks for the boot.img. Actually, I think that's the name of a song, right?
I want to try AR, but did want to keep it stock for a few days frist! Fortunately, at my bandwidth the download took several hours and by the time I looked your boot.img was here! Everything seems back to normal now.
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
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.
Hello. I've tried many different ways to install the customs ROMs on here for Moto G8 Power (XT2041-3) but nothing has worked. When I try to flash using fastbootd every ROM except the Lineage one fails at the stage where I try to load the system.img. Even when I think I've correctly installed Lineage that way, when I go to reboot my phone it won't boot properly. I keep getting the screen alternating between the Motorola icon and the unlocked bootloader warning screen. It does that repeatedly for a while and then eventually boots as if I am powering on my phone for the first time out of the box after buying it.
So I've also tried TWRP. Again, I can seemingly install some of the flashable zips (Lineage and Omnirom), but when I reboot the same thing happens. Motorola screen, unlocked bootloader warning screen, etc, repeately for a couple of minutes, and then it boots to the Android system that came with the phone. As if there's been a total factory reset and I am turning on the phone for the first time. ADB sideload doesn't work either because even though it can detect ADB devices at first, as soon as I go to sideload on TWRP and then try "adb sideload .....zip" on the terminal of my computer (Linux) it doesn't seem to recognise any ADB devices any more.
I know it says to reboot to recovery after installing a custom ROM, but the same thing happens if I try that. Some sort of bootloop I think, and then basically a factory reset start.
TWRP doesn't seem to permanently install on my phone. If I try going into bootloader and then recovery after I have just used TWRP then all I get is the 'No Command' screen. Could this be part of the reason? I recently found out about DM-Verity. Could something on my phone be preventing changes to the system? It's really frustrating. Previously when I've installed custom ROMs on other Motorola phones I haven't had any problems. Any suggestions would be much appreciated. Thanks
Check out my post here.
Thanks tinbilly but I'm still unsure what to do. I hadn't tried CrDroid before so before anything I tried flashing those image files via fastbootd. Same problem - it failed at system.img. Which leaves me unable to boot into custom ROM or stock ROM. Before when that has happened I have always been able to just reflash stock using the commands on the XML file. Now even the first command fails (fastboot getvar max-sparse-size) so I don't seem to be able to get back to stock at the moment. I'll keep trying.
I didn't know how you flashed stock ROM to partition b. The only way I can think to change to partition b is to go into fastbootd and use the "fastboot set_active b" command. Or to flash TWRP (which doesn't work at the moment) and change slots that way. I think changing it on fastbootd might have messed me up a bit because it just went into a bootloop when I tried to do anything after that. For some reason I seem to be back in partition a now though (I typed "fastboot getvar all" while I was in fastbootd and it came back showing slot a).
Here is my suggestions:
1. Hard reset your device following this or this. They are basically the same instruction. Hopefully this will get your phone back to the stock rom. If not, then just try step 2 below.
2. Install the xt2041-3 stock rom on your device by following the instructions in the download link. Or you could try this method.
3. Once you are back to stock rom, you can install any custom rom via fastboot mode.
Hope that will help.
Thanks for that. I'm going to work on it over the weekend and see how I get on. I feel like I've spent too many valuable hours of my life trying to figure this out. If only this custom ROM thing could just be straightforward for everyone all the time.
tinbilly said:
Here is my suggestions:
1. Hard reset your device following this or this. They are basically the same instruction. Hopefully this will get your phone back to the stock rom. If not, then just try step 2 below.
2. Install the xt2041-3 stock rom on your device by following the instructions in the download link. Or you could try this method.
3. Once you are back to stock rom, you can install any custom rom via fastboot mode.
Hope that will help.
Click to expand...
Click to collapse
Cheers for your suggestions but nothing has worked. The phone wasn't taking any commands to reinstall stock ROM so I went to fastbootd (via recovery - no command - hold power button and up) and did a factory reset from there. Then I was able to flash the commands on the stock ROM xml file via the bootloader. So I got back to stock fine. But after trying to flash Lineage OS it seems to have worked fine but when I go to reboot I keep booting to bootloader. I tried fastboot oem fb_mode_clear but that didn't change anything. I'll keep trying different things and let people know if I find a solution.
lazzr said:
Cheers for your suggestions but nothing has worked. The phone wasn't taking any commands to reinstall stock ROM so I went to fastbootd (via recovery - no command - hold power button and up) and did a factory reset from there. Then I was able to flash the commands on the stock ROM xml file via the bootloader. So I got back to stock fine. But after trying to flash Lineage OS it seems to have worked fine but when I go to reboot I keep booting to bootloader. I tried fastboot oem fb_mode_clear but that didn't change anything. I'll keep trying different things and let people know if I find a solution.
Click to expand...
Click to collapse
Did you format data before or after installing lineage os? As in, where you have to type yes, not just wiping data.
Beetle84 said:
Did you format data before or after installing lineage os? As in, where you have to type yes, not just wiping data.
Click to expand...
Click to collapse
Hi Beetle. I always swipe to the right to wipe the cache etc. And after flashing I swipe to wipe the dalvik. But I'm never given the option to type yes. I'm not sure what you mean.
I've spent a lot of time wondering why TWRP never reboots when I try to reboot into recovery after flashing a zip. I just realised (after reading the instructions for flashing ArrowOS on this forum) that I can flash TWRP to partition b as well by using the commands:
fastboot flash recovery twrp.img
fastboot flash recovery_b twrp.img
By doing that I was able to (or so I thought) install the zip to the inactive slot b, and then reboot to recovery using TWRP, and it comes back as having the active slot b. I got excited but when I went to reboot system the same thing happened. Just some sort of bootloop thing. Nothing seems to work. I've tried OmniROM and Stag zips as well.
lazzr said:
Hi Beetle. I always swipe to the right to wipe the cache etc. And after flashing I swipe to wipe the dalvik. But I'm never given the option to type yes. I'm not sure what you mean.
I've spent a lot of time wondering why TWRP never reboots when I try to reboot into recovery after flashing a zip. I just realised (after reading the instructions for flashing ArrowOS on this forum) that I can flash TWRP to partition b as well by using the commands:
fastboot flash recovery twrp.img
fastboot flash recovery_b twrp.img
By doing that I was able to (or so I thought) install the zip to the inactive slot b, and then reboot to recovery using TWRP, and it comes back as having the active slot b. I got excited but when I went to reboot system the same thing happened. Just some sort of bootloop thing. Nothing seems to work. I've tried OmniROM and Stag zips as well.
Click to expand...
Click to collapse
When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.
Then reboot.
Beetle84 said:
When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.
Then reboot.
Click to expand...
Click to collapse
Thanks. I tried it but then I end up with no zip file in my internal storage so have nothing for twrp to install. I tried copying and pasting the file from my PC to my Android folder but it was going to take about a week to copy over. I also can't use ADB sideload for some reason. I get this:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
and
E:Unable to get child ID
on my phone when I cancel the sideload. I can't figure it out at all.
I also just tried flashing my stock recovery to replace twrp. After I had already used twrp to format everything. Then went to fastbootd and tried flashing the image files. They looked like they had installed but now when I reboot it automatically takes me to bootloader instead of into system.
In twrp, there's no option to wipe system. So in my case, I replaced twrp with stock recovery, then did a Factory Reset [Advanced > Reset options > Erase all data (factory reset)].
Before "tried flashing the image files" in fastbootd, did you "fastboot set_active a"?
tinbilly said:
In twrp, there's no option to wipe system. So in my case, I replaced twrp with stock recovery, then did a Factory Reset [Advanced > Reset options > Erase all data (factory reset)].
Before "tried flashing the image files" in fastbootd, did you "fastboot set_active a"?
Click to expand...
Click to collapse
I've tried the "fastboot set_active a" but it still doesn't work. I've factory reset through stock recovery too, and seem to have tried everything I can think of. I miss my old original Moto G which was easy to install on. I've been trying for weeks and keep running into the same issues. I'll keep trying over the next few days and report back if I solve it in case anyone else has the same problem.
Mine is a XT2041-1. What I did:
1. flashed back to stock ROM 10_QPE30.69-16
2. rebooted the phone, then set it up (I did not upgrade to Android 11 as notified by the system)
3. wiped the phone using System > Advanced > Reset (just to be safe)
4. flashed to crDroid 7.4 (Android11-based)
You said you failed to load the custom ROM's system.img. What is the exact error message? Please attach some screenshots as well.
tinbilly said:
Mine is a XT2041-1. What I did:
1. flashed back to stock ROM 10_QPE30.69-16
2. rebooted the phone, then set it up (I did not upgrade to Android 11 as notified by the system)
3. wiped the phone using System > Advanced > Reset (just to be safe)
4. flashed to crDroid 7.4 (Android11-based)
You said you failed to load the custom ROM's system.img. What is the exact error message? Please attach some screenshots as well.
Click to expand...
Click to collapse
I thought I'd try some more possible ways to fix it before replying but I've just wasted another few hours to no avail. I have the flashable zips for OmniROM 11 and Lineage, but I can't even get TWRP to ask for a password anymore so all my files show up as gobbledegook. Not that I think they would work either because they haven't so far.
The one that I thought had been successful was installing Lineage images using fastbootd, but whenever I go to reboot I end up in bootloader. The bootloader log says "Reboot mode set to fastboot". I have no idea how to get out of that. Fastboot fb_mode_clear doesn't work.
I thought I would try to root the phone (I know people say you don't need to do that first but I'm sure in the past I have done) but I can't get Magisk to install.
I installed Lineage images again, and then after it rebooted into bootloader I installed TWRP and tried entering the dd commands on this page in the terminal (I didn't know how to do the backup in section 2 of the instructions):
Troubleshooting: TWRP Boot Loop after OTA update in MOTO G4 (XT1621 Athene)
Hi. This is my first post in this forum. I had this problem, the phone always started in TWRP Mode after updating by OTA update, I should NOT have updated it this way, but I have done it still. :cyclops: XD To fix it, try this: TWRP Method: 1-...
forum.xda-developers.com
All I got back was "no such file or directory".
The error message from installing images (the one below was CrDroid 7.4 but it happens with most of them) seems to be quite common from what I can tell from reading other people's posts. I have also I tried "sudo" before flashing the system image because I've seen that recommended, but it didn't work either:
writing 'system_a' 5/6 (usually 3/3 on other ROMs)...
FAILED (remote: Operation not permitted)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wiping my data and formatting has caused me some issues too. I've done that many different things that I can't remember what exactly, but I do know that when I tried to install ZIP files using TWRP the Failed to mount '/system_root' error message came up a few times.
I've attached an images below to give an example of the types of other red screen messages I've had:
Forgive the long message. If any of this gives you any ideas or you've seen it before then please let me know. To be honest I just want a phone without all the google stuff on it and the amount of time I've spent on this I'm feeling like I should just get myself a different phone it would be easier to install on.
By the way, the image at the bottom there was the error message I got while trying to wipe in TWRP
A final attempt for now. I factory reset through fastbootd. Then "installed" Lineage image files. Rebooted and ended up in bootloader. Flashed TWRP, which this time could recognise my folders. ADB pushed Omnirom zip to my data folder. Tried a wipe, got lots of error messages, then tried installing the zip, and got the below:
This whole experience has been brutal.
From my experience with TWRP on my XT2041-1, I won't go with TWRP to flash a custom ROM. So just forget TWRP for now.
One important question, I think: Can you flash and boot your device to stock Android 10? [Note: I find this is a reliable method to go back to stock ROM. Just make sure you get the correct one matching your device.]
If yes, let take it as a starting point. From there, I suggest you wipe the phone using System > Advanced > Reset then flash to a Custom ROM using fastbootd. Btw, which custom ROM you prefer and intend to flash on your phone?
lazzr said:
A final attempt for now. I factory reset through fastbootd. Then "installed" Lineage image files. Rebooted and ended up in bootloader. Flashed TWRP, which this time could recognise my folders. ADB pushed Omnirom zip to my data folder. Tried a wipe, got lots of error messages, then tried installing the zip, and got the below:View attachment 5309925
This whole experience has been brutal.
Click to expand...
Click to collapse
What did you do after factory reset? How did you install Lineage image files? Please briefly describe what you did step-by-step. Just briefly.
tinbilly said:
From my experience with TWRP on my XT2041-1, I won't go with TWRP to flash a custom ROM. So just forget TWRP for now.
One important question, I think: Can you flash and boot your device to stock Android 10? [Note: I find this is a reliable method to go back to stock ROM. Just make sure you get the correct one matching your device.]
If yes, let take it as a starting point. From there, I suggest you wipe the phone using System > Advanced > Reset then flash to a Custom ROM using fastbootd. Btw, which custom ROM you prefer and intend to flash on your phone?
Click to expand...
Click to collapse
I can boot to stock using the same list of commands in that link. Starting with fastboot getvar max-sparse-size. Then I set up my phone to enable USB debugging and "file transfer" under default USB configuration. Then "ADB reboot bootloader", and click to enter recovery. I get the "No command" screen so I hold the power button and press up. Then "enter fastboot" to enter fastbootd. I've followed the next few instructions exactly as everyone says. Set active a, flash boot then system etc, then erase userdata.
This time I enabled "PTP" instead of "File Transfer" under default USB configuration to see if it made any difference. It still won't load system and I get this message:
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 20.736s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
I don't understand how it helps to install stock ROM and then wipe the phone using System > Advanced > Reset. That just puts me back to the same place as after I installed stock and I have to go in Developer Options etc again.
I'll try any ROM. I'm trying CrDroid now but it doesn't work. Lineage is the only one that seems to install system but I can't reboot to system.