Hello,
I made a full "original" restore from the file C2105_15.3.A.1.17 R1B 1272-2166_Generic Central Europe 3 1272-2166.ftf, rooted, and installed TWRP (also tryed with CWM) but installing "Custom" firmware like cm11 or AOSB fails with "Error executing updater binary", Wath am I missing here?
If I record well there used to be sticky posts with guides but i am not finding it anymore!
thanks
Ok, find it
for future and someone who needs
Install boot.img extracted from the rom you are going to use through fastboot (attention win 8/8.1 needs specific version of fastboot and drivers)
Enter Recovery
Flash Zip(s) of your new Rom
regards
Related
Hi folks! It has been a while since I have been on this forum; and I have a question about how to update from 4.1.2. to 4.2.2.
The process is not quite clear to me. Can I just download the Asus Firmware and flash through existing TWRP recovery (4.1.2 version)? Do I have to flash a kernel and new recovery using fastboot first? I see some step-by-step guides but also a view warnings. It is a littlebit vague to me what to do.Can anyone guide me through the process please?
I am on Hydro 7 but looking to update preferably to another custom 4.2.2. base rom. Tips are welcome
Best way is to download the firmware from asus website extract it (theres a zip inside the zip) and flash it with twrp, this will get rid of twrp so after the first boot find the approprate version of twrp and reflash it with fastboot, from there you can flash custom roms/ kernels at will
goodluck
I'm not sure if twrp will work. My upgrade path was to use fastboot the official zip from the Asus website, then fastboot twrp. Be careful which version of twrp you fastboot because it will cause a brick. I think twrp-2.5-4.2 should work for the US version for the official blob from the Asus website. For the WW version of the blob I used twrp version 2.4-4.2 successfully. Good luck!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
JoinTheRealms said:
Best way is to download the firmware from asus website extract it (theres a zip inside the zip) and flash it with twrp, this will get rid of twrp so after the first boot find the approprate version of twrp and reflash it with fastboot, from there you can flash custom roms/ kernels at will
goodluck
Click to expand...
Click to collapse
Doen't work, will try the method above
extract the blob from the firmware zip.
usw via cmd: fastboot flash system blob
thats all
Hi
I'm also still running 4.1.1 on my TF300TG (WW-version).
The bootloader is unlocked with the asus-tool, cwm-recovery (CWM-based recovery v6.0.1.3) flashed with fastboot and the system is rooted with supersu.
Now i want to update to 4.2.1 but it won't work. neither with the SOP for manual update nor from cwm-recovery.
From what i found it should work like this:
- download the 4.2.1 (10.6.2.6) rom file from the asus website
- extract the zip (once)
- open the second zip and open \META-INF\com\google\android\updater-script
- delete everything except "assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
set_progress(1.000000);"
- save file and save the zip
- put zip on sdcard and install from cwm-recovery
can someone tell me, if this is correct? or if i should only flash the blob with fastboot?
any help is appreciated!
thx!
Hi,
I want to root my Mate7 but I am not comfortable with messing with recovery. What is the way to backup stock recovery so I can put it back with fastboot flash recovery after rooting is done?
Thanks.
Hi xtonda - the package going around for unlocking/rooting the Mate7 currently that contains the recovery_b60.img also contains a copy of the stock recovery.
If you follow any of the guides available (off hand I can remember http://mate7.net/ascend-mate7-bootloader-unlock/ from the other day, but plenty guides available on XDA and elsewhere) the tools/driver package includes the stock recovery.
Flashing the stock is done in exactly the same way as flashing the CWM, just with the different file.
So you'd unlock, flash CWM, root the device, then flash the stock recovery again
Cheers - hope that helps!
Hi, I found two guides to root Mate7 here and each has own package with CWM recovery and some original recovery. However these original recoveries are not the same so I am not convinced that they are exactly the same as the one in my device (obviously at least one of them is not) since there are several Mate7 variants and ROM version and is unknown where these "original" recovery images come from. That is why I want to download original recovery from my device and flash it back after rooting.
Or to boot CWM recovery only temporarily without flashing it, I found that it should be possible using "fastboot boot" command. Is that possible?
Hey guys,
Im having problem to revert from CM12 to new Lollipop-version or Stock in general. When I try to flash with flashtool the package a get an error message that it can´t open the bundle.
Im sure this is an common problem but I have tried almost everything but it wont work. I got an CM-based recovery (never seen it before, its not like CWM). I have all the necessary drivers and I using an win 7 computer.
Any idea? Should I try to flash an ordinary cwm and then try to flash stock firmware again?
I have also backed up my DRM-keys, any good with them? I have unlocked bootloader and of course rooted device.
Could really use some help right now
restore to .93, root with giefroot, restore keys, reboot and flash lollipop. if you want root, flash a lollipop zip which you can find somewhere around here.
kuboweb said:
restore to .93, root with giefroot, restore keys, reboot and flash lollipop. if you want root, flash a lollipop zip which you can find somewhere around here.
Click to expand...
Click to collapse
Restore to .93? How can I restore key? Right now its just matters with the stock firmware, root comes later
You can flash the stock pre-rooted ZIP from Android Development Section through your recovery instead of using flashtool. You won't have to go through the whole rooting process again. If the CM recovery is failing, flash/replace it with TWRP/CWM/xZDualrecovery (tutorials are in their respective threads).
If you want to use your DRM keys, relock your bootloader (after flashing a stock (based) ROM) and restore them with the tool you used for backing them up. You will regain all the functionality.
Did you try different .ftf files with flashtool?
Omario-242 said:
You can flash the stock pre-rooted ZIP from Android Development Section through your recovery instead of using flashtool. You won't have to go through the whole rooting process again. If the CM recovery is failing, flash/replace it with TWRP/CWM/xZDualrecovery (tutorials are in their respective threads).
If you want to use your DRM keys, relock your bootloader (after flashing a stock (based) ROM) and restore them with the tool you used for backing them up. You will regain all the functionality.
Click to expand...
Click to collapse
Awesome! I will try it! Thanks man!
Got a huge problem!
I tried to flash over with Flashable stock 23.1.A.0.690 (5.0.2) pre-rooted with XZ dualrecovery but it didnt work. I got an Cyanogen recovery so I removed it and replaced it with cwm instead but now I have no OS at all and I really need help to get stock again
Edit: When I try to flash the stock fw I get this error message: "Cannot open bundle. Flash operation canceled"
use flashtool.
kuboweb said:
use flashtool.
Click to expand...
Click to collapse
I already use flashtool when I get this error message. I also tried to delete the "prepared" folder but it didnt work. I try right now to flash in fastboot mode but it doesnt seems to work. I think there is a problem with drivers.
17/002/2015 17:02:20 - INFO - Device disconnected
17/002/2015 17:02:24 - INFO - Device connected in flash mode
17/002/2015 17:02:35 - INFO - Selected Bundle for Sony Xperia Z3 (D6603). FW release : 23.1.A.0.690_R3C. Customization : Customized BAL_1288-5530
17/002/2015 17:02:35 - INFO - Preparing files for flashing
17/003/2015 17:03:24 - INFO - Device disconnected
17/003/2015 17:03:38 - ERROR - Drivers need to be installed for connected device.
17/003/2015 17:03:38 - ERROR - You can find them in the drivers folder of Flashtool.
I have already downloaded the usb drivers for fastboot and flashmode but it doesnt work anyway.
It looks like whether the drivers aren't installed correctly (did you reboot your pc at least once?) or you may get the whole connect - disconnect - connect in flashmode procedure wrong.
Hi,
Here is my situation:
1) Recieved OTA Upgrade to Lollipop CM12s, not very comfortable with some features gone or not as expected.
2) Looking to go back to CM 11s
3) Unlocked bootloader, flashed custom recovery twrp, rooted
4) Created backup
5) Downloaded the CM11ROM and Updates to be at CM11s
Problem faced:
While flashing CM11 ROM, its failing.
Question(s):
1) Do I need to flash the CM11 firmware and then flash CM11 ROM?
2) Can someone guide me to the steps from here (flash CM11 firmware->flash CM11ROM) and correct firmware files for CM11s?
Relatively new...and don't want to fool around and get bricked
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2765455
pretty much: download the files, flash it through fastboot and NOT recovery.
Also, this post is pretty awesome: http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
The_Symbiote said:
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2765455
pretty much: download the files, flash it through fastboot and NOT recovery.
Also, this post is pretty awesome: http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
Click to expand...
Click to collapse
So you are suggesting:
1) Device in Fastboot Mode:
2) Copy the Firmware and ROM image in the same ADB and Fastboot Directory
3) Flash 11s Firmware .... (command)?
4) Reboot in Fastboot or just Flash CM 11 ROM right after the firmware flashing?
5) What command to run to flash the ROM in fastboot?
I guess I am confused with the order of execution and commands .... can you help me with that please?
I've used CM12.1 based ROMs for a while now, and with my talent have managed to brick my bacon (oneplus one global 64GB), and unbrick it (using this guide)
I've restored it to stock with no problem using this tool.
my problem begins when i try to update to any LP ROM - flashing such ROMs' zip files in TWRP returned "E: error executing updater binary in zip". i found two solutions to this error:
1. first one is described in this thread. i ditched this method after it got me stuck in bootloop every time after flashing a ROM
2. second one (probably the way it should be done) is to update device firmware like described in this oneplus forums thread. flashing this zip indeed allowed me to successfully install my ROM but with one big problem - the SIM card is detected for a few seconds (even then the device wont find any networks) and then drops to "no SIM card detected - emergency calls only" then it gets detected again and so on...
I've also tried flashing some different modems like described here but it didn't change anything
have anyone encountered any network related problem after upgrading to a CM12.1 based ROM or have any idea how to solve my problem (mobile network connections won't function after upgrading to cm12 firmware)?
help would be very appreciated!
edit: if it helps, i also found that OTA updating to the latest build XNPH44S also breaks the phone's ability to connect to a mobile network
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
yashshan said:
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
Click to expand...
Click to collapse
1. TWRP must be installed before installing OxygenOS as it comes as a flashable zip and not an OTA/Cyanodgen update...
2. installing OxygenOS was no problem without the firmware, however after it booted i noticed it broke my mobile communications in a very similar way, so no luck with that one.
3.even after installing oxygen the firmware update is required to install anything like a CM nightly or a CM based LP ROM, and my problem was that this firmware upgrade broke my network connection, so i don't see how that could help me in any way
3.1 after flashing OxygenOS not even the firmware update would allow me to install a different ROM...
4. i linked the forum thread my firmware update came from (also found a similar suggestion in a YouTube video) and couldn't find any reference to it in any of the main ROMs' threads like you suggested, they all just say to install TWRP wipe everything and flash their zip (some say to flash a nightly before)
any other ideas? I'm starting to get desperate around my suddenly not-so-functional bacon :crying:
!!SOLVED!!
steps:
1. flash the latest CM12S fastboot image
2 .delete line 2 "aassert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");" from the updater-script file in the custom ROM's ZIP installation file
3. flash the "hacked" zip file with no problem
4. enjoy your custom ROM installed bacon, WITH your mobile connection.
thanks for the help anyway!