Hello, I've got an S3 from Bell Canada earlier this week.
I followed a tutorial here: How to Root U.S. and Canada Galaxy S3 AT&T, T-Mobile, Sprint/US Ceullar! [Fail-Proof][Noob-Proof] to root it, all went great! (wont let me post the actual link yet, but that was the name of the article)
I'm trying to put task650's 4.2.2 build on but it failed, so i recovered from my backup.. worked great!
When i researched my error it indicated i may have an outdated CWRecovery in stalled. I've got 5.5.0.4.. When i check the clockworkmod website it says the latest version is 6.0.3.1.. awesome.
This is where i'm hitting a wall. I see the .img file there, but i cant find a .tar file to use to flash my phone with Odin.
I've installed ROM MANAGER (even bought the full version) but it's behaving as if i dont have a recovery mod installed.. even though i do. When i go through the 'install' options in ROM MANAGER it only lists the metroPCS version of the S3.. where I need the ATT version.
So that's where i'm at. i *think* i need to find 6.0.3.1 for an SGH-i747m in tar format. i've been googling and searching forums but i'm coming up empty. This is my first android device and it's a week old.. everything i've done i've learned this week so please forgive me if i'm missing the obvious here.
thanks in advance
If I was you, I'd just forget CWM and install TWRP. Install goomanager from the play store, open it up, hit the menu button and select to install an open recovery script. Voilà, you have TWRP recovery.
itrunner said:
Hello, I've got an S3 from Bell Canada earlier this week.
I followed a tutorial here: How to Root U.S. and Canada Galaxy S3 AT&T, T-Mobile, Sprint/US Ceullar! [Fail-Proof][Noob-Proof] to root it, all went great! (wont let me post the actual link yet, but that was the name of the article)
I'm trying to put task650's 4.2.2 build on but it failed, so i recovered from my backup.. worked great!
When i researched my error it indicated i may have an outdated CWRecovery in stalled. I've got 5.5.0.4.. When i check the clockworkmod website it says the latest version is 6.0.3.1.. awesome.
This is where i'm hitting a wall. I see the .img file there, but i cant find a .tar file to use to flash my phone with Odin.
I've installed ROM MANAGER (even bought the full version) but it's behaving as if i dont have a recovery mod installed.. even though i do. When i go through the 'install' options in ROM MANAGER it only lists the metroPCS version of the S3.. where I need the ATT version.
So that's where i'm at. i *think* i need to find 6.0.3.1 for an SGH-i747m in tar format. i've been googling and searching forums but i'm coming up empty. This is my first android device and it's a week old.. everything i've done i've learned this week so please forgive me if i'm missing the obvious here.
thanks in advance
Click to expand...
Click to collapse
Another choice is download andromizer from play store and then download the .img file. Next use andromizer to make a flashable recovery and now you have a flashable CWM....or use the goomanager method above. I prefer TWRP anyway but if you want CWM what I stated works well.
If you go with twrp, remember to make a backup as your cwm backup will no longer be of use to you anymore.
If you decide to remain on cwm, there is a recovery flashable touch version 6.0.3.1 in the link in my signature. At the bottom of post #2. Boot into recovery, flash zip, advanced > reboot recovery
xBeerdroiDx said:
If you go with twrp, remember to make a backup as your cwm backup will no longer be of use to you anymore.
If you decide to remain on cwm, there is a recovery flashable touch version 6.0.3.1 in the link in my signature. At the bottom of post #2. Boot into recovery, flash zip, advanced > reboot recovery
Click to expand...
Click to collapse
I just tried both, the TWM fails with an MD5 checksum error before it even reboots (right after the download)
When i try your 6.0.3.1 file i get the following:
"assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.product.device") == "d2att" e:Error in /sdcard/CWMTouch-recovery_ATT-6.0.3.1.zip (Status 7) Installation Aborted
:silly:
By "both" do you mean both cwm flashable zips in that post or did you mean you tried flashing a cwm one AND a twrp one?
xBeerdroiDx said:
By "both" do you mean both cwm flashable zips in that post or did you mean you tried flashing a cwm one AND a twrp one?
Click to expand...
Click to collapse
Hey xBeerdroidDx,
My exact steps were:
1.) Tried TWRP (seen his reply before yours) it failed the checksum on the download.
2.) Seen your post, copied over the 6.0.3.1 zip file of yours, booted to recovery and tried to install. Got the error i posted above... rebooted.
3.) Tried TWRP again, went successful this time.
I think i still have something wonky.. ROM MANAGER still says i have no recovery installed, and if I go back into GOOMANAGER it's behaving as if i didnt install a recovery yet either.. even though it just did.
I did make a backup using TWRP as soon as it was installed.. i'm not brave enough to try the 4.2.2 yet as it seems something is still screwy. or i'm just being overly paranoid
If you booted into twrp and were able to perform a successful backup then you're all set.
Here's a copy of 6.0.3.1 touch i just made. Try it
http://d-h.st/HTi
---------- Post added at 04:01 PM ---------- Previous post was at 03:50 PM ----------
itrunner said:
Hey xBeerdroidDx,
My exact steps were:
1.) Tried TWRP (seen his reply before yours) it failed the checksum on the download.
2.) Seen your post, copied over the 6.0.3.1 zip file of yours, booted to recovery and tried to install. Got the error i posted above... rebooted.
3.) Tried TWRP again, went successful this time.
I think i still have something wonky.. ROM MANAGER still says i have no recovery installed, and if I go back into GOOMANAGER it's behaving as if i didnt install a recovery yet either.. even though it just did.
I did make a backup using TWRP as soon as it was installed.. i'm not brave enough to try the 4.2.2 yet as it seems something is still screwy. or i'm just being overly paranoid
Click to expand...
Click to collapse
Goomanager will always install recvoery if you try to....you are using ROM manager or Goo manager to actually install install the rom's are you ?
hednik said:
Here's a copy of 6.0.3.1 touch i just made. Try it
---------- Post added at 04:01 PM ---------- Previous post was at 03:50 PM ----------
[/COLOR]
Goomanager will always install recvoery if you try to....you are using ROM manager or Goo manager to actually install install the rom's are you ?
Click to expand...
Click to collapse
That was my plan, but before ROM MANAGER wouldn't let me do anything as it kept saying i didn't have a recovery installed (which it still does).
Am i pretty safe to try applying my 4.2.2 ROM on there at this point? I've done 2 backups just to be safe hah
itrunner said:
That was my plan, but before ROM MANAGER wouldn't let me do anything as it kept saying i didn't have a recovery installed (which it still does).
Am i pretty safe to try applying my 4.2.2 ROM on there at this point? I've done 2 backups just to be safe hah
Click to expand...
Click to collapse
Do not use an app to flash a ROM. Always boot into recovery to flash them.
Make sure you do a complete wipe and flash in the recovery as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
If you booted into twrp and were able to perform a successful backup then you're all set.
Click to expand...
Click to collapse
It bombed again in TWRP. Did my 3rd recovery of the day
Here's the error, looks the same as when i was doing it via CWRecovery
-- Dalvik Cache Wipe Complete!
I:command is: 'install' and I:value is: '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
Installing zip file '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
Installing '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip.md5
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
script aborted: assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error executing updater binary in zip '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
E:Error installing zip file '/sdcard/aokp_JB_4.2.2_d2att-ota-eng.task650-4.23.2013.zip'
Done processing script file
hednik said:
Do not use an app to flash a ROM. Always boot into recovery to flash them.
Make sure you do a complete wipe and flash in the recovery as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
We just replied at the same time, my error is posted in my previous reply. If nothing else, recovering from backup 3 times today has built my confidence a bit hah:good:
i get the impression from this error: script aborted: assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
that the script is calling my device name and d2att is not being returned. how can i figure out what it really is?
itrunner said:
i get the impression from this error: script aborted: assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
that the script is calling my device name and d2att is not being returned. how can i figure out what it really is?
Click to expand...
Click to collapse
Looked in the build.prop file, mine is ro.product.device=d2can
so i guess that's why it's failing.
used root toolbox, changed the d2can to d2att, tried again.
failed with getprop("ro.product.device") == ""
this time nothing, i think i'm getting closer. will keep updating this thread in case anyone has a suggestion
I've Solved this!!
1.) Root Toolbox to change build.prop's ro.device from d2can to d2att
2.) Rom Manager, download and apply Clockwork Recover , downloaded and applied 6.0.3.1
3.) Boot to recovery.. BACKUP to internal memory, BACKUP #2 to external SD (paranoid)
4.) Wipe system, Wipe Cache, Wipe Davlink
5.) Applied my custom Rom with success
its good to see users figuring things out for themselves through research and trial/error. the best way to learn.
congrats, buddy.
Related
ATTENTION: Custom Android 3.2 ROM available! Both 3G and Wi-Fi users can enjoy Team Tiamat Xoom Rom 2.0.1 Manta Ray. If you want the latest features implemented by Team Tiamat, install Manta Ray; otherwise, if you want stock 3.2 with root, continue below.
IMPORTANT NOTE: This update is for the US Xoom Wi-Fi MZ604 with Android 3.1 ONLY!!! As of v05 of this update, the update script performs NO CHECKS of files before flashing rooted stock 3.2 system and boot images. This means it won't stop you from flashing on a Xoom 3G; it will just flash and you're left with the mess, if any. Please proceed only if you're tech-savvy with Android and the Xoom, ready to restore to stock 3.1 in case of issues, and good at troubleshooting. Please provide feedback and corrections, and I'll update the post as quickly as I can. Thanks!
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WI-FI MZ604 with Android 3.1 HMJ37. If you have a non-US Xoom Wi-Fi, this procedure may break your device. If you have a Xoom 3G, this procedure may break your device. If you're running a version of Android prior to 3.1, this procedure may break your device (update to 3.1 first).
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom Wi-Fi from 3.1 HMJ37 to 3.2 HTJ85B using ClockworkMod Recovery (update.zip)
Flashes system partition with rooted stock 3.2 image (minus the recovery overwrite script)
Includes Superuser.apk and su binary to enable functioning root (thanks, chainsdd)
Flashes the boot (kernel) partition with rooted stock 3.2 kernel (thanks, solarnz)
Stock kernel means no extras (overclocking, etc.) from custom kernels
Leaves existing recovery partition intact (stock 3.2 update overwrites it on every reboot)
Leaves user data intact
Includes Android 3.2 support for hardware SDCard (shows in Settings|Storage, /mnt/external1)
Outstanding Issues:
Too many steps: Include the edited updater-script, su, Superuser.apk in a custom update.zip
Requires stock 3.1 Boot partition (kernel): Need to include solarnz's stock rooted 3.2 boot.img and just flash that over whatever is there
Requires stock 3.1 HMJ37 System partition (ROM): Might include a stock 3.2 system.img and remove the checks for stock 3.1 system files, but it will make the .zip huge
Users with custom ROM's report issues after update: users suggest factory reset/full wipe (including user data) in ClockworkMod Recovery prior to updating (read through the thread for more info)
Superuser update available in market, but update fails: my bad for not including the latest and putting the apk in /system/app makes upgrading less easy. Delete superuser.apk using adb, terminal, or rootish file manager app, and the upgrade should work (thanks, GeekyGuy)
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You are currently running Android 3.1 (stock 3.1 images here, thanks, bwcorvus)
You've downloaded the modded Xoom Wi-Fi Android 3.2 update v05 (thanks to kurt5510 for the original OTA, thanks to solarnz for the rooted stock boot.img)
You've flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
[size=+1]PROCEDURE[/size]
Rename the modded Android 3.2 Update file to update.zip
Reboot into recovery
Reboot your Xoom
When the Motorola logo splash screen appears, press the Volume Down button to scroll through boot options and select "--> Android Recovery"
Press the Volume Up button to enter Android recovery
Perform update
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select. Note also if you are coming over from a custom ROM, users suggest doing a factory reset/full wipe (including user data) ClockworkMod Recovery prior to performing the following steps (read the thread for more info).
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "apply update from sdcard"
Select "Yes - Install /sdcard/update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
Enjoy your rooted Xoom Wi-Fi, running on Android 3.2!
[size=+1]POST-UPDATE NOTES[/size]
Custom kernels: [KERNEL][AOSP]Tiamat Xoom 2.0.0 "Katana" [Update: 07/14]
[size=+1]CHANGELOG[/size]
v05: Removed system file checks and patches; instead flashes 3.2 system image with Superuser.apk and su binary preinstalled and recovery overwrite removed.
v04: Included Superuser.apk and su binary; no need to have them prior to updating. Still requires stock 3.1 HMJ37 system/ROM.
v03: First release of modded update.zip, removes check for stock 3.1 boot partition, flashes solarnz rooted stock 3.2 boot.img
v02: Added su symlink to updater-script
v01: First release, modded updater-script for manual mod to update.zip file
Excellent work! Guide stuck for the time being.
Nice. Had just finished "downgrading" to stock 3.1 and was about to try my luck with the original update file. Then i saw this. Installs fine, but i do not seem to have root nor will superuser from market update su. (i did replace the file in the .zip and installed via cwm).
But damn 3.2 seems fast at first glance, but might just be me
If you have your Xoom powered down before you start, can you drag and drop the update.zip file to the SD card on your PC rather than doing the mount-and-copy? (If this seems like a stupid question, I only just rooted last weekend and don't want to take anything for granted!)
LynnL said:
If you have your Xoom powered down before you start, can you drag and drop the update.zip file to the SD card on your PC rather than doing the mount-and-copy?
Click to expand...
Click to collapse
As long as the file is there, you're good to go.
Can't seem to make it work. I have tried several different times.
My output is always:
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
are you on stock 3.1? afaik this only works on stock roms. thats the same error i get, and im running tiamat 1.1
By the way, i have a UK Xoom but i went to 3.1 via stock US FW.
eliteone said:
are you on stock 3.1? afaik this only works on stock roms. thats the same error i get, and im running tiamat 1.1
Click to expand...
Click to collapse
I'm running stock with a custom kernel and getting the same error.
you need to be running stock kernel i believe
eliteone said:
you need to be running stock kernel i believe
Click to expand...
Click to collapse
At this time, yes. solarnz made a rooted stock boot.img which i'm working on including in an update.zip.
xMemphisx said:
Can't seem to make it work. I have tried several different times.
My output is always:
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
Click to expand...
Click to collapse
Xoom 3G users will likely get this error.
Xoom Wi-Fi users on any ROM other than stock 3.1 HMJ37 will likely get this error.
You need to be Wi-Fi on stock 3.1 HMJ37 at this point.
I'm getting some corby apk error when trying to run the update. Using stock 3.1 but rooted.
Xoom wi-fi US version.
Oh never mind. I missed that i needed to be rooted on stock 3.1... I will await solarnz boot.img or start over tomorrow if i get too impatient
will this method wipe any of my data ?
Were do i find the stock 3.1 Kernel?
getting same problem as above
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
i'm on stock 3.1 wifi us rooted
Sk8er Boi said:
will this method wipe any of my data ?
Click to expand...
Click to collapse
It currently flashes over your boot partition and updates your system partition. User data is not affected.
jzun223 said:
Were do i find the stock 3.1 Kernel?
Click to expand...
Click to collapse
[IMAGES] HMJ37 (USA WiFi 3.1)
Sk8er Boi said:
getting same problem as above
"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
i'm on stock 3.1 wifi us rooted
Click to expand...
Click to collapse
What does it say on Settings | About tablet? Looking for Android version, Kernel version, and Build number.
EDIT: Also, through a terminal or ADB, look at /system/build.prop
What's the value for ro.build.fingerprint?
stachre said:
It currently flashes over your boot partition and updates your system partition. User data is not affected.
[IMAGES] HMJ37 (USA WiFi 3.1)
What does it say on Settings | About tablet? Looking for Android version, Kernel version, and Build number.
Click to expand...
Click to collapse
this is also happening to me my data is
build# hmj37
kernel 2.6.36.3-gc2bee64 [email protected]#1
version3.1
v03 posted, see OP.
I'm unable to install the 1.28.401.9 OTA update and was wondering if anyone else has the same issue - or whether I'm missing something obvious.
My 1X is unlocked and rooted but still running stock.
On completion of the OTA download I select to install and it boots into CWM Recovery with "Installation Aborted" at the bottom and
"E: Unknown volume for path [PATH] E: Can't mount INTERNALSDCARDownload..." etc.
So I select 'Install from SD card'>'choose zip...'> then go to Downloads and select the update file and get:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
So I disable signature verification, try again and get:
assert failed: check_cid(getprop("ro.cid")...
Then a string of 8 digit numbers and alphanumeric codes and finally
E: Error in /sdcard/Download...[PATH]
(Status 7)
Installation aborted
Anyone have any ideas why it's not working?
same problem......
Me too
Kevin & Orel - just to be sure, can you confirm that you are rooted and running stock as well please?
Yep unlocked and rooted, but running stock. Once in CWM Recovery I see the same errors as you.
yes before I was sfr version and my htc is root & recovery & stock htc .....
Reinstall stock recovery
Sent from my HTC One X using XDA
tested stock recovery, but nothing happens ....
if I try to flash the uptade I receive an error message.
Appears when I have the stock recovery, I can not access the recovery to flash, I have a black page with a phone 3 green arrow and then a red box ...
And people told me I was silly to tell people NOT TO TRY AND RUN AN OTA ON A ROOTED PHONE!!!
Seriously, guys. Historically it's been nothing but problematic trying to apply an OTA to a rooted phone. If you want it THAT bad go custom
orel28 said:
tested stock recovery, but nothing happens ....
if I try to flash the uptade I receive an error message.
Appears when I have the stock recovery, I can not access the recovery to flash, I have a black page with a phone 3 green arrow and then a red box ...
Click to expand...
Click to collapse
Did you relock?
http://forum.xda-developers.com/showpost.php?p=25002854&postcount=736
You need stock recovery to apply OTA...
You dont flash it yourself from recovery!!!
The update program does that
i just flash .zip stock ...
---------- Post added at 07:02 PM ---------- Previous post was at 06:54 PM ----------
how to get back to a stock rom compatible?
Where can I find the .zip file to install stock recovery?
Squidinker said:
I'm unable to install the 1.28.401.9 OTA update and was wondering if anyone else has the same issue - or whether I'm missing something obvious.
My 1X is unlocked and rooted but still running stock.
On completion of the OTA download I select to install and it boots into CWM Recovery with "Installation Aborted" at the bottom and
"E: Unknown volume for path [PATH] E: Can't mount INTERNALSDCARDownload..." etc.
So I select 'Install from SD card'>'choose zip...'> then go to Downloads and select the update file and get:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
So I disable signature verification, try again and get:
assert failed: check_cid(getprop("ro.cid")...
Then a string of 8 digit numbers and alphanumeric codes and finally
E: Error in /sdcard/Download...[PATH]
(Status 7)
Installation aborted
Anyone have any ideas why it's not working?
Click to expand...
Click to collapse
I have the same problem....
After i restore the first rom my phone comes i dont get the error.....
1.28
kevin_d said:
Yep unlocked and rooted, but running stock. Once in CWM Recovery I see the same errors as you.
Click to expand...
Click to collapse
Same problem over here!!!
broncogr said:
You need stock recovery to apply OTA...
You dont flash it yourself from recovery!!!
The update program does that
Click to expand...
Click to collapse
+1 that
1. Download the OTA using the handset
2. Flash stock recovery (there's a download link in the CWM thread iirc)
3. Reboot
4. Go to Settings -> About -> Software Updates -> Check now
Assuming you already downloaded it, you'll be prompted to install it
5. Once the OTA update runs (it reboots twice) reboot into fastboot mode and reflash CWM
CWM can't flash the OTA and I personally didn't have to relock my device (It's not an RUU update)
Flash RUU DONT root and try again...
Once updated root again
amacrobie said:
2. Flash stock recovery (there's a download link in the CWM thread iirc)
Click to expand...
Click to collapse
Where can I find this download?
http://loadbalancing.modaco.com/download.php?file=endeavoru_recovery_signed.img
Squidinker said:
endeavoru_recovery_signed.img
Click to expand...
Click to collapse
Sorry, but how do I load this file?
first time posting here, and it's my first time trying to root my phone.
i used the toolkit, and that went without any problems. the phone was rooted and unlocked, and I downloaded CWM.
After I dl'ed CWM, I downloaded the ROM Android Revolution HD. There were two files I downloaded, the actual rom itself, and the firmware that comes alongside with it. They are both zip files, and I placed them both into my phone's storage.
I booted CWM, and chose to flash the actual ROM first. That worked fine, and I thought I should flash the firmware as well. Some error came up, and it said it was aborted. No big deal, so I reboot, and it shows the screen of the phone trying to boot for at least 30 minutes.
I restart my phone, and then I flash the ROM again. Tried it again, and I'm going to leave it attempting to boot into the ROM over night.
If I wake up with this problem still, what is a method to work around this?
okay it seems that i can not restore my phone back to the factory settings, and I can't connect to a mobile network.
the phone does now boot into android revolution HD, but I just need to figure out why I can't get on a mobile network
Welcome kyro- okay usually ARHD has 2 files and one is the ROM itself and the other may be the Superwipe file, they are both .zip files but perhaps you are confusing the Superwipe file with a firmware file (I am going from memory here so bear with me)
If this is the case go into CWM again and flash the Superwipe FIRST then flash the Rom file.
I am hoping it's something simple like this.
Just a suggestion
LL13-
i wish it was that simple, but i seem to have messed my firmware up in some way. everything else works fine, except for the radio. Baseband version is unknown at the moment, after wiping data cache system battery and using the super wipe as well.
from the website, here are the three links to download from
Firmware package
Flash it in recovery by selecting "apply update.zip from /sdcard"
Firmware package contains newest radio and bootloader for 4.0.x ROMs
Android Revolution HD 4.0.0
MD5 Checksum: 8C5E76C0665E088F721780BF1391C040
Direct link to 6 fast server that will randomly use one of our sources ---
Thanks to Mavy170, Whiskey103, MarcoHD, Pili21181, Lizard & Denngie ---
Super Wipe Lite
This script will erase and format your system and cache partition using EXT4 file-system
It will also wipe /data partition, but /data/media (virtual SD card) will be untouched
Click to expand...
Click to collapse
when i flash it in recovery mode, this is the error
assert failed: getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
so i can't connect to a mobile network until this is properly installed i'm assuming.
My Kindle Fire has bad hardware, so I need to return it. Currently has TWRP 2.5.0.0 installed, and had CM until I wiped it.
I downloaded the stock software and have been following this thread's instructions. However, whenever I try to install the stock ROM I get this:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
In doing further research, it may mean I need to downgrade TWRP - some people have had trouble with versions newer than 2.3.3.0. And I just can't figure out how to do that successfully. I download the img file, follow these instructions, but when I put in "su" it says
su: not found
I tried connecting the Kindle Updater but the drivers don't seem to recognize it when I've got a ROM installed and booted up (though USB storage works when enabled), and while it DOES seem to see it and proceed when I'm booted into TWRP recovery, it doesn't actually do anything and just sits on updating partition information or something.
I'm VERY f'n frustrated. Could someone please do me a favor and hold my hand through this? I just can't get the damn thing to revert to stock.
QFT said:
My Kindle Fire has bad hardware, so I need to return it. Currently has TWRP 2.5.0.0 installed, and had CM until I wiped it.
I downloaded the stock software and have been following this thread's instructions. However, whenever I try to install the stock ROM I get this:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
In doing further research, it may mean I need to downgrade TWRP - some people have had trouble with versions newer than 2.3.3.0. And I just can't figure out how to do that successfully. I download the img file, follow these instructions, but when I put in "su" it says
su: not found
I tried connecting the Kindle Updater but the drivers don't seem to recognize it when I've got a ROM installed and booted up (though USB storage works when enabled), and while it DOES seem to see it and proceed when I'm booted into TWRP recovery, it doesn't actually do anything and just sits on updating partition information or something.
I'm VERY f'n frustrated. Could someone please do me a favor and hold my hand through this? I just can't get the damn thing to revert to stock.
Click to expand...
Click to collapse
Well if you can still access USB storage in TWRP, you can download a .zip file for the TWRP version you want and flash it in recovery. Ichigo has made a number of TWRP versions into .zip files for easy flashing.
Guitarman said:
Well if you can still access USB storage in TWRP, you can download a .zip file for the TWRP version you want and flash it in recovery. Ichigo has made a number of TWRP versions into .zip files for easy flashing.
Click to expand...
Click to collapse
OK, downloaded a zip for a 2.3.3.0 build... booted into TWRP, then ran Install with the ZIP. I get:
E:Error executing updater binary in zip '/sdcard/twrp-2.3.3.0.test5.p500.zip'
Error flashing zip '/sdcard/twrp-2.3.3.0.test5.p500.zip'
Any ideas? Am I doing something wrong?
What exactely do you mean by "bad hardware"? It's also possible that your downloaded update.zip file has been corrupted somehow.
Guitarman said:
What exactely do you mean by "bad hardware"?
Click to expand...
Click to collapse
It shuts the screen off and won't come back on until a forced reboot while plugged in is performed. It's an issue multiple owners report; Amazon typically replaces them for new owners (which I'm not)
QFT said:
It shuts the screen off and won't come back on until a forced reboot while plugged in is performed. It's an issue multiple owners report; Amazon typically replaces them for new owners (which I'm not)
Click to expand...
Click to collapse
Did it ever do that on the stock software?
Guitarman said:
Did it ever do that on the stock software?
Click to expand...
Click to collapse
I rooted it pretty soon after getting it, but yeah I think I did notice that happened once.
I had the same issue and re installed COTR and it worked
Hi Guys,
I am trying to Flash CM 10.1.2
http://get.cm/?device=d2att&type=stable
I followed the usual steps
1. Installing the latest CWM recovery (recovery-clockwork-6.0.3.6-d2att)
2. USB Debugging is ON
3. Boot into Recovery
4. Restore Factory Settings
5. Wipe cache partition
6. Wipe Dalvik Cache
7. Flash CM 10.1.2.zip
8. I get Error 7 and installation is not completed.
Upon looking online I found out that I have to edit 'updater-script' and remove asserts
The file looks like this and I deleted the asserts, Line 1 only
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
symlink("/system/xbin/su", "/system/bin/su");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/adjtimex", "/system/xbin/arp", "/system/xbin/ash",
"/system/xbin/awk", "/system/xbin/base64", "/system/xbin/basename",
Then same steps and I get error Installation Aborted.
Then I remove all the asserts in the file i.e. Line 2 - Line 5
Then same steps and I get error Installation Aborted.
Not sure what am I missing
Right now I am on 4.1.2
Somewhere online I read that I have to update my modem manually but it is already updated.
PFA the screen shot of my About Device
After the installation is aborted, I am able to boot into stock Android i.e. 4.1.2
Let me know what am I missing ?
Is your bootloader updated also?
DMF1977 said:
Is your bootloader updated also?
Click to expand...
Click to collapse
not sure about that, how to check that and update if it is not updated ?
praddz said:
not sure about that, how to check that and update if it is not updated ?
Click to expand...
Click to collapse
As you can see, from your error that you posted, CM 10.2 only accepts up to DLK3 for I747. If you have updated your phone to MG2 for the bootloader (which I'm assuming you did since your having issues, as well as your baseband has been updated), then CM 10.2 will fail. You would need to downgrade to DLK3 for the I747.
To do so, simply download the recovery-flashable DLK3 zip in the OP of this bootloader thread. Don't forget: FOR RECOVERY TO RECOGNIZE A NEWLY FLASHED BOOTLOADER, A REBOOT IS NECESSARY BEFORE PROCEEDING WITH FLASHING ROMS REQUIRING CERTAIN BOOTLOADERS.
MercilessLTD said:
As you can see, from your error that you posted, CM 10.2 only accepts up to DLK3 for I747. If you have updated your phone to MG2 for the bootloader (which I'm assuming you did since your having issues, as well as your baseband has been updated), then CM 10.2 will fail. You would need to downgrade to DLK3 for the I747.
To do so, simply download the recovery-flashable DLK3 zip in the OP of this bootloader thread. Don't forget: FOR RECOVERY TO RECOGNIZE A NEWLY FLASHED BOOTLOADER, A REBOOT IS NECESSARY BEFORE PROCEEDING WITH FLASHING ROMS REQUIRING CERTAIN BOOTLOADERS.
Click to expand...
Click to collapse
Yes i did the same, downloaded the bootlaoder, flashed using ODIN, restart, then again boot into recovery, wiping everything
again got the same error while flashing
Can you give us a detailed line for line output concerning the Installation Aborted message?
praddz said:
Yes i did the same, downloaded the bootlaoder, flashed using ODIN, restart, then again boot into recovery, wiping everything
again got the same error while flashing
Click to expand...
Click to collapse
If you flashed using ODIN, you didn't use the right package. You're supposed to use the recovery-flashable .ZIP package for DLK3. (Unless you want to switch your modem at the same time. No reason to do that though.)
Also, never remove asserts from a flasher script unless you intend on forcing things to flash when they shouldn't. There's usually a good reason for ROMs and other flashable tools to require a specific bootloader, device, or modem.
MercilessLTD said:
Can you give us a detailed line for line output concerning the Installation Aborted message?
Click to expand...
Click to collapse
BB version is now:I747UCDLK3
Between CWM recovery menu and the below error message I see Android bunny lying down with a red rectangle on it.. something like warning...
the error is as below:
ClockworkMod Recovery v6.0.3.6
Warning:No file_contexts
-- Installing: /sdcard/goomanager/cm-10.1.2-d2att.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
praddz said:
BB version is now:I747UCDLK3
Between CWM recovery menu and the below error message I see Android bunny lying down with a red rectangle on it.. something like warning...
the error is as below:
ClockworkMod Recovery v6.0.3.6
Warning:No file_contexts
-- Installing: /sdcard/goomanager/cm-10.1.2-d2att.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
Baseband version has nothing to do with the bootloader. Those are 2 separate parts of your device. The steps you need to follow are:
Flash this ZIP in recovery
Reboot back to recovery
Install the ROM
Don't modify the ROM in any way.
If you keep having issues, you might want to switch to TWRP; I stopped using CWM a long time ago because of poor logging and the unfriendly UI.
praddz said:
BB version is now:I747UCDLK3
Between CWM recovery menu and the below error message I see Android bunny lying down with a red rectangle on it.. something like warning...
the error is as below:
ClockworkMod Recovery v6.0.3.6
Warning:No file_contexts
-- Installing: /sdcard/goomanager/cm-10.1.2-d2att.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
Have you ensured a good download? Have you checked the md5 of your cm-10.1.2-d2att.zip versus the md5sum that get.cm gives as: d64cbc114d46d479997c38f5cf070043
dstruct2k said:
Baseband version has nothing to do with the bootloader. Those are 2 separate parts of your device. The steps you need to follow are:
Flash this ZIP in recovery
Reboot back to recovery
Install the ROM
Don't modify the ROM in any way.
If you keep having issues, you might want to switch to TWRP; I stopped using CWM a long time ago because of poor logging and the unfriendly UI.
Click to expand...
Click to collapse
I did the same, reverted to original rom dump,
Flash was successful.
Now its on the boot screen for the last 7 minutes..
is this usual ?
praddz said:
I did the same, reverted to original rom dump,
Flash was successful.
Now its on the boot screen for the last 7 minutes..
is this usual ?
Click to expand...
Click to collapse
I usually give up waiting after about 15 minutes goes by. Sometimes things don't flash correctly I guess, I've never understood it.
You did wipe /data and also flash GApps, right? Most ROMs should still boot without GApps, but they're next to useless without the apps. If you didn't wipe /data, you might not be able to boot on a new ROM.
dstruct2k said:
I usually give up waiting after about 15 minutes goes by. Sometimes things don't flash correctly I guess, I've never understood it.
You did wipe /data and also flash GApps, right? Most ROMs should still boot without GApps, but they're next to useless without the apps. If you didn't wipe /data, you might not be able to boot on a new ROM.
Click to expand...
Click to collapse
I think I dont have the right gapps,, the phone has started but its showing Set up Wizard has stopped
The Gapps I have are for 4.1.2, may be thats y,, can u share the link for the one related to this ?
praddz said:
I think I dont have the right gapps,, the phone has started but its showing Set up Wizard has stopped
The Gapps I have are for 4.1.2, may be thats y,, can u share the link for the one related to this ?
Click to expand...
Click to collapse
http://goo.im/gapps
You need to read the chart to see which one to download depending on your Android version.
Do not just flash the right ones over top of the wrong ones. Wipe /system and /data, flash the ROM again, then flash (the correct) GApps. This can all be done in one trip through your recovery, you don't need to reboot between steps.
At op, these people are helping u out tremendously, especially with posting links and everything for u when they could just as easily not answer, or make u search yourself... The very least u could do is hit the "thanks" button to show your appreciation!! That is all...
dstruct2k said:
http://goo.im/gapps
You need to read the chart to see which one to download depending on your Android version.
Do not just flash the right ones over top of the wrong ones. Wipe /system and /data, flash the ROM again, then flash (the correct) GApps. This can all be done in one trip through your recovery, you don't need to reboot between steps.
Click to expand...
Click to collapse
Finally it worked, thanks a ton, I think your Bootloader link did the trick
praddz said:
Finally it worked, thanks a ton, I think your Bootloader link did the trick
Click to expand...
Click to collapse
Worked great for me too! thanks a lot! I've been searching a lot for the past few minutes with no avail. I'm glad I found this thread!
I am facing a weird issue.
My internal memory is shown as full even though I don't have stuff > 4 GB
When I scan sd card using ES Explorer it scans only 3.3 GB but shows 11.57 GB is used
This is pretty weird as I have looked up the data using my laptop as well, nothing shows ?
Did I install it properly ? Somebody else knows about this issue ?
I am attaching the screen shot of ES Explorer
praddz said:
I am facing a weird issue.
My internal memory is shown as full even though I don't have stuff > 4 GB
When I scan sd card using ES Explorer it scans only 3.3 GB but shows 11.57 GB is used
This is pretty weird as I have looked up the data using my laptop as well, nothing shows ?
Did I install it properly ? Somebody else knows about this issue ?
I am attaching the screen shot of ES Explorer
Click to expand...
Click to collapse
You may not be showing hidden folders (in Android, they start with a period '.') or Android data, like downloads from games, other apps, etc.
In ES File Explorer, you can go to the settings and I believe under display, there is a way to show hidden folders. Also, a great app that will show the breakdown of all storage is called DiskUsage. It will give a graphical breakdown of either your internal phone storage or external SD card.
MercilessLTD said:
You may not be showing hidden folders (in Android, they start with a period '.') or Android data, like downloads from games, other apps, etc.
In ES File Explorer, you can go to the settings and I believe under display, there is a way to show hidden folders. Also, a great app that will show the breakdown of all storage is called DiskUsage. It will give a graphical breakdown of either your internal phone storage or external SD card.
Click to expand...
Click to collapse
That issue has been resolved, some backups were buried deep down which I was unable to find, got hold of them now.
BTW when I pull down the notification Drawer if i do i short press on time it takes me to CM10 alarm clock, can I modify this to a custom app of alarm clock ?
when i long press, I got an option to select an app for alarm and i selected the app i want.
I just want to know if there is any where I can update the short press as well.
I did not find anything in the settings