Related
Current status:
My MS is now stuck in the bootloader screen and couldn't boot into the launcher...When I turn my MS on, it just show the bootloader screen below:
Bootloader
90.78
Code Corrupt
Battery OK
OK to Program
Trasnfer Mode:
USB
Before that, I've seen the Bootloader got some error (?) code too...
err:a5,69,4e,00,3d
I had rooted my MS through the app "Universal androot" (one-button-root app) for a few months. I was getting sick of android 2.1 (plus disappointed with stock 2.2) and so I wanted to try flashing ROM...
I was following the instructions in the forum:
http://forum.xda-developers.com/showthread.php?t=983516
But apparently I might did something wrong (?)....
Anyway, does that mean I brick my milestone?? Is there anyway that I can revert this...?
maybe you have flashed a wrong verson sbf.
Try flash the official 2.0.1 sbf file using RSD.
Bootloader need to reinstall, only official sbf contain bootloader program.
if it works, flash openrecovery, update the software using openrecovery, not RSD.
goodluck.
btw, do you change your baseband after u flash the sbf? if yes, try to do nothing after flashing the roms.
letears said:
maybe you have flashed a wrong verson sbf.
Try flash the official 2.0.1 sbf file using RSD.
Bootloader need to reinstall, only official sbf contain bootloader program.
if it works, flash openrecovery, update the software using openrecovery, not RSD.
goodluck.
Click to expand...
Click to collapse
So I should flash 2.0.1 sbf instead of 2.1?
letears said:
btw, do you change your baseband after u flash the sbf? if yes, try to do nothing after flashing the roms.
Click to expand...
Click to collapse
No, I can do nothing. The flashing progress had never been successful.
It always say fail in RSD lite.
could you sumbit what is shown in RSD lite when it said fail to flash the phone?
RSD status:
Failed flashing process. Failed flashing process. Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE0030040 Command: ERASE (0xE0132040); phone connected
RSD result:
FAIL
And Milestone:
SW Update
In progress...
It keeps on like that for 20+ mins until I unplugged the battery.
Ok so I tried flashing 90.78_2.01recovery_only.sbf (a 4.06mb file)
The first time it ever said success & pass on RSD Lite for me...
But still...I'm stuck in the bootloader screen...
Only now the bootloader shows the following...
Bootloader
90.78
err:a5,69,4e,00,3d
Battery OK
OK to Program
Trasnfer Mode:
USB
it seems you should reinstall the Moto flash driver, or maybe somthing wrong with the usb cable, make sure the computer recognize the phone completely.
if you are using win7 or win visita, make sure you run the RSD lite as administrator.
these tip may help you http://androidforums.com/droid-all-...-failed-flashing-process-0x7100-rsd-lite.html
af424 said:
Ok so I tried flashing 90.78_2.01recovery_only.sbf (a 4.06mb file)
The first time it ever said success & pass on RSD Lite for me...
But still...I'm stuck in the bootloader screen...
Only now the bootloader shows the following...
Bootloader
90.78
err:a5,69,4e,00,3d
Battery OK
OK to Program
Trasnfer Mode:
USB
Click to expand...
Click to collapse
ok, now you could try flashing a full sbf. you can visit http://and-developers.com/sbf:milestone221
i think you need Service version
updated...wrong website.
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!
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
Hi guys is title says its stuck on formation data (via recovery) and if I try wiping emmc (via factory mode) it gets stuck there.
It all started when I shared 3 apps superbeam,lucky patcher and busybox installer .as I was transferring I started installations them both super beam and lucky patcher installed successfully but in busybox got stuck in installation I tried to switch off by power key but didn't work so I powered off by small key (hidden near SD card) then restarted but got stuck on android logo (bootloop) then I booted into recovery for clearing data and caches but it got stucked there . then I booted into factory mode to wipe emmc but also got stuck there ..
Now here I am with uncharged phone , if I charge it I boot in clearing data and got stuck but if I boot in factory mode and try to wipe emmc it get stuck there ... Please help here I really need to revive it
Please guys help here I really don't wanna lose this phone too (without doing anything) and its Ben detected as v com port....
*been
I am able to connect as fastboot but fastboot OEM get_unlock_data not working for some reason it just keep processing
All you can try now is go and flash the factory firmware stock (according previous android version 5.0.2 or 6.0)
Factory firmware flashing doesnt require bootloader to be unlocked so u can try this
ArtRahul said:
All you can try now is go and flash the factory firmware stock (according previous android version 5.0.2 or 6.0)
Factory firmware flashing doesnt require bootloader to be unlocked so u can try this
Click to expand...
Click to collapse
You mean booting in fastboot then flash stock ROM ?? Sorry man I am new to Motorola and thanks for reply .... Any link to guide would be appreciated.
Mak29 said:
You mean booting in fastboot then flash stock ROM ?? Sorry man I am new to Motorola and thanks for reply .... Any link to guide would be appreciated.
Click to expand...
Click to collapse
Link to Motorola Android 6.0 Stock Firmware, this is the perfect guide with all the steps. viola bhava !
ArtRahul said:
Link to Motorola Android 6.0 Stock Firmware, this is the perfect guide with all the steps. viola bhava !
Click to expand...
Click to collapse
Really sorry to bother you again but now I got it what and how to do (since I m new to Motorola) but after I researched I found I can only flash firmware it was built on so I just need to start flashing xt 1068 br version right? (I found firmware too) I just need pro advice please...
ArtRahul said:
All you can try now is go and flash the factory firmware stock (according previous android version 5.0.2 or 6.0)
Factory firmware flashing doesnt require bootloader to be unlocked so u can try this
Click to expand...
Click to collapse
i tried your method but when trying to flash mfastboot.exe flash partition gpt.bin it says "not supported partition"
Mak29 said:
i tried your method but when trying to flash mfastboot.exe flash partition gpt.bin it says "not supported partition"
Click to expand...
Click to collapse
As I previously said (according to your previous android version means when phone is dead then whatever is the android version (5.0.2 or 6.0) you need to flash the files.)
For eg.
If (your phone is on 5.0.2) then
you need to flash stock 5.0.2 firmware.
elseif (your phone is on 6.0) then
you need to flash stock 6.0 firmware.
endif.
Note: Don't flash wrong files, else it's gonna brick the device.
Don't ever downgrade from latest android version to previous.
Thanks
ArtRahul said:
As I previously said (according to your previous android version means when phone is dead then whatever is the android version (5.0.2 or 6.0) you need to flash the files.)
For eg.
If (your phone is on 5.0.2) then
you need to flash stock 5.0.2 firmware.
elseif (your phone is on 6.0) then
you need to flash stock 6.0 firmware.
endif.
Note: Don't flash wrong files, else it's gonna brick the device.
Don't ever downgrade from latest android version to previous.
Thanks
Click to expand...
Click to collapse
Bro I tried that but unable to flash since gpt.bin is not supported partition
Mak29 said:
Bro I tried that but unable to flash since gpt.bin is not supported partition
Click to expand...
Click to collapse
Have you re-tried that.
That was the last and the least option I knew, hope someone else with higher knwldge will help u out in this.
ArtRahul said:
Have you re-tried that.
That was the last and the least option I knew, hope someone else with higher knwldge will help u out in this.
Click to expand...
Click to collapse
If I retry is is not gonna damage phone?
Mak29 said:
If I retry is is not gonna damage phone?
Click to expand...
Click to collapse
Flashing the factory image never damages the device.
So you can try again but with right things right files and carefully.
ArtRahul said:
Flashing the factory image never damages the device.
So you can try again but with right things right files and carefully.
Click to expand...
Click to collapse
Just 1 more thing ..do I need to start direct flash or follow whole process (locking unlocking) command?
Mak29 said:
Just 1 more thing ..do I need to start direct flash or follow whole process (locking unlocking) command?
Click to expand...
Click to collapse
You can start without lock/unlocking BL.
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.