I have tried to update my bootloader
downloaded XT1033_Bootloader_v41.18.zip from http://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793
Extracted motoboot.img from the zip and used twrp to flash boot image.
But now I get this error invalid boot image size failed to validate boot image.
The reason I flashed the image using twrp is because my usb does not work it works only for charging. so no adb and fastboot. I cant get any new files in my phone because the otg is dead as well.
I also tried to flash the boot image from the terminal inside twrp using
flash_image boot /sdcard/motoboot.img
this return error: -1
What you are doing is extremely dangerous. Don't mess around with Bootloaders. The motoboot.img can only be flashed via fastboot.
Alternatively, flash the Android 5.0.1 Stock ROM from here: (and accept the OTA Update to Android 5.1)
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection
Note: The OTA Update will require the ROM to be unrooted (remove supersu from zip before flashing) and Stock Recovery installed. You can also search XDA for the 5.1 OTA Update zip.
This will also update your Bootloader to v41.18.
lost101 said:
What you are doing is extremely dangerous. Don't mess around with Bootloaders. The motoboot.img can only be flashed via fastboot.
Alternatively, flash the Android 5.0.1 Stock ROM from here: (and accept the OTA Update to Android 5.1)
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection
Note: The OTA Update will require the ROM to be unrooted (remove supersu from zip before flashing) and Stock Recovery installed. You can also search XDA for the 5.1 OTA Update zip.
This will also update your Bootloader to v41.18.
Click to expand...
Click to collapse
The problem is that my usb does not work. So I cant use fastboot and can't even get anything into the phone. So I guess getting the usb repaired is the first thing i need to do. Also when I cd into the /boot folder from the terminal inside twrp I dont see anything. The folder is empty. I have a cm12.1 zip in the memory when I flash it I get
This package supports bootloader 0x4118, 0x4119, 0x411A; This device has bootloader 0x4113.
kirantambe said:
The problem is that my usb does not work. So I cant use fastboot and can't even get anything into the phone. So I guess getting the usb repaired is the first thing i need to do. Also when I cd into the /boot folder from the terminal inside twrp I dont see anything. The folder is empty. I have a cm12.1 zip in the memory when I flash it I get
This package supports bootloader 0x4118, 0x4119, 0x411A; This device has bootloader 0x4113.
Click to expand...
Click to collapse
You flash the ROM zip via TWRP.
lost101 said:
You flash the ROM zip via TWRP.
Click to expand...
Click to collapse
The problem is my usb does not work so I cannot get the ROM into the internal memory. Tried OTG as well but that too is dead
kirantambe said:
The problem is my usb does not work so I cannot get the ROM into the internal memory. Tried OTG as well but that too is dead
Click to expand...
Click to collapse
If you are running Windows on PC, try a Linux LiveCD (Ubuntu) - no need to install, simply boot from CD / USB.
In Ubuntu Terminal:
sudo apt-get install android-tools-adb android-tools-fastboot
Test Fastboot:
sudo fastboot devices
Test ADB:
sudo adb devices
lost101 said:
If you are running Windows on PC, try a Linux LiveCD (Ubuntu) - no need to install, simply boot from CD / USB.
In Ubuntu Terminal:
sudo apt-get install android-tools-adb android-tools-fastboot
Test Fastboot:
sudo fastboot devices
Test ADB:
sudo adb devices
Click to expand...
Click to collapse
yes i have ubuntu. I have fastboot and adb as well. but it does not show up in devices. And this problem has been there even when my moto g was working. So I guess there must be some hardware problem with the usb port. Even when Im in bootloader and if I connect usb cable it still says 'Connect USB Data Cable'
kirantambe said:
yes i have ubuntu. I have fastboot and adb as well. but it does not show up in devices. And this problem has been there even when my moto g was working. So I guess there must be some hardware problem with the usb port. Even when Im in bootloader and if I connect usb cable it still says 'Connect USB Data Cable'
Click to expand...
Click to collapse
Make sure to always use the 'sudo' command before any fastboot or ADB command.
It could be the USB Cable, or the port as you say.
Same here in Moto G XT1040 when trying to access Recovery option (from bootloader): "Invalid boot image size! failed to validate recovery image. Boot up failed".
It happened after I tried to upgrade CM (13 > 14) from their recovery mode.
Although I had the same error message of you, my USB was working fine and could enter in Android (although lots of "failed" popup messages).
From Linux I noted that "adb devices" command showed my mobile, but "fastboot devices" not.
After I installed drivers on Windows also "fastboot devices" worked.
It worked like a charm!
How I solved:
1. Windows: install Android SDK (to provide adb and fastboot commands), install drivers, download TWRP (for my specific device model), download CM custom ROM (for my specific device model) and copy to device (adb push);
2. Device: enter in bootloader, connect USB cable;
3. Windows: fastboot flash recovery twrp_image_filename_downloaded.img
4. Windows: fastboot reboot
5. Device: install CM from the TWRP recovery mode.
lost101 said:
What you are doing is extremely dangerous. Don't mess around with Bootloaders. The motoboot.img can only be flashed via fastboot.
Alternatively, flash the Android 5.0.1 Stock ROM from here: (and accept the OTA Update to Android 5.1)
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection
Note: The OTA Update will require the ROM to be unrooted (remove supersu from zip before flashing) and Stock Recovery installed. You can also search XDA for the 5.1 OTA Update zip.
This will also update your Bootloader to v41.18.
Click to expand...
Click to collapse
Hey lost101, I got the same problem as OP and I tried to do what you suggested here, but how do I install stock recovery via adb ? After flashing the 5.0.2 untouched version to my phone, I got the OTA update notification to 5.1, i tried to run it then the phone booted to twrp. If I reboot the phone, the system loads but after a few seconds it reboots again to twrp. What do you suggest?
You can also search XDA for the 5.1 OTA Update zip.
Click to expand...
Click to collapse
Is that what you meant? Can I install it thru twrp? https://forum.xda-developers.com/moto-g/general/ota-xt1033-5-1-brazilian-lollipop-t3196328
Thanks
@POWBlock - Don't mess around with OTA Updates. They can make your phone buggy and slow. Best advice is the flash Optimized 5.1 from thread above or Identity Crisis 6 (Stock 6.0):
[ROM][FALCON][6.0][STOCK] Identity Crisis 6 v1.5c
lost101 said:
@POWBlock - Don't mess around with OTA Updates. They can make your phone buggy and slow. Best advice is the flash Optimized 5.1 from thread above or Identity Crisis 6 (Stock 6.0):
[ROM][FALCON][6.0][STOCK] Identity Crisis 6 v1.5c
Click to expand...
Click to collapse
Yeah, I was actually trying to flash Cyanogen to this phone, but I couldnt do it since bootloader wasnt updated, so, instead of updating to 5.1 thru OTA, I flashed the whole firmware doing this method: https://forum.xda-developers.com/showthread.php?t=2542219 , but I got the file from another forum.
Then I installed TWRP again, then finally installed Cyanogen. But thanks for answering!
xt1032 flash problems
I was recently struggling with out of the blue flash problems. Recovery or boot flash didn't work. Size mismatch error. Recovery on phone was corrupted. System didn't start. Only remote boot recovery using fastboot worked. Eventually I extracted boot.img from the last official lineage 14.1 zip and flashed that to boot. After that all was working again. Hope this is useful to others.
Related
Hi XDA,
I am a complete noob, and this is my first time posting, so bear with me.
Some time ago I rooted and unlocked my TF300 with SuperSu. Recently I wanted to upgrade to 4.4 kitkat. However, my Tablet was stuck at Andriod 4.1 because of the the unlock.
I went to manually update my TF via the Asus website. I installed the 10.6.1.8 using my TWRP 2.5, and Oem 4.1 OS. Installation worked just fine. After install, I booted up and I had 4.2 with everything working correctly.
Next step was to install TWRP 2.7.0.1. I reset my TF and went into RCK to see something went wrong when updating.
My TWRP will not load, and I get the Android on his back with the red triangle when I try to enter RCK.
Thanks in advance!!
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
TallMilk said:
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
Click to expand...
Click to collapse
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
cmendonc2 said:
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
Click to expand...
Click to collapse
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
TallMilk said:
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
Click to expand...
Click to collapse
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
You are amazing. I will give it a try tonight and report back!
cmendonc2 said:
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
Click to expand...
Click to collapse
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
TallMilk said:
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
Click to expand...
Click to collapse
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
cmendonc2 said:
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
Click to expand...
Click to collapse
Awesome! Worked like a charm. twrp 2.7.0.1 installed perfectly.
Then I tried to flash the cyanogenmod. Said it installed fine, but it just gets stuck on the loading screen...
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
TallMilk said:
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
Click to expand...
Click to collapse
Damn, so I'm screwed. Why does Asus have to such so much...? You can no longer unlock afaik.
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
cmendonc2 said:
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
Click to expand...
Click to collapse
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
SilentSpartan said:
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
Click to expand...
Click to collapse
Did you ever get your tablet fixed? I am having some problems myself after a miserable m9 update.
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/
LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok
Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file
emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb
I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...
emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.
I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going
Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.
Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image
To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).
Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.
If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.
Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?
MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.
Boot into twrp. Then format data. Phone will boot then.