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.
Related
[Completely Recoded!]
[Is made to only work for evo, will not run on any other phone]
Hello I'm here to present my Format all utility.
I know there is already one out but i just got bored and decided to whip one up.
Big Thanks to Calkulin
Wipes all the listed file systems Three different times to insure a full wipe.
Wipes the fallowing:
System
Data
Dalvik
Cache
Boot
Battery Stats
All Temp files
Flash .zip in recovery before flashing a rom, Enjoy!
I'll give this a try soon. Thanks!
Sent from my PC36100 using XDA Premium App
Cool gonna test it out now
Sent from my PC36100 using Tapatalk
Same as all other format all .zips
Thanks guys, tell me your results!
Will this work with the newest cwm and amon?
Tapa tapa tapa
mlin said:
Will this work with the newest cwm and amon?
Tapa tapa tapa
Click to expand...
Click to collapse
Yes it will, I just tested to make sure.
I guess i can use this one as well w the other two
This i like cause it wipes dalvik.. nice nice.
Thanx op!
Sent from my PC36100 using Tapatalk
I don't think this differs at all from Calkulin's format all posted many moons ago.
tzbigworm said:
I don't think this differs at all from Calkulin's format all posted many moons ago.
Click to expand...
Click to collapse
calk's doesn't wipe dalvik
gotshores said:
calk's doesn't wipe dalvik
Click to expand...
Click to collapse
exactly, i think mine is the only one that does
The other difference is this one wipes 3x - saves some time and wear on the evo hw buttons.
I like you work - this is nicer than caulk's if only because it has more messages. Would you mind making one to clear temp files which can be used before upgrading a rom or installing a kernel.
gotshores said:
calk's doesn't wipe dalvik
Click to expand...
Click to collapse
Nor does it work with the newest CWM
mlin said:
Nor does it work with the newest CWM
Click to expand...
Click to collapse
+1 I hate that about Cal's. No need to sweat that now. Thanks.
Sent from my PC36100 using XDA Premium App
I'll most def give it a shot before flashing a new rom.
Ok. This script isn't doing what you're selling bud.
1. It formats the cache, data, boot, and system once.
2. You delete_recursive on the dalvik cache. For some people, like myself, the dalvik cache is in /cache. Not /data.
3. You're using half Edify and half Amend scripting. Your show_progress is the wrong syntax for Edify. So is the rest of your format/delete commands.
4. You have so many spelling mistakes that it looks like a 10 year old whipped this up.
You asked for feedback, here it is. I could write up a better wipe and you've actually motivated me to do it.
Edit: Attached is a quick Format & Wipe that I made. It's an update-script but it's 100% Edify. Someone who's willing try this and let me know if it works. <--- Read below.
Edit 2: I had to modify the script a little bit due to syntax errors, renamed it to updater-script and added an update-binary. I used it before flashing my latest update to my rom and it worked perfect.
and this seems a lot like
http://infectedrom.com/showthread.php/238-Vr_superwipe
I just typed the one I made up. I have no idea what anyone else's format all scripts do. I just know mine isn't going to do it 3 damn times. It deletes /boot, /cache(includes dalvik-cache since that's /cache/dalvik-cache), /data(includes dalvik-cache since that's /data/dalvik-cache), & /system. It then formats boot, cache, data, & system.
That's all. Should work perfect.
DrRyder said:
Ok. This script isn't doing what you're selling bud.
Edit: Attached is a quick Format & Wipe that I made. It's an update-script but it's 100% Edify. Someone who's willing try this and let me know if it works.
Click to expand...
Click to collapse
I fixed it now,tested and it ran perfect with my evo
I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Managed to compile it, finally, check posts below.
Sources: https://github.com/Siarc/a9
Shark- said:
I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Sources: https://github.com/Siarc/a9
Click to expand...
Click to collapse
Dude, the only help i could give is test the ROM , let me know when you want it and i will be more than happy to help :fingers-crossed:
I've spent a lot of time, and it's simply not worth it, cannot even manage to get it to compile in the right directory. I can't believe there are so many people who have the knowledge but not one single reply.
CM7!
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I will test it bro..
thnks for compiling.
Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "
vijetaverma said:
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "
Click to expand...
Click to collapse
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Great work Friend's
Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
Bro please reply fast cant Waite now.I also want to install cm7
Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
just woke up..
I m adding that line.. will Post result in a while
---------- Post added at 10:28 AM ---------- Previous post was at 10:00 AM ----------
Still not able to install..
Error
"
same as previous one..
(status 7)
Installation aborted
"
Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app
Shark- said:
Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
all same as before..nothing changed..
Can you post the complete log
Sent from my A9 using xda app-developers app
There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app
SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app
No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app
Well thanks for the encouragement
Sent from my A9 using xda app-developers app
mahfoozceecy said:
There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
mahfoozceecy said:
No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
Well thanks for the encouragement
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
So guys is anyone working on CM7 for A9 ?
MiUi Rom released..
http://forum.xda-developers.com/showthread.php?p=41289727
Hi Guys,
I have a Samsung Tab 2 GT-P5113, rooted, and love it. I had to install drives and use Odin to get this ROM installed but it worked and it worked really well. Um, this is the one I used:
http://www.androidauthority.com/galaxy-tab-2-10-1-root-clockworkmod-recovery-cwm-95536/
It is great, I love it, but it is not Jellybean. I have 4.0.4. Now I have ClockworkMod, love it, it really works well. So I downloaded the Milestone zip from here:
http://forum.xda-developers.com/showthread.php?t=1892046
I got the gapps to go with it, and used CWM to install it. CWM works really well, I rebooted to the CWM boot screen and chose the zip file, wiped all caches, and I did pick the make a backup first option and performed the install. The device booted to the little green guy and all the text details appeared. Wiping cache, etc., but when the zip installed, it failed with a Status 7 error, failed to mount /system/ errors such as fonts, device or resource busy, /system/app/ApplicationProvider.apk "Read only file system".
I saved the report log, it is very informative down at the end, last paragraph gives all the juicy details. I should publish this log if I want real help. Let me do it now. Yeah, here ya go:
http://home.comcast.net/~theohmster/text/cwm_fail.txt
Oh, I can attach it! The original CWM recovery.log is attached as a txt file. Duh! :silly:
Look at the last page of the attached log. I understand Linux so I actually know what all these errors mean. Read only files means that the installer does not have root permission. Resource busy means an open file. Can't find /sd-ext in /etc/fstab, now that is a good one, there is no fstab in the /etc/ directory, not even on the phone. But why they are occurring is out of my grasp as I am not a ROM developer and android OS is not Linux, exactly. ...ugh!
Why? I mean, I do not know what to do about this. I tried this several times, first time was a total failure, the MD5 was off by a mile, downloaded it again, got a good copy, could view in Winzip, MD5 matched, but this failure. I did this several times, thank God I had chose the backup first option in CWM and was able to restore the system in short order. The entire process took about ½ hour or less. Am I doing this wrong? I tried to understand cmenard's instructions and I don't quite understand what he is saying to do. The instructions are simple. Here is the URL to the download and instruction page:
http://forum.xda-developers.com/showthread.php?t=1892046
But, it fails by my method, what do these instructions mean in plain English? Flash Rom, what do you mean "flash the Rom"? I got two zip files, gapps and milestone. What is this "Rom" to flash? Wipe I can do in CWM. Flash the zip. You mean install with CWM? Wipe the cache. Again? How? Run CWM again?
Flash Rom in CWM or TWRP
Wipe data/factory reset if you are coming from another ROM
Flash the zip
Wipe cache/dalvik cache
Then flash GApps.
Reboot
So like what am I doing wrong? I really want this Jellybean, especially for my Razr Maxx, but if it will not work on the tablet, I will not mess with my rooted 4.0.4 Razr where I really want JB. The phone was pretty fast 6 months ago, but it seems that all these updates and apps have slowed the thing to a crawl. I use Micro CPU Monitor and love it, two single pixel wide green lines at top screen, one for each core. They are often both pinned all the time so the phone is slow. Use it on the tablet too, same issue but nowhere near as bad on the tablet as it is on the phone. Like who wants to wait 60 seconds every time you touch the screen to make a call or use the maps? Jellybean is said to make things a LOT smoother and really grease the wheels to make ICS really slick and that would help, yes?
I showed the log to a developer on droidxforums, he is really good and made the CD iso files that boot the PC to Linux and rooted the phone. But he really was not sure of the issue and does not have this device.
Somebody help me please. I really want to fix this and am really bummed. Thanks. Happy New Year. :crying:
Okay folks, don't break a leg or anything in your mad dash to render assistance here. It is not worth it, take your time...
OK let me start up my computer and I'm gonna take a look...
Ok...
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Click to expand...
Click to collapse
AFAIK these are fine.
EDIT: The datadata one is questionable though.. that might be a typo somewhere (maybe... not totally sure. I know there's a /data/data directory, maybe a missing slash? Just thinking out loud here. Whatever it is, I doubt that this is your real problem. That would be the inability to mount /system
Couple questions/things to try.
Firstly, can you remount /system as RW in terminal emulator?
Second, can you install any custom ROMs other than CM10? Try any really, just want to see if the problem is CM10 or your device/CWM setup (Let's hope not the second one)
You do seem to be doing the CM10 install correctly from what I can see.
Oh, and thank you for having the sense to make a backup. Too many people don't and complain about bricking their device and having to ODIN to stock.
Sent from my GT-P3110 using Tapatalk HD
FYI, datadata is a partition symlinked to /data/data, it is only present on some devices like my Fascinate where /data/data is stored on a different memory chip.
Posted from my Fascinate using XDA Premium
So, I do have the newest TWRP installed, but I get a "Status 7" error message anytime I want to flash a new Jelly Bean rom. I'm on AOKP 4.2.1 right now. Can anyone help me?
Here is the error message:
Code:
--Installing: /sdcard/aokp_tf300t)_unofficial_20120625_2002_build-40.zip
Finding Update package...
Opening Update package...
Installing update...
assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf30
0t"
E:Error in /sdcard/aokp_tf300t_unnoficial_20120625_2002_build-40.zip
(Status 7)
Installation aborted.
Frank11 said:
So, I do have the newest TWRP installed, but I get a "Status 7" error message anytime I want to flash a new Jelly Bean rom. I'm on AOKP 4.2.1 right now. Can anyone help me?
Here is the error message:
Code:
--Installing: /sdcard/aokp_tf300t)_unofficial_20120625_2002_build-40.zip
Finding Update package...
Opening Update package...
Installing update...
[B][COLOR=Red]assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf30
0t"[/COLOR][/B]
E:Error in /sdcard/aokp_tf300t_unnoficial_20120625_2002_build-40.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Your problem shown in red. updater-script tested your build.prop for tf300t and did not find that. If your unit is tf300t then edit updater-script and remove the assert lines.
Inside the zip you will find /META-INF/com/google/android/updater-script. Edit with notepad or notepad++; not word, wordpad, or other. Save rezip and flash.
tobdaryl said:
Your problem shown in red. updater-script tested your build.prop for tf300t and did not find that. If your unit is tf300t then edit updater-script and remove the assert lines.
Inside the zip you will find /META-INF/com/google/android/updater-script. Edit with notepad or notepad++; not word, wordpad, or other. Save rezip and flash.
Click to expand...
Click to collapse
Okay, thanks, so I deleted that first line...But the update still failes, yet a I don't get an Error Code anymore.
Frank11 said:
Okay, thanks, so I deleted that first line...But the update still failes, yet a I don't get an Error Code anymore.
Click to expand...
Click to collapse
Sorry for the long delay! Search is still down here on XDA.
I'll have to ask questions I would have searched for.
The rom you are trying to flash is 20120625. That is very old and I can't remember any JB aokp roms on XDA during that time. I didn't catch the date earlier because the assert error was staring at me.
Is this from XDA? Give me some info about the rom or better yet a link. I feel that is an ICS rom with a date that old. Maybe that is not actually a date but appears so. With a link to the rom I might be able to find your current issue.
Note: your recovery you are flashing with should be twrp 2.4.1.0 JB.
XDA search is alive again.
This is an ICS rom. Choose a JB rom and try again I think you will have success.
Good Luck!
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
mikep2323 said:
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
Click to expand...
Click to collapse
Did you do your editing with notepad or notepad ++?
Error 6 is usually files that were edited with wordpad or word. It can also be an editing error such as not completely removing the line or partially deleting or editing a line that is still included.
Note: Wasn't blsckbean 6 ICS?
mikep2323 said:
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
Click to expand...
Click to collapse
Not sure but was blackbean 6 an ics rom? I've not looked to see for myself but I have ran 7 and it's great!
Sent from my SAMSUNG-SGH-I747 using xda premium
I unziped it on tablet and edited it with a text editor from tablet then reziped it.If it was a ics one that would make sense but on goo site it says blackbean 6 jbl so I assumed that the jbl meant jellybean boot loader.I also opened the bb7 zip and in that script updater it doesnt have the few lines with the build prop stuff,so after I deleted the first few lines in the bb6 zip it looked exactly like bb7 script updater.I don't think I left any of the lines there.After I edited the stuff I went down to the next line and pressed back button to move the rest of the lines up.If the jbl doesn't mean jellybean loader and it was for icecream sandwhich then I would assume that's why it isn't working.Thanks for writing back.Ive tried almost all the roms for tf300t and like that one the most but without ability to move my game data to microsd card I can't use it.I guess ill have to wait till they can figure out how to make directory bind workwork with jb 4.2.
I also just looked it up and bb6 is for jb bootloader.
mikep2323 said:
I unziped it on tablet and edited it with a text editor from tablet then reziped it.If it was a ics one that would make sense but on goo site it says blackbean 6 jbl so I assumed that the jbl meant jellybean boot loader.I also opened the bb7 zip and in that script updater it doesnt have the few lines with the build prop stuff,so after I deleted the first few lines in the bb6 zip it looked exactly like bb7 script updater.I don't think I left any of the lines there.After I edited the stuff I went down to the next line and pressed back button to move the rest of the lines up.If the jbl doesn't mean jellybean loader and it was for icecream sandwhich then I would assume that's why it isn't working.Thanks for writing back.Ive tried almost all the roms for tf300t and like that one the most but without ability to move my game data to microsd card I can't use it.I guess ill have to wait till they can figure out how to make directory bind workwork with jb 4.2.
I also just looked it up and bb6 is for jb bootloader.
Click to expand...
Click to collapse
I'm downloading it now, when finished I'll see what I can do and give you an update.
tobdaryl said:
I'm downloading it now, when finished I'll see what I can do and give you an update.
Click to expand...
Click to collapse
Thanks I would appreciate the help,I've searched for endless hours and everything always points back to editing those lines..If you need anymore info let me know.I've also tried to download diffrent times.Bb7 flashes fine and hydro and clean rom and blue rom but bb6 wont.I even flashed bb7 then tried to flash bb6,same error as frank got.I also made sure my build prop said tf300t for the errors.I've tried many combonations and wipes.I'm on blue rom now if that matter
mikep2323 said:
Thanks I would appreciate the help,I've searched for endless hours and everything always points back to editing those lines..If you need anymore info let me know.I've also tried to download diffrent times.Bb7 flashes fine and hydro and clean rom and blue rom but bb6 wont.I even flashed bb7 then tried to flash bb6,same error as frank got.I also made sure my build prop said tf300t for the errors.I've tried many combonations and wipes.I'm on blue rom now if that matter
Click to expand...
Click to collapse
OK. Sorry for the delay, I've been recovering my tablet. I edited the updater-script, flashed BB6. Stuck on bootanimation, flashed again, stuck on bootanimation, restored my previous backup, stuck on bootanimation. Flashed stock rom back to a working tablet.
I can't suggest you install the rom but I have uploaded updater-script.
For the future I also edit on the tablet. I suggest jota free on the playstore, it does not add extra characters that cause errors. Example most editors end a line with both linefeed and carriage return which will not work for these files.
Good Luck!
Thanks for getting back to me,I will probably try this at some point,if it didn't work on your tablet then maybe it wont work on mine as well.I do have a few backups and all my apps on titanium back up so maybe ill give it a try.Maybe I just might have to wait till they make directory bind work with jb 4.2 to flash Bb7.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
mikep2323 said:
Thanks for getting back to me,I will probably try this at some point,if it didn't work on your tablet then maybe it wont work on mine as well.I do have a few backups and all my apps on titanium back up so maybe ill give it a try.Maybe I just might have to wait till they make directory bind work with jb 4.2 to flash Bb7.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You're welcome. Sorry my results weren't better.
tobdaryl said:
OK. Sorry for the delay, I've been recovering my tablet. I edited the updater-script, flashed BB6. Stuck on bootanimation, flashed again, stuck on bootanimation, restored my previous backup, stuck on bootanimation. Flashed stock rom back to a working tablet.
I can't suggest you install the rom but I have uploaded updater-script.
For the future I also edit on the tablet. I suggest jota free on the playstore, it does not add extra characters that cause errors. Example most editors end a line with both linefeed and carriage return which will not work for these files.
Good Luck!
Click to expand...
Click to collapse
Can you upload an updater-script for Gingerbread MT6575 models ? Also the link is not working.
Ive already flashed my phone acouple of times over the past couple years. But I tried downloading GloriousOverDose V5. At my current location the internet connection is horribly slow.
I have red voodoo so I know its not a mounting issue
Wipe Data
Wipe Cache
Install zip from SD, selecting file
starting unpacking
Installation Aborted: Bad
Im guessing the Download got messed up because of connection speed? Or am I just missing something here?
Thanks
there are issues with it but it shouldnt abort installation out right, i would assume a bad download and would check the md5sum
If you need im sure i or another can post a mirror, i like dev-host for the only limitation is speed but they never take down link and well theyre free!
but yeah GOV5 is a work in progress right now and you may need to flash ROM, then flash the package again, this time skipping ROM and doing the rest... not fun and it does appear to be a mount issue but im in the middle of too many projjects right now to finish fixing it... maybe the weekend...
no worries
No Worries Mate, Aint in no rush. Having some phone issues so i thought I would swap to something more updated. I'll just try something else for a couple days then come back and try again.
Thanks again
Found the Fault
i tried a new download and tada, didnt notice before but the download never "finished" the zip was still spereated into a zip.part file and never combined... *sigh* second download was a success, installed with no issues... But with the aroma installer i find myself wiping it every 10 minutes to look at all the options lol.
Is aroma only available on a fresh boot? or is there a backdoor to add/delete without reflashing the rom?
work in progress
Love the concept of this. Cant wait to see when up and running perfectly. Is there issues with aroma installer? I select the programs i want but none seem to make them to the phone? lol or is it me again?
Don't use the download from first post, use the one on the second or so page I posted.
There is an issue right now, first flash ROM and nothing else, then exit aroma but no need to reboot. After this choose flash zip again, say no to flashing ROM and here choose what you want to install. There is an issue with the mounts that is connected partly to how aroma works and partly to how the recovery for this phone works,
I'm working on this and may in the end have to build a whole new recovery.
Sent from my Nexus 7 using xda premium