Related
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
reno55 said:
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
Click to expand...
Click to collapse
Try using Titanium Backup to freeze MotorolaOTA
samwathegreat said:
Try using Titanium Backup to freeze MotorolaOTA
Click to expand...
Click to collapse
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
reno55 said:
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
Click to expand...
Click to collapse
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
samwathegreat said:
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
Click to expand...
Click to collapse
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
reno55 said:
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
Click to expand...
Click to collapse
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
samwathegreat said:
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Click to expand...
Click to collapse
Can I flash philz?
reno55 said:
Can I flash philz?
Click to expand...
Click to collapse
Don't see why not. Just substitute the filename for philz recovery instead.
Get Philz here: http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
I have not used Philz personally...I prefer TWRP, but it looks like (unlike TWRP), that there is a different img for each variant of the Moto X. You will need to be careful to download the correct one.
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup, TWRP and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is there no way to complete the OTA without flashing a stock recovery? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
YES, that is the best way to do it. You can -try- disabling xposed, and un-doing any major modifications you have done (like freezing or removing any system apps). You want it to be as close to stock as possible before you try to accept the OTA, which includes flashing back the stock recovery.
SBFing back to stock 4.4.2 FIRST, and accepting the update, THEN flashing TWRP and rooting, then re-configuring everything and installing your apps is MUCH safer and pretty much guarantees that your filesystem will be 100% intact.
If it were ME, I would SBF first -- for whatever that's worth...
Good Luck
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
reno55 said:
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
Click to expand...
Click to collapse
Sure. It's just slightly more complicated. You'll need the entire 4.4.2 SBF for your carrier.
Do this: Reboot to bootloader
FIRST, JUST flash gpt.bin and motoboot.img:
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Now you need to REBOOT back into bootloader (to prevent gpt.bin mis-match -- if you don't reboot here, you will get errors). Do this by typing:
mfastboot reboot-bootloader
Now flash the rest of the files:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Reboot, and you should be back to stock 4.4.2
And finally the disclaimer: DO NOT TRY TO DOWNGRADE TO ANY VERSION PRIOR TO 4.4.2 .....if you don't want a brick.
It's ok to downgrade 4.4.3 to 4.4.2 because the bootloader version did not change. It is NOT safe to downgrade to anything prior (4.4 or 4.2.2).
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
First, woohoo!
Flashing now, thanks bud!
EDIT: Hey Bunny, maybe I'm missing something. Where are those bootloader images available?
@bunny0007 is this pre-rooted, or stock ?
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
bunny0007 said:
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
Click to expand...
Click to collapse
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Moe5508 said:
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Click to expand...
Click to collapse
I flashed the ota file before i made the system dump.
Im not sure if the new bootloader an stuff are required for this update, but the ota are not a new rom, just patched files, no new boot image or recovery image.
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Moe5508 said:
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Click to expand...
Click to collapse
The only way to flash the ota file are from stock non rooted 5.0.1 via sideload from recovery.
You might fastboot flash stock 5.0.1 system, boot and recovery, then you shuld be able to flash the ota from recovery.
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system-rooted.img
Stock 5.0.2 boot partition dump download (sorry for the partiton size): http://www68.zippyshare.com/v/4v4NAT5J/file.html
Stock 5.0.2 recovery partition dump download (sorry for the partiton size): http://www3.zippyshare.com/v/hpeV5W22/file.html
Stock 5.0.2 System rooted: http://d-h.st/IGov
Smaller 5.0.2 boot.img and recovery.img might fe found here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if nessesary.
Extract the files and use the flash cmd file from windows cmd, or flash the files manually with fastboot.
bootloader.aboot.img
bootloader.imgdata.img
bootloader.rpm.img
bootloader.sbl1.img
bootloader.sdi.img
bootloader.tz.img
Download Bootloader Stuff : http://d-h.st/bDXl
Click to expand...
Click to collapse
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
akaHardison said:
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
Click to expand...
Click to collapse
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
fronc said:
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
Click to expand...
Click to collapse
yep have changed the error in new zip
@bunny0007 can you please post a step by step guide for how to flash this?
I am on rooted 5.0.1 and do not understand the order, or not even which imgs are necessary to flash?
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash system system-rooted.img
Stock 5.0.2 System rooted: http://d-h.st/IGov
Click to expand...
Click to collapse
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
BostonDan said:
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
Click to expand...
Click to collapse
Just uncheck the "Download with Dev-Host Download Manager" box.
Spleeno said:
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
Click to expand...
Click to collapse
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
b0gd4n said:
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
Click to expand...
Click to collapse
Boot into fastboot, then make sure you can use fastboot from windows in cmd shell.
Then use this to flash
1. Unzip and flash bootloader stuff with cmd file.
2. Flash system with "fastboot flash system filename.img"
3. Flash boot with "fastboot flash boot boot.img"
4. Flash Stock 5.0.2 recovery with "fastboot flash recovery recovery.img"
5. Reboot the watch
Is there coming a stock rooted 5.1.1?
TimV_ said:
Is there coming a stock rooted 5.1.1?
Click to expand...
Click to collapse
Yep here http://forum.xda-developers.com/g-watch-r/development/rom-stock-rooted-5-1-1-t3124921
How do you come around to get the watch listed in adb (adb devices command). I installed several drivers for my lg g watch r, tried both in win10 test and non test mode, but the watch is not recognized. DEvice manager lists it as "unknown usb device descriptor request failed".
I appreciate any type of suggestion. Thanks in advance!
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.
2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.
danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.
I currently am on Android 5.1 system ver. 222.21.15.ghost_row.Retail.en.US
Currently I have TWRD fastboot installed but in order to perform a successful OTA update I must install mfastboot. Here is my question, where can I find the latest/compatible mFastboot img? The only copy I have is version 4.4.2 from way back when I was still running Kitkat.
Thanks.
You must first unroot your device from the Supersu option (if rooted), then.
You can DOWNLOAD TMobile 5.1 Firmware, then extract "recovery.img" and flash it from CMD.
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
After that you can take OTA.