Database Info

2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX

Hey everyone,
Short intro:
If you updated to 2.3.6 and got bootloop/blackscreen, and then tried to downgrade to 2.3.5 and stuck with FlashBoot screen, with something like:
Invailid CG OTV (CG: cdrom): Invalid SP Data
Invailid CG OTV (CG: webtop): Invalid SP Data
or
Invailid CG Version (CG: boot):
Invailid CG Version (CG: recovery):
Then this topic is for you.
I got into same situation couple of days ago and bricked my phone. However, 2.3.5 fast boot files with replaces part didnt work out for me. And original 2.3.6 patch gave me something to think about. Allright no more words. Just the steps to fix it.
Special thanks to ri4naire for nandroid backup of the 2.3.5 - 2.3.6 rom. Unfortunately I didnt find there files I was looking for but the backup structure gave me roadmap for future findings.​
Recovering from: Invalid CG Version - Fast way (no 2.3.5 flashing)
1. Go and download moto-fastboot here (fastboot command from sdk will work too)
2. Download boot.img from here and put it in the folder with moto-fastboot
SHA1: 4add80cb4d5d54bc382ac1cb5c9bed3602853dce (same as in 2.3.6)
3. Boot your moto in FlashBoot mode (vol up + vol down + power)
4. Open command prompt and go to the above folder
5. Check if your device is present : moto-fastboot.exe devices
6. Next type: moto-fastboot.exe flash boot boot.img
You should see:
sending 'boot' (8192 KB)... OKAY [ 0.760s]
writing 'boot'... OKAY [ 1.455s]
Then reboot and you device will boot up..
Standard recovery is not working in this way, so no factory resets from inside the device, no reboots to recovery, no updates from OTA.
For recovery use Atrix 2 Bootstrap.
And from Bootstrap do a factory reset, as after update your cache partition maybe only 5 mb instead of about 700mb.​
Recovering from: Invalid CG Version (long way) or
Reflashing to 2.3.5 and then going to 2.3.6 if standard method didnt work
1. Go to Beginners guide here and download 2.3.5 InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip
2. Download boot.img from here and put it in the above zip file (replace old one)
3. Download replace.zip and put all the files except .xml into the above zip file.
4. Download xml fileand replace original one in the zip.
5. Go to FastBoot mode and flash resulting zip file via RSD Lite.
Once it is done, you will get 2.3.5 Rom with normal cache (no factory reset needed this time but recommended)
Standard recovery doesnt work here too.
Now its time to do an update to 2.3.6
If you need root in 2.3.6: edit mount_ext3.sh as described in noob guide.
6. Get Blur_Version.55.11.16.MB865.ATT.en.US.zip
7. Download modified updater-script from here link
and put it in above file in \META-INF\com\google\android (replace old one)
Use 7-zip or the update file will not be read by the phone.
Put it on SDcard
(the script difference is that it doesnt delete recovery from system, doesnt update lbl, cdt.bin,device_tree.bin and doesnt update motorola steflash file, probably this is why it reports old baseband, but i dont know how to make it update)
8. Get BootStrap and go into recovery, apply this update from sdcard.
Upon rebooting you will have 2.3.6 Rom with working stock recovery
Notes:
Root can be obtained by editing mount_ext3.sh as described in noob guide.
And BaseBand version reports to be a 2.3.5 version. Maybe it cant be updated for some reason this way or it just reports wrong version being a new one. Weird.
​
Hope it will help someone fix their phones and give some ideas for updates.
Dont forget to click Thanks on this post and ri4naire's post below if you found this info useful
​
CYA

I'm having the same issue but I've been able to use RSD to flash the modified FXZ used to return to 2.3.5 if you've ever updated. It won't update to 2.3.6 but I have a functional phone, albeit a bit crippled.
Sent from my MB865 using Tapatalk

ri4naire said:
I'm having the same issue but I've been able to use RSD to flash the modified FXZ used to return to 2.3.5 if you've ever updated. It won't update to 2.3.6 but I have a functional phone, albeit a bit crippled.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
May I ask you to install Atrix 2 Bootstrap recovery from here
http://forum.xda-developers.com/showthread.php?t=1346977
And do a nandroid backup from recovery. It will dump your system,boot,recovery partitions to sd-card. Maybe it will be enough to flash them to mine
Thanks

Alright, I'm going to reflash so it doesn't have any identifying material and then I guess I'll try uploading it.
I wasn't aware nandroid backed up everything like that, my last phone had some nice automated software. Do you think someone could dump us a full stock functional backup we could then flash?
Sent from my MB865 using Tapatalk

I guess so.
I checked flashboot files for 2.3.5 and the latest OTA update.
The update is just a patch and applied in the same way as custom roms and tweaks.
For example. boot.img from 2.3.5 is patched to 2.3.6 using binary difference with the latest. So 2.3.6 replaces only the part of data in 2.3.5
bsdiff/bspatch utility can do it and its crossplatform but I'm stuck at IMGDIFF2 protocol which is described well on developer resources. however I dont have enough experience to unpack it, take required part, patch it and pack it back
But yes, I guess it is really possible to make a semi-official flashboot file for 2.3.6
http://www.netmite.com/android/mydroid/donut/build/tools/applypatch/imgpatch.c
imgdiff example here for donut eclair

I mean, that would be fantastic, but all I'm asking is can we copy someone else's /mnt/sdcard/clockworkmod/backup/* into ours and then restore from that?

ri4naire said:
I mean, that would be fantastic, but all I'm asking is can we copy someone else's /mnt/sdcard/clockworkmod/backup/* into ours and then restore from that?
Click to expand...
Click to collapse
I really hope it is possible.
Thats why I need nandroid backup to try to flash new boot and recovery images to mine.
Because downgrading to 2.3.5 using the method mentioned here didnt work me and my phone says recovery / boot images are wrong version. Maybe this will help...

have the same problem, when try go from 2.3.6 back to 2.3.5, described method with file change don't help. phone loaded in fastboot with CG errors

Shaliuno said:
And do a nandroid backup from recovery. It will dump your system,boot,recovery partitions to sd-card. Maybe it will be enough to flash them to mine
Thanks
Click to expand...
Click to collapse
Shoot me a PM with an email and I can YouSendIt.
Would someone else though, please, upload a stock functional backup?

ri4naire said:
Shoot me a PM with an email and I can YouSendIt.
Would someone else though, please, upload a stock functional backup?
Click to expand...
Click to collapse
Email sent Hows the progress?

Ok, I had to sign up for a Pro account but I think it's going to be worth it. Expect an email in the next half hour or so.
Whoever wants to send me their stock working backup can send me a PM with their email and I'll give them write permissions on a folder in my account. I'm not above trying to bribe you all with beer, cookies, and thanks.

Got the file. Thanks.
I'll go checking what it contains. Will post up with any results later.

IT WORKS! Updated first post! Check this out!

Q'apla, Shaliuno! I hope this gets some people back on their feet, I'm very pleased to have been able to help.
I just want to make a point of clarification, though; the files I sent you are not 2.3.6, they're modified 2.3.5 based on the directions for downgrading. I'm still interested in getting my hands on a backup that has a functional recovery image, please PM me if you need a place to post said backup, I know it's big.

Do this, phone boot up, thank you very much!

Thanks guys for the work found myself in the same situation and your directions worked! I'm sorry if it was my directions that got you here, but I'm very thankful you had a working solution or I would have had a dead paperweight

Updated the guide.
Now modified 2.3.5 can be upgraded to 2.3.6 + root.
Maybe some parts of the guide would be useful to be added in "The Beginners Guide"
I also need help if anyone knows what "steflash" is. And why it is needed to be updated.

Well I guess this sort of explains why I could flash from SD the Deodexed 2.3.6 but my phone was telling me I was on 2.3.5.
[EDIT] Any idea why I'm getting a "Preflash validation failure"? No matter what I try to send it outputs:
Code:
moto-fastboot.exe flash * *.img
sending '*' (#### KB)... OKAY [ ####s]
writing '*'... INFO Preflash validation failure
FAILED (remote: )
jimbridgman tried to help me on my original post [Q] Botched rootkeep... with a similar instructions and I was getting the same result.
[/EDIT]

Tried both methods and doesnt work for me. 1st cant use moto-fastboot tried with cd/cmd no path and no file name. 2nd option when I use blur zip it comes up inRSD with no xml. Please help

1. your cmd shoud "cd" into the folder where moto-fastboot stays
2. I didnt write that RSD should be used for blur. Put it on SDcard

[Q] help me: help my atrix 2 flash failure

I just use RSD 5.6 to flash my atrix 2 to 2.3.5 but flash failure .
it is notice that
"Failed flashing process. Failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> USB error occured while reading/writing.; phone connected."
and then, when i go to FastBoot mode, it is notice that
"AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Baterry OK
OK to Program
Connect USB
Data Cable."
help me, thanks all

manbk401 said:
I just use RSD 5.6 to flash my atrix 2 to 2.3.5 but flash failure .
it is notice that
"Failed flashing process. Failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> USB error occured while reading/writing.; phone connected."
and then, when i go to FastBoot mode, it is notice that
"AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Baterry OK
OK to Program
Connect USB
Data Cable."
help me, thanks all
Click to expand...
Click to collapse
We need more info to help you. which version of the phone? were you on 2.3.6 or 2.3.5 before the flash? do you have drivers installed correctly?

lkrasner said:
We need more info to help you. which version of the phone? were you on 2.3.6 or 2.3.5 before the flash? do you have drivers installed correctly?
Click to expand...
Click to collapse
the first, i use Retail Indian - 5.5.1-EDEM-28-37-SEARET rom (2.3.6). I want to up to Supercharged v5 (following that ). but when completed, my phone just stops at boot screen (i wait 10 minutes but not change).
after that, i go to FastBoot mode and flash to 2.3.5 via RSD Lite. the failure was happended
i use RSD lite 5.6 and Motorola 5.2 Drivers.
ps: I tryed Flashboot following this topic: 2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX but nothing change

manbk401 said:
the first, i use Retail Indian - 5.5.1-EDEM-28-37-SEARET rom (2.3.6). I want to up to Supercharged v5 (following that ). but when completed, my phone just stops at boot screen (i wait 10 minutes but not change).
after that, i go to FastBoot mode and flash to 2.3.5 via RSD Lite. the failure was happended
i use RSD lite 5.6 and Motorola 5.2 Drivers.
ps: I tryed Flashboot following this topic: 2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX but nothing change
Click to expand...
Click to collapse
go to the noob thread and follow the instructions for replacing files in the fxz, just use the same replace files but the indian fxz that you can download.

lkrasner said:
go to the noob thread and follow the instructions for replacing files in the fxz, just use the same replace files but the indian fxz that you can download.
Click to expand...
Click to collapse
sorry, i don't understand u. i don't have the indian fzx. i'm vietnamese. when i bought atrix 2 at&t, my phone is still on stock 2.3.6.

manbk401 said:
sorry, i don't understand u. i don't have the indian fzx. i'm vietnamese. when i bought atrix 2 at&t, my phone is still on stock 2.3.6.
Click to expand...
Click to collapse
No problem. Just go here: http://forum.xda-developers.com/showthread.php?t=1396650 and read the section on how to flash the FXZ. make sure to look at the bottom part where it tells you to replace some files. you will need to do that. Instead of using the ATT FXZ file like they say use the one that matches your current version (SEARET I think you said) and follow the same directions, but use that file instead. Get if from here: http://sbf.droid-developers.org/edison/list.php

lkrasner said:
No problem. Just go here: http://forum.xda-developers.com/showthread.php?t=1396650 and read the section on how to flash the FXZ. make sure to look at the bottom part where it tells you to replace some files. you will need to do that. Instead of using the ATT FXZ file like they say use the one that matches your current version (SEARET I think you said) and follow the same directions, but use that file instead. Get if from here: http://sbf.droid-developers.org/edison/list.php
Click to expand...
Click to collapse
ok, thanks u. i will try to do follow your help. in vietnam, it's 1 am, i need to sleep .
have a nice day

manbk401 said:
I just use RSD 5.6 to flash my atrix 2 to 2.3.5 but flash failure .
it is notice that
"Failed flashing process. Failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> USB error occured while reading/writing.; phone connected."
and then, when i go to FastBoot mode, it is notice that
"AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Baterry OK
OK to Program
Connect USB
Data Cable."
help me, thanks all
Click to expand...
Click to collapse
This is right sbf or FXZ for SEART ROM
http://sbf.droid-developers.org/edison/5.5.1-EDEM-27-SEARET_cfc.xml.zip
Reinstall Drivers and RSD Lite and try flashing it, it should work

prasannapmv said:
This is right sbf or FXZ for SEART ROM
Reinstall Drivers and RSD Lite and try flashing it, it should work
Click to expand...
Click to collapse
can i should replace some file in above zip? because my phone is 2.3.6
Code:
How to flash the FXZ once applying the OTA update and get back to 2.3.5, ONCE YOU UPDATE TO THE OTS 2.3.6 YOU WILL NOT BE ABLE TO FLASH THE 2.3.5 FXZ WITHOUT FOLLOWING THESE STEPS BELOW!!
NOTE: Download this file HERE -
Unzip it and move all the the items in it to the stock fxz. You might get a warning about replacing files, just click OK. NOTE that Windows might not be able to handle the size of the fxz. I have 6 GB RAM but Windows still wasn't able to perform a drag-and-drop through the fxz's zip. I recommend that you just unzip the fxz and then put the files in. (You don't have to rezip it either, RSD Lite will still recognize it and will flash faster).
You should be able to use RSD Lite to flash the file.

lkrasner said:
No problem. Just go here: http://forum.xda-developers.com/showthread.php?t=1396650 and read the section on how to flash the FXZ. make sure to look at the bottom part where it tells you to replace some files. you will need to do that. Instead of using the ATT FXZ file like they say use the one that matches your current version (SEARET I think you said) and follow the same directions, but use that file instead.
Click to expand...
Click to collapse
i've downloaded the india FXZ and the replace file. but the xml file is not same name.
in replace file is InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285, and in india FZX is 5.5.1-EDEM-27-SEARET_cfc
and a question, my phone use code unlock AT&T, so if I flash to india FXZ, any problem happen with my atrix 2?

manbk401 said:
i've downloaded the india FXZ and the replace file. but the xml file is not same name.
in replace file is InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285, and in india FZX is 5.5.1-EDEM-27-SEARET_cfc
and a question, my phone use code unlock AT&T, so if I flash to india FXZ, any problem happen with my atrix 2?
Click to expand...
Click to collapse
Yeah, I was being stupid. Was the phone originally ATT when you bought it, or was it indian. that makes a big difference. you need to know what it said under settings > about phone.
anyways this should fix it, just use which ever fxz is right (from my post in the noob thread:
just thought of an easier way to get you restored. Most of the time you only really need to do system. download the moto-fastboot utility (it's similar to normal fastboot but you MUST use it instead or it will not work) and the fxz for your region. Extract the fxz and put the system.img from it and moto-fastboot in the same folder. open a command prompt in that folder (hold shift and right click) and type
Code:
moto-fastboot.exe flash system system.img
moto-fastboot.exe erase userdata
obviously you need to have your phone in fastboot mode to do that. it does the exact same thing as rsd, just only the 2 important steps, flashing system and wiping data.)
Let me know how that works for you. It may not since you have had flash failures, but we'll see.
moto-fastboot: http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440 you should actually extract it and put all the things in it in the folder with system.img
Good luck!

lkrasner said:
Yeah, I was being stupid. Was the phone originally ATT when you bought it, or was it indian. that makes a big difference. you need to know what it said under settings > about phone.
anyways this should fix it, just use which ever fxz is right (from my post in the noob thread:
just thought of an easier way to get you restored. Most of the time you only really need to do system. download the moto-fastboot utility (it's similar to normal fastboot but you MUST use it instead or it will not work) and the fxz for your region. Extract the fxz and put the system.img from it and moto-fastboot in the same folder. open a command prompt in that folder (hold shift and right click) and type
Code:
moto-fastboot.exe flash system system.img
moto-fastboot.exe erase userdata
obviously you need to have your phone in fastboot mode to do that. it does the exact same thing as rsd, just only the 2 important steps, flashing system and wiping data.)
Let me know how that works for you. It may not since you have had flash failures, but we'll see.
moto-fastboot: http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440 you should actually extract it and put all the things in it in the folder with system.img
Good luck!
Click to expand...
Click to collapse
hi, i'm a lucky man. i flashed my phone following Return to Stock 2.3.5 Fastboot SCRIPT. and now, my phone is ok
thanks 4 your help

manbk401 said:
hi, i'm a lucky man. i flashed my phone following Return to Stock 2.3.5 Fastboot SCRIPT. and now, my phone is ok
thanks 4 your help
Click to expand...
Click to collapse
yep, that works pretty well too. It does exactly what I said to do, but more. I do this because it goes faster

want to get back to 2.3.6
plz help me ma phone was on 2.3.6 then i tried to flash indian rom but it says flash error
n i tried several rom bt it didnt work ... all are the same
how can i get back to 2.3.7 ..thank you

i have this 5.5.1 EDEM 27 searet file which is 517 mb
should i flash this or download another 5.5.1 EDEM 28 27 searet WHICH IS 519 mb and will that hard brick my phone if i flash wrong file? im from india and recently purchased this phone and im on 2.3.6

hemanbond said:
i have this 5.5.1 EDEM 27 searet file which is 517 mb
should i flash this or download another 5.5.1 EDEM 28 27 searet WHICH IS 519 mb and will that hard brick my phone if i flash wrong file? im from india and recently purchased this phone and im on 2.3.6
Click to expand...
Click to collapse
Look in settings>about phone..then download accordingly..55.28.37 is the latest in gb 2.3.6..
Sent from my MB865 using xda app-developers app

ye i have 55.28.37 ...so which file should i download?
---------- Post added at 01:30 PM ---------- Previous post was at 01:27 PM ----------
5.5.1-EDEM-28-37-SEARET_cfc.xml.zip
is this the one which ill have to download? and is this 2.3.5 or 2.3.6 and do i need to replace the files in order to flash ...just asking cause im curious...i dont wanna hard brick

hemanbond said:
ye i have 55.28.37 ...so which file should i download?
---------- Post added at 01:30 PM ---------- Previous post was at 01:27 PM ----------
5.5.1-EDEM-28-37-SEARET_cfc.xml.zip
is this the one which ill have to download? and is this 2.3.5 or 2.3.6 and do i need to replace the files in order to flash ...just asking cause im curious...i dont wanna hard brick
Click to expand...
Click to collapse
Yup this is the zip u need..its 2.3.6..no replacing..just flash
Sent from my MB865 using xda app-developers app

Flashed my atrix 2 and fastboot fail
I bought my atrix 2 from US and unlocked it and am using this in india now. I tried to flashboot the phone with "5.5.1-EDEM-28-37-SEARET_cfc.xml". I added the new files thats available in the noob called replace.zip. I also tried the moto fast boot. Now am not able to flashboot and when i run flashboot i get this error "failed flashing process. 11/21 flash ebr "ebr"-> Phone returned fail; Phone connected" .
Please help me.

I just got my ATT Atrix 2 and I think I've already bricked it, soft at least. I used a script to go from 2.3.6 back to 2.3.5 stock, then OTA to 2.3.6, then I flashed the ICS leak and flashed SCV7, it was running horribly, kept crashing and was being extremely unstable so then I tried to use the FXZ script to go from ICS back to GB, and all my phone was doing was showing the Motorola dual core screen and boot looping or just staying on that screen I couldn't tell. I can get into fastboot, when I try to get into recovery there is an icon of a box with an arrow coming out of it and a little android and a yellow progress bar and when that finishes it goes to fastboot and it says "AP FastBoot Flash Mode (S) (Flash Failure) what can I do?
---------- Post added at 07:12 PM ---------- Previous post was at 06:55 PM ----------
The battery is low going by my luck I'm going to assume the phone will not charge while in fast boot. I've been at this for way too many hours, if someone could tell me how to get this phone working I'd appreciate it.

JB ota update installation aborted SOLVED

Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks

coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
I have the same exact problem, however it also occurs when I try to install the zip directly from CWM...perusing the other threads it seems as though it's an issue with BusyBox overwriting some files in /system/bin. For the life of me I cannot find how to correct this issue even though the it is repeatedly mentioned in the threads that is has been covered already. Seeing as I'm nearing my wits' end, I'd appreciate someone pointing me in the right direction. Thanks in advance.:crying:
---------- Post added at 10:02 PM ---------- Previous post was at 09:42 PM ----------
Just to clarify this is what I get when I try to install 4.1.1:
Verifying current system...
assert failed: apply_patch_check
('/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869", "5ba3b3ecd509cf6dcee37b2f27110310a1f55045")
E:Error in /cache/9ZGgDXDi.zip
(Status 7)
Installation aborted.
Even flashing 4.0.4 vias CWM doesn't overwrite the problematic /system/bin files. I got as far as trying to flash a factory image of 4.0.4 but got too frustrated with the fastboot commands in Terminal on OSX.
Again, while not a total neophyte, I could really use some hand holding regarding this mess. Thanks in advance.

Bumping in hope that some kind soul can walk me through replacing the /system/bin files that were overwritten by busybox. Tried factory reset and reflashing the 4.0.4 OTA to no avail. I think that flashing a factory image of 4.0.4 would work but I can't figure that out. I'm on OS X for what it's worth.
I appreciate your time.

Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.

albundy2010 said:
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
Click to expand...
Click to collapse
Thanks for the prompt reply. I dl'ed the factory image for my device (I9020T) from the developers/google site but couldn't get the ./flash-all.sh script to run. I then took the image.zip file from the factory tgz file and tried to flash it via CWM but got installation aborted/ Error 7 as well. Seems to be the only way to overwrite the system/bin filed that BusyBox replaced is to flash a factory image via fastboot.
Is there a way in which I can replace the problematic system/bin files that are preventing me from installing JB without flashing a stock factory image? And if there isn't, could I get some help with the Terminal commands for getting the /.flash-all.sh script to run on Mac?
Thanks again for your help and patience.

Those images are not mean to flashed through any recovery.
You can ignore that script. Extract what you have downloaded until you are left with ALL .img files. You should have system.img boot loader, radio, and userdata.img
Flash them one at a time with fastboot. Can't remember the exact Mac command but its fastboot flash system system.img etc for windows. Just look it for Mac. Think its fastboot-mac then the command but not sure. I hate Macs.

This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium

jayjay3333 said:
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those two links were extremely helpful, thanks for that. I got as far as having all the requisite factory image files ready to be flashed in the same folder, but when I issue the command to flash the bootloader.img I get
Code:
-bash: ./fastboot-mac: Permission denied
.
Think I may have gotten a little over my head with this whole rooting business
For the record I am rooted and have an unlocked bootloader.

coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
try latest touch version here http://bit.ly/QHLhXs when the update go to install in cmw there one dailoge box come choose yes and choose reboot and its appear again dailoge box choose yes disable recovery flash.

I solved the problem flashing this stock rom. http://forum.xda-developers.com/showthread.php?t=1784497

Finally sussed it out as well! Thanks to all for the help. Flashing the stock ICS image allowed me to install the JB OTA - will never install the BusyBox from the market again.
Cheers again to all.

[Tutorial][S4/S3] How to use OTA zip to get back to Stock OS

Lately, many people, including myself, have been at a disadvantage of not having an official RUU for JellyBean so that stock environment can be achieved. Although sometimes, OTA's are available which can do the job. Hence this Tutorial. Also this saves the effort to do S-OFF/SuperCID which often brings along more problems.
This Tutorial, in principle, can be applied to both S4 and S3 variants.
All thanks to @xander1993 at the VilleC2 Development Section who created the original thread Here. Though somewhat unclear and related to VilleC2, I thought of making a thorough guide for Ville with some minor changes.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For T-MOBILE UK Users: (UK people with other operators e.g Three, Vodafone etc can also try the Jellybean Nandroid backup IF their firmware is upgraded to that of Jellybean)
ICS Users: Those stuck on ICS custom ROMs and can't get stock, Use This RUU to get to stock ICS and then update to Jellybean via System Updates Check. Thanks to @ppm48
Jellybean Users:Those stuck on Jellybean custom ROMs wanting to get stock, I have a Stock Jellybean 4.1.1 Nandroid backup for you guys Here Since there isn't any OTA.zip for T-Mobile UK for Jellybean. You can just flash this Nandroid right away without using this tutorial. Again, Thanks to @ppm48 for this. Also, if you have bootloops after restoring this backup, flash a Jellybean Sense boot.img.
Additionally refer to this post by @mkoev , should prove a lot helpful. Then you can follow the tutorial.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For OPTUS Users with CID OPTUS001: (All thanks to @salac)
Get the modified OTA.zip Here. by @salac
salac said:
Follow the instructions from step 12.
Step 14. Flashing the firmware.zip worked the second try for me
Step 22. I did flash the boot.img to make sure it will work since I don't think I had the original one.
Good Luck
Click to expand...
Click to collapse
Optus users please follow @salac 's post above to flash the OTA.zip
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pre-requisites:
1. Notepad++
2. 7-Zip (Recommended)
3. ADB+Fastboot (Get it Here)
4. HTC drivers (Standalone OR HTC Sync Manager Drivers)
5. Unlock_code.bin from HTCDev to unlock bootloader.
6. Any OS (Custom/Stock) present on the phone. (I have not tested it for phones without any OS, you may try it at your own risk and post results here) Not Needed anymore.
Common Steps:
In this guide, I will ask you to go to fastboot/adb so you should know how you would do that. (All fastboot/adb commands are to be given via Command Prompt from PC)
To execute Fastboot Commands:
- Go to fastboot folder on your PC
- Go to fastboot via bootloader on your phone
- Connect the Phone to PC and on the Phone it should say Fastboot - USB Mode
- Now in the fastboot folder on your PC, Hold Shift + Right-Click and click Open Command Window Here
- Now you can enter commands given in the guide for fastboot.
To execute ADB Commands:
- Same procedure except that you don't need to go to fasboot on your phone. You can execute adb commands while in Android OS/desktop.
To boot into Bootloader:
- While the phone is turned off, Press Volume Down + Power Button simultaneously.
OR
- If you are in Android OS, use the following adb command to boot into bootloader:
Code:
adb reboot bootloader
OR
- If you want to reboot into bootloader from fastboot:
Code:
fastboot reboot-bootloader
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Caution for SuperCID users: Please click the CROSS button on your Browser Tab, as flashing this is not intended for you. Either don't flash the OTA.zip, which will brick your phone if you do, OR change your CID to original one. e.g. H3G__001, BM___001, ORANG001
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Procedure:
- ** - ** - ** - Make Nandroid Backups before you do anything, remember you are doing this at your own risk - ** - ** - ** -
1. Download a OTA.zip – Most likely from Here. (You can rename the OTA file which usually has a long name to simply OTA.zip for ease)
2. Extract firmware.zip from OTA.zip. Then extract boot.img from firmware.zip. For now, copy Boot.img to ADB+Fastboot Folder..
3. Now to match the CID of your phone. You can get the CID of your phone via CID Getter from Play Store. Once opened, at the top will be your CID in Red color.
Alternatively, You can also get CID of your phone via Fastboot. Command for that is:
Code:
fastboot getvar cid
and it should display your CID.
4. Inside firmware.zip, look for android-info.txt. Supported CIDs should be mentioned inside this file. If it matches with that of your phone, Proceed otherwise stop and don't put yourself into more problems. (CID Match Exception: This 4th step may not be applicable to you if & only if you are to skip steps 11 to 16, if this is the case, you may flash OTA.zip skipping steps 11 to 16; Read step 10 for more info and then come back here)
5. We need to remove some code lines from inside the OTA.zip. For this, Open the OTA.zip with 7-zip (Right-click ---> 7-zip ---> Open Archive).
6. Head over to META-INF\com\google\android and find a file named updater-script. Drag it out of the archive to the folder/desktop where you can edit it. You should make an extra copy of this file.
7. Once you drag it out, delete the original updater-script inside the archive. It will recompress OTA.zip.
8. Edit with Notepad++ the extracted updater-script file. Find these lines (in the beginning of the file) and delete them altogether:
Code:
[COLOR="Purple"]assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"BM___001") == "t");[/COLOR]
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4011000") == "t");,
assert(check_mid("simple", "PJ4011000") == "t");
);
You should delete these lines up to exact semi-colon ; at the end. (the purple lines with different CIDs can be different from those mentioned here, so no need to panic, just delete them)
9. Once edited, Copy this edited updater-script into the OTA.zip archive at the same location from which it was removed. It will recompress OTA.zip. You may now transfer OTA.zip to your SD-Card on your phone.
10. If you previously updated to JellyBean via OTA (Or if you have the exact or newer firmware on your phone than that present inside OTA.zip), skip steps 11 to 16. For example, if you have HBOOT Version 2.15.0000/2.13.0000 or above, it means you have already upgraded to Jellybean firmware so no need for Steps 11 to 16.
In case, if you are to proceed to step 11, that is if you are to flash firmware.zip, make sure to match CID as mentioned in step 4 to avoid any bricks. This is especially useful for those who have ICS and want to get stock JB or those on JB but want complete stock HBOOT, recovery etc.
11. Place firmware.zip extracted from OTA.zip inside ADB + Fastboot Folder.
12. Lock the bootloader, if unlocked. For this, go to fastboot on your phone and give the command:
Code:
fastboot oem lock
The phone reboots after this.
13. While in Android OS/Desktop, fire up Command window on PC to give the following ADB command to boot into OEM Update Mode.
Code:
adb reboot oem-78
OR (if you can't access OS to execute adb)
From Fastboot:
Code:
fastboot oem rebootRUU
You should be seeing HTC logo.
14. While in OEM Update Mode, give the following fastboot command to flash firmware:
Code:
fastboot flash zip firmware.zip
If it fails with error and doesn't show any Green Progressbar, keep trying the above command. Usually works after a few tries.
********** DO NOT REBOOT MANUALLY UNTIL IT FINISHES FLASHING FIRMWARE OR YOU'LL BRICK YOUR PHONE *************
15. Once firmware is updated, reboot into bootloader. Go into fastboot.
16. Place Unlock_code.bin inside ADB + Fastboot Folder. Use the following fastboot command to unlock your bootloader again. (This will wipe your phone except for SD, so you must make a backup before doing this)
Code:
[COLOR="Blue"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
17. Download a recovery. Preferred Recovery is TWRP 2.3.3.0 and I have not tested this guide with any other version. Put the recovery in the ADB + Fastboot folder.
18. Now go into bootloader again. This time to flash the recovery anew.
Code:
fastboot flash recovery recovery.img
19. Now go to the recovery via bootloader. Wipe data/factory reset, cache, dalvik.
20. Restore the Nandroid backup you had made earlier.
21. Now Flash the OTA.zip which is on your SD-Card. It should flash fine.
22. Go to fastboot via bootloader. We are now going to flash kernel with the following command, boot.img you had earlier copied to ADB+Fastboot folder.
Code:
fastboot flash boot boot.img
23. Reboot to the OS and you should see complete stock JB OS.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Please Rate the thread and Hit the Thanks button if this tutorial helped you!

I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Well, When I edited OTA.zip, it was the same size before/after. But maybe OS X uses different compression values.
I think you should go ahead with it and try it.

I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
.......................
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Can you use Winzip/Winrar? Might want to check with those two..

mortek said:
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
Click to expand...
Click to collapse
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.

khan.orak said:
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
Click to expand...
Click to collapse
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.

mortek said:
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
Click to expand...
Click to collapse
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.

khan.orak said:
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
Click to expand...
Click to collapse
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.

mortek said:
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
Click to expand...
Click to collapse
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.

khan.orak said:
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
Click to expand...
Click to collapse
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.

mortek said:
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
Click to expand...
Click to collapse
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!

khan.orak said:
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
Click to expand...
Click to collapse
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
sending 'zip' (400 KB)...
OKAY [ 0.226s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.735s
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s

mortek said:
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
...........
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
Click to expand...
Click to collapse
I suspect hardware failure.
Sent from my HTC One S using Tapatalk 4 Beta

Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.

booenson said:
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
Click to expand...
Click to collapse
What recovery did you use? And did you edit updater script using notepad++?
Edit: Yup, after searching, Error Status 6 appears when you edit the UPDATER-SCRIPT using wordpad/windows editor which messes all that is inside it. Use Notepad++

khan.orak said:
What recovery did you use? And did you edit updater script using notepad++?
Click to expand...
Click to collapse
TWRP 2.4.1.0. No, I used notepad, but after googling and reading the differences between notepad++ and notepad, I will have to re edit with notepad++. Will try again tomorrow when I have more time, I still need to use this phone for work and can't have it bricked lol

Tried this again, flash went through and then flashed the boot.img included with the OTA zip, and my phones stuck at the "htc one" loading screen
Edit: relocked, flashed the stock recovery, thought it was still stuck at the loading screen so I unlocked it then went to install TWRP again to restore my nandroid, and it decided to finally boot. I guess I just needed to give it more time, currently back on 4.1.1, time to send this thing in under warranty so I can get my 3G/HSPA+ fixed. Thanks!

Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app

asdfasdfvful said:
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think yes. You can check if you CID is supported. It is inside the OTA.zip\firmware.zip, a file named android-info.txt and the supported CIDs will be there.
Edit: You should first check your CID. Download CID GETTER from Play Store. Shows CID in red on top.

[Q] Orange France Version of XT925 and no LTE/4G

I bought a Motorola XT925 on ebay branded Orange France and loaded with Jelly Bean 4.1.1 firmware.
The phone was sold to me as a 4G/LTE capable device. Not seeing an option for 4G/LTE in the phones menu, I then dug around the Orange France web portal. There it says the phone is not 4G/LTE compatible. This was confirmed by Motorola France.
So my big question: is the radio hardware in this Orange France phone the same as an XT925 that I would by from Rogers Canada, but just not initialized for 4G/LTE? Or is the actual Radio hardware different? Even Motorola France was not able to tell me over the phone about the exact hardware.
Do I have a hope to get 4G/LTE working on this phone?
I want to try a Rogers firmware on this phone, but don't want a 200,00$ paperweight.
Thanks for reading.

is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.

hbenz2008 said:
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
Click to expand...
Click to collapse
I have a custom recovery utility installed after rooting and unlocking the bootloader and just completed a backup on the phone. I figure since the phone is wearing jelly bean 4.1.1 I ought to be able to take the Rogers firmware jellybean 4.1.2 and flash that onto the phone. Just not sure how to make sure that the modem gets flashed when I do fastboot flash system system.img. So I am looking around to piece together the instructions on how to flash the modem or does the system image contain all I need for the modem and all else?
I kinda like the lock screen on the Orange.fr firmware -- has a sliding mute feature that might not stick around after a system flash. minor detail though as all I really want is a working LTE device.
Thanks

Rsd lite 6.1 to flash

hbenz2008 said:
Rsd lite 6.1 to flash
Click to expand...
Click to collapse
RSD Lite is a windows utility and at the present time I do not have a windows computer. I have unlocked the bootloader and flashed the recovery successfully with mfastboot for linux. So that;s where I am at. ( I find it ironic that a phone OS based oin linux should be largely dependent on a non-linux OS. Strange but true.
@hbenz2008 tell me about flashing the modem so that I can have LTE/4G access. What do I need to do?

excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.

hbenz2008 said:
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
Click to expand...
Click to collapse
I have downloaded the 4.1.2 Rogers firmware but to be honest I don't know exactly what or how to do with the zip file. I've opened the archive -- I even flashed the modem and all the rest of the blobs onto the phone, one by one based on a batch file from another archive. What happened was I lost my patience waiting for the phone to reboot as it appeared to be stuck on the Motorola boot logo. (Maybe it was rebuilding the cache??) I used the recovery to get the phone back. So if you can give me a clue as to what to do exactly with the firmware zip -- much appreciate your council.

i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918

hbenz2008 said:
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
Click to expand...
Click to collapse
I dug up an old netbook with xp on it and managed to use RDSlite it to flash the Rogers firmware and voila! Full service phone. except for one tiny snag. Earlier I had installed a custom recovery utility cwm6.2.2.8-XT925(epinter) and it worked. Now though the cwm recovery util got wiped and my subsequent attempts to re-install fail. I speak: "linux-fastboot flash recovery cwm.img. response: Max 30M sending recovery.
Weird it never progresses or finishes. Beginning to think I have the syntax wrong.

Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd

hbenz2008 said:
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
Click to expand...
Click to collapse
Thats what I have as a linux version (mfastboot). Got it from a link posted by @ATTACK and it worked properly before I flashed 4.1.2 today. I'll work on it at least now I have a phone that works and shows the options I was sold. Just wondering if RSDLite does something crippling when it writes the flash to the phone.

Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.

hbenz2008 said:
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
Click to expand...
Click to collapse
So something does seem to have changed. I no longer have permission to erase with the mfastboot utility. And I am refering to permission on the device not in my local shell. I sudo to the shell locally then run fastboot which returns the following:
gryphon platform-tools # fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.034s
gryphon platform-tools
the device status code is 3 and unlocked so I am baffled.

i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.

hbenz2008 said:
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
Click to expand...
Click to collapse
If you think of another possible solution let me know. As of now no fastboot utility works on my phone now.

At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.

hbenz2008 said:
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
Click to expand...
Click to collapse
I have the android-sdk installed and the fastboot included is known to cause problems with image files that are large. Thats where mfastboot comes in handy.
Now everytime I powercycle the phone fastboot appears on the screen and shows a failed flash notice. I'd like to clear up this issue pronto. what a pain . An adventurous pain

Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones

while you at it man, can you please grab "gps.conf " from system/etc and post here .It is about 2kb size. Merci

hbenz2008 said:
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
Click to expand...
Click to collapse
Good news! I got the fastboot flash failure flag cleared away and cwm recovery reinstalled. Still can't flash anything with fastboot of any stripe and I am betting this is because the image files in the sbf archive are signed. My phone is now vritualy identical to any Fido branded phone, complete with a Fido boot logo. Cute.
There ought to be a way to overwrite signed images, besides waiting for a new firmware release. The bootloader is unlocked and phone rooted yet fastboot flashing is not currently possible.
How can I unlock the signed images on my phone?
BTW heres my gps.conf. Whats your interest in this file?
Code:
#Test
#NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 2
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000