Database Info

[Q] trying to update my Pure Root WW 8.4.4.11 via CWM

Very new to this stuff but have experimented in simple tweaking of the tf101
- I tried updating to 3.2 via the file uploaded from this thread" [UPDATE][WW] CWM Rooted Update to STOCK 8.6.5.7 from STOCK 8.4.4.11 WW only "
but I keep getting this error:
assert failed: apply_patch_check("/system/app/SystemUI.apk"
Error in /sdcard etc etc
(Status 7)
- please correct me if im wrong(cause maybe I am), the steps I did was:
access CWM (power, -volume then a quick +volume)
install zip from sd card/ choose zip from sd card . .. yes - Install 8.6.5.7_FOTA_WW_root_rec.zip
then after "Verifying Current System..."
i get
assert failed: apply_patch_check("/system/app/SystemUI.apk"
Error in /sdcard etc etc
(Status 7)
- just so you'd know, i changed the looks of my bar buttons from this thread" [MOD] Stock/Xoom bar buttons for 3.1 rom (8.4.4.5 - 8.4.4.11 - Prime 1.6) "
- but as per the instructions before updating to 3.2, I switched back to the stock buttons which were still included in the thread w/o problems . . did it a second time after my first fail of attempting to update to 3.2
Any ideas on how to fix this, w/o wiping my entire data is very much appreciated..
current build: ww 8.4.4.11-20110711

FOTA check EVERY files it update, so since your MOD changed SystemUI.apk. FOTA will not work for you. You need to be very very close to stock for any FOTA patch to work.

Wiping /data will have no effect. The SystemUI in on your /system partition.
The updated script will check all the sha1 hashes of the system apps that it patches to make sure that it is patching the right one. If these fail, then the patch fails, which means the update fails.
After the patches apply, reboot into recovery from the menu. It will flash the blob!
You can unzip the update, and edit the updater-script in META..com...google...android
You could probably keep the odex file if it isn't modded. There will be two references- one to check the patch and one to apply the patch. Delete them both. Zip it all back together, maybe sign it for good measure, then try flashing again. You might not need to sign, but it wouldn't hurt.
EDIT: Ohh, I'm not sure if CWM will finish the OTA. It will probably patch all the system files and then bomb on the blob because it tries to copy it to the staging partition, which isn't mounted. You might be able to mount it through adb, or you could mod CWM to mount it automatically

it worked! thanks!!
i updated the updater-script , maybe removed too much since im now getting a force close on the systemui.apk and currently dont have any home buttons.. bummer..
but i believe i could just push a 3.2 systemui.apk file from one of the forums here
currently at WW 8.6.5.7
3.2
btw, this is what i removed from the line:
assert(apply_patch_check("/system/app/SystemUI.apk", "b630f0a4f2d1c8e450f6269a997c950d11694ce9", "4cbd4f2cb3f4ba71d803f930b5a9c8f850bdda31"));
set_progress(0.397204);
overdid it, or under did it? i'll keep this as reference for the future

That will be OK. There is another line much further down that actually applies the patch. That is probably why you are getting FC's. The modded file was patched, but since it was modded, the patch probably corrupted it. Pushing a new version would probably work.
Sent from my T-Mobile G2 using XDA App

[Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G Updated by Romman0

It was requested that I port a tool from the A100 to the Blaze 4G, so here it is.
I do not own a Blaze 4G, this was ported with information provided by a fellow member, please report any issues and I will fix them ASAP!
Blackhole System Wipe
What is it?
It's a tool designed to make your life just a little bit easier by doing all of your wiping for you, then setting UMMU for use with dKnight reset ROM.
What does it do?
it's pretty straight forward, it formats then checks /cache /system /data, then aligns the same partitions, then does a little extra clean up at the end. It then places a log file on your sdcard for troubleshooting if anything goes wrong, or right.
What does it NOT do?
It does NOT touch internal or external SD, boot, recovery, sd-ext or any other partitions besides cache, data and system, and some directory cleaning on sdcard.
How do I use it?
It's flashed via Install from SD, same as a ROM. After it completes (around 60 seconds) flash your new ROM. Now it sets UMMU according to dKnight-reset, however it shouldn't interfere with any other ROM installation. Leaves it nice and clean and in better shape then normal Wiping via CWM options.
Other versions?
This is the Wipe only version of what is normally a full Nullify script, which is a much longer and in depth process of cleaning your partitions. It uses DD to write zeros all the way across the partition, ensuring no stray data is left behind, at all. Its about as factory fresh as you can get without coming from the factory. There is also a Cache Wipe, which wipes /cache only and leaves /system and /data alone, and does dalvik-cache and some sd card cleanup, then fixes permissions. Good for cleanup for bugs or after changes to the ROM, such as kernels or flashable mods, or after extensive TiBu activity/removal of system apps, etc. Also available as a Nullify version. I don't intend to release these other versions here, however if you want them, I'll deliver!
Download
Blackhole System Wipe 2.0a Blaze Updated by Romman0
Updated, 2.0a was fixed by Romman0 to work with the ICS update, should now work and not give the device ID error.
UPDATE
Romman0 was kind enough to do some more work on this and update it, as you can see in this post HERE Please give it a test and give him some thanks!
Thanks to:
Trevor7428: For inspiring the idea to port to this device, it seems to need some loving.
da-pharoah: The original work I based this on came from his Hellfire Kindle Nullifier, rewritten and modified into the Blackhole Wipe/Nullifier for A100, then made into this port here.
Romman0: Updating it with some long needed fixes, thanks!
More to come as I remember, this is a quicky post.

Ya this guy is awesome, just like everyone else Helping us blaze owners who don't own the device. If u have the erikmm rom. Try to flash this first then flash rom right after. Its set up so u don't have to do anything else in cwm. Except flash these too things. He just put this together in the past 24 hours for the blaze basically. If have any probs during flash. Send him a log by opening file manager then navigate too /cache/recovery then long click on the only item there and share . If enough people try this. He can profect it more. And the rom would run more smoothed then just normal follow instructions flash. It won't hurt to try. If something goes wrong. Just flash rom how u norm would then send him the log.

trevor7428 said:
Ya this guy is awesome, just like everyone else Helping us blaze owners who don't own the device. If u have the erikmm rom. Try to flash this first then flash rom right after. Its set up so u don't have to do anything else in cwm. Except flash these too things. He just put this together in the past 24 hours for the blaze basically. If have any probs during flash. Send him a log by opening file manager then navigate too /cache/recovery then long click on the only item there and share . If enough people try this. He can profect it more. And the rom would run more smoothed then just normal follow instructions flash. It won't hurt to try. If something goes wrong. Just flash rom how u norm would then send him the log.
Click to expand...
Click to collapse
+1 to this! great job bro!

Wow, what an awesome tool. Who doesn't like user friendly?
Sent from my SGH-T769 using xda premium

Hey this seems pretty cool so i figured i would give it a try but...As soon as i go to accept the install from cwm it says
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/Blackhole-System-Wipe-Blaze-2.0.zip
(status 6)
Installation aborted.
Thought maybe it was a bad download so i re-downloaded it and it still did the same thing. Not sure what happend.

chrisxbell714 said:
Hey this seems pretty cool so i figured i would give it a try but...As soon as i go to accept the install from cwm it says
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/Blackhole-System-Wipe-Blaze-2.0.zip
(status 6)
Installation aborted.
Thought maybe it was a bad download so i re-downloaded it and it still did the same thing. Not sure what happend.
Click to expand...
Click to collapse
Status 6 usually means I forgot a space or " or ; somewhere, thanks for reporting it I'll see what I missed and fix it. I can't tonight but I'll try to get it ironed out tomorrow!
Tapatalked from my Galaxy S II.

Alright everyone, I'm sorry it took me so long to get this taken care of, but I didn't forget!
Blackhole System Wipe 2.0a is now available! Now including correct punctuation!
Seems I missed a few " marks in there, so, status 6.
If someone could please give this a run and verify the status 6 error is gone, I would greatly appreciate it, sadly I can't do it myself so I'm running it kind of blind.
Now back to taking on to many projects and getting buried under my A100 again.

Status 6
Just ran it. Status 6 error is gone however it is now replaced by status 7
here's exactly what it says:
--setting ummu--
mount() expects 3 args, got 1
E: error in /sdcard/blackhole-system-wipe-blaze-2.0a.zip
(status 7)
Installation aborted

is this a dead project?

Re: [Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G
tonytaylor said:
is this a dead project?
Click to expand...
Click to collapse
No one ever reported on the fixed version, I don't own nor ever owned this device, so I just left it. There's not really much to do, if it works then it did its job, not really a project for it.
Sent from my HTC DNA

Re: [Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G
tonytaylor said:
is this a dead project?
Click to expand...
Click to collapse
I'd like one that works for our device too this old one doesn't work since we got ICS I think
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!

Re: [Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G
johnb380 said:
I'd like one that works for our device too this old one doesn't work since we got ICS I think
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!
Click to expand...
Click to collapse
Again, I don't have one, you guys have to tell me what's not working and get me logs or I can't fix it.
Sent from my HTC DNA

Re: [Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G
pio_masaki said:
Again, I don't have one, you guys have to tell me what's not working and get me logs or I can't fix it.
Sent from my HTC DNA
Click to expand...
Click to collapse
How do u get a log cat of a wipe in recovery? And it seems to me when it gets to the get.prop it is now different then it was so it aborts the process I'm gonna try to look again
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!

All that needs to be fixed for this to work on our device is to change a couple of lines in the updater script:
remove the assert lines in the original and replace with this: #assert(getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze");
Then remove the UMMU lines at the bottom of the script as these are not needed and are not written correctly..
If it is ok with the original dev I will post an updated zip.. Just let me know either here or via pm...
Thanks

i cant even get it to install
Finding update package...
Opening update package...
Installing update...
Check Failed! Wrong device!
assert failed: getprop("ro.build.product") == "blaze4g" || getprop ("ro.build.product") == "full_blaze4g"
E:Error in /sdcard/Install ROMS/Blackhole-System-Wipe-Blaze-2.0a.zip
(Status 7)
Installation aborted.

Re: [Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G
Racing19969 said:
All that needs to be fixed for this to work on our device is to change a couple of lines in the updater script:
remove the assert lines in the original and replace with this: #assert(getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze");
Then remove the UMMU lines at the bottom of the script as these are not needed and are not written correctly..
If it is ok with the original dev I will post an updated zip.. Just let me know either here or via pm...
Thanks
Click to expand...
Click to collapse
Yeah go ahead, feel free. The UMMU was added as I was told it was needed at the time, I just went by the information I was given, never even seen a blaze before. I know every other device I've used didn't need that added at all, mounts were handled normally.
Sent from my HTC DNA

Pio, fancy to see you here. Lol. Thx for taking to time to port over your script.

Re: [Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G
Romman0 said:
Pio, fancy to see you here. Lol. Thx for taking to time to port over your script.
Click to expand...
Click to collapse
Lol hey romman! Yeah an a100 user requested it a long time ago, hopefully they can get it back into working shape, should be easy as they have the device
Sent from my HTC DNA

pio_masaki said:
Yeah go ahead, feel free. The UMMU was added as I was told it was needed at the time, I just went by the information I was given, never even seen a blaze before. I know every other device I've used didn't need that added at all, mounts were handled normally.
Sent from my HTC DNA
Click to expand...
Click to collapse
I made the tweaks that Racing suggested and tested it out. It seemed to work. All I did to verify was wipe and try to boot. It failed to boot so I'm guessing /system got wiped, and I assume all the others went fine also.
I'll pm pio to see if he will update the op with this version, if you guys test it out and like it.
View attachment Blackhole-System-Wipe-Blaze-2.0b.zip

[Port][Recovery][Tool] Blackhole System Wipe 2.0a Blaze 4G
Romman0 said:
I made the tweaks that Racing suggested and tested it out. It seemed to work. All I did to verify was wipe and try to boot. It failed to boot so I'm guessing /system got wiped, and I assume all the others went fine also.
I'll pm pio to see if he will update the op with this version, if you guys test it out and like it.
View attachment 1841819
Click to expand...
Click to collapse
Still subscribed lol thanks for the update, I'll add it in if it seems to work for them.

[Q] Flashing problems.

Hello everybody.
I've scoured these forums for a few days now, in hope that I can resolve this very frustrating problem but, alas, I've failed in my mission and have had to resort to picking your brains. (sorry about that!)
I'm running Cyanogen mod 7 on my T-Mobile G2 GSM and so far the ROM has worked brilliantly. The only reason I'd like to change is because of the poor GPS. I've tried a patch and the command fix but both of them didn't work for me.
Anyway... When I boot into Clockwork mod recovery (and wipe all the necessary files) and try to load my new ROM, I'm presented with an error message similar to this:
------------------------------------
finding update package...
opening update package...
E:error in / [ROM NAME & LOCATION]
Install Aborted
------------------------------------
I've tried downloading the rom several times via different websites, tried different ROMs all together, followed every bit of advice I could muster on here, and even purchased a new memory card... Just in case.
It's really frustrating though because I have to use recovery to get Cyanogen back (I need it to tether or I have no internet at home!) and that takes so long each time.
As you can probably imagine, it's really frustrating .
Any help would be massively appreciated!
Thanks again,
Bacoon.

Bacoon said:
finding update package...
opening update package...
E:error in / [ROM NAME & LOCATION]
Install Aborted
Click to expand...
Click to collapse
on sdcard /mnt/sdcard/clockworkmod folder there is a log take a look at it
I think you have to flash a corresponding CWM by fastboot utility

Thank you for getting back to me!
There are 2 that I can see. Should i go for Recovery.log or Report.log?
It's also giving me lots of options to view it... Should I use html viewer? It seems like the only thing that'd work.
Cheers!
EDIT:
I used the HTML viewer on "Report.log" and it came up with a HUUUGE list. Anything in particular I should be looking for, mate?

Bacoon said:
Thank you for getting back to me!
There are 2 that I can see. Should i go for Recovery.log or Report.log?
It's also giving me lots of options to view it... Should I use html viewer? It seems like the only thing that'd work.
Cheers!
Click to expand...
Click to collapse
report.log is generated from cwm recovery menu to report them errors
It says open ROM Manager to repport the issue
recovery.log in a general log to describe CWM activity
I think easy way is to change to a CWM that will allow you to flash that ROM
(I can't tell you exactly because I don't have links)
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
to see/edit files use notepad or better Notepad++ that's a decent editor/viewer best Notepad replacement
I don't know give me a link to that log or better think to change CWM recovery...

alsnxpl Ancient
try CM 10.1
---------- Post added at 03:34 AM ---------- Previous post was at 03:29 AM ----------
Android_Number17 said:
try CM 10.1
Click to expand...
Click to collapse
By Mardon

REALLY NEED HELP assert failed: motorola.steflash("/tmp/steflash")

need help... I cannot apply any updates to my AT&T Atrix 2.
i keep getting this error
assert failed: motorola.steflash("/tmp/steflash")

Milenko2121 said:
need help... I cannot apply any updates to my AT&T Atrix 2.
i keep getting this error
assert failed: motorola.steflash("/tmp/steflash")
Click to expand...
Click to collapse
What update are you trying to install? OTA updates usually require a stock system, so if you've modded your system then you'll probably need to FXZ a clean setup. *Note - ICS has no offical FXZ and should use the appropriate resources according to the version you have.
If you post more info about what you have and what you're trying to achieve then I'm sure we'll be able to help you along.

I'm trying to flash the official AT&T ICS that released yesterday.
I was originally rooted with bootstrap on 2.3.6 with the Lithium Rom.
I unrooted the phone, flashed 2.3.6 with RSDLite to get a clean phone. This is when I tried the OTA which gives me that error.
I have tried multiple scripts here. I've used RSDLite and also the fastboot scripts to return to 2.3.5/2.3.6 from ICS(or GB) countless times.
I've never had this much trouble before.

has anyone had this issue? i can't even find anything about this on google.

well if this helps anyone at all.
I am flashing above 50% battery.
after RSDLite to 2.3.6 I still get this error, but it shows 2.3.6 just fine when I start up again.
When I do the update for ICS it does everything just fine all the way up until "updating STE BP"
this is where it gets held up and throws the error.
updating STE BP ..
assert failed: motorola.steflash("/tmp/steflash")
E:error in /cache/Blur_Version.55.13.25.MB865.ATT.en.US.zip
(Status 7)
Installation Aborted
I have tried the method of downloading it straight from OTA and also from copying the file from their website to my SD Card and installing this way.
Both methods result in the problem.
the exact method I have been doing is this.
I was originally on 2.3.6 rooted bootstrap on Lithium rom
I did the clean up method for bootstrap and then ran the unroot script.
Then used RSDLite to flash to 2.3.5 (tried straight to 2.3.6 as well)
when it reboots it still throws the error even for 2.3.5/6 steflash
I then do the OTA for ICS over WiFi which again throws the error.
I would extremely appreciate any possible help you guys could give.
UPDATE:
grabbed this from the log file. here is where the STEFLASH code starts.
Code:
Extracted file "/tmp/steflash/config.txt"
minzip: Extracted file "/tmp/steflash/cops_data.csd"
minzip: Extracted file "/tmp/steflash/flash_archive.zip"
minzip: Extracted file "/tmp/steflash/production_loader.ldr"
minzip: Extracted file "/tmp/steflash/prologue_loader.ldr"
Entered SteFlashFn()
updating devtree ...
Unmounted system image
updating STE BP ..
MID launched
Flashing timed out. killing mid(97); waiting for MID exit.
Flashing failed, MID exited;; retry.
MID launched
Got MfaResult signal with value fail
Flashing failed, MID exited;; retry.
MID launched
Got MfaResult signal with value fail
Flashing failed, MID exited;; retry.
script aborted: assert failed: motorola.steflash("/tmp/steflash")
assert failed: motorola.steflash("/tmp/steflash")
E:Error in /cache/Blur_Version.55.13.25.MB865.ATT.en.US.zip
(Status 7)
Installation aborted.
blk: partition "userdata" size 4961730560 not a multiple of io_buffer_size 524288
I:Set boot command ""

Anyone?
Sent from my MB865 using xda app-developers app

Milenko2121 said:
I'm trying to flash the official AT&T ICS that released yesterday.
I was originally rooted with bootstrap on 2.3.6 with the Lithium Rom.
I unrooted the phone, flashed 2.3.6 with RSDLite to get a clean phone. This is when I tried the OTA which gives me that error.
I have tried multiple scripts here. I've used RSDLite and also the fastboot scripts to return to 2.3.5/2.3.6 from ICS(or GB) countless times.
I've never had this much trouble before.
Click to expand...
Click to collapse
Milenko2121 said:
has anyone had this issue? i can't even find anything about this on google.
Click to expand...
Click to collapse
While I'd like to tell you that you searching on Google was the right approach, you have come up short because these things have been addressed countless times here on xda. So, anyone else reading this, please include "xda" in your Google searches. That will point you back here, whereas otherwise searching xda FROM xda yields less than satisfactory results at times.
You were on 2.3.6 and wanted to update to ICS, but you had the Atrix 2 Bootstrap app and likely CWM Recovery as well. That said, and if so, you have some file finding and deleting to do:
You will need to delete all the files associated with CWM and the Atrix 2 Bootstrap (if ever installed) via Root Explorer or ADB:
Removing Atrix 2 Bootstrap:
Delete file /system/bin/logwrapper
Delete file /system/bin/hijack
Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
Delete directory /preinstall/recovery (Note: This directory might not exist)
Since you also installed the recovery on boot you need to restore the following:
Removing Bootstrap Recovery on Boot:
Delete file /system/bin/mot_boot_mode
Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
Thanks jboxer
Sent from my rooted Mayan Calendar

Quick question before doing all that again.
Since I did the RSD flash, shouldn't it have made it stock and not require those steps?
Sent from my MB865 using xda app-developers app

Milenko2121 said:
Quick question before doing all that again.
Since I did the RSD flash, shouldn't it have made it stock and not require those steps?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
has anyone solved this because if you flashed back to stock then i agree with you, you shouldnt need to delete these files

blackiceboi said:
has anyone solved this because if you flashed back to stock then i agree with you, you shouldnt need to delete these files
Click to expand...
Click to collapse
No, it doesn't work that way. Post number 8 details how to solve this issue. Simply flashing back to stock doesn't remove the files, and therefore they must be removed manually.
Brought to you by Carl's Jr.

Apex said:
While I'd like to tell you that you searching on Google was the right approach, you have come up short because these things have been addressed countless times here on xda. So, anyone else reading this, please include "xda" in your Google searches. That will point you back here, whereas otherwise searching xda FROM xda yields less than satisfactory results at times.
You were on 2.3.6 and wanted to update to ICS, but you had the Atrix 2 Bootstrap app and likely CWM Recovery as well. That said, and if so, you have some file finding and deleting to do:
You will need to delete all the files associated with CWM and the Atrix 2 Bootstrap (if ever installed) via Root Explorer or ADB:
Removing Atrix 2 Bootstrap:
Delete file /system/bin/logwrapper
Delete file /system/bin/hijack
Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
Delete directory /preinstall/recovery (Note: This directory might not exist)
Since you also installed the recovery on boot you need to restore the following:
Removing Bootstrap Recovery on Boot:
Delete file /system/bin/mot_boot_mode
Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
Thanks jboxer
Sent from my rooted Mayan Calendar
Click to expand...
Click to collapse
Does this work? I have the same problem..

jackdowsan said:
Does this work? I have the same problem..
Click to expand...
Click to collapse
Are you still on 2.3.6?
"Laughter is the best medicine, except for treating diarrhea."

Apex said:
Are you still on 2.3.6?
"Laughter is the best medicine, except for treating diarrhea."
Click to expand...
Click to collapse
Lol.. Great sig..
jackdowsan said:
Does this work? I have the same problem..
Click to expand...
Click to collapse
Apex's question.. Plus, do you have the hijack and .bin files? Are you rooted?
Sent from my MB865 using xda app-developers app

Apex said:
Are you still on 2.3.6?
"Laughter is the best medicine, except for treating diarrhea."
Click to expand...
Click to collapse
Hey bro you still visit these forums?Haven't seen you in here like forever.How've you been?
Sent from my MB865 using xda premium

Yea, I was on 2.3.6 and had /system/bin/logwrapper.bin but no hijack file or any other files you mentioned..
alteredlikeness said:
Lol.. Great sig..
Apex's question.. Plus, do you have the hijack and .bin files? Are you rooted?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
yea, I was rooted, that was needed to change those bin files..after that, I fxz back to 2.3.6 stock again and hopefully this time the update will work ...
UPDATE: Again the same error
updating STE BP ..
assert failed :motorola.steflash("/tmp/steflash")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Should I have an unlocked boot-loader or something?

deveshmanish said:
Hey bro you still visit these forums?Haven't seen you in here like forever.How've you been?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'm doing well, thanks! Long time, so see is right! PM me when you get a chance.
jackdowsan said:
Yea, I was on 2.3.6 and had /system/bin/logwrapper.bin but no hijack file or any other files you mentioned..
yea, I was rooted, that was needed to change those bin files..after that, I fxz back to 2.3.6 stock again and hopefully this time the update will work ...
UPDATE: Again the same error
updating STE BP ..
assert failed :motorola.steflash("/tmp/steflash")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Should I have an unlocked boot-loader or something?
Click to expand...
Click to collapse
The bootloader is locked up tighter than a 16th Century King's daughter's chastity belt, so don't worry about that being an issue. Are you using Root Explorer to delete and rename the appropriate files? Also, you say you've already tried to use the above steps, then used the FXZ back to stock 2.3.6 and you still can't get the Moto Server update, correct?
"Laughter is the best medicine, except for treating diarrhea."

Apex said:
I'm doing well, thanks! Long time, so see is right! PM me when you get a chance.
The bootloader is locked up tighter than a 16th Century King's daughter's chastity belt, so don't worry about that being an issue. Are you using Root Explorer to delete and rename the appropriate files? Also, you say you've already tried to use the above steps, then used the FXZ back to stock 2.3.6 and you still can't get the Moto Server update, correct?
"Laughter is the best medicine, except for treating diarrhea."
Click to expand...
Click to collapse
Yea, I used root explorer to rename and delete files..and yea, even after these and fxz back to stock 2.3.6 I still cant get the update to work. Also, weird thing is it shows no IMEI, no baseband and is always stuck in Airplane mode.

jackdowsan said:
Yea, I used root explorer to rename and delete files..and yea, even after these and fxz back to stock 2.3.6 I still cant get the update to work. Also, weird thing is it shows no IMEI, no baseband and is always stuck in Airplane mode.
Click to expand...
Click to collapse
Were you able to verify that the Atrix 2 Bootstrapper files and the Bootstrap Recovery on Boot files were in fact deleted and renamed correctly? Also, which FXZ file did you use in RSDLite?
"Laughter is the best medicine, except for treating diarrhea."

TWRP unable to flash CM10

Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app

the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.

thorrules said:
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!

tobdaryl said:
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
Click to expand...
Click to collapse
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
mike-y said:
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
Click to expand...
Click to collapse
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.

thorrules said:
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
Click to expand...
Click to collapse
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.

tobdaryl said:
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
Click to expand...
Click to collapse
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).

thorrules said:
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
Click to expand...
Click to collapse
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.

tobdaryl said:
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
Click to expand...
Click to collapse
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.

thorrules said:
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
Click to expand...
Click to collapse
OK, that is the reason I mentioned 4.2 and multi-user.
Good Luck!