188 replies to this topic

[vache]

Acer-Club.ru got hands on a JellyBean leak for the CloudMobile (thanks to them). The other good news is that it have an unlockable bootloader. "fastboot oem unlock" is back.


So, you will need :

- Installed drivers for the phone. (You can find them here)
- AcerDownloadTools (also known as ADT) to flash the firmware.
- Leaked firmware


Extract both ADT and firmware.
Launch ADT with acer_DownloadTool.exe.

Reboot the phone in bootloader by removing batery, insert it again and then plug your phone with USB cable while pressing Vol+.
You should see "boot mode: fastboot".

Select "Mobile Phone" tab, select the folder where you extract the firmware and tick checkboxes as shown below :

Click "Start" button and wait ~5min until the phone reboot by itself.

Once booted, we will know unlock bootloader. For that, reboot again in bootloader, then launch command :

fastboot -i 0x0502 oem unlock

If you don't know how to do that, you can download this automated script : http://vache-android...auto_unlock.zip. Unzip the "auto_unlock" folder then launch "unlock_CM.bat" when booted in bootloader.


Enjoy you're updated/unlocked CloudMobile. You can now safely flash the recovery.

[ian00009]

Thanks, is everything wiped?
Will I have to re-install everthing

Ian

[Chrispynutt]

This is great news thank you. Will hold off and see what comes out of this.

[vache]

ian00009, on 13 December 2012 - 10:31 PM, said:

Thanks, is everything wiped?
Will I have to re-install everthing

Ian

Yes it will make a factory reset.

[scarba]

If anyone tried it will he/she be kind and post 1-2 screenshots?

[johndoemodaco]

The russians tested it.

Attached Files

•  post-3-0-09894500-1354901117.jpg   75.72K   251 downloads
•  post-3-0-26366500-1354901117.jpg   62.56K   290 downloads
•  post-3-0-79394400-1354901116.jpg   62.09K   226 downloads

[trics]

Anyone tried it yet? Post your experience here (any issues as well)

[Rendevous]

This thing don`t work ,tried it but i have Flash Process Failed what to do ?

[vache]

Post the ADB log to know what appends. (in LogFile folder)

[Rendevous]

BaseFastboot start

Flash Process Beginning
[OutputMsg_Devices] 46c144c5 fastboot

[OutputMsg_Devices] Device_ID [46c144c5]

[Ft_Command_Devices] Exit code is [0]

flash aboot "C:\Smartphone\A9\Corp_Campaign\Acer_AV041_S500_RV41RB01_WW_GEN1\ExtractBinFolder\emmc_appsboot.mbn"
[Ft_Command] : [Info] : Args : flash aboot "C:\Smartphone\A9\Corp_Campaign\Acer_AV041_S500_RV41RB01_WW_GEN1\ExtractBinFolder\emmc_appsboot.mbn"
[ErrorMsg] sending 'aboot' (259 KB)...

[ErrorMsg] OKAY [  0.016s]

[ErrorMsg] writing 'aboot'...

[ErrorMsg] OKAY [  0.078s]

[ErrorMsg] finished. total time: 0.094s

[Ft_Command] Exit code is [0]

flash aboot OKAY. iRet0

Reboot the device while flash bootloader before bin files!

[Ft_Command] : [Info] : Args : reboot-bootloader
[ErrorMsg] rebooting into bootloader...

[ErrorMsg] OKAY [  0.000s]

[ErrorMsg] finished. total time: 0.000s

[Ft_Command] Exit code is [0]

flash bin "C:\Smartphone\A9\Corp_Campaign\Acer_AV041_S500_RV41RB01_WW_GEN1\Acer_AV041_S500_RV41RB01_WW_GEN1_1.bin"
[Ft_Command] : [Info] : Args : flash bin "C:\Smartphone\A9\Corp_Campaign\Acer_AV041_S500_RV41RB01_WW_GEN1\Acer_AV041_S500_RV41RB01_WW_GEN1_1.bin"
[ErrorMsg] < waiting for device >

[ErrorMsg] sending 'bin' (166949 KB)...

[ErrorMsg] OKAY [ 12.391s]

[ErrorMsg] writing 'bin'...

[ErrorMsg] (bootloader)  rpm update ready!

[ErrorMsg] FAILED (remote: failed to write bin!)

[ErrorMsg] finished. total time: 113.620s

[Ft_Command] Exit code is [0]

[Clean_Fastboot_Data] Delete fastboot.exe
[Clean_Fastboot_Data] Delete AdbWinApi.dll

Attached Files

•  Untitled.jpg   77.46K   159 downloads

Edited by Rendevous, 14 December 2012 - 07:47 AM.

[vache]

Something strange here :

Looks like you didn't untick "Flash bootloader before bin". (or just for the screenshot )
You have a Acer_AV041_S500_RV41RB01_WW_GEN1 where the leak is Acer_AV051_S500_RV14RB02_WW_GEN1 ?!?

You sure this is the good log ? (LogFile/Date/Log_date_time_UI.txt)

Edited by vache, 14 December 2012 - 07:58 AM.

[Rendevous]

you are right the log provided is old this is the newtest one


BaseFastboot start

Flash Process Beginning
[Ft_Command_Devices] Exit code is [0]

[OutputMsg_Devices] 58921b24 fastboot

[OutputMsg_Devices] Device_ID [58921b24]

flash bin "C:\Users\Roberto\Desktop\Acer\Acer_AV051_S500_RV14RB02_WW_GEN1\Acer_AV051_S500_RV14RB02_WW_GEN1_1.bin"
[Ft_Command] : [Info] : Args : flash bin "C:\Users\Roberto\Desktop\Acer\Acer_AV051_S500_RV14RB02_WW_GEN1\Acer_AV051_S500_RV14RB02_WW_GEN1_1.bin"
[ErrorMsg] sending 'bin' (163723 KB)...

[ErrorMsg] OKAY [ 12.107s]

[ErrorMsg] writing 'bin'...

[ErrorMsg] FAILED (remote: Device is fused and CPU_TYPE does not match!)

[ErrorMsg] finished. total time: 23.363s

[Ft_Command] Exit code is [0]

[Clean_Fastboot_Data] Delete fastboot.exe
[Clean_Fastboot_Data] Delete AdbWinApi.dll

Edited by Rendevous, 14 December 2012 - 08:00 AM.

[vache]

So this is not the good log file, check my previous post.

That's a bad news : Leak can be flashd on CPU_TYPE=8260a-3, where you may have CPU_TYPE=8260a-1.

If you now how to use fastboot could you post result of "fastboot -i 0x0502 oem device-infos" ?

Edited by vache, 14 December 2012 - 08:05 AM.

[Rendevous]

look at the picture ,what to do ?

Attached Files

•  dada.png   227.76K   300 downloads

Edited by Rendevous, 14 December 2012 - 08:09 AM.

[wimmme]

This should mean that if I had the balls i could try this and it should work:                               
I'll first repair my ZTE Blade's digitizer this evening so I have a backup Phone in case it goes wrong ...

Edited by wimmme, 14 December 2012 - 11:36 AM.

[paugustin]

Yup it worked for my 8260a-3

[gkai]

paugustin, on 14 December 2012 - 11:44 AM, said:

Yup it worked for my 8260a-3

Is there a way to know the proc version before buying (like, for example, from serial number, or all S500 available now are  a-3 while a-1 was only the first selled units)?

I ask because the locked bootloader was the only thing preventing me to buy (well, that and the availability of an extended battery, from acer or any other supplier - still no luck on this one)...But it seems that depending on the proc version, some S500 can still be unlockable...

[paugustin]

No way to know. I thought the 8260-a1 was for the dual-carrier version that is sold in a few countries.

[vache]

gkai, on 14 December 2012 - 12:00 PM, said:

Is there a way to know the proc version before buying (like, for example, from serial number, or all S500 available now are  a-3 while a-1 was only the first selled units)?

I ask because the locked bootloader was the only thing preventing me to buy (well, that and the availability of an extended battery, from acer or any other supplier - still no luck on this one)...But it seems that depending on the proc version, some S500 can still be unlockable...

Hard to say. My CM had 8260a-1 before i brick it and goes to SAV, after they changed motherboard, it's now 8260a-3.

[vache]

Rendevous, on 14 December 2012 - 08:03 AM, said:

look at the picture ,what to do ?

At the moment, we don't have a workaround for that.