Hi,
My Moto G-XT1033 one day failed to boot up, even in recovery it won't.
I unlocked the device and tried flashing a Custom ROM using ADB, but the device is not getting detected in ADB mode, however it is getting detected in Fastboot mode. So I wanted to ask, is there a way I can Fash a ROM(any as a matter of fact, i just need it running) in the Fastboot mode?
sushantgupta90 said:
Hi,
My Moto G-XT1033 one day failed to boot up, even in recovery it won't.
I unlocked the device and tried flashing a Custom ROM using ADB, but the device is not getting detected in ADB mode, however it is getting detected in Fastboot mode. So I wanted to ask, is there a way I can Fash a ROM(any as a matter of fact, i just need it running) in the Fastboot mode?
Click to expand...
Click to collapse
Just flash a custom recovery like philiz it is better than twrp in case of xt1033
Download philiz recovery inage file in pc any doubt u can msg me
What recovery are you using?
Related
So I have my bootloader unlocked, but for some reason I can't flash a recovery (CWM or TWRP). I've tried to flash recovery through fastboot using adb fastboot commands, mfastboot commands, and mototool aio. I've also tried to flash recovery through rom manager and rashr. ( I am rooted )
cmd: getvar:max-download--size
cmd: download:007b1800
cmd: flash:recovery
mismatched partition size (recovery)
Click to expand...
Click to collapse
I get
Boot up failed
Click to expand...
Click to collapse
Whenever trying to enter recovery afterwards. I get the warning bootloader unlocked motorolla screen for .1s before going back to fastboot.
Can anyone point me towards what I should be doing please? Thank you
Is the phone being detected when you type "adb devices" in cmd window ?
If not you need to install correct and drivers, then in while in the boot loader type "fastboot flash recovery RECOVERYNAME.img" obviously you change it to your Recovery's image file and it has to be in the directory with adb and fastboot of course.
Sent from my Nexus 5
Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters
kdbrown5 said:
Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters
Click to expand...
Click to collapse
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?
kdbrown5 said:
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?
Click to expand...
Click to collapse
Yeah, of course there are recoveries for 4.4.3/4.4.4. Try to flash another recovery bro
Sent from my Moto G using XDA Premium 4 mobile app
I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.
kdbrown5 said:
I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.
Click to expand...
Click to collapse
You can try to go back to stock, and after, flash a custom recovery and see what happens
Sent from my Moto G using XDA Premium 4 mobile app
Ok, I guess I'll try that tomorrow. The thing I'm wondering is, If it doesn't work flashing through fastboot, outside of the ROM, how would reverting back to stock help at all? A stock flash shouldn't change the bootloader at all?
bump : (
After Lollipop Update of my phone (Lava iris icon), I had to root in again and while trying to root it from custom recovery, I bricked it ( may be the recovery is not compatible). So,it stuck in the bootloop and by pressing Power and volume buttons, I am only able to access Fastboot mode. I downloaded the stock rom of device and tried to flash recovery , boot etc. with fastboot commands, but it is still in bootloop. I also tried to flash cwm recovery (though it is not available for device, I chose the nearest one), but in vain.
When I try to flash system partition, it gives error while erasing system <unknown command> (may be due to fact that phone is not rooted as of now). Also, SP flash tools are not recognizing the device and I cant use adb commands also. So, I am stuck with only fastboot in hand and I have stock rom as well as lollipop update, but i am unable to use these due to errors. Can anyone help? I will be very thankful for an advice. Thanks in advance.
rishab951 said:
After Lollipop Update of my phone (Lava iris icon), I had to root in again and while trying to root it from custom recovery, I bricked it ( may be the recovery is not compatible). So,it stuck in the bootloop and by pressing Power and volume buttons, I am only able to access Fastboot mode. I downloaded the stock rom of device and tried to flash recovery , boot etc. with fastboot commands, but it is still in bootloop. I also tried to flash cwm recovery (though it is not available for device, I chose the nearest one), but in vain.
When I try to flash system partition, it gives error while erasing system <unknown command> (may be due to fact that phone is not rooted as of now). Also, SP flash tools are not recognizing the device and I cant use adb commands also. So, I am stuck with only fastboot in hand and I have stock rom as well as lollipop update, but i am unable to use these due to errors. Can anyone help? I will be very thankful for an advice. Thanks in advance.
Click to expand...
Click to collapse
is there a partition file with the stock rom you downloaded?
if so, try to flash that first with fastboot.
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
jungl1st said:
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
Click to expand...
Click to collapse
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
greenys' said:
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
Click to expand...
Click to collapse
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
jungl1st said:
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
Click to expand...
Click to collapse
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
indeeed, custom recovery is the turning point to recover almost anything ! given the point that one manages to install it in the first place
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
Hi, I actually managed to flash the recovery, how ever it seem not to properly overwrite the original recovery.
I mean, i can flash and boot in to TWRP, only once at a time, once I exit TWRP and reboot into recovery, I land into the Realme recovery again !!!!! dont know whats wrong
hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help
Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.
https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide
One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
luka0954 said:
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
Click to expand...
Click to collapse
Just to be sure, do you have USB debugging enabled?
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
I do, and of course I went and enabled it again after I bootloaded the device
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
You said you tried volume down+power, on most devices, that is the combination to boot into bootloader mode, fastboot mode or download mode, depending on the device. Volume up+power is generally the combination to boot into recovery mode. This doesn't seem to be your issue though. Are you sure you flashed TWRP to the correct partition? If your device is an A/B partitioned device, you may have flashed to one of these partitions when you needed to flash to the other partition.
Try flashing a copy of your stock recovery then see if that repairs the recovery partition and allows stock recovery to boot. If it works correctly after flashing stock recovery, you may not be flashing TWRP correctly or the actual flash might be being blocked by something that you're overlooking. Are you certain that your bootloader is unlocked?