Related
Someone have the logo_signed for Retail EU JB? I just want it to quit this message "Warning Unlocked"
Thanks in advance...
AW: [Q] Help Unlocked Bootloader Message
There's no logo.bmp for jb. We have to life with it. Moto isn't stupid > They upgraded the secure Level of the unlocked Logo and doesn't give us the ability to change it anymore.
Sent from my XT890
HSD-Pilot said:
There's no logo.bmp for jb. We have to life with it. Moto isn't stupid > They upgraded the secure Level of the unlocked Logo and doesn't give us the ability to change it anymore.
Sent from my XT890
Click to expand...
Click to collapse
Yup
Only thing I can think of is downgrading the boot loader... But Motorola stated the radio and boot loader cannot be flashed away from the current required signature, this would include secure version checks I'd assume. Which explains why people bricked trying to RSD back to ICS after doing the full ota update.
Sent from my Galaxy Nexus using Tapatalk 2
So.. I have to live with this horrible message? its sad...
AW: [Q] Help Unlocked Bootloader Message
We can downgrade with RSD if the Bootloader is unlocked. But we have to delete the line gpt.bin and motoboot.
I had to do it by myself today, because my i won't boot into the System or recovery anymore. I tried some stuff today. Switching between the full OTA's.
I was able to switch from EU JB OTA to O2 JB with the Homemades. But after i tried to revert back to EU JB with the same method the OTA aborted by setting simlinks and permissions. No Recovery was working (CWM or Stock) and it stucked @ the warning Logo.
RSD saved my ass and i did an Backup of my Retail EU JB before i started to mess around. So i'm back on track :thumbup:
Sent from my XT890
HSD-Pilot said:
We can downgrade with RSD if the Bootloader is unlocked. But we have to delete the line gpt.bin and motoboot.
I had to do it by myself today, because my i won't boot into the System or recovery anymore. I tried some stuff today. Switching between the full OTA's.
I was able to switch from EU JB OTA to O2 JB with the Homemades. But after i tried to revert back to EU JB with the same method the OTA aborted by setting simlinks and permissions. No Recovery was working (CWM or Stock) and it stucked @ the warning Logo.
RSD saved my ass and i did an Backup of my Retail EU JB before i started to mess around. So i'm back on track :thumbup:
Sent from my XT890
Click to expand...
Click to collapse
do i have to downgrade to ICS and quit this message?
Don't know how exactly but i'm bootloader unlocked and currently running the EU jelly bean (installed via the homemade fastboot) and I don't have the warning message.
crunchie-uk said:
Don't know how exactly but i'm bootloader unlocked and currently running the EU jelly bean (installed via the homemade fastboot) and I don't have the warning message.
Click to expand...
Click to collapse
>installed via the homemade fastboot
There ya go.
Sent from my Galaxy Nexus using Tapatalk 2
mattlgroff said:
>installed via the homemade fastboot
There ya go.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So, with JB, who used homemade fastboot AND DON'T USED OTA (capital to alert others), can still change the logo the same way?
diogo.sena said:
So, with JB, who used homemade fastboot AND DON'T USED OTA (capital to alert others), can still change the logo the same way?
Click to expand...
Click to collapse
Homemade doesn't increase the secure version or use partition tables that the ota update does.
Sent from my Galaxy Nexus using Tapatalk 2
M logo on JB
mattlgroff said:
Homemade doesn't increase the secure version or use partition tables that the ota update does.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So Matt there's no way to change the logo on devices unlocked with OTA JB Retail.EU that have the Unlock Warning Message?
It shows that message coming from a particular sector of the kernel? The BMP code is embedded?
Thx in advance
My fiance has a VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
triton302 said:
My fiance just got her VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
Click to expand...
Click to collapse
have you tried holding vol/power down for 10+ seconds or more?
triton302 said:
My fiance just got her VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
Click to expand...
Click to collapse
If you are within the 14 day return period, return it.
Otherwise post on the Slap My Moto thread and ask for help.
triton302 said:
My fiance just got her VZW Moto X, 16GB. Since mine was a DE, it was simple to get it rooted and whatnot.
So, I tried the guide that was posted to downgrade to the 4.2.2 camera update, got all of the fastboot stuff done successfully and went to reboot it.
NOW... the damn thing won't even turn on. Not even when I plug it into the charger. F*ck.
So... what do I need to do to get this think back up and running? I really don't want to owe her $300 for whatever happened.
Click to expand...
Click to collapse
Can you access the fastboot screen?
Sent on my Gummy running Lenoto X
I got it. The whole "QHSUSB_DLOAD" thing was the issue. Somehow I bricked it while flashing and rebooting.
Went through the steps, now it's alive. However, it won't boot. It'll go into fastboot, but not the OS. So now I have to figure out how to flash the correct stuff.
Alright so I f*cked up BIG TIME.
Now I'm getting the CID error, it won't let me flash anything now.
Any help would be awesome... now I'm probably going to owe her $300.
I thought it wasn't possible to downgrade if you had a locked bootloader...
Sent from my XT1060 using Tapatalk
I'm simply following the steps listed in the various tutorials for rooting 4.4...
All I care about now is getting 4.4 back up and running, but I'm not sure if that's possible anymore.
You might want to check this thread:
http://forum.xda-developers.com/showthread.php?t=2629057
Already did, that gets me back into fastboot, but the phone is no longer able to flash the OS from there. So basically, I'm stuck.
And I just found out that it is two days past the 14-day return period. Fantastic.
you might want to try this:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
triton302 said:
And I just found out that it is two days past the 14-day return period. Fantastic.
Click to expand...
Click to collapse
Are you flashing your carriers sbf firmware? It also needs to be the exact same version that was originally installed ie 4.4
How did you flash it, rsdlite or fastboot? You should be using mfastboot if you manually flashed the firmware, did you get any errors during flashing ?
Sent on my Gummy running Lenoto X
flashallthetime said:
Are you flashing your carriers sbf firmware? It also needs to be the exact same version that was originally installed ie 4.4
How did you flash it, rsdlite or fastboot? You should be using mfastboot if you manually flashed the firmware, did you get any errors during flashing ?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I am using mfastboot using the manual method, no dice. Most of the items i'm flashing give me this error in CMD...
Preflash validation failed
FAILED (remote failure)
On the phone, however, it's telling me this...
Failed to hab check for recovery: 0x39
preflash validation failed for recovery
When I tried to flash the system.img, this...
Failed to hab checkfor system: 0x39
PIV block validation for system failed
Invalid PIV image: system
When having to use the manual method to get into fastboot (http://forum.xda-developers.com/showthread.php?t=2629057), this is the first message that pops up...
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP partition found
Fastboot Reason: Invalid CID
I have a VZW Moto X that I rooted. The process was fairly complicated, so I wrote a tutorial for myself--based on a reddit thread--with all the files I needed to do it in case I needed to do it, again, in the future. I'm not sure if it will help you, but maybe it will. I'll PM you a link.
Lesson learned before marriage. Leave the wife's phone alone seriously though man I hope you work it out.
Sent from my XT1060 using Tapatalk
triton302 said:
I am using mfastboot using the manual method, no dice. Most of the items i'm flashing give me this error in CMD...
Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
I am no expert, but this sounds like whatever you are trying to flash may be corrupted. And maybe mfastboot is corrupted, too.
Redownload everything, check the MD5SUMs and try again.
If the CID partition is messed up or it didn't validate anymore then you're done. You will not be able to flash anything to the phone.
Sell the screen as replacement part on eBay. You'll make more money on the parts of you take it apart than selling it as a whole.
sent via tapatalk
triton302 said:
I am using mfastboot using the manual method, no dice. Most of the items i'm flashing give me this error in CMD...
Click to expand...
Click to collapse
instead of fastboot, have you tried flashing the entire ROM via RSDLite?
KidJoe said:
instead of fastboot, have you tried flashing the entire ROM via RSDLite?
Click to expand...
Click to collapse
Rsd lite is your best bet
Sent from my XT1056 using xda app-developers app
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
capricorn85 said:
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
Click to expand...
Click to collapse
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
skeevydude said:
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
Click to expand...
Click to collapse
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
capricorn85 said:
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
Click to expand...
Click to collapse
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
skeevydude said:
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
Click to expand...
Click to collapse
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
capricorn85 said:
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
Click to expand...
Click to collapse
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
skeevydude said:
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
Click to expand...
Click to collapse
Came here after trying all that
Tried manually flashing but the phone returns FAIL on EVERY command, same with myth tools it executes but nothing really happen in the phone, dont know what went so wrong with the OTA
i am just confused if i should let it be or keep trying until i find a solution
COuld battery charge level be the problem, when it all started it was more than 70 percent and i didnt keep it on for long. it says battery ok but dont know whats the exact battery level as fastboot oem battery-status or voltage level are also restricted
Well, it seems that skeevydude told you all I want to say
Solved: Using Nextel (Mex Retail)
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
capricorn85 said:
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
Click to expand...
Click to collapse
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
palmbeach05 said:
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
Click to expand...
Click to collapse
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
capricorn85 said:
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
Click to expand...
Click to collapse
I told ya Mex Retail would work....
skeevydude said:
I told ya Mex Retail would work....
Click to expand...
Click to collapse
It is worth a shot for me too!
I have RSDLite and attempted to flash. It gives me error about unknown <getvar>. Deleted those line(s) according to another post I found.
Then everything passes but I am stuck on the Fastboot Flash Mode?
God I will be happy when uncle same gets through with my son so he can help is ole man, lol.
---------- Post added at 06:14 PM ---------- Previous post was at 05:55 PM ----------
PROGRESS! I recalled skeevydude saying to stay alway from front USB ports and moved to back one and I now also have the Mex Retail version working. What a relief.
Now the bearing question is should I move on to another version like carbon or holoblur?
If ok to stay with this version, meaning will NOT get busted out by AT&T by using hotspot?
What do you recommend skeevydude?
Thank you so so so much.
Woody
Mexico Retail link
can someone provide me any link of Mexico Retail stock rom? Please.
ErickST18 said:
can someone provide me any link of Mexico Retail stock rom? Please.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=7
quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Thanks man
Pleas hlep me for alive my set thanks advance
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
shamshadhashmi said:
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
Click to expand...
Click to collapse
Please stop whining and being pathetic and actually search for moto sbf files. A new site popped up and comes up very easily. No need to make us die of laughter at someone begging for an sbf like a guy begging to get with a girl b/c he's thirsty. Smh lol
Sent from my ATRIX HD using XDA Free mobile app
need working link of file
i search everywhere but no file found i need file if anybody have so please share with me or upload thanks
quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Need 4.1.1..where can I find it? Tyvm
I'm not entirely sure how to troubleshoot this problem, but here goes...
I was charging my phone and it just attempted to reboot itself. I saw it in the corner of my eye and figured "oh well, let it finish". It never finished, and it seems it won't get past the boot screen.
I entered Fastboot mode. Device is still locked. It also states that the charger is connected, regardless of whether it is or isn't. Additionally, I cannot access Recovery or Factory, instead receiving the following error:
No valid PIV block in SP for system
piv validation failed (system)
Boot up failed
Click to expand...
Click to collapse
Anyone know what's going on here? Did my phone really just brick itself?
Edit: I apologize if my first post goes against any of the rules here. I've searched for a similar thread, but mostly found cases in which people failed to root and are receiving this message. I have some minor experience with rooting a Motorola Droid, Verizon Droid Incredible 2 and a Nexus 10. I was hoping to do the same with this phone, but it came with 4.4.2 already installed.
Don't take my word for it, but if you Google no valid piv moto x....it doesn't look good.
Then again if you read through some of the stuff you find, even other phones with issue....perhaps you'll stumble on a fix.
Last moto x thread I read with that error was solved by a replacement unfortunately.
Hope you find a fix, or can send it in. Your warranty should be in tact if its locked and unrooted.
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
SymbioticGenius said:
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
Click to expand...
Click to collapse
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
samwathegreat said:
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
Click to expand...
Click to collapse
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
ed0421 said:
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
Click to expand...
Click to collapse
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
samwathegreat said:
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
Click to expand...
Click to collapse
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
I didn't have the same issue but I did just RMA my X for another reason and got a brand new 2014 X, was expecting a refurbished phone and was surprised to get a new one. They shipped it next day air that same day which also surprised me.
ed0421 said:
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
Click to expand...
Click to collapse
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
samwathegreat said:
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
Click to expand...
Click to collapse
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
ed0421 said:
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
Click to expand...
Click to collapse
Really dumb question but when flashing... Are you using the command fastboot or mfastboot?
I had all kinds of errors and thought I was bricked too until I used mfastboot. Then everything went perfect. Moto uses their own version of fastboot.exe that's included in the sbf/fxz or whatever they are called now. Even the XML file states fastboot as the command but never worked for me. Just a thought.
Hey, i would like to update from ics to jb but what is the difference between using an ota and flashing a firmware from the sbf droid developers site or even here?
http://forum.xda-developers.com/showthread.php?t=2239706
I have bootloader unlocked and ics rooted already if that makes any difference.
I recomend a lot install the jb firmware and not usibg the ota service, for avoid phone bricks, also, if you install the jb firmware with rsd lite, you have the posibility to return to ics without brick (i dont know why you will return but its a extra)
Enviado desde mi XT890 mediante Tapatalk
Marco Lomas said:
I recomend a lot install the jb firmware and not usibg the ota service, for avoid phone bricks, also, if you install the jb firmware with rsd lite, you have the posibility to return to ics without brick (i dont know why you will return but its a extra)
Enviado desde mi XT890 mediante Tapatalk
Click to expand...
Click to collapse
That's not entirely true that u cant go back when u have installed it by OTA update. With rsd and with ota update u will upgrade some files exactly the same way with both methods, that must not be downgraded. Those files are the bootloader and partition files aka motoboot, gpt, dns, ifwi and (bos?).
I recommend if u ever want to downgrade, flash all things manually. Flash the boot, recovery and system partitions only when going from JB to ICS and erase the cache/data partition or u will get a software-brick. Is fixable though.
But to go from ICS to JB (upgrade), I go with Marco for the rsd flash. Especially when rooted i think. There is a small change that u will relock the bootloader, but i don't know that for sure. However it should work with OTA in theory if u have stock recovery...
Thanks alot guys I updated with rsd lite and it worked my bootloader is still unlocked, but i noticed the when i boot up, the initial screen changed from the motorola logo with "bootloader unlocked" written, to a sort of warning notification about the bootloader being unlocked.
Hazou thats exactly what i wanted to know actually because i was confused about the downgrading process, seeing that many have hard-bricked. One more question, you say i must flash those files individually, but what about restoring a nandroid backup i made when on ics?
tangonegr said:
Thanks alot guys I updated with rsd lite and it worked my bootloader is still unlocked, but i noticed the when i boot up, the initial screen changed from the motorola logo with "bootloader unlocked" written, to a sort of warning notification about the bootloader being unlocked.
Hazou thats exactly what i wanted to know actually because i was confused about the downgrading process, seeing that many have hard-bricked. One more question, you say i must flash those files individually, but what about restoring a nandroid backup i made when on ics?
Click to expand...
Click to collapse
No problem, as long as u don't touch any of those bootloader files there is almost no chance that things can go wrong.
Verstuurd van mijn GT-P5110