The San Diego hacking topic - root progress etc.

[Guest ben1066]

There will be in the same folder as the exe a file named AndroidFlash.xml, try replacing that with what I posted above.

[Guest rickywyatt]

if you go to setting click the IFW then look at the one the tgst say 0x80000041 this number needs to be changed but i just put 0x80000094

also i need the driver id eg vid pid for adb

[Guest darkvicious]

hello I'm sorry for my english low level, but thanks to google translation I can express myself and make myself understood by everyone. I have a question you have managed to rooter whether the san diego. How did you done thank you

Edited July 29, 2012 by darkvicious

[Guest shootomanUK]

its in the "mflash3.3_userdata_lenovo.rar"

[Guest 0072121]

Anyone know when the ICS update is coming/ can you link me to an official page/site telling us?

[Guest rickywyatt]

i beleave the flasher wont work if you dont inclued ifw so i used the ics form the ics and got this far i can feel that we close i no it has something to do with the settings in the flasher as the vid pid are diff form the k800

[Guest rickywyatt]

its in the "mflash3.3_userdata_lenovo.rar"

yes

[Guest ben1066]

i beleave the flasher wont work if you dont inclued ifw so i used the ics form the ics and got this far i can feel that we close i no it has something to do with the settings in the flasher as the vid pid are diff form the k800

Try doing what I said, I think that command fails on our device since I can't see where /sbin/PartitionSystem.sh could be. I think it should work without since the rest is the common fastboot flash commands. So edit AndroidFlash.xml to

<?xml version="1.0"?>

<fastboot>

<command id="10">

  <string>flash /tmp/modem.fls $modemfw_file</string>

  <timeout>30000</timeout>

  <retry>2</retry>

</command>

<command id="11">

  <string>oem system "loadfw_modem.sh /tmp/modem.fls"</string>

  <timeout>120000</timeout>

  <retry>2</retry>

</command>

<command id="2">

  <string>erase factory</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="3">

  <string>erase system</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="4">

  <string>erase data</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="6">

  <string>erase sdcard</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="7">

  <string>erase cache</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="8">

  <string>flash boot $kernel_file</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="9">

  <string>flash system $rootfs_file</string>

  <timeout>400000</timeout>

  <retry>2</retry>

</command>

<command id="10">

  <string>flash data $userdata_file</string>

  <timeout>200000</timeout>

  <retry>2</retry>

</command>

</fastboot>

Edited July 29, 2012 by ben1066

[Guest rickywyatt]

what happing is the phone anit switching into fastboot because the vid and pid are worg

[Guest rickywyatt]

i did try but the flasher dont work if i change that file lol

[Guest shootomanUK]

my osd with orange fw is:

USB\VID_8087&PID_09F2&REV_0224&MI_01

USB\VID_8087&PID_09F2&MI_01

[Guest ben1066]

Oh, well that's easy enough. Win key + R -> devmgmt.msc, find the phone there. Once you have found it right click on it and go to properties. Go to details and from the dropdown select Hardware IDs. There should be a VID and PID listed. That's what you need. The PID and VID are likely different to the above since it's in a different mode. How doesn't the flasher work now? Crash? If it crashes try

<?xml version="1.0"?>

<fastboot>

<command id="1">

  <string>getvar all</string>

  <timeout>10000</timeout>

  <retry>1</retry>

</command>

<command id="10">

  <string>flash /tmp/modem.fls $modemfw_file</string>

  <timeout>30000</timeout>

  <retry>2</retry>

</command>

<command id="11">

  <string>oem system "loadfw_modem.sh /tmp/modem.fls"</string>

  <timeout>120000</timeout>

  <retry>2</retry>

</command>

<command id="2">

  <string>erase factory</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="3">

  <string>erase system</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="4">

  <string>erase data</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="6">

  <string>erase sdcard</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="7">

  <string>erase cache</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="8">

  <string>flash boot $kernel_file</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="9">

  <string>flash system $rootfs_file</string>

  <timeout>400000</timeout>

  <retry>2</retry>

</command>

<command id="10">

  <string>flash data $userdata_file</string>

  <timeout>200000</timeout>

  <retry>2</retry>

</command>

</fastboot>

getvar all should never fail :)

Edited July 29, 2012 by ben1066

[Guest rickywyatt]

yep same as mine lol i no it has soming to do with setting as it dont boot into fastboot when its meant to so it cant flash the system part of the update

[Guest fishb00n]

keep it up! :-)

[Guest rickywyatt]

Oh, well that's easy enough. Win key + R -> devmgmt.msc, find the phone there. Once you have found it right click on it and go to properties. Go to details and from the dropdown select Hardware IDs. There should be a VID and PID listed. That's what you need. The PID and VID are likely different to the above since it's in a different mode. How doesn't the flasher work now? Crash? If it crashes try

<?xml version="1.0"?>

<fastboot>

<command id="1">

  <string>getvar all</string>

  <timeout>10000</timeout>

  <retry>1</retry>

</command>

<command id="10">

  <string>flash /tmp/modem.fls $modemfw_file</string>

  <timeout>30000</timeout>

  <retry>2</retry>

</command>

<command id="11">

  <string>oem system "loadfw_modem.sh /tmp/modem.fls"</string>

  <timeout>120000</timeout>

  <retry>2</retry>

</command>

<command id="2">

  <string>erase factory</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="3">

  <string>erase system</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="4">

  <string>erase data</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="6">

  <string>erase sdcard</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="7">

  <string>erase cache</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="8">

  <string>flash boot $kernel_file</string>

  <timeout>45000</timeout>

  <retry>2</retry>

</command>

<command id="9">

  <string>flash system $rootfs_file</string>

  <timeout>400000</timeout>

  <retry>2</retry>

</command>

<command id="10">

  <string>flash data $userdata_file</string>

  <timeout>200000</timeout>

  <retry>2</retry>

</command>

</fastboot>

[/CODE]


getvar all should never fail :)



just comes up with 


all 


lol

[Guest ben1066]

But after that it carries on? It doesn't necessarily need to boot into fastboot, nothing saying there isn't two fastboot interfaces, it's happened before. Also, it must be enumerating the device under fastboot to get it's serial number.

Edited July 29, 2012 by ben1066

[Guest rickywyatt]

ok ill try my best to explane it

the flasher dose not change it still trys to do this /sbin/PartitionSystem.sh even if i change the file

also if i change the other xml the flasher crashes

the ifwi tab with 0x80000041 the ifwi dont flash but if i change it to 0x80000094 it flashes

[Guest ben1066]

But what happened after it displayed all?

[Guest]

Anyone know when the ICS update is coming/ can you link me to an official page/site telling us?

Not released yet but it will be in August some time, you will get a notice on your device.

hello I'm sorry for my english low level, but thanks to google translation I can express myself and make myself understood by everyone. I have a question you have managed to rooter whether the san diego. How did you done thank you

No not rooted yet, but getting there, keep your eyes on the progress.

[Guest rickywyatt]

But what happened after it displayed all?

nothing lol just says

all

[Guest]

Could this be what is getting in the way, " One of the features of our devices is the programmable security engine on the platform. This is done to protect the ROM and the boot loader from corruption or from being overwritten. All production devices are secured utilizing keyed encryption. "

[Guest ben1066]

Right then, open up a command window in the same folder as the flasher exe and run fastboot devices, does the OSD show up? There is a fastboot executable there.

[Guest rickywyatt]

i dont think so as the flasher work at low level so it should bypass key encryption

[Guest kabirsaini2011]

Its 4:00 am in india and i am still watching the show

[Guest rickywyatt]

(waiting for device) and i think i no why because are fastboot is like this 'fastboot -i 0x8087 but the flasher enters this

fastboot -s 324B076AA1D1B3E9 oem system /sbin/PartitionDisk.sh /dev/mmcbl0