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!
Hello guys,
When I tried to update my Moto X for AT & T to RETAIL BR "VICTARA_RETBR_XT1097_5.1_LPE23.32-14.2_cid12_CFC.xml" version, now only comes into fastboot boot and says "Bad check failed for boot, downgraded version for boot, failed to validate boot image ".
Then I thought that would solve flashing with "VICTARA_ATT_XT1097_5.1_LPE23.32-21.2_cid1_CFC.xml" and I found this legend now, "downgraded version for primary_gdt"
Any idea how to fix it?
Thank you in Advance.
mseverini said:
Hello guys,
When I tried to update my Moto X for AT & T to RETAIL BR "VICTARA_RETBR_XT1097_5.1_LPE23.32-14.2_cid12_CFC.xml" version, now only comes into fastboot boot and says "Bad check failed for boot, downgraded version for boot, failed to validate boot image ".
Then I thought that would solve flashing with "VICTARA_ATT_XT1097_5.1_LPE23.32-21.2_cid1_CFC.xml" and I found this legend now, "downgraded version for primary_gdt"
Any idea how to fix it?
Thank you in Advance.
Click to expand...
Click to collapse
Sorry but there is no solution to that error. You upgraded your bootloader and partition table to the ones from 6.0 and it is impossible to downgrade those. Do not under any circumstances take an OTA or it could cause a hard brick which is impossible for us to fix.
As far as getting your phone working, flash that firmware file you have. When you get to the errors about downgraded version, just ignore them and continue. You will need to erase cache and data to get back to 5.1. So make sure that you do:
fastboot erase cache
fastboot erase userdata
If all goes well your phone should be on 5.1 and working. But as I said before, taking an OTA now would most likely cause a permanent hard brick.
Sent from my XT1095 using Tapatalk
AGISCI said:
Sorry but there is no solution to that error. You upgraded your bootloader and partition table to the ones from 6.0 and it is impossible to downgrade those. Do not under any circumstances take an OTA or it could cause a hard brick which is impossible for us to fix.
As far as getting your phone working, flash that firmware file you have. When you get to the errors about downgraded version, just ignore them and continue. You will need to erase cache and data to get back to 5.1. So make sure that you do:
fastboot erase cache
fastboot erase userdata
If all goes well your phone should be on 5.1 and working. But as I said before, taking an OTA now would most likely cause a permanent hard brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
motoboot v60.16 in retailbr and att,
gpt.bin both v5.1,
when flashed retail brazil stopped in boot.img, then can´t flash gpt.bin of att version.
I don't understand what was caused the downgrade.
Thank you in advance.
Sorry for my english
mseverini said:
motoboot v60.16 in retailbr and att,
gpt.bin both v5.1,
when flashed retail brazil stopped in boot.img, then can´t flash gpt.bin of att version.
I don't understand what was caused the downgrade.
Thank you in advance.
Sorry for my english
Click to expand...
Click to collapse
I did the same thing, the problem was flash de cellphone with the bootloader locked, did you found a solution ?
At&t xt1097
I have the same problem, i flashed Brazilian XT1097 firmware on my AT&T XT1097 and i can't power on my device, please help us to flash correct firmware and bootloader
samkhara said:
I have the same problem, i flashed Brazilian XT1097 firmware on my AT&T XT1097 and i can't power on my device, please help us to flash correct firmware and bootloader
Click to expand...
Click to collapse
Which firmware did you have until the flash? you need to download the last firmware with the Stagefright patch and re-flash it.
lucasdursi said:
Which firmware did you have until the flash? you need to download the last firmware with the Stagefright patch and re-flash it.
Click to expand...
Click to collapse
I had before flash
System Version: 23.16.9.victara_att_att.en.US.att
Build namber LPE23.32-21.9
can you explain to me how can i flash correct firmware and return to stock?
samkhara said:
I had before flash
System Version: 23.16.9.victara_att_att.en.US.att
Build namber LPE23.32-21.9
can you explain to me how can i flash correct firmware and return to stock?
Click to expand...
Click to collapse
You need to re flash it with this firmware, is the last one with the Stagefright Patch: http://www.filefactory.com/file/705qta2o0wrt/VICTARA_ATT_XT1097_5.1_LPE23.32-21.9_cid1_CFC.xml.zip
Before the flash, power up you phone and put this command: fastboot oem fb_mode_clear
Then, turn it off amd be sure to power up your phone in FASTBOOT mode pressing the Power Button and Volume Down at the same time, when the phone boots, connenct it to the PC and flash it with RSD Lite like you did with the Brazilian firmware.
I hope it works! :good:
lucasdursi said:
You need to re flash it with this firmware, is the last one with the Stagefright Patch: http://www.filefactory.com/file/705qta2o0wrt/VICTARA_ATT_XT1097_5.1_LPE23.32-21.9_cid1_CFC.xml.zip
Before the flash, power up you phone and put this command: fastboot oem fb_mode_clear
Then, turn it off amd be sure to power up your phone in FASTBOOT mode pressing the Power Button and Volume Down at the same time, when the phone boots, connenct it to the PC and flash it with RSD Lite like you did with the Brazilian firmware.
I hope it works! :good:
Click to expand...
Click to collapse
I can not flash with RSD Lite , because my bootloader is locked and can't be unlocked , because it can't officially unlcok AT&T XT1097 bootloader. i try to flash my phones software but i can not power on it
samkhara said:
I can not flash with RSD Lite , because my bootloader is locked and can't be unlocked , because it can't officially unlcok AT&T XT1097 bootloader. i try to flash my phones software but i can not power on it
Click to expand...
Click to collapse
Do you speak spanish ?
Yes you can! I have the same Moto X and i did it that way.
It does not matter if you have the bootloader lock, to flash with RSD you don't need to unlock the bootloader.
You actually try to flash the phone with the lastest firmware ?
lucasdursi said:
Do you speak spanish ?
Yes you can! I have the same Moto X and i did it that way.
It does not matter if you have the bootloader lock, to flash with RSD you don't need to unlock the bootloader.
You actually try to flash the phone with the lastest firmware ?
Click to expand...
Click to collapse
can you send me a tutorial how can i flash it via RSD lite i can not recognize my phone via this software
samkhara said:
can you send me a tutorial how can i flash it via RSD lite i can not recognize my phone via this software
Click to expand...
Click to collapse
- Download the latest Motorola drivers for Windows: http://www.motorola.com/getmdmwin
- Download the latest firmware for your phone.
- Install drivers and RSD Lite to your PC.
- Make sure your battery at least 80% before we proceed.
- Turn off your phone and press both volume keys and power on. You'll enter bootmenu. (IMPORTANT!)
- Connect your phone to PC and your PC will detect and install the drivers automatically.
- Open RSD Lite and click ... beside filename. Browse to the firmware and double click it. A menu will popup and choose "uncompress and start flashing".
Hello
I TRY TO FLASH VIA RSD LITE , but i got error FAILED, VERSION DOWNGRADED FOR PRIMARY_GPT
CAN YOU TELL ME WHAT CAN I DO?
samkhara said:
Hello
I TRY TO FLASH VIA RSD LITE , but i got error FAILED, VERSION DOWNGRADED FOR PRIMARY_GPT
CAN YOU TELL ME WHAT CAN I DO?
Click to expand...
Click to collapse
You try with this firmware: VICTARA ATT XT1097 5 1 LPE23 32-21 9 cid1 CFC ????
Exactly, because you need the latest firmware for your phone. When you try to flash the Brazil Firmware, you already have the latest firmware, and now the flash fail because you need a new one...
A days ago, I receive a new update, you need to wait for the new firmware with this last update, and then try to flash it, be patient
lucasdursi said:
You try with this firmware: VICTARA ATT XT1097 5 1 LPE23 32-21 9 cid1 CFC ????
Exactly, because you need the latest firmware for your phone. When you try to flash the Brazil Firmware, you already have the latest firmware, and now the flash fail because you need a new one...
A days ago, I receive a new update, you need to wait for the new firmware with this last update, and then try to flash it, be patient
Click to expand...
Click to collapse
OK, where can i find this firmware ?
samkhara said:
OK, where can i find this firmware ?
Click to expand...
Click to collapse
You need to wait for the release, check this page, be patient: http://www.filefactory.com/folder/dd05c058d3ff8dbe
lucasdursi said:
You need to wait for the release, check this page, be patient: http://www.filefactory.com/folder/dd05c058d3ff8dbe
Click to expand...
Click to collapse
I have tried it and it works.
Thanks.
lucasdursi said:
Do you speak spanish ?
Yes you can! I have the same Moto X and i did it that way.
It does not matter if you have the bootloader lock, to flash with RSD you don't need to unlock the bootloader.
You actually try to flash the phone with the lastest firmware ?
Click to expand...
Click to collapse
can i unlock bootloader of moto x 2 at&t model
Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras
rassle said:
Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras
Click to expand...
Click to collapse
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
im actually trying with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml which has the title of XT890_emara-user 4.1.2 9.8.2I-50_SMI-26 1358465787 release-keysSUNRISE_SMB_REV30_V2_R3_1251.B
i do have problems of finding stock roms as most links are pointing to sbf droid developers (cant post link due to beeing new) which is dead for me.
ive used shadows mirror list, but its only showing non-4.1.2 versions for me. however, im not quite sure which firmware was one the phone before *sorry*
by commands of the xml file u mean the xml file which is contained in the "firmware" downloads for the XT890?
Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/
rassle said:
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/
Click to expand...
Click to collapse
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root
Hazou said:
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root
Click to expand...
Click to collapse
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?
rassle said:
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?
Click to expand...
Click to collapse
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support
rassle said:
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support
Click to expand...
Click to collapse
Good that it worked. The message will remain there. I don't know how to fix that issue. But I don't think it is a huge issue, but its annoying.
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.