After almost a full day of flashing I now have a 100% successful method of flashing any stock JB Firmware
With this method I have been able to successfully flash any stock JB Firmware from 10.4.2.9 all the way through to 10.6.1.27.5 without issue.
unfortunately you can not go back to ICS bootloader or firmware (there is a signature mismatch issue here).
Try this at your own risk, I will not be responsible for a bricked device.
Recommend doing NVFlash first so your tablet is Unbrickable
NVFlash for ICS bootloader
NVFlash for JB bootloader
Warning:
If you flash an incorrect recovery to a 4.2 bootloader there is about a 90% chance that fastboot flash commands will now just freeze the tablet - When you attempt to flash via fastboot everything will seem to go ok on the command prompt but you will not see the blue progress bar on the tablet when flashing & the reboot command will not reboot the tablet after the flash command & nothing will have flashed to the tablet.
If this is the case try this solution.
Please read below for how to check your bootloader version and confirm your flashing the correct recovery.
Requirements:
Must be unlocked (Method 1 seems to work fine for locked devices but must be unlocked for Method 2 to flash custom recovery).
Must have working fastboot
Working adb in recovery (optional). I use adb in this method for rebooting but this can be done manually with vol- & power.
Always make a backup first.
Files Needed:
Download the stock JB firmware you wish to flash from either the Asus website or from the Index thread here, be sure to download the correct SKU version you wish to use On your tablet you can check what SKU your using by going to settings>about tablet, scroll down to build number and you can see SKU version..
If using method 2 download the TWRP recovery you require, Here is a link to the TWRP thread. When you download a version of TWRP it will have a name like "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - You can rename to something shorter for flashing if you like, I rename like so "twrp-2.5.0.0-4.2.blob".
What recovery to flash for bootloader version: example for TF300T model:
Check & confirm what bootloader your on - boot to bootloader menu (vol- & power) and look at the text in top left, your bootloader version number is there.
JB 4.1 firmwares
If current bootloader = 10.4.2.9 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.13 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.17 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.18 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.20 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
JB 4.2 Firmwares
If current bootloader = 10.6.1.8 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.4.4.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device. Also flashing 2.5.0.0-tf300t-4.2 on the 10.6.1.8 bootloader results in a split-screen issue.
If current bootloader = 10.6.1.15.3 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.1 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.5 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
My Notes about TWRP 2.4.4.0-4.2:
TWRP 2.4.4.0-4.2 will not mount my sandisk 64gb micro SDXC UHS-1 class 10 card, but previous versions of TWRP have no issue. I believe this is a UHS-1 issue. TWRP 2.5.0.0-4.2 has fixed this bug and and can now mount 64gb micro SDXC UHS-1 class 10 card again.
Method 1
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method apply's for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Now unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
or
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC.
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight the usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]When complete
Code:
fastboot reboot
This method should work fine but have found that sometimes the device will get stuck at the boot animation, if this happens method 2 works fine every time.
Method 2
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method applys for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Place a copy of the WW_epad-user-10.4.2.20.zip on your microSD card.
[*]Now on PC unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
[*]Now copy the "twrp-version.blob" file you downloaded to your android-sdk\platform-tools folder.
--Make sure you have the correct twrp version for the firmware your flashing.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command.
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder.
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
You can now check that your bootloader has upgraded/downgraded, look at the text in the top left of the bootloader screen and make sure it's changed to the firmware version you just flashed.
[*]Now again depending on the bootloader version go to fastboot.
Next
[*]In the below command I am using "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" for JB firmware 10.4.2.20, and shortened the name "twrp-JB.blob" so just change command according to TWRP version needed.
Code:
fastboot -i 0x0b05 flash recovery twrp-JB.blob
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
[*]Now this time in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery select "Wipe".
[*]Here I do a complete wipe (cache, Dalvik cache, Factory Reset, System, Internal Storage & Format Data) I don't believe Internal Storage & Data Format are necessary but I like a full clean flash.
[*]Once you have done full wipe type in command prompt.
Code:
adb reboot-bootloader
or manually reboot to bootloader, hold vol- and power button.
[*]Now again in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery disconnect your device usb cable from PC.
[*]Select "Install" & select the firmware zip you copied to your external sd card and slide to flash/install.
[*]Once completed reboot, you will get message at top of recovery saying there is no OS installed are you sure you want to reboot - slide to confirm yes, another message will popup asking if you want root permissions installed - I select NO "Do not install" you can probably select yes here if you want twrp to root.
The device will reboot, you'll see a progress bar as the signature is being matched, it will reboot again when done.
Now device will boot with the stock JB bootloader & firmware you have chosen.
Done.
You can now flash twrp, then flash any custom rom for that firmware.
As I have said I have done this with all stock WW JB firmware available and can confirm that the bootloader does change and system will boot and run without any issues. But try at own risk.
Firmware I have done this with: Only tried with WW SKU
10.6.1.27.5
10.6.1.27.1
10.6.1.15.3
10.6.1.8
10.4.2.20
10.4.2.18
10.4.2.17
10.4.2.13
10.4.2.9
More Info:
Downgrading from CROMi-X back to CROMi-3.4.6
Upgrading from ICS to JB
If you this information is helpful please hit the thanks button.
Nice work and thanks for sharing it PJC21. Looks like you've got quite a bit of time invested in this info. :thumbup:
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
jimpmc said:
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
Click to expand...
Click to collapse
Yeah quite possibly, I didn't even think to try it that way :laugh:
However if just flashing the system blob via fastboot then rebooting, my devices will get to the boot animation screen and just sit there.
I do prefer being on the correct bootloader before flashing the firmware though and this way allows for that.
Maybe consider making this two parts.
1. with twrp recovery installed
2. with stock recovery installed
Good info and needed!
Note: I should have added with twrp, fastboot, or adb to flash I always loose root and data. With stock if I am using the same version or anything numerically higher I keep root and data but going to a lower numeric I loose root and data.
I hope this is understandable.
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Q-Logic said:
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Click to expand...
Click to collapse
+1 works
Sent from my GT-I9100 using xda app-developers app
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Just to make sure ...
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
To be honest - I'm not sure, I didn't downgrade, let pjc21 say did he. I would be afraid to do mess with file system just like you.
But I would be interested to try this if his downgrading method works.
funnel71 said:
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure here, but would think no as the new update has a different file system arrangement. I myself would not try this as I really have no idea what would happen.
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Works fine
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Witch much satisfaction I can confirm this working. Had to sideload the update zip, though, 'cause I forgot to copy it to my external micro sd card. in the course I ****ed up the update (progress indicator not progressing, so i did a vol-+power-reset, subsequently rom did not load), but adb-d recovery again, inserted micro sd and did the update (downdate) to 10.4.2.20. running cm 10.1 nightly now.
Yeah, this brickproof mod sounds really good. I wouldn't want to miss up on jb's smoothness, though. IMHO JB and ICS are worlds apart. Maybe those guys give it a go with a 4.2-brickproof-mod one fine day
Thanks pjc21 for this outstandig work. This is what Android OS is about: being able to explore all possibilities of a fine piece of hardware you actually own instead of being led on a leash by a corporation. :good::good::good:
This worked pretty easy, returning from 4.2.1 ( 10.6.1.8) I flashed the 4.1.1 (10.4.2.20) blob through fast boot,then flashed twrp 2.3.3.0 in fast boot, rebooted into recovery restored my 4.1.1 backup and all is well.
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
wetbiker7 said:
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
treo4life said:
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
Click to expand...
Click to collapse
Exactly. But........ he also said he was going to try and modify the signatures to see if he can get them to match. If he can succeed, it will be a huge breakthrough.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
treo4life said:
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No doubt. Hopefully he'll continue working on it.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
I just received my new tablet ... Need to downgrade to 4.1.1 to be able to run AOSP Rom.
Thanks for the procedure. I will give it a try.
hi everyone
i'm explaining the problem that's getting me crazy!
I've got an a500 tab. it was HoneyComb 3.1 at first, I downloaded ICS 4.0.3 Stock Rom and installed it via SD Card, Power + Vol- button.
i've been using it a few monthes now i want to use a custom rom like tegraowners JB.
my current version of rom (ICS 4.03) can't be rooted with ICS Root for a500 because it's version is'nt supported.
so i decided to install a 3.1 HC Stock rom, root it and use custom roms.
i downloaded 3.1 stock rom, named it update.zip and copied it on a sd card.
inserted SD card in tab and turned it on with Power + Vol-. here is the problem!
first i see recovery mode loading then an android logo with a (!) sign on it.
cdn.gooyait.com/uploads/android-recovery-mode-600x276.jpg
and tab get's restarted...
any idea?
I don't know maybe i've downloaded the wrong rom.
if yes please link to the correct rom for thei version:
Kernel Version:
2.6.39.4+
Image Version:
Acer_AV041_A500_RV21RB01_WW_GEN1
Build Number:
Acer_AV041_A500_0.014.00_WW_GEN1
PLEASE!
AHashemi said:
hi everyone
i'm explaining the problem that's getting me crazy!
I've got an a500 tab. it was HoneyComb 3.1 at first, I downloaded ICS 4.0.3 Stock Rom and installed it via SD Card, Power + Vol- button.
i've been using it a few monthes now i want to use a custom rom like tegraowners JB.
my current version of rom (ICS 4.03) can't be rooted with ICS Root for a500 because it's version is'nt supported.
so i decided to install a 3.1 HC Stock rom, root it and use custom roms.
i downloaded 3.1 stock rom, named it update.zip and copied it on a sd card.
inserted SD card in tab and turned it on with Power + Vol-. here is the problem!
first i see recovery mode loading then an android logo with a (!) sign on it.
cdn.gooyait.com/uploads/android-recovery-mode-600x276.jpg
and tab get's restarted...
any idea?
Click to expand...
Click to collapse
Stock recovery probably isn't designed to flash anything other than ICS. (Or it can't go backwards?). As for rooting, the blackthud3r ICS root tool oughta get ya done. (There are 2 methods, search and find one. For your case I recommend number 2)
[Anyway, don't worry about rooting the stock ROM, on an A500 this doesn't help you get jellybean.]<- MAY BE WRONG. In order to install a custom ROM, you must install a custom bootloader and recovery. Here is a guidehttp://forum.xda-developers.com/showthread.php?t=1622425 Once you've gotten through that(and assuming you haven't died of heart attack), you can install a custom ROM. Just follow the instructions on said ROM's thread. My favorite(albeit, a bit buggy) one is here :http://forum.xda-developers.com/showthread.php?t=2239476&highlight=jellybean+rom&nocache=1. Good luck!:good:
EDIT:
You need a CPUID to flash your bootloader. I don't know if you need root to get that.
Install a custom bootloader
You shold read about custom bootloader, it isnt that difficult, you get root of your iconia, download a flex software it automaticly downloads the latest recovery I recommend TWRP, and from ther you could touch the option install and select you zip file
Hi, I'm trying to unroot my iconia.
I've tried blackthunder unroot tool, seems to work but doesn't (as stated elsewhere).
So I'm trying to flash a stock firmware.
I downloaded the same firmware I have on the tablet:
Acer_A500_1.031.00_WW_GEN1
renamed as update.zip, put it onto sd card, rebooted the tablet with vol down + power, the android appears, then falls down with a red triangle in.
So I've tried acer update decrypt, even if in the diagram was not contemplated, but I get an out of memory message.
Then I've tried to install a custom recovery, downloaded Acer Recovery Installer from the market, chose cwm, then when booting into recovery i get a red error message, recovery verified failed.
luckily the tablet still works, but I really need to unroot it, any help would be appreciated.
Thanks, cheers
edit: I followed this:
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44
and, with some issues, I think I was able to unlock the bootloader, in fact I could flash the stock rom.
many many thanks
Hello all,
A while back I installed a pre-rooted ROM on my A500 which identifies itself as HTJ858 (HC 3.2).
TWRP 2.1.3 is the recovery installed.
Now for the first time since I installed it, I'm trying to get into the bootloader (update to newer ver
TWRP), and something is locking me out. It simply bypasses the bootloader. I've tried powering off,
then Power On + Vol Up. It goes from the white acer logo into the normal boot process just as if I wasn't
doing anything. Power On + Vol Dwn puts some text on the screen, notifies looking for update.zip on
SD card. I want to install the MR2 ROM referrenced in the A500 Android forum here, but don't want to
flash without taking care of the BL problem first, so don't have an update.zip on SD card.
I've also tried selecting bootloader from TWRP reboot - same thing. Have Quick Book apk installed
which also fails to enter the BL.
Please help! I'm a long time Linux user, but not an android dev. I've used adb and fastboot on the PC
with various Android devices. I've read through related threads here. Found a EnterBootloader.zip file
on Xperia forum - I presume it would be risky at best to use a utility that's for a different platform.
John
===
A500 3.2 rooted HC
A100 w/ stock ICS 4.01 rooted
Nexus 4 w/ stock 4.4.3 rooted
I eventually decided to flash Kitkat onto my Defy+.
Followed this guide here:-
http://forum.xda-developers.com/showthread.php?p=52342403#post52342403
Everything worked fine until I got to the actual flashing of the KK Rom. TWRP had loaded fine but insisted I had no OS installed and on exit suggested device was not rooted?
Phone kept saying failed and to re partition. So I tried the Resize.zip from another guide. This did nothing either , still the same.
It had also had the following error, "Error Executing Updater Binary In Zip".
So I tried the solution here:-
https://kalitutorials.wordpress.com/2015/06/19/solve-error-executing-updater-binary-in-zip/
Now I cannot boot into TWRP or Clockworkmod recovery. When I try to boot phone it just sits on Motorola Sign but doesn't progress and no led flashes to enter TWRP. Battery needs to be removed to switch off.
If I power up with Volume down pressed, I get picture of Android Green Robot standing up with an yellow exclamation in a white lined triangle. No options are shown.
Pressing Vol up and down I get me to Android System Recovery <3e>. Options there are, reboot system now, apply update from sdcard, wipe data/factory reset, wipe cache partition.
I can also enter bootloader using vol up and power.
Any ideas anyone, found this guide to try to fix but don't want to try anything else without some confidence it will work.
http://www.tech-zealots.com/tutorials/unbrick-motorola-defy-or-defy-100-working/
I have a nandroid backup created in normal recovery btw. I would prefer to flash back to it if possible.
Thanks
G
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
dc239 said:
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
Click to expand...
Click to collapse
Thanks for your reply.
Tried what you suggested but after flashing that sbf the phone tries to boot up but after logo drops back to bootloader 9.10 with ERR:a5,69,35,00,27 .
I managed to get the Retail UK sbf referred to here:-
http://forum.xda-developers.com/showthread.php?t=1421526
Tried flashing it but end up with a black screen bootloader and just white led lit. Reflashed the sbf u suggested and back to Bootloader with Err.
Googling seems to suggest I am just needing to get the right sbf for the phone.
I have the Nandroid backup made with Clockworkmod recovery. Is there anyway to flash it?
TIA
G
Sorted
After extensive digging and climbing the steep learning curve. Decided the problem was that the sbf file u suggested was DFP 231 and possibly my phone was DFP 2311. Found Firmwares here:-
https://firmware.center/firmware/Motorola/Defy+ (MB526)/Stock/
And downloaded the DPF 2311 Rom, only was one. (DEFYPLUS_U3_4.5.1-134_DFP-2311_BLUR_SIGN_USADEFYEMARAB1B8TFDE004.0R_PDS03C_USAJRDNGIBRO2DE_P020_A025_M002_Service1FF.sbf). Tried flashing it and voila system is back, albeit it started up in German.
Gonna try the rooting mehod here:-
http://forum.xda-developers.com/showthread.php?t=1820282
For anyone elses benefit, the links for Roms at Android Developers don't work. The retail EU Firmware mentioned in the rootong guide is available on the site referred to above. U can tell when you click the link to the Android Developers site as the browser URL shows the full file name as follows.
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
The rooted one I think is the same one you linked me to and is still valid in the Rooting guide too.
Thanks for all help and I hope this is of use to someone else.
G
Minor question still remains.
If I am trying to install Kitkat rom. DO I still need to Root phone if the rooted 231 has been installed, I presume not?
G
Followed rooting guide and so now have a rooted 231. All good
Now for KK.
G