I apologize in advance if this all seems basic, but I've googled and googled and I'm not getting anything but confused. My girlfriend has a Photon Q that she OTA upgraded to Jelly Bean, and she absolutely hates it. She desperately wants to go back to ICS. Is that possible, and if so how can I do it?
Use the FXZ thread.
There's the getvar lines to remove, and there's some additional lines which need to be removed if you're downgrading.
Edit - this post may help you with the additional lines that need to be removed in order to downgrade.
arrrghhh said:
Use the FXZ thread.
There's the getvar lines to remove, and there's some additional lines which need to be removed if you're downgrading.
Edit - this post may help you with the additional lines that need to be removed in order to downgrade.
Click to expand...
Click to collapse
Okay, so I think I get it for the most part. I download RSD Lite and the proper FXZ file for what I'm downgrading to, which would be 4.0.4 in my case since I'm going ICS. I edit the XML file to remove the line <step operation="getvar" var="max-download-size" /> and should be good to go. Assuming I'm correct with my understanding, I'm still confused about one three. There appear to be three different FXZ for 4.0.4, I'm not sure which of the three I should use.
dereckbarker said:
Okay, so I think I get it for the most part. I download RSD Lite and the proper FXZ file for what I'm downgrading to, which would be 4.0.4 in my case since I'm going ICS. I edit the XML file to remove the line <step operation="getvar" var="max-download-size" /> and should be good to go. Assuming I'm correct with my understanding, I'm still confused about one three. There appear to be three different FXZ for 4.0.4, I'm not sure which of the three I should use.
Click to expand...
Click to collapse
Well since you're downgrading there are some additional lines which you have to remove from the XML file. Read my edit, I linked you to another post which talks about that.
As for which one to download, that is up to you. Motorola released 3 OTA's for ICS, and one for JB. I have no clue which one was being used previously on your device, but it's likely ASA-14 as it was the last ICS firmware.
arrrghhh said:
Well since you're downgrading there are some additional lines which you have to remove from the XML file. Read my edit, I linked you to another post which talks about that.
As for which one to download, that is up to you. Motorola released 3 OTA's for ICS, and one for JB. I have no clue which one was being used previously on your device, but it's likely ASA-14 as it was the last ICS firmware.
Click to expand...
Click to collapse
Well it appear I may be SOL anyways as I can't seem to get into recovery mode. Upon starting up and pressing power + Vol up I get nothing but a screen of an android with an ! coming out of its chest for about a minute or two and then the phone reboots. Damn thing isn't rooted or anything, it's a stock phone.
dereckbarker said:
Well it appear I may be SOL anyways as I can't seem to get into recovery mode. Upon starting up and pressing power + Vol up I get nothing but a screen of an android with an ! coming out of its chest for about a minute or two and then the phone reboots. Damn thing isn't rooted or anything, it's a stock phone.
Click to expand...
Click to collapse
That's stock recovery. You need to put the phone in fastboot mode, not recovery mode.
Code:
adb reboot bootloader
should bring you to fastboot mode. Or, use cam+power to get the menu when the phone turns on.
arrrghhh said:
That's stock recovery. You need to put the phone in fastboot mode, not recovery mode.
Code:
adb reboot bootloader
should bring you to fastboot mode. Or, use cam+power to get the menu when the phone turns on.
Click to expand...
Click to collapse
Boy you must be real sick of hearing from me already. Even in fastboot mode, the phone doesn't show up under my list of devices in RSD Lite
dereckbarker said:
Boy you must be real sick of hearing from me already. Even in fastboot mode, the phone doesn't show up under my list of devices in RSD Lite
Click to expand...
Click to collapse
Nah, I'm here to help.
So do you have fastboot functioning?
What is the output of
Code:
fastboot devices
arrrghhh said:
Nah, I'm here to help.
So do you have fastboot functioning?
What is the output of
Code:
fastboot devices
Click to expand...
Click to collapse
Absolutely nothing. The command prompt gives me a blank space.
dereckbarker said:
Absolutely nothing. The command prompt gives me a blank space.
Click to expand...
Click to collapse
Well, I'd guess you don't have adb or fastboot setup.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
If you'd like, I can help you out "live" on IRC. Freenode, I'm in a few rooms... I spose #oudhitsquad is the best.
Thanks.
Okay I figured out why I wasn't getting anything to show in RSD, I didn't have the stupid phone unlocked yet. I do now, and everything seemed to be working out until I actually tried flashing. I get the error:
Failed flashing process. 1/21 flash partition "gpt_main0.bin" -> Phone returned fail.
Click to expand...
Click to collapse
The lines I deleted were two instances of
<step operation="oem" var="fb_mode_set" />
Click to expand...
Click to collapse
and two instances of
<step operation="getvar" var="max-download-size" />
Click to expand...
Click to collapse
The error on the phone itself says
preflash validation failed for GPT, downgraded security version
Click to expand...
Click to collapse
From that other guy's post, it looks like you need to also remove the gpt_main0.bin lines.
Danger!!
Maybe it's too late for you as it's for me now: but doing this erased my IMEI data. I hope nobody else try this.
arrrghhh said:
From that other guy's post, it looks like you need to also remove the gpt_main0.bin lines.
Click to expand...
Click to collapse
msxisalive said:
Maybe it's too late for you as it's for me now: but doing this erased my IMEI data. I hope nobody else try this.
Click to expand...
Click to collapse
No, I never tried to downgrade to ICS... I still have a stock backup of ICS, never saw the need to flash it.
Sorry, I misunderstood the original problem.
In my case, my phone came already with jelly bean, so I did'nt have an ICS backup. I wanted to downgrade in order to get MSL number, and ended with a phone with IMEI 00000... :crying:
Fortunately I did a bull nandroid backup before that, so I restored it and my IMEI came back. :victory:
Edit: Finally I could downgrade without losing IMEI using TWRP and the ICS backup from this thread.
With that, I could get my MSL and then return to CM11.
arrrghhh said:
No, I never tried to downgrade to ICS... I still have a stock backup of ICS, never saw the need to flash it.
Click to expand...
Click to collapse
Related
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
biupil said:
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
Click to expand...
Click to collapse
First of all your phone is fine, since it is booting. You can continue to choose normal power up and be fine.
To fix you need to flash the fxz and replace the files to allow you to do it after being on 2.3.6. see here http://forum.xda-developers.com/showthread.php?t=1396650
unfortunately i cant flash the fxz it says failed all the time, its like its locked, i tried.
biupil said:
unfortunately i cant flash the fxz it says failed all the time, its like its locked, i tried.
Click to expand...
Click to collapse
did you replace the files
Sent from my MB865 using xda premium
yes my friend and this is what it says
biupil said:
yes my friend and this is what it says
Click to expand...
Click to collapse
hmm. Is your phone the AT&T version or one of the international ones? Make sure you are using the correct fxz file for your device, that is most likely the problem with the step it is failing on find a list here: http://sbf.droid-developers.org/edison/list.php
Go to settings- about phone and look at system version. That should tell you what version you are. it will be 55.13.25.MB865.VERSION.... or something like that, you should be able to tell which you are
it is At&t
system version 55.11.16.MB865.ATT.en.US i have downloaded the
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.Zip that is for At&t is that correct?
biupil said:
it is At&t
system version 55.11.16.MB865.ATT.en.US i have downloaded the
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.Zip that is for At&t is that correct?
Click to expand...
Click to collapse
yep that is the correct one. have you ever tried to flash a different one? that may have messed something up.
Try this, it may work. It is just a script that runs the fastboot comands. Extract it and run the stock restore file in it:
https://docs.google.com/open?id=0B_F787JD56X9SjZSUlljQ2ZYdFk
yes i have tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc as i said before. I will try the one that you told me and i will inform you...
biupil said:
yes i have tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc as i said before. I will try the one that you told me and i will inform you...
Click to expand...
Click to collapse
that is probably the problem. there are some files you will have to skip flashing in order to make it work I think. PM jimbridgman (i think thats how you spell it and ask him for help)
nope still the same lets hope that jimbridgman can help
lkrasner thank you for your time.
biupil said:
nope still the same lets hope that jimbridgman can help
lkrasner thank you for your time.
Click to expand...
Click to collapse
he should be able to just link him to this thread and be nice.
I also just replied to your PM, but I wanted to put this here as well, so others can also see it.....
This just a theory, since no one has done this yet, so we might have to try a few things to get it right
my first guess is to do this:
Take the following files from the update that you flashed and replace their counterparts in the 2.3.5 fxz, and update the md5 sums in the xml file, you can google for a windows md5sum executable for windows.
Here is a link to a good place to find the m5sums for windows7:
http://www.walkernews.net/2009/12/26/how-to-check-md5-checksum-in-windows-7/
files you will need from the leak:
cdt.bin
device_tree.bin
lbl
now once you have them in the same folder as the rest of the 2.3.5 fxz, use that exe I told you grab to get their md5 sums, and replace those numbers in the xml file in the 2.3.5 fxz, this should get you back to 2.3.5, in theory.
Jim
wtf my brain hurts already lol. I will try to do it in the morning i will inform you for the results.
i realy understand nothing at all of this. unfortunatly my phone will stay as it is.
biupil said:
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
Click to expand...
Click to collapse
download the fxz and replace files from noob thread. extract and replace files, after replacing erase third line
i.e <step operation="flash" partition="mbmloader" filename="mbmloader.bin"MD5="9D1958ED3F5E971FF079B195E338BA86" />
from InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.xml and flash it using rsd lite it will definetely work as i had the same problem
thanks man i just love u my phone works perfectly
Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.
ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.
kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.
kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style
Failed all the way.
kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.
I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:
Did you try the manual steps that I posted in my links?
i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.
What do you mean with recovery?
kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.
Keeps saying it can't mount anything.
kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen
So the usual things has happened.. I have looked many different places, forums, and posts and the closest thing I have found was this thread.
http://forum.xda-developers.com/showthread.php?t=2423716
However it didnt help me at all so now I am posting this to see if there is an angel out there that can help me.
He is the problem.
1. It will show this if I plug it in to my PC but I cant turn on the device by its self.
"AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure"
2. It doesnt charge.. I dont think
3. When I hold the Vol- and PWR for 10 ten then add the Vol+ it sometimes will go to the bootloader and then it will boot.
Can I fix this to not show this message every time?
Thanks for your time
-Avethepizzaman
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
K I have it charged..
Avethepizzaman said:
K I have it charged..
Click to expand...
Click to collapse
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
bweN diorD said:
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
Click to expand...
Click to collapse
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Avethepizzaman said:
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Click to expand...
Click to collapse
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
bweN diorD said:
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
Click to expand...
Click to collapse
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Avethepizzaman said:
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Click to expand...
Click to collapse
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
bweN diorD said:
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
Click to expand...
Click to collapse
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
That's a lower version. Unless you unlocked your bootloader, which it appears you haven't, you cannot downgrade from 182.46.15. If you didn't unlock your bootloader (which I'm assuming because in your first post, you showed that the status said "locked" in fastboot mode), then you have no way to root, unlock the bootloader nor downgrade. You can only reflash the latest which is 182.46.15.
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
ok, i was tired and forgot about the "tz".
to avoid any further confusion, download the firmware from here and replace the xml file with this one. i already edited it. then flash again.
now that we have all the facts straight, and files in line, it should go fine this time.
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Avethepizzaman said:
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Click to expand...
Click to collapse
wow, your phone is being a pita lol
follow the instructions here to fix that.
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Avethepizzaman said:
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Click to expand...
Click to collapse
np! happy to help