Xt701 leaked bootloader - Milestone XT720 General

Hi Guy this the deal are xt720 bootloader 8089 and the leaked bootloader 8090 don't flash this and no link yet I don't want you to brick your phone.
I will sweeking developers help with this one I will soon flash this on one extra phones if I get good info.
Sent from my XT720 using XDA Premium App

mchlbenner said:
Hi Guy this the deal are xt720 bootloader 8089 and the leaked bootloader 8090 don't flash this and no link yet I don't want you to brick your phone.
I will sweeking developers help with this one I will soon flash this on one extra phones if I get good info.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
If you're committed to doing this please coordinate with #milestone-modding developers. Please read the logs very carefully, this does not seem to be an easy thing to do. They were writing and compiling custom programs to flash and verify the flash as they went. If/when the phone bricks, you want to be able to know that it bricked because the bootloader doesn't work (i.e. you want to rule out the possibility that you didn't make a mistake doing the flash). Also, from the logs it looks like there are many incorrect dumps of the XT701 bootloader.
Have you thought about how you might try to convince us to follow in your footsteps if you were to succeed?
Edit: sorry, didn't mean to call you names, poor wording

can someone explain what he means exactly ?
does he know to crack bootloader of xt701 or what ? i don't get it

http://www.mod2xtreme.com/showthread.php?t=8720
hmm our bootloader is 8089 right ? so it's gonna be impossible with the leaked bootloader of xt701 ? cause just
BL_8090_umts_stcu_Consumer_replacer.sbf
BL_8091_umts_stcu_Consumer_replacer.sbf
BL_8094_umts_stcu_Consumer_replacer.sbf
are leaked.. ??

Will do try tommorow on broken xt720.
Will se... will it work.. or i get breaked on it.

what is the worst thing that could happen by trying to unlock the bootloader with those files?
irreparable software damage?
or could we just flash original rom back if something goes wrong?

Knoedelkopf said:
what is the worst thing that could happen by trying to unlock the bootloader with those files?
irreparable software damage?
or could we just flash original rom back if something goes wrong?
Click to expand...
Click to collapse
The bootloader is the software that runs on the phone to receive and flash the sbf. If that stops working... you can't flash any sbf.
A whole crew tried flashing the XT720 bootloader onto an A853 middle of last nov and ended up with a brick. See http://milestone.bekaakut.de/index.php?date=2010-11-16 starting around 20:00.
Sent from my XT720 using XDA Premium App

those guys seem to have bricked their phones right? so no chance with these xt701 bootloader unlockers ?

Unttil this has been test for work or not don't flash those ABC's okay you get a brick for your trouble.
Sent from my XT720 using XDA Premium App

critical error \n febe \n 0047
pacient just rebooted to android... =)

fjfalcon said:
critical error \n febe \n 0047
pacient just rebooted to android... =)
Click to expand...
Click to collapse
So the sbf simply errored and didn't apply? Did you flash the CG32 or the CG30? I think CG30 is the right one, but you mentioned CG32 on #mm. Did you use sbf_flash or RSD Lite? And which bootloader version did you try?
I wonder if the cdt.bin table records the locations of the signatures? Since the XT701 bootloader seems to be smaller than the XT720, we may have to pad more FF's in there to get the signature to the correct location? But I don't know if the trailing FF's are included when computing the signature, so that may invalidate the signature... hmmm.

I'am have tryed 80.90.
Tryed to flash cg30, cg32.
Now will try to do so for cg30 only.
Second error was:
critical error \n DEA1
Will make third attemp to cg30 only now.
RSD lite was used...
cg30 don't flash at all - said to small size.
phone alive.. so new attemps tommorow.
Mioze7Ae, thanks for pm's - will try to improve.

Sent from my XT720 using XDA Premium App

./sbf_flash ../other/BL_8090_hack.sbf
SBF FLASH 1.11 (mbm)
=== BL_8090_hack.sbf ===
00: RDL03 0x82000000-0x8204CFFF 9571 AP
01: CG30 0xB0020000-0xB005FFFF 20ED AP
02: CG32 0xB0160000-0xB017FFFF 2151 AP
Milestone found.
>> uploading RDL03
Uploading: 100% OK
>> verifying ramloader
-- OK
>> executing ramloader
!! unexpected response
--(9) [02]ACK[1e]JUMP
RX(9) [02]ERR[1e]G[03]08
!! failed
>> rebooting
Thats an error.
I think we should prepare ramloader for it...

fjfalcon said:
./sbf_flash ../other/BL_8090_hack.sbf
SBF FLASH 1.11 (mbm)
=== BL_8090_hack.sbf ===
00: RDL03 0x82000000-0x8204CFFF 9571 AP
01: CG30 0xB0020000-0xB005FFFF 20ED AP
02: CG32 0xB0160000-0xB017FFFF 2151 AP
Milestone found.
>> uploading RDL03
Uploading: 100% OK
>> verifying ramloader
-- OK
>> executing ramloader
!! unexpected response
--(9) [02]ACK[1e]JUMP
RX(9) [02]ERR[1e]G[03]08
!! failed
>> rebooting
Thats an error.
I think we should prepare ramloader for it...
Click to expand...
Click to collapse
Did it survive for another attempt? Was the bootloader modified at all?

Youp, it still alive.
Bootloader 80.89.. still..

Great work were are getting close any modification bootloader sbf give link wensday I can flash them I have also download different roms to try.
Sent from my XT720 using XDA Premium App

fjfalcon said:
critical error \n febe \n 0047
pacient just rebooted to android... =)
Click to expand...
Click to collapse
I'm a little confused now. Did you use sbf_flash on this one? Did the RDL03 upload this time but not on the next one?
Edit: Re-read thread, this attempt used RSD lite--I suspect probably this the same ramloader error but this is how RSD displays it.
fjfalcon said:
./sbf_flash ../other/BL_8090_hack.sbf
SBF FLASH 1.11 (mbm)
=== BL_8090_hack.sbf ===
00: RDL03 0x82000000-0x8204CFFF 9571 AP
01: CG30 0xB0020000-0xB005FFFF 20ED AP
02: CG32 0xB0160000-0xB017FFFF 2151 AP
Milestone found.
>> uploading RDL03
Uploading: 100% OK
>> verifying ramloader
-- OK
>> executing ramloader
!! unexpected response
--(9) [02]ACK[1e]JUMP
RX(9) [02]ERR[1e]G[03]08
!! failed
>> rebooting
Click to expand...
Click to collapse
Based on the second output it looks like the phone has only seen RDL03 at the point that it fails and never saw any bits from the CG30/32? (I think "RDL03 0x82000000-0x8204CFFF 9571" matches what I see for the BL_8090_umts_stcu_Consumer_replacer.sbf?)
In any case, we should expect a RDL03 from any XT720 sbf will definately get further than this and probably at least attempt to upload the CG30/32... Anyway, I dug into my archive of sbf files and extracted all the ramloaders to compare md5sums. I can only find one version of the ramloader for the Milestone XT720 in the sbf's I have managed to find:
Code:
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.18.2_UCASHLSTABB1B4DEMA033.0R_USASHLSTBRTINT_P027_A009_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.1E.0_SIGNED_UCASHLSTABB1B4DEMA039.0R_UCASHOTBRTLRTCEE_P001_A008_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.1E.0_SIGNED_UCASHLSTABB1B4DEMA039.0R_USASHLSTBRTINT_P029_A014_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.1E.2_SIGNED_UCASHLSTABB1B4DEMA039.0R_USASHLSTBSTARSG_P019_A019_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_02.1E.0_SIGNED_UCASHLSTABB1B4DEMA039.0R_UCASHOTBRTLRTFR_P018_A009_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_02.1E.0_SIGNED_USASHLSTAB14P2XAPCNRTI039.0R_USASHOTBRTLRTIT_P001_A009_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_03.20.1_SIGNED_UCASHLSTABB1B4DEMA039.0R_USASHLSTBRTRU_P012_A013_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_04.1E.1_SIGNED_UCASHLSTABB1B4D039.0R_NAREG_P011_A006_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_04.1E.1_SIGNED_USASHLSTAB14P2XAPCNCBW039.0R_NACBW_P011_A006_HWp3_1FF.sbf-RDL03.img
I can find two versions for Motoroi XT720 (we do know STSKT_N_79.33.50R works on Milestone XT720--do we know what version bootloader Motoroi has?):
Code:
461609fa5926c075574cd7f34311f6da [79.11][39]_00.sbf-RDL03.img
9f9783cf9bfd562b129522c844c5b1e9 STSKT_N_79.33.50R.sbf-RDL03.img
There have been multiple versions for XT701:
Code:
d999b61c5b92a76a6e4b157fe5a24bd3 BL_8090_umts_stcu_Consumer_replacer.sbf-RDL03.img
bd0b1166aded8a5f379de3972832a268 BL_8091_umts_stcu_Consumer_replacer.sbf-RDL03.img
62e043373170f96f86e004395a05fb0f BL_8094_umts_tcu_Consumer_replacer.sbf-RDL03.img
93be019fab4eb26e95ab4a2d97a6b01c BL_8099_umts_sholestabletcu_Consumer_replacer.sbf-RDL03.img
b413884e61b7410b5b32093012e8cb58 STCU_U2_11.04.1_USASHLSTAB125P2XAPCNCU01D.0R_HWp3_1FF.sbf-RDL03.img
aa29c6ce24b6d769079c158ffff14f56 STCU_U2_21.05.0_USASHLSTAB125P2XAPCNCU024.0R_HWp3_1FF_0325.sbf-RDL03.img
aa29c6ce24b6d769079c158ffff14f56 STCU_U2_21.05.0_USASHLSTAB125P2XAPCNCU024.0R_HWp3_1FF.sbf-RDL03.img
aa29c6ce24b6d769079c158ffff14f56 STCU_U2_31.05.0_USASHLSTAB125P2XAPCNCU029.0R_HWp3_1FF.sbf-RDL03.img
67f1aeb51e7760d23341b5ef7603d5fe STCU_U2_31.05.4_USASHLSTAB125P2XAPCNCU029.0R_HWp3_Service1FF.sbf-RDL03.img
Idea
If we pair the RDL03's from XT701 with CG's that we know will fail signature check (because we've messed with their bits) then we can try all the XT701 RDL03's and see if any will be accepted by the XT720 with a low chance of permanently damaging the phone (the RLD isn't flashed, right?)

Mioze7Ae said:
I'm a little confused now. Did you use sbf_flash on this one? Did the RDL03 upload this time but not on the next one?
Edit: Re-read thread, this attempt used RSD lite--I suspect probably this the same ramloader error but this is how RSD displays it.
Based on the second output it looks like the phone has only seen RDL03 at the point that it fails and never saw any bits from the CG30/32? (I think "RDL03 0x82000000-0x8204CFFF 9571" matches what I see for the BL_8090_umts_stcu_Consumer_replacer.sbf?)
In any case, we should expect a RDL03 from any XT720 sbf will definately get further than this and probably at least attempt to upload the CG30/32... Anyway, I dug into my archive of sbf files and extracted all the ramloaders to compare md5sums. I can only find one version of the ramloader for the Milestone XT720 in the sbf's I have managed to find:
Code:
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.18.2_UCASHLSTABB1B4DEMA033.0R_USASHLSTBRTINT_P027_A009_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.1E.0_SIGNED_UCASHLSTABB1B4DEMA039.0R_UCASHOTBRTLRTCEE_P001_A008_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.1E.0_SIGNED_UCASHLSTABB1B4DEMA039.0R_USASHLSTBRTINT_P029_A014_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_01.1E.2_SIGNED_UCASHLSTABB1B4DEMA039.0R_USASHLSTBSTARSG_P019_A019_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_02.1E.0_SIGNED_UCASHLSTABB1B4DEMA039.0R_UCASHOTBRTLRTFR_P018_A009_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_02.1E.0_SIGNED_USASHLSTAB14P2XAPCNRTI039.0R_USASHOTBRTLRTIT_P001_A009_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_03.20.1_SIGNED_UCASHLSTABB1B4DEMA039.0R_USASHLSTBRTRU_P012_A013_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_04.1E.1_SIGNED_UCASHLSTABB1B4D039.0R_NAREG_P011_A006_HWp3_1FF.sbf-RDL03.img
48a6cea6428b4b300419f210b0bf53a4 STR_U2_04.1E.1_SIGNED_USASHLSTAB14P2XAPCNCBW039.0R_NACBW_P011_A006_HWp3_1FF.sbf-RDL03.img
I can find two versions for Motoroi XT720 (we do know STSKT_N_79.33.50R works on Milestone XT720--do we know what version bootloader Motoroi has?):
Code:
461609fa5926c075574cd7f34311f6da [79.11][39]_00.sbf-RDL03.img
9f9783cf9bfd562b129522c844c5b1e9 STSKT_N_79.33.50R.sbf-RDL03.img
There have been multiple versions for XT701:
Code:
d999b61c5b92a76a6e4b157fe5a24bd3 BL_8090_umts_stcu_Consumer_replacer.sbf-RDL03.img
bd0b1166aded8a5f379de3972832a268 BL_8091_umts_stcu_Consumer_replacer.sbf-RDL03.img
62e043373170f96f86e004395a05fb0f BL_8094_umts_tcu_Consumer_replacer.sbf-RDL03.img
93be019fab4eb26e95ab4a2d97a6b01c BL_8099_umts_sholestabletcu_Consumer_replacer.sbf-RDL03.img
b413884e61b7410b5b32093012e8cb58 STCU_U2_11.04.1_USASHLSTAB125P2XAPCNCU01D.0R_HWp3_1FF.sbf-RDL03.img
aa29c6ce24b6d769079c158ffff14f56 STCU_U2_21.05.0_USASHLSTAB125P2XAPCNCU024.0R_HWp3_1FF_0325.sbf-RDL03.img
aa29c6ce24b6d769079c158ffff14f56 STCU_U2_21.05.0_USASHLSTAB125P2XAPCNCU024.0R_HWp3_1FF.sbf-RDL03.img
aa29c6ce24b6d769079c158ffff14f56 STCU_U2_31.05.0_USASHLSTAB125P2XAPCNCU029.0R_HWp3_1FF.sbf-RDL03.img
67f1aeb51e7760d23341b5ef7603d5fe STCU_U2_31.05.4_USASHLSTAB125P2XAPCNCU029.0R_HWp3_Service1FF.sbf-RDL03.img
Idea
If we pair the RDL03's from XT701 with CG's that we know will fail signature check (because we've messed with their bits) then we can try all the XT701 RDL03's and see if any will be accepted by the XT720 with a low chance of permanently damaging the phone (the RLD isn't flashed, right?)
Click to expand...
Click to collapse
Tryed to read img as smg.. get nothing..(RLD img don't found) But i had some headeache so must be that a reason.
Using SBF_RECALC for that process.

Related

HELP!! M logo reboot loop

after remove all files in /pds, rm -r /pds/*
my defy keep to reboot loop.
power on, the screen show the motorola (M) logo, after few second, then reboot.
i can go to bootlooder mode (power + sound up),
or go to wipe data/cache (power + sound down).
and i can flash sbf with rsdlite.
after tried all still keep boot loop
(full power changed 100%)
i tried reflash few different sbf rom
3.4.2-155, 3.4.2-133, 3.4.3-11
i'm sure all sbf rom work fine before.
i did flashed those sbf rom a few times, and all is work.
anyone know why keep reboot loop?
and how to solve it?
what is /pds/* files for?
please help, and thank you.
This was not a good idea. I think someone here on XDA (Tenfar) already tried to remove /pds and his Defy is dead now. Present sbf files probably do not include /pds.
peetr_ said:
This was not a good idea. I think someone here on XDA (Tenfar) already tried to remove /pds and his Defy is dead now. Present sbf files probably do not include /pds.
Click to expand...
Click to collapse
OMG, my defy is dead?
How can it be... you did wipe before sbf flash?
Why did you deleted these files?
Sent from Barebones-Defy using tapatalk.
johnw.xda said:
OMG, my defy is dead?
Click to expand...
Click to collapse
yep is dead , pds is Phone Descriptor Security and you delete IMEI number
http://forum.xda-developers.com/showthread.php?t=988115
Try to flash the bootloader the sbf files you can find in the forum then it should work if it does not flash with the latest sbf file then it had to work otherwise. My defy had many bootlops and do not start but i got it to work Sorry for my englisch my defy is alive ;-)
Send from my brain using Tapatalk
here the bootloader i used http://uploaded.to/file/ofcxbyhj
dumrul said:
Try to flash the bootloader the sbf files you can find in the forum then it should work if it does not flash with the latest sbf file then it had to work otherwise. My defy had many bootlops and do not start but i got it to work Sorry for my englisch my defy is alive ;-)
Send from my brain using Tapatalk
here the bootloader i used http://uploaded.to/file/ofcxbyhj
Click to expand...
Click to collapse
i did it, but still not work.
thank you.
wipe you phone
turn device off
vol down and power
you should see an android with a ! mark
press on the bottom left or right (im not sure)corner until you see an option to wipe
reboot
hope it helps
Try to use SBF depacker to incert CG38.smg to sbf file and reflash it,
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
USE AT YOUR OWN RISK
have you tried re-flashing with a full sbf instead of a fixed sbf? also, try to make sure your RSD lite is the latest version
sunoldman said:
Try to use SBF depacker to incert CG38.smg to sbf file and reflash it,
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
USE AT YOUR OWN RISK
Click to expand...
Click to collapse
i can not use those tools to repack it with CG38.smg
MotoAndroidDepacker.exe
MotoAndroidDepackerMono.exe
SBF-Recalc 1.2.9.1.exe
did you tried it? (repack sbf with CG38.smg)
thank you.
anyone can share /pds/* files to me?
maybe use bootloader recovery/update.zip, can copy those files to /pds
thank you.
Sorry for that, I can't do that either. Maybe it really needs to be back to factory.
I send back to factory on Saturday , and get back today.
they say need to replace another mainboard.
free of charge, good service.
thank all, thank moto.
I live in Hong Kong.
sunoldman said:
Try to use SBF depacker to incert CG38.smg to sbf file and reflash it,
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
USE AT YOUR OWN RISK
Click to expand...
Click to collapse
This idea maybe work.
Thank god, you are lucky.

[Q] Atrix 2 Telecom NZ - tried to flash JB leak, stuck on fastboot

Hi all,
First of all, I have done tons of reading and searching the past 24 hours. I cannot find a definitive solution and really want to be sure not to brick my handset.
Handset is on OTA ICS
Here's what I did:
1) Downloaded official JB leak from the thread on XDA
2) installed RSD Lite 6.1
3) Installed Motorola Device Manager
4) plugged in my Telecom NZ Atrix 2 in fastboot mode
5) opened RSD
6) ran flash with the JB leak
Then I get "Flash Failed 1/14". Now my phone boots straight into fastboot. If I hold down both vol + pwr I can select normal boot and it's all ok. Cannot reset through Recovery as it shows !android then boots back to fastboot.
From the reading I've done, this is either the wrong firmware or a driver problem (I am on Win 8 but tried on a Win 7 machine too).
It looks like I now need to flash a correct fxz for my device. I'm a bit hesitant to try flash again in case I brick for good!
2 Questions:
Why won't the JB leak work on Telecom NZ handset?
Would it be ok to flash "6.7.2_EDEM-18-MEARET" from the ICS Firmwares Superthread?
Current system version:
672.1.20.MB865.TNZ.en.NZ
4.0.4
GAS_ASIA_EDISONICSTNZ_P015
Build:
6.7.2_EDEM-20
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
So, you're phone is AT&T, not international. You can't use Jelly Bean.
Thanks
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
Thanks so much. I'v been looking for something like this for hours, but this method is the first one that worked.
Rhys C said:
Thanks so much. I'v been looking for something like this for hours, but this method is the first one that worked.
Click to expand...
Click to collapse
Cool. Seems this will be helpful for NZ users
After a bit of playing around, I have come to the conclusion that RSDLite flashing will not work with Telecom NZ handsets. Next thing to investigate is if we can upgrade to JellyBean through a script like the above.
BTW, To get root I ran the 2nd file in this thread
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
Rhys C said:
Thanks so much. I'v been looking for something like this for hours, but this method is the first one that worked.
Click to expand...
Click to collapse
Yaaah, me too!
Many Thanks to gilda311 and alteredlikeness and jimbridgman. You saved me guys. Thank you soooo much! :laugh::good:
gilda311 said:
Cool. Seems this will be helpful for NZ users
After a bit of playing around, I have come to the conclusion that RSDLite flashing will not work with Telecom NZ handsets. Next thing to investigate is if we can upgrade to JellyBean through a script like the above.
BTW, To get root I ran the 2nd file in this thread
Click to expand...
Click to collapse
I have a kiwi A2 and I have successfully flashed through RSDLite every time I have used it. I've been on the JB leaks and ICS flashed with RSDLite with no issues. I think this problem occurs when the phone is flashed with a mismatched ctd file and is then tried to be overwritten again. I know it's no help for you guys now, but for all others with NZ phones, it's something to keep an eye out for.
I have a A2 from telecom, ive soft bricked my phone a lot of times and always been successful on fastbooting/RSDLite. I use a AT&T official firmware to RSDLite and once successful i root it, install bootstrap and restore nanroid backup to TelecomNZ's firmware. At the moment im running CM10(JB 4.1.2) flashed via CWM. I have never encountered any fail flashing. gilda, my system info is exactly the same as yours i guess im lucky to get a good a2.
JB TELECOM NZ flashing
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
Hi,
Thank you very much.. This helped me to restore back to ICS(MEARET) from the telecom NZ one after flash failure. Is there any batch file similar to the one used to restore back to ICS for Telecom NZ users to install JB on those mobiles? or any other way to install official JB leak? Thanks in advance.
msbaditya said:
Hi,
Thank you very much.. This helped me to restore back to ICS(MEARET) from the telecom NZ one after flash failure. Is there any batch file similar to the one used to restore back to ICS for Telecom NZ users to install JB on those mobiles? or any other way to install official JB leak? Thanks in advance.
Click to expand...
Click to collapse
The issue seems to be with RSD itsself. Maybe we could edit the 'restore-to-ics.bat' script to flash the JB firmware instead? I'm not particularly keen to be my own test subject but I REALLY want to try CM10 and MIUI... If I'm feeling adventurous tonight I'll give it a crack and post the results :good:
MGinshe said:
The issue seems to be with RSD itsself. Maybe we could edit the 'restore-to-ics.bat' script to flash the JB firmware instead? I'm not particularly keen to be my own test subject but I REALLY want to try CM10 and MIUI... If I'm feeling adventurous tonight I'll give it a crack and post the results :good:
Click to expand...
Click to collapse
All CM10/CM10.1 based ROMs and variants can be flashed on the stock ICS kernel. Most, if not all, of them actually REQUIRE you to be on ICS before flashing including the version of MIUI found here:
http://forum.xda-developers.com/showthread.php?t=2259993
There's no need to take the risk of modifying or attempting to modify the restore-to-ics.bat script just to flash those ROMs. You just need root, Boot Menu Manager, and a little knowhow and you'll be good to go.:thumbup:
Brought to you by time and relative dimensions in space.
There is a way to install stock jb on at&t atrix2, but cant get camera working!
Telecom NZ JB
MGinshe said:
The issue seems to be with RSD itsself. Maybe we could edit the 'restore-to-ics.bat' script to flash the JB firmware instead? I'm not particularly keen to be my own test subject but I REALLY want to try CM10 and MIUI... If I'm feeling adventurous tonight I'll give it a crack and post the results :good:
Click to expand...
Click to collapse
Thanks for replying, and as was quoted by u.. issue was not only with RSD.. over writing cdt fails during running that "restore-to-ics.bat" script and displays " INFO: PRE FLASH VALIDATION FAILURE". but flashing doesnt stop and skips that cdt file and proceeds to next step. Hopefully u will crack that and help many Telecom NZ usere like me. Thanks again
Downgrading
Hi,
I had the same problem. RDSLite fails on cdt.bin flashing
Seems that the problem is that RDSLite will NOT downgrade your device.
Telecom NZ OTA version is 6.7.2_EDEM-20
The fxz available online is 6.7.2_EDEM-18
This fails.
AT&T fxz is later version, and it works fine in RDSlite
Regards
Dejan
gilda311 said:
Hi all,
First of all, I have done tons of reading and searching the past 24 hours. I cannot find a definitive solution and really want to be sure not to brick my handset.
Handset is on OTA ICS
Here's what I did:
1) Downloaded official JB leak from the thread on XDA
2) installed RSD Lite 6.1
3) Installed Motorola Device Manager
4) plugged in my Telecom NZ Atrix 2 in fastboot mode
5) opened RSD
6) ran flash with the JB leak
Then I get "Flash Failed 1/14". Now my phone boots straight into fastboot. If I hold down both vol + pwr I can select normal boot and it's all ok. Cannot reset through Recovery as it shows !android then boots back to fastboot.
From the reading I've done, this is either the wrong firmware or a driver problem (I am on Win 8 but tried on a Win 7 machine too).
It looks like I now need to flash a correct fxz for my device. I'm a bit hesitant to try flash again in case I brick for good!
2 Questions:
Why won't the JB leak work on Telecom NZ handset?
Would it be ok to flash "6.7.2_EDEM-18-MEARET" from the ICS Firmwares Superthread?
Current system version:
672.1.20.MB865.TNZ.en.NZ
4.0.4
GAS_ASIA_EDISONICSTNZ_P015
Build:
6.7.2_EDEM-20
Click to expand...
Click to collapse
dejannk said:
Hi,
I had the same problem. RDSLite fails on cdt.bin flashing
Seems that the problem is that RDSLite will NOT downgrade your device.
Telecom NZ OTA version is 6.7.2_EDEM-20
The fxz available online is 6.7.2_EDEM-18
This fails.
AT&T fxz is later version, and it works fine in RDSlite
Regards
Dejan
Click to expand...
Click to collapse
Do you mean to say this which is available in firmware superthread? "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip".
Does RSDLite flashing of Telecom NZ OTA "6.7.2_EDEM-20" also works ?
I used sbf.droid-developers.org/edison/list.php source for fxz.
There's no 6.7.2_20, only _18. That might be the leak before the final OTA.
If you can find 6.7.2_20, that should work, or use AT&T one. That worked fine on my bricked telecom mobile:
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
msbaditya said:
Do you mean to say this which is available in firmware superthread? "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip".
Does RSDLite flashing of Telecom NZ OTA "6.7.2_EDEM-20" also works ?
Click to expand...
Click to collapse

Is there hope?

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

[Q] Help me.. How To Install VZW_XT926_4.1.2.xml

Hello friends I have a problem with my phone : cry : .. past days I made ​​a mistake of firmware and install a rom on my phone of xt925 and is a ' ' xt926 ' ' I need lots of help to return to the rom Original Verizon
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
I am trying to install via RSD Lite , but I get the following error appears in the image :crying:
please help dont know what else to do to install the rom on my phone, this unlocked and root for procedures
try this, hope you understand how to use it.
Resp
TOYEP said:
try this, hope you understand how to use it.
Click to expand...
Click to collapse
Thanks buddy , I'll try ... I imagine these are only replacing the I have ..
Js.Vicious said:
Thanks buddy , I'll try ... I imagine these are only replacing the I have ..
Click to expand...
Click to collapse
TOYEP said:
try this, hope you understand how to use it.
Click to expand...
Click to collapse
there is no way to flash an equal version of trust zone with rsd.
he needs to replace all the files anyways.
2 possible solutions come to mind,
1. flash the next newer firmware with rsd, if that fails,
2. flash the same version with Mfastboot, if that fails, try the newer version.
figuring out how to bypass the tz fail is easy, but it will just throw another error when it gets to the next file you cant downgrade or re-write equal. thats why the steps i have suggested should be tried.
bweN diorD said:
there is no way to flash an equal version of trust zone with rsd.
he needs to replace all the files anyways.
2 possible solutions come to mind,
1. flash the next newer firmware with rsd, if that fails,
2. flash the same version with Mfastboot, if that fails, try the newer version.
figuring out how to bypass the tz fail is easy, but it will just throw another error when it gets to the next file you cant downgrade or re-write equal. thats why the steps i have suggested should be tried.
Click to expand...
Click to collapse
yes, he must replace files IF current rom defferent from mine, i use latest stock rom released.
and i assume he know how to put md5-hash to the .xml file if he wish do some experimental :laugh:
Keep in mind he flashed 925 FW to a 926, he could be toast.
Sent from my HTC6525LVW using Tapatalk
correct. i think he stuck at bootloader.
You may be right, but it doesn't hurt to at least try the most correct method to fix it.
Sent from my G3, with mods made possible by team Codefire.
RegiArt exceptional
i think what he got when research with "firmware" or "ROM".. worst case is softbrick. correct?
TOYEP said:
i think what he got when research with "firmware" or "ROM".. worst case is softbrick. correct?
Click to expand...
Click to collapse
not really, depending on what files flash, if not all, it surely could be toast also.

[Q] i KILLED IT

I have a razr hd. was experimenting trying to root it And killed it.. it will boot to the set up page but not set up. just said wait for ever. Can get into fast boot but when i run rsd light it shows connection but no data on the phone. when i try and restore phone with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip, it says unknown fast boot command. I amnot that save on this stuff but want to learn. can anybody help?
can you get your phone to apfatboot? how did you get where you are? i mean what did you have on your phone, what did you flash....what errors are you getting if you try apfastboot....?
hbenz2008 said:
can you get your phone to apfatboot? how did you get where you are? i mean what did you have on your phone, what did you flash....what errors are you getting if you try apfastboot....?
Click to expand...
Click to collapse
There is no problem getting into fast boot. theres no errors other than when i get into apfastboot it says device is locked, status code 0 I was trying to root it off of instructions off of other posts it had android version 4.4.1 . sorry if if cant be more specific but i'm just learning about these things.
c:\fast>mfastboot update VZW_XT926_4.0.4-7.7.1Q-144_VQW_S3-34-25_CFC.xml.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txtThis is what i get when i try running a update on fast boot.
That is old FW, like when the phone first came out. You really need to stop trying to flash random things and get the latest FW out of the General section and flash that.
Sent from my HTC6525LVW using Tapatalk
Thanks to all of any one is currently having probloms with ther "bricked" phone foloww this post.
http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083
I used the rsd flash methode and it worked for me.

Categories

Resources