So i was flashing unleashed rom which I've done a bunch of times already but this time i formatted system and realized i forgot to put the zip file on my card to flash and i accidentally rebooted device...now it just stays at motorola screen...i went into fast boot and tried the one click fast boot but it isn't working....it says this....which I'm not sure why cuz i have it hooked up right...
I'm on a mac and I'm not sure if thats why
***************************************************************************
* *
* dhacker29 Presents: One-Click Fastboot Restore and ROOT for the BIONIC *
* An easier way to recover after bricking or bootlooping your BIONIC *
* This script will restore your phone to stock unrooted, *
* and then give you the option to reroot your phone *
* *
* A special thanks for the info and files to: *
* http://BriefMobile.com/droid-bionic-recieves-fastboot-recovery-files *
* Visit us at TH3ORYROM.com *
* *
***************************************************************************
*
* Please make sure you do the following:
*
* (a) Hold down the Volume down button and push power to enter AP Fastboot mode
* (b) plug in your phone by USB
*
_EOF
read -n1 -s -p "* Press enter to continue..."
$adb kill-server > /dev/null 2>&1
echo "* Flashing boot.img"
echo "* Enter your root password to continue or ctrl-c if you do no wish to continue"
`sudo $fastboot flash boot boot.img`
echo "* Flashing system.img"
`sudo $fastboot flash system system.img`
echo "* Wiping data"
`sudo $fastboot -w`
echo "* Rebooting your phone now, factory restore complete"
`sudo $fastboot reboot`
echo "*"
echo "* Do you want to root your phone now?"
echo "*"
echo "* If so press 1 after your phone has rebooted and you have turned on"
echo "* USB debugging under Settings/Applications/Development and switched"
echo "* USB to PC mode or press 2 to exit"
select yn in "Yes" "No"; do
case $yn in
Yes ) echo "* Rooting your phone now..."; break;;
No ) exit;;
esac
done
cat <<_EOF
You have to follow the instructions for a fastboot FXZ:
edit: There are multiple places you can find the FXZ, xda bionic dev forums has it I do believe, but I can't post links yet... if you google search All Things Root for Android Forums that thread has links for the small file and the complete file.
Here is a list of files you are going to need:
RSD Lite 5.5 - MD5 EAE167B9F9ABE207579F29285E9BBF84
Motorola USB Drivers (Windows only)
32-bit - MD5 417375F263AE83C973CF8F2F317F88FE or
64-bit - MD5 FACAE88CA21B0C37E99D027F1F63628D
The fastboot binary (LINUX AND OSX ONLY) - MD5: 2DC253F848307C4A33DE7E8A2580772B
The FXZ file (MINIMAL - 213MB) - MD5: 08C76A533D74060A842EF5DDEEA95A47
You also need to:
Have a Windows PC (For Linux or Mac OS X users, refer to this XDA thread)
Charge your Bionic all the way
Back up your data (SD card or Titanium for rooted users) as /data will be erased
Now that the prerequisites are over with...
How to restore (Linux and OS X)
Put the fastboot binary into its own folder
Extract all of the files from the FXZ to that folder
Enable USB Debugging and Charge Only mode or if you don't have access to the OS (soft-brick, bootloops, etc), put your Bionic into Fastboot mode by holding the volume-down button and pressing the power button. Then use the volume down button to select AP Fastboot, then the volume up to select. Continue on.
Open up a terminal, change directories to the folder you made in step 1, then run these commands:
Code:
./fastboot flash system system.img
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot -w
Shut off the phone using the power button
Turn it back on
Click to expand...
Click to collapse
---------- Post added at 04:04 PM ---------- Previous post was at 03:59 PM ----------
I've done this to my phone multiple times with the unleashed on Bionic just days ago, I know the screen you're talking about... the FXZ fastboot brought me back, but i'm on Windows 7 -- wouldn't know how to navigate on Mac's
There's a sticky in the dev forum labeled Bionic FAQ.
It contains many links including this one.
http://forum.xda-developers.com/showthread.php?t=1263009
guys pls help me,i was using liquid next 1.9.2 rom when i flashed the official 2.2 rom with acer download tool.Now my cell works with every button combo but it only vibrates and does not show any on-screen responses
I tried and flashed 2 or 3 different bins for my device but each time i boot my phone, it keeps on vibrating and all the three notification led's blink at the same time
Plaese Help A.S.A.P
>> No Flashing dinfo.bin.
>> .bin Class is : A1
>> Read MgFl Header Ok!!
>> AMSS FileFlag : 63
>> OS FileFlag : 95
>> Please do Not remove USB cable, unless the program indicates you can do it.
>> Download Process Started at AMSS mode.
>> Hex file Start
>> Hex file Succ !!
>> AMSS Start
>> AMSS Succ !!
>> Cmd [AMSS => Fastboot]
>> Wait UsbEvent [AMSS => Fastboot]
>> No UsbEvent [AMSS => Fastboot], Now quit process...
>> Process finished. [Not Succ]
>> Process Result : Download Process was failed...
>> Process finished, USB cable can be removed now.
common guys 72 veiws and not even one reply pls help guys
I ran into the bad flash issue and bootloop when attempting to put Jellybean on my Droid. After attempting some nandroid backups I had (which resulted in the no touch issue), I found that CWR is gone and I am back to stock recovery. At this point I've got no touch, stock recovery, and a stock rom (I think).
I have downloaded SBF and ran this command:
Code:
./sbf_flash -r --recovery recovery-clockwork-2.5.0.1-sholes.sbf MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf
with the following output:
Code:
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
>> waiting for phone: Connected.
CG63 0xC0000000-0xC001FFFF mbmloader.img
CG30 0xC0020000-0xC00BFFFF mbm.img
CG55 0xC00C0000-0xC015FFFF mbmbackup.img
CG31 0xC0160000-0xC01BFFFF cdt.bin
CG38 0xD01CE000-0xD0359FFF pds
CG34 0xC035A000-0xC03BCFFF lbl
CG57 0xC03BD000-0xC041FFFF lbl_backup
CG41 0xC0400000-0xC057FFFF sp
CG42 0xC0580000-0xC061FFFF logo.bin
CG44 0xC0620000-0xC067FFFF misc
CG35 0xC0680000-0xC09FFFFF boot
CG47 0xC0A00000-0xC0E7FFFF recovery
CG39 0xD0EF4000-0xD9FB6FFF system
CG40 0xD9FB7000-0xDFF3BFFF cache
CG37 0xDFF3C000-0xF0D29FFF userdata
CG53 0xDFD40000-0xDFF3FFFF kpanic
CG54 0xDFF40000-0xDFFFFFFF rsv
CG47 recovery -> recovery-clockwork-2.5.0.1-sholes.sbf
=== MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf ===
00: RDL03 0x80500000-0x8054CFFF DECE AP
01: CG47 0xC0A00000-0xC0D5C7FF 02C0 AP
Skipping CG47 0xC0A00000-0xC0E7FFFF
>> Adding CG47 0xC0A00000-0xC0E7FFFF
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG47: 100.0%
>> rebooting
After reboot, if I go into the recovery again it is still the stock recovery. I am hopeful if I can get CWR back I can try the safe kernel version of Jellybean, but for some reason I'm not getting CWR on it. What am I doing wrong?
Here are some flashable zips I've created to check your system partition and optionally replace any files with their stock counterparts. This is particularly useful for preparing your phone for an OTA (when you get those annoying error messages that say "{APP} has unexpected contents"). You'll need to flash the zip for your specific version of Android. You can flash this as many times as you want and can flash the OTA directly after flashing this.
You need a custom recovery to flash these! For the Lollipop OTA, after flashing the correct check/fix zip, you will need to flash the stock recovery in order to install the OTA!
KTU84P to LRX21O
Just check your system files
Code:
File: system_check_hammerhead_lrx21o-from-ktu84p.zip
[url=http://goo.gl/ooEpTy]Google Drive[/url]
[url=http://goo.gl/HPxP9O]MEGA[/url]
MD5: 10e436b5d4042145b3789ee9b9fcecb5
Size: 267 kb
Check and fix your system files:
Code:
File: system_fixer_hammerhead_lrx21o-from-ktu84p.zip
[url=http://goo.gl/mFfusU]Google Drive[/url]
[URL=http://goo.gl/VA9tuo]MEGA[/URL]
MD5: 2ae0f21d76429538f4ae854da67f5857
Size: 153 mb
KTU84M to KTU84P
Just check your system files:
Code:
File: system_check_hammerhead_ktu84m.zip
[url=http://goo.gl/ESNUH0]Google Drive[/url]
[url=http://goo.gl/fYKyvn]MEGA[/url]
MD5: 79b54a842debb992d0ef03eb2d7bc661
Size: 192 kb
Check and fix your system files:
Code:
File: system_fixer_hammerhead_ktu84m.zip
[url=http://goo.gl/sZsjz4]Google Drive[/url]
[url=http://goo.gl/1z732L]MEGA[/url]
MD5: a80331b5406042e2212fa0fe3bfeaa30
Size: 244 mb
KOT49H to KTU84M
Code:
File: check_hammerhead_kot49h_system.zip
[url=http://goo.gl/xLlREk]Google Drive[/url]
[url=http://goo.gl/lNRLlk]MEGA[/url]
MD5: 3a810e0d67e2f7b17af947a9c46664ec
Size: 402 MB
If you want to check the updater-script that is in the zip file without downloading the whole thing, [url=http://pastebin.com/kUAimyYK]I've made a paste for easy access.[/url]
Standard disclaimer: I am not to be held responsible if this messes up your phone in any way. Make sure you have backed up your phone and have backups of your backups. I created it for myself and figured I'd share what I created to benefit others. Just because it works for me does not mean it will work for you. If an alien pops out of your phone or it suddenly implodes or you lose everything on it and have no backups is not my problem.
For those of you who are interested in how I generated this, you'll find the script I created to generate the file below.
System checker script (not for the faint of heart!):
If you want to run this to create the zip file yourself, you'll need a zip file of the system directory for the version you're upgrading from and the OTA zip. I'm sure there's a better way to do all this, but this is what my convoluted mind gave me...
Call the script as (2nd argument is optional) ${0} OTA.zip [system_files.zip]
Code:
#!/bin/bash
# This requires 1 argument: the update zip filename
# Also accepts 1 optional argument: system files zip filesname
update_zip=$1
if [ -z ${update_zip} ]; then
echo "Need to let me know the name of the ota zip file!"
exit 1
fi
extract_dir=/tmp/update_zip_check
update_dir="META-INF/com/google/android"
eval $(echo ${update_zip} | sed 's!\([^\.]*\)\.signed-\([^-]*\)-\([^-]*\)-from-\([^\.]*\).*!update_hash=\1\nhw_name=\2\nnew_ver=$(echo \3 | tr [A-Z] [a-z])\ncurr_ver=$(echo \4 | tr [A-Z] [a-z])!')
system_zip=${2:-$(ls system*${hw_name}*${curr_ver}.zip)}
fixer_zip="system_fixer_${hw_name}_${new_ver}-from-${curr_ver}.zip"
check_zip="system_check_${hw_name}_${new_ver}-from-${curr_ver}.zip"
echo -e "\n\n${update_hash}\n${hw_name}\n${new_ver}\n${curr_ver}\n${system_zip}\n${check_zip}"
sha1sum -c <<EOF
${update_hash} ${update_zip}
EOF
if [ $? != 0 ]; then
echo "${update_zip} doesn't match hash; please re-download"
exit 255
fi
[ -d "${extract_dir}" ] && rm -rf "${extract_dir}"
mkdir "${extract_dir}"
echo "Updating updater-script for checking and replacing files."
unzip -q -d "${extract_dir}" "${update_zip}" "${update_dir}/update-binary" "${update_dir}/updater-script"
# The following was the old way of updating files
#unzip -q "${system_zip}" $(grep -e 'mount' -e 'getprop' -e 'assert(apply_patch_check(' -e 'assert(apply_patch_space(' ${extract_dir}/${update_dir}/updater-script | sed 's|^assert(\(apply_patch_check("/\)\([^"]*\)\(.*")\));|ifelse(\1\2\3, "", (package_extract_file("\2", "/\2"); ui_print("\/\2")));|' | tee -i ${extract_dir}/${update_dir}/updater-script_check | grep -e 'ifelse' | sed 's|^ifelse(apply_patch_check("/system/\([^"]*\)".*|\1|') -d ${extract_dir}
unzip -q -d "${extract_dir}" "${system_zip}" $(grep -e 'mount' -e 'getprop' -e '^apply_patch_check(' -e '^apply_patch_space(' ${extract_dir}/${update_dir}/updater-script | sed 's!^\(apply_patch_.*\) || abort("\\"/system/\(.*\)\\" .*);$!\1 || (ui_print("Need to fix /system/\2"); package_extract_file("\2", "/system/\2"));!' | sed 's!^\(apply_patch_check.*\) || abort("\\"\(EMMC:/dev/block/platform/.*/by-name/boot\).*);$!\1 || (ui_print("Flash boot partition"); package_extract_file("boot.img", "\2"));!' | sed 's!abort!ui_print!' | tee -i ${extract_dir}/${update_dir}/updater-script_fixer | grep -e '^apply_patch_check("/' | sed 's!^apply_patch_check("/system/\([^"]*\)".*!\1!')
sed 's!; package_extract_file([^)]*)!!' ${extract_dir}/${update_dir}/updater-script_fixer >${extract_dir}/${update_dir}/updater-script_check
mv "${extract_dir}/${update_dir}/updater-script_fixer" "${extract_dir}/${update_dir}/updater-script"
cur_dir="$(/bin/pwd)"
cd "${extract_dir}"
echo "Now creating the zip file for flashing."
zip -qr "${cur_dir}/${fixer_zip}" *
mv "${extract_dir}/${update_dir}/updater-script_check" "${extract_dir}/${update_dir}/updater-script"
zip -qr "${cur_dir}/${check_zip}" META-INF
cd "${cur_dir}"
rm -rf "${extract_dir}"
echo 'Done! Please remember to backup any APKs you have replaced on the /system partition of your device; this file will replace with the stock version for your build.'
Clever and people will find this usefull.
Thanks
Very Nice, Thanks
You could also include checks for other partitions (boot, recovery...)
no fix option for KTU84P? or am I blind, cheers for the zips though
pedja1 said:
Very Nice, Thanks
You could also include checks for other partitions (boot, recovery...)
Click to expand...
Click to collapse
In the OTA checks and fixes, the zip checks everything the OTA does, which usually includes free space, modem, and kernel. The zip will alert you to these and, in the case of boot/kernel, it will install the stock kernel. You're on your own for the modem, though.
Natherul said:
no fix option for KTU84P? or am I blind, cheers for the zips though
Click to expand...
Click to collapse
Right now, that file would be HUGE since it would include every file in the system partition. I was planning on waiting for the OTA to drop to make one, but... Give me half an hour and I'll cook something up for you
Edit: I have added a new file that checks and fixes all KTU84P system files.
I have uploaded the new zips for the released OTA! Get them now!
KTU84P to LRX21O
Just check your system files
Code:
File: system_check_hammerhead_lrx21o-from-ktu84p.zip
[url=http://goo.gl/ooEpTy]Google Drive[/url]
[url=http://goo.gl/HPxP9O]MEGA[/url]
MD5: 10e436b5d4042145b3789ee9b9fcecb5
Size: 267 kb
Check and fix your system files:
Code:
File: system_fixer_hammerhead_lrx21o-from-ktu84p.zip
[url=http://goo.gl/mFfusU]Google Drive[/url]
[URL=http://goo.gl/VA9tuo]MEGA[/URL]
MD5: 2ae0f21d76429538f4ae854da67f5857
Size: 153 mb
I'm slightly confused by the red labels. I have version KTU84P and want to return it to stock so I can update using the OTA (when it's available). Which file should I download to ensure my files are stock again? (I would assume the files named KTU84P to Lxxxx would be the ones?)
Also, will this remove root at all so I would be able to simply download and install the OTA?
danaconda1 said:
I'm slightly confused by the red labels. I have version KTU84P and want to return it to stock so I can update using the OTA (when it's available). Which file should I download to ensure my files are stock again? (I would assume the files named KTU84P to Lxxxx would be the ones?)
Also, will this remove root at all so I would be able to simply download and install the OTA?
Click to expand...
Click to collapse
Yes, use the KTU84P to LRX21O to check/fix your KTU84P version. This will not remove root, it just checks the APKs and files that the OTA checks to make sure they're at the right version for patching.
crazycaveman said:
Yes, use the KTU84P to LRX21O to check/fix your KTU84P version. This will not remove root, it just checks the APKs and files that the OTA checks to make sure they're at the right version for patching.
Click to expand...
Click to collapse
Hi how to run that script on Windows?
Im trying to run adb sideload system_fixer_hammerhead_lrx21o-from-ktu84p.zip and Im getting error:
Veryfing update package....
E: footer is wrong
E: signature veryfication failed
Instalation aborted.
Any ideas?
Thanks,
K.
Please help me how to apply fix script.
Thanks,
K.
ikavior said:
Hi how to run that script on Windows?
Im trying to run adb sideload system_fixer_hammerhead_lrx21o-from-ktu84p.zip and Im getting error:
Veryfing update package....
E: footer is wrong
E: signature veryfication failed
Instalation aborted.
Any ideas?
Thanks,
K.
Click to expand...
Click to collapse
Sounds like you have stock recovery; these zip files are like custom ROMs and need a custom recovery (e.g. ClockworkMod, TWRP)
crazycaveman said:
Sounds like you have stock recovery; these zip files are like custom ROMs and need a custom recovery (e.g. ClockworkMod, TWRP)
Click to expand...
Click to collapse
So I cant fix thish without wipe my data ?
ikavior said:
So I cant fix thish without wipe my data ?
Click to expand...
Click to collapse
If your bootloader is locked, that is correct. However, if you are getting an "unexpected contents" error when flashing the OTA and are rooted, you can extract this zip file and replace the file(s) manually with the stock version.
ikavior said:
So I cant fix thish without wipe my data ?
Click to expand...
Click to collapse
Actually, on 4.4 you could root with Towelroot and unlock ur bootloader without wiping.
Script error
So I am getting an error that the script (and the OTA.zip) says the script expects that my device should have 4.4.4/KTU84P/1227136 or 5.0/LRX21O/1570415 release keys but my device has 4.4/KRT16M/893803 release keys. However when looking at device status my device says the following:
-Device Version 4.4.4
-Baseband Version M897A-2.0.50.1.16
-Kernel Version 3.4.0-gd59db4e [email protected] #1
-Build Number KTU84P
I'm in the same situation, the checker and supposed fixer both produce the same message as above. I tried un-rooting and reflashing both zips (I'm on stock recovery but using fastboot to boot into CWM - efrant's old way for the Galaxy Nexus, worked with SuperSu so far) but the message persists.
pauleyc said:
I'm in the same situation, the checker and supposed fixer both produce the same message as above. I tried un-rooting and reflashing both zips (I'm on stock recovery but using fastboot to boot into CWM - efrant's old way for the Galaxy Nexus, worked with SuperSu so far) but the message persists.
Click to expand...
Click to collapse
Instead of using CWM to flash the OTA update, try sideloading the update using the stock recovery. Something has changed with the lollipop update, and it doesn't seem like TWRP or CWM can flash it (at least I haven't been able to do it).
Sent from my Nexus 5 using Tapatalk
Remind me where I can get the stock recovery?
Sent from my Nexus 5 using XDA Free mobile app
efrant said:
Instead of using CWM to flash the OTA update, try sideloading the update using the stock recovery. Something has changed with the lollipop update, and it doesn't seem like TWRP or CWM can flash it (at least I haven't been able to do it).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
To be honest, "nothing" changed, only that now it reads kitkat's kernel properties instead of the build.prop file directly. As I posted in the help-desk:
RusherDude said:
The fun part is that this is a bug that I saw loong ago coming.. I don't why recoveries can't STILL access android kitkat kernel properties, but they work ok reading the file, so the OTA 4.4.4 worked fine, that tries:
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/hammerhead/hammerhead:4.4.3/KTU84M/1158763:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys" ||
abort("Package expects build fingerprint of google/hammerhead/hammerhead:4.4.3/KTU84M/1158763:user/release-keys or google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Which works OK, tho if you notice the error case, the description would fail because it uses getprop...
NOW on 5.0 they use the same getprop for both cases, and fail:
getprop("ro.build.fingerprint") == "google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys" ||
getprop("ro.build.fingerprint") == "google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys" ||
abort("Package expects build fingerprint of google/hammerhead/hammerhead:4.4.4/KTU84P/1227136:user/release-keys or google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
So modifying the update scripts its a simple solutions (tho It changes the file signature and so, and it's official OTA so no way..).
Click to expand...
Click to collapse
This is a custom recoveries bug from 2013 when Kit Kat came out, still unsolved and if they don't do something we will need to flash stock recovery and stuff every OTA from now on.
I didn't understand - does the fixer flashes a new recovery? (currently can't download the zip file to check if there is any recovery img inside.. )
Hi friends,
The app recommended by BQ "MTK Tool Flash" (SP_Flash_Tool_exe_Linux_v5.1612.00.100.zip) just didn't work for me on my Debian PC. There were always some excuses. So I tried some black command-line magic with fastboot and now I'm with a bricked device.
See ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5 link I cannot post...
The good news is, I have installed the TWRP (twrp-3.1.1-0-freezerfhd.img) before I shot myself in the toe. So power + volume up gives me the comforting bluish screen of TWRP.
Question is, how can I bring the lovely device back to life? I wanted to flash official Android on it (which failed - 2.3.0_20170405-1553_bq_aquaris_m10_FHD_-FW.zip) and I'd like to complete that, but if it's a no go, I can go back to Ubuntu.
I have tried installing the image zip from twrp, but it said the image has invalid zip file format!
Thanks a lot for your help
Rob
failures
I've been struggling with this one. So I can switch to the bootloader mode and run fastboot commands. However, when I try to flash the system image I get some funny error:
Code:
sudo fastboot flash system ./system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
With the flash tool (after fixing all it's complaints) I'm stuck with a timeout on detecting the USB port (while fastboot works just fine)
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
And with TWRP as mentioned earlier:
Code:
Invalid zip file format
I read the stock rom can be adjusted somehow to allow TWRP to flash it but I'm quite like what...? Android kitchen doesn't list my device as supported.
progress
Aha! This got us further:
Code:
sudo fastboot flash system -u -S 1G ./system.img
Which means do not erase the partition upfront, and sparse the file at max 1 GB.
Code:
sudo fastboot flash userdata -u -S 1G ./userdata.img
sudo fastboot flash boot -u -S 1G ./boot.img
sudo fastboot reboot
Now device is "powered by ubuntu" and stuck there... not sure what's happening
S now I tried flashing some more exotic partitions and the device is completely dead. I hope BQ can help...
undead
Wow, so BQ contacted me right away with a hard reset procedure. The key bit of information I must have overlooked somewhere is that for the flash tool to detect the device, the device must be plugged in while it's off and while the tool is waiting. We're now "powered by android" and system is ready to use. Oh my... thanks BQ