Database Develop

[Q] Help: Can't get to recovery or system?!?!?

Hi, Gang... Please be patient as I'm not normally playing at this level...
I recently had a kid kill my TF700 so I bought at TF701 as a replacement. I immediately unlocked it, forgetting to take the latest Asus update OTA beforehand. Anyways, I manually downloaded v11.4..1.17 and put it on a blank microSD and stuck it into the tablet where the update was recognized as available and I set the update in motion... Something went sideways after I walked away to let the update run and now I can't get back into the system and I can't get into recovery.
I have the bootloader up (1.00e as released by 10.14.1.47) and I can communicate with the device via fastboot. Can someone help me wipe and get a recovery.img and/or a full stock image onto this thing. Right now it just keeps rebooting unless I manually force it to the bootloader.
I'm hoping someone more knowledgeable can chastise me for being a moron an point me in the right direction. Ultimately, I was tying to get to the latest ASUS ROM to the the bootloader that goes with it and then move onto a custom ROM.
Many thanx.

Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I wouldnt flash a recovery/bootloader especially the new ones til you can verify an older recovery works. Try booting this one https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img but dont flash til someone else takes a look at this. This is an old philz touch without touch.

Still nothing...
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
Where did you get the full firmware update you tried to flash?
I can't find a recovery that is compatible with that old bootloader, so your best bet would be to update via Asus firmware.
What happens if you choose RCK in the bootloader menu? Is the stock recovery still working?
What's your SKU?
If the manual stock update doesn't work you may have to flash the system blob in fastboot, but answer above questions first and then we'll see.
If you're getting frustrated, stop and come back to it later. Don't do anything desperate! No reason for it yet.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse

Fixed!
YayYouFixedIt said:
kartman_canada said:
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
Good to hear. For the Asus updates you just put them in /sdcard and reboot dont you? Its fairly automatic wasnt it? Then unlock after being updated? What went wrong in your case, Hard for me to say i guess because I and others unlocked at or before 4.3.
Click to expand...
Click to collapse

[Q] Stuck on Fastboot

Hi everybody,
A few days ago, I rooted my Mexican XT1225. I shut it down for a day (my main cellphone is the new Moto X), turn it on again and now it's stuck on fastboot.
I could boot into TWRP (by flashing it temporarily with fastboot on Linux) and then I decided to wipe data and then install the new lollipop zip file. But it failed saying it could not mount /system /data or anything really, I basically have it without format, all partitions say 0MB.
So I tried flashing with fastboot, but it gave me an error when flashing the partition gpt.bin, it didn't give me an error when flashing other files. Still stuck, now I cannot even access the recovery menu, it goes just into fastboot mode and does not show the little recovery menu anymore.
Then I tried flashing with RSD, still same problem. It fails when setting the fb_mode_set and when I delete that line from the xml it fails again on flashing gpt.bin
EDIT: I am attaching a log file of TWRP evidencing this.
Any ideas on how to get back to normal? How can I redo the partition in another way?
Thanks in advance,
Gustavo

Unlocked bootloader? Just remove the got. Bin flash line

Jaocagomez said:
Unlocked bootloader? Just remove the got. Bin flash line
Click to expand...
Click to collapse
Yes, unlocked bootloader. Removed the gpt.bin flash line and still no luck. Tried flashing several files, the Indian Lollipop, the Mexican Kitkat, nothing has worked.

gusbeto37 said:
Yes, unlocked bootloader. Removed the gpt.bin flash line and still no luck. Tried flashing several files, the Indian Lollipop, the Mexican Kitkat, nothing has worked.
Click to expand...
Click to collapse
After re reading your post I understood what's wrong, you have to flash the lollipop OTA on stock recovery not twrp or rsd lite, once you flash it you can put back twrp

Jaocagomez said:
After re reading your post I understood what's wrong, you have to flash the lollipop OTA on stock recovery not twrp or rsd lite, once you flash it you can put back twrp
Click to expand...
Click to collapse
I have the xml.zip file, extracted it and manually flashed partition by partition. Something I have previously done with my 1st gen Moto X, my Razr HD and even my Atrix, if I remember correctlly. Even RSD Lite should work with those files.
Still, I will try to boot with the stock recovery, since right now I cannot access it. I will also seek a way to get the xml.zip file inside the storage, since I cannot even mount it with TWRP (It shows 0mb drive)

gusbeto37 said:
I have the xml.zip file, extracted it and manually flashed partition by partition. Something I have previously done with my 1st gen Moto X, my Razr HD and even my Atrix, if I remember correctlly. Even RSD Lite should work with those files.
Still, I will try to boot with the stock recovery, since right now I cannot access it. I will also seek a way to get the xml.zip file inside the storage, since I cannot even mount it with TWRP (It shows 0mb drive)
Click to expand...
Click to collapse
Twrp for this device it's not very stable I got that errors too
Just flash mexico firmware then the OTA zip on stock recovery and you will be good to go.
If you can't access recovery press vol- and power with the phone turned off and you'll be able to select recovery

Hi,
I have tried the vol+power and cannot access recovery.
When I try to flash Mexico's firmware (through either RSD or manually in Linux using fastboot), I am unable to flash partition gpt.bin, but I can flash everything else. Yet, in spite of flashing everything else, I cannot get out of the fastboot loop.

I am attaching some photos of what happens. The first one is the only thing that boots, cannot access recovery, cannot boot normally. The second photo is what happens when I press the volume button many times.

So when you select recovery does it power off or just go back to fastboot again?

Steve-x said:
So when you select recovery does it power off or just go back to fastboot again?
Click to expand...
Click to collapse
Hi, I dan only go yo fastboot. The menú does not appear. The only thing that appears is the photo of my previous post.
I can boot into TWRP by manually doing fastboot boot twr-recovery.IMG

Hmmm, doesn't look good. The fastboot screen doesn't even load the picture of the green Android. I am thinking the partition table is messed up. I know I saw something similar with the original(2013) Moto X a while back. You may want to do some searching in that forum.

gusbeto37 said:
Hi, I dan only go yo fastboot. The menú does not appear. The only thing that appears is the photo of my previous post.
I can boot into TWRP by manually doing fastboot boot twr-recovery.IMG
Click to expand...
Click to collapse
flash mexican stock rom with rsd lite

Steve-x said:
Hmmm, doesn't look good. The fastboot screen doesn't even load the picture of the green Android. I am thinking the partition table is messed up. I know I saw something similar with the original(2013) Moto X a while back. You may want to do some searching in that forum.
Click to expand...
Click to collapse
Hola Steve,
Indeed, it looks like the partition table is messed up, I will look for that Moto X thread.
@Jaocagomez I have tried that, but it fails with gpt.bin partition flash and even after flashing everything else (RSD, fastboot or TWRP) it does not work.

After reading quite a lot on the Internet, it seems that my problem happened to some Moto G and Moto X users. Seems to be that I am trying to flash a gpt.bin that is older than the one already in my phone. I will try again when the Mexican Lollipop image is released in xml.zip format.
In the mean time, I will continue to search for solutions.

Hi
I think I have the same issue.
I have XT1225 bought it from Amazon (I asked the company and they said Puerto Rico origin) factory unlocked. had 4.4.4 and tried to upgrade to 5.0.2. Here is what I exactly did:
devices not rooted, locked bootloader
downloaded RSD Lite
downloaded the official 5.0.2 India Firmware
tried to flash it using RSD
got an error in flashing boot from RSD
I tried to do it again and I get the same issue, I tried to flash the Puerto Rico 4.4.4 and it didnt work (it get stuck in partition gpt) and my device is dead. I tried to unlock the bootloader using the code from motorola and it says allow oem unlock from developer menu
tried doing it manually using mfastboot with both 5.0.2 and 4.4.4 and still didnt work.
please let me know if you managed to fox your problem or if anyone can help us get back our devices

Stuck in fastboot
rehaili said:
Hi
I think I have the same issue.
I have XT1225 bought it from Amazon (I asked the company and they said Puerto Rico origin) factory unlocked. had 4.4.4 and tried to upgrade to 5.0.2. Here is what I exactly did:
devices not rooted, locked bootloader
downloaded RSD Lite
downloaded the official 5.0.2 India Firmware
tried to flash it using RSD
got an error in flashing boot from RSD
I tried to do it again and I get the same issue, I tried to flash the Puerto Rico 4.4.4 and it didnt work (it get stuck in partition gpt) and my device is dead. I tried to unlock the bootloader using the code from motorola and it says allow oem unlock from developer menu
tried doing it manually using mfastboot with both 5.0.2 and 4.4.4 and still didnt work.
please let me know if you managed to fox your problem or if anyone can help us get back our devices
Click to expand...
Click to collapse
I am facing the same problem
Though my device is different : XT1254 (verizon locked)
As bootloader is not unlocked, i cannot flash any software any way. Tried all the software from all the countries but to no avail.
The Phone is stuck in fastboot mode.
Please help

You 1225 folks might want to wander into this thread... http://forum.xda-developers.com/droid-turbo/general/tutorial-to-kk-soak-lollipop-t3041129 ... I've hashed my phone out a couple times between CM, lollipop, exposed, playing with the kernal and so on and it got me back up and running.

guys I need ASAP help, stuck in reboot after update, got intsallation error 7. now im stuck on logo reboot, cannot enter recovery (I see "dead" android icon. Please help!

jazzus said:
guys I need ASAP help, stuck in reboot after update, got intsallation error 7. now im stuck on logo reboot, cannot enter recovery (I see "dead" android icon. Please help!
Click to expand...
Click to collapse
We need more information. What is your original firmware, what did you try to update to and is your bootloader unlocked?

Steve-x said:
We need more information. What is your original firmware, what did you try to update to and is your bootloader unlocked?
Click to expand...
Click to collapse
Ok fixed, after 20 or 30 tries I was able to enter recovery Thx!

[ROM] Stock Rooted 5.1.1

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.

Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.

akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
worst case just reflash TWRP =]

akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
You can use whatever recovery you would like, the system image does not affect the recovery in any way.

Thanks - flashed your bootloader files which got me out of a never ending boot animation issue

j32olger said:
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
Click to expand...
Click to collapse
The bootloop have nothing to do with my bootloader files, they are completley stock from the ota file!
If you installing the new bootloader files on older roms you are asking for troubles.
Boot the watch in bootloader mode and flash the files as described and you watch will work.
Af if it bootlooping run a "Fastboot -w" after flashing.

Greetings, Is the newly released OTA compatible with your rom?

drmcatchr said:
Greetings, Is the newly released OTA compatible with your rom?
Click to expand...
Click to collapse
No ota files will only work with stock untouched rom.

bunny0007 said:
No ota files will only work with stock untouched rom.
Click to expand...
Click to collapse
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!

2k4ever said:
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
Click to expand...
Click to collapse
Have added it today.

I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.

GuiyeC said:
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
Click to expand...
Click to collapse
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.

bunny0007 said:
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
Click to expand...
Click to collapse
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".

GuiyeC said:
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
Click to expand...
Click to collapse
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??

bunny0007 said:
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
Click to expand...
Click to collapse
Yes, it had the boot loader unlocked, and I can't try again flashing the aboot because I can't get it to recovery mode or fast boot mode or anything.

Who can I get the images from?

bunny0007 said:
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.
Click to expand...
Click to collapse
By people, do you mean 1 person ???
Pretty unfair for other, isn't it ?

I am looking for bootloader files for the G Watch R to flash over what I believe to be a corrupt bootloader on my device. It will only boot when on the charging stand, and so far I have only been able to get it to boot to 5.0.1 successfully. Once the device tries to pull down the OTA update it reboots and proceeds to run the update and then it fails and powers off.
Currently I can access fastboot and I can get it to boot a stock recovery and twrp with the 5.0.1 boot.img flashed to my device.

Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.

fnj00 said:
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
Click to expand...
Click to collapse
Hi there ,
Why don't you try this one ??
http://forum.xda-developers.com/g-w...edroid-r-urbane-port-v1-0-0-june-6th-t3128850

Bricked Nexus 6 and cant unlock bootloader

I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?

win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
without enabling oem unlock in the developer options, nope. but you can use the stock recovery to check if a factory reset would help.

Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).

win465 said:
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
Click to expand...
Click to collapse
Had you unencrypted?

Yes, but i flashed backed to stock kernal.

win465 said:
Yes, but i flashed backed to stock kernal.
Click to expand...
Click to collapse
How?

Using the nexus tool kit. After that I locked the bootloader to sideload the update.

win465 said:
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
Click to expand...
Click to collapse
Were you rooted before all of this too?

Nope

Evolution_Tech said:
Were you rooted before all of this too?
Click to expand...
Click to collapse
Nope

win465 said:
Nope
Click to expand...
Click to collapse
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.

Evolution_Tech said:
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Click to expand...
Click to collapse
Thank you for your help

Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.

RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
Click to expand...
Click to collapse
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.

Possible idea
Evolution_Tech said:
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Click to expand...
Click to collapse
There's some more concrete info in the first couple pages, especially regarding our N6's:
http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119
Hope this helps.
I'll keep my eyes open for anything that seems pertinent.
Best of luck

RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
Click to expand...
Click to collapse
I get this error message "system partition has unexpected contents" (Status 7).

win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
Can you fastboot boot twrp recovery? And if that is possible, will twrp flash zips with a locked bootloader?
Edit: I'm almost certain fastboot boot recovery won't work with a locked bootloader. I almost thought I had a good idea.

I am in the same situation. Bootloader locked and no custom recovery nor adb enabled. surprisingly enough, yesterday my phone could boot up but it's stuck now in the configuration process. I cannot access to the settings so I can check usb debugging or oem unlock. I can only access the dialer. my question is: is there anyway to do that with just a dialer code?

Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).

Didgeridoohan said:
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Click to expand...
Click to collapse
Sorry for the noob question but where can I find these OTAs and how to install one of them? Does it require usb debugging to be enabled?

bootloop xt1254 mcg24.251-5-5

Hi.
My cell came in bootloop, I loaded the original rom by adb fastboot, and everything comes out correct in the load, however, follow the bootloop.
In recovery mode does nothing, re-enter bootloop always.
Has it happened to someone else?
p.d. sorry for my english.

chio_chilo said:
Hi.
My cell came in bootloop, I loaded the original rom by adb fastboot, and everything comes out correct in the load, however, follow the bootloop.
In recovery mode does nothing, re-enter bootloop always.
Has it happened to someone else?
p.d. sorry for my english.
Click to expand...
Click to collapse
Are you sure you flashed mcg24.251-5-5 (with extra -5 at the end?) And not the previous (mcg24.251-5-5) which would give you a bootloop? You can't flash a lower version with a locked bootloader.
You're not trying to use the temp root posted in another thread as perpetual temp are you? That also causes bootloop. It's posted here in this forum only for using Sunshine to unlock the bootloader.
Just curious, is your bootloader unlocked?

ChazzMatt said:
Are you sure you flashed mcg24.251-5-5 (with extra -5 at the end?) And not the previous (mcg24.251-5-5) which would give you a bootloop? Your can't flash a lower version with a locked bootloader.
You're not trying to use the temp root posted in another thread as perpetual temp are you? That also causes bootloop. Its only for using Sunshine to unlock the bootloader.
Just curious, is your bootloader unlocked?
Click to expand...
Click to collapse
hi.
I am sure you will try with the rom 5-5
At the end of flashing, everything gave me "OK" (radio, boot, bootloader ...)
I remember if I install the sunshine, but in the end I do not know how to use it. Thinks that maybe that caused the damage.
No, my bootloader is locked.

chio_chilo said:
hi.
I am sure you will try with the rom 5-5
At the end of flashing, everything gave me "OK" (radio, boot, bootloader ...)
I remember if I install the sunshine, but in the end I do not know how to use it. Thinks that maybe that caused the damage.
No, my bootloader is locked.
Click to expand...
Click to collapse
Did you flash an initroot? If you flashed an initroot you'll get it into bootloader and in the ADB & fastboot tools use this command
fastboot oem config fsg-id ""
With two "
Sent from my Droid Turbo using XDA Labs

I'm having the same problem =(
Could you help me to solve this? (It's my wife's phone.... so I'm in trouble kkk)
I did everything... and it still in bootloop. I flashed the mcg24.251-5-5 (with extra -5 at the end).
Please, someone help me!!!

Wellingtonwff said:
I'm having the same problem =(
Could you help me to solve this? (It's my wife's phone.... so I'm in trouble kkk)
I did everything... and it still in bootloop. I flashed the mcg24.251-5-5 (with extra -5 at the end).
Please, someone help me!!!
Click to expand...
Click to collapse
Did you just flash the mcg24.251-5-5 or did you also flash initroot (temp root) file?
See below.
Ricardo2003 said:
Did you flash an initroot? If you flashed an initroot you'll get it into bootloader and in the ADB & fastboot tools use this command
fastboot oem config fsg-id ""
With two "
Sent from my Droid Turbo using XDA Labs
Click to expand...
Click to collapse
Also note there is a space before and between double quotation marks:
beaups said:
fastboot oem config fsg-id " "
Note the space in between the quotes.
Click to expand...
Click to collapse

I just flashed the ROM with the rsd and it get in the bootloop when I restarted the phone.
How can I flash this initiroot? Does it came in the Root's folder? I flash this before the stock room? I'm confused, sorry about that hehehehe.
Thanks for all attention!

if you use the auto#initroot tethered jailbreak tool in before , just run it again.
I get this moto logo reboot problem in few days before, and I read many page for get this answer.
the temp root tool use some system issue , and it will cause this xt1254 boot loop issue , just run the auto#initroot.windows.bat again . phone will reboot to normally.