Develop Bugs

[Update] Pre-rooted stock 6.2.1 update (secure and unsecure boot images)

I've put together a rooted version of the stock 6.2.1 update if anyone wants to have at it. I flashed this on my own Fire with TWRP and it boots and runs fine, but I haven't done any other testing. Shouldn't need to wipe /data if you're coming from a 6.2 system, not sure about other ROMs like CM. Of course, I highly recommend you make a backup before flashing (good habit, and all that). To install just put it onto your Fire's /sdcard partition, boot into TWRP and install the zip. Note that TWRP will complain that it can't find the /misc or /sd-ext partitions. This is normal, those partitions don't exist on the Fire, but it won't affect the installation.
I downloaded the stock zip from the link in this post: http://forum.xda-developers.com/showpost.php?p=20509203&postcount=91 and then I changed the following from the stock zip file:
Removed the bootloader and recovery.img updates
Removed the backup_data.zip because it doesn't make sense, really (it looks like it just extracts to /backup/, but if you flash it it will wipe your /data partition?)
Added busybox, Superuser and the su binary. Should be properly symlinked and permissions set correctly.
Modified the updater-script for the above things.
Additionally, if you have the Market installed you may need to re-install it after updating since Amazon didn't do this as a patch - it just formats /system and replaces it. If you updated the Market manually then the newer version should survive in /data/app. Also, if you installed any custom frameworks or libraries (e.g. the maps framework to use Google Currents and whatnot) then you'll need to reinstall those. Basically, anything you added or modified on /system will be gone.
Edit: Thanks sadlius for pointing me to dsixda's kitchen! I've added a version with an unsecure boot image (so you get root by default on a shell). I'll leave the old one in case anyone would prefer the secure boot image. I've also uploaded the boot image itself for anyone who might have already flashed the secure 6.2.1 zip. I tried it with fastboot and it booted up fine, so you can test it first with:
Code:
fastboot boot 6_2_1rootboot.img
If it works, you can flash it (permanently overwrites your current boot partition) with:
Code:
fastboot flash boot 6_2_1rootboot.img
Downloads
MOD EDIT: Links no longer valid so removed.
Multiupload, courtesy sadlius:
update-6.2.1-rooted-secureboot.zip
Stock rooted update 6.2.1, secure boot image
update-6.2.1-rooted-unsecureboot.zip
Stock rooted update 6.2.1, unsecure boot image
Multiupload, courtesy intel352 (md5's should be the same):
update-6.2.1-rooted-secureboot.zip
Multiupload:
6_2_1rootboot.img Unsecure 6.2.1 boot image
Original Downloads:
Removed these so Dropbox won't yell at me anymore ​

First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.

You sir are a good Man....

sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.
Click to expand...
Click to collapse
I got the "Cannot load volume /misc!" error, too, but it seems to be okay anyway. The KF simply doesn't have a /misc partition.
Curious that it can't open the zip, though, but I'll wait until after your second attempt to try troubleshooting.

sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
Click to expand...
Click to collapse
I have seen the same errors when I installed TWRP. It didn't seem to make a difference to it loading.
All but the last line.
E:Unable to open zip file.
Click to expand...
Click to collapse
I think that is the real error.

I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?

isn't 6.2 is latest ? where did 6.2.1 came from?

HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!

sadalius said:
I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?
Click to expand...
Click to collapse
I do it manually. The update had a .bin extension but it was really a .zip, so I renamed it, extracted it, and made the modifications I wanted (like adding su/Superuser). Then I just re-zipped it.
Don't know if it's the most "efficient" way to do it, but it's straightforward enough and it's how I've always done it...

Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.

tes5884 said:
HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!
Click to expand...
Click to collapse
Edit: Pointed out in another post - the system image might be too big to flash via fastboot (like I said, I've never actually tried to use these). If you can get into fastboot you can try flashing a recovery, though, and then use that to try dd'ing the system image over or something.
Edit 2: Took down links since I exceeded my Dropbox bandwidth.

Can anyone verify this works? I mean the 6.2.1 pre rooted update zip
Sent from my Triumph using XDA App

dueltothedeath said:
Can anyone verify this works?
Sent from my Triumph using XDA App
Click to expand...
Click to collapse
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.

sadalius said:
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.
Click to expand...
Click to collapse
Anychance you could explain them to me? Working for me as well just curious what they mean.

sadalius said:
Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.
Click to expand...
Click to collapse
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!

fbm111 said:
Anychance you could explain them to me? Working for me as well just curious what they mean.
Click to expand...
Click to collapse
When I first tried to install I got these error messages:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
since the kindle fire does not have a /misc volume or /sd-ext/ partition, it would give those errors. Those are nothing to worry about. The last error, Unable to open zip file was a real error, but it was cause when I transferred the file to flash to the KF, it got corrupted somehow. I just deleted it from the kindle using file expert and re-transferred it then tried flashing again. All was well at that point. I still got the cannot load volume /misc! and unable to stat '/sd-ext' but like I said, those do not exist on the kindle, thus the messages. But it still installs correctly.
---------- Post added at 05:05 PM ---------- Previous post was at 04:49 PM ----------
eldarerathis said:
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!
Click to expand...
Click to collapse
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.

I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.

sadalius said:
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.
Click to expand...
Click to collapse
I just tried using dsixda's kitchen to modify the boot image and it looks like it worked. I can boot it in fastboot at least! I'm going to package it up and try flashing it for some testing. Thanks a lot!
neilrl79 said:
I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.
Click to expand...
Click to collapse
It seems like a lot of little changes, so far. You can remove things from your carousel by long pressing them, and you can restrict certain access to your one-click and stuff. It also looks like the "Device" menu in settings got a little facelift because it lists "Application Storage" and "Internal Storage" separately (which I don't think it did before).

I flashed 6.2.1 unsecured .zip via twrp and received two E:Cannot load volume /misc! errors. I then wiped cache and dalvik, and booted up. Everything including Voodoo OTA root works fine. As you said though, google market was obliterated. I am about to put it back.
Edit: after sticking vending.apk back in /system/app and fixing permissions it appears everything is 100% back to order including market and running 6.2.1. I can't thank you enough. 6.2.1 feels much snappier, although it might be a placebo effect.

does this work if i am already on 6.2.1?

[Q] After an hard reset, my GPad V500 is recognized in 4.4.2 ??

Hi, I'm new here and I wanted to ask a question about my problem.
Yesterday, I wanted to change my CM11 into an Malladus 1.2.5 (was rooted), but it went wrong with an bootloop..
This morning after fully charged my GPad, I've succed to do an hard reset.
I was happy (finally) to do this before failing in re-rooting my GPad
I used the root.bat named "Easy root for LG G Pad 8.3, Modified By Dalingrin, Originally by IOMonster (thecubed on XDA)" at the beggining of the program.
I already used it before for root my GPad, it worked fine but now not.
It says
Code:
Mouting system RW and pushing SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only fil system
Unabled to open /system/xbin/su: No such file or directory
Unabled to open /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superuser
5177Kb/s (2025538 bytes in 0.382s)
pkg: /data/local/tmp/superuser.apk
Sucess
Well, I've trying 5 times to root with this and once with OneClickRoot and nothing.
But I've seen something really weird in the properties of the tablet.
Like I said, I've done an hard reset, then I'm in 4.2.2, but in the properties of my tablet it says it's in 4.4.2.
I don't have a LPE GPad but a GPad v500
Additionnal informations, my version build is "KOT49I.V50020a" and the software version is "V50020a"
Maybe that's why it won't root my tablet ? Why it says I'm in 4.4.2 ? Maybe because there was changes in the build.prop with CM11
I've searched everywhere, on XDA, french forums (because I'm French x) ), and I got nothing useful..
Please help me, I'm stucked and I don't know what I can do for this problem

Shoko84 said:
Hi, I'm new here and I wanted to ask a question about my problem.
Yesterday, I wanted to change my CM11 into an Malladus 1.2.5 (was rooted), but it went wrong with an bootloop..
This morning after fully charged my GPad, I've succed to do an hard reset.
I was happy (finally) to do this before failing in re-rooting my GPad
I used the root.bat named "Easy root for LG G Pad 8.3, Modified By Dalingrin, Originally by IOMonster (thecubed on XDA)" at the beggining of the program.
I already used it before for root my GPad, it worked fine but now not.
It says
Code:
Mouting system RW and pushing SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only fil system
Unabled to open /system/xbin/su: No such file or directory
Unabled to open /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superuser
5177Kb/s (2025538 bytes in 0.382s)
pkg: /data/local/tmp/superuser.apk
Sucess
Well, I've trying 5 times to root with this and once with OneClickRoot and nothing.
But I've seen something really weird in the properties of the tablet.
Like I said, I've done an hard reset, then I'm in 4.2.2, but in the properties of my tablet it says it's in 4.4.2.
I don't have a LPE GPad but a GPad v500
Additionnal informations, my version build is "KOT49I.V50020a" and the software version is "V50020a"
Maybe that's why it won't root my tablet ? Why it says I'm in 4.4.2 ? Maybe because there was changes in the build.prop with CM11
I've searched everywhere, on XDA, french forums (because I'm French x) ), and I got nothing useful..
Please help me, I'm stucked and I don't know what I can do for this problem
Click to expand...
Click to collapse
Have you downloaded SuperSu?

First, thanks for reply
Each time I try to root by the program, it install Superuser, which tell me when I open it :
Code:
The Superuser binary (su) must be updated.
Please choose an installation method
Recovery mode installation is recommended for HTC devices.
I've the choice between "Cancel", which done nothing and "Recovery Install" which tell me "There was an error installing Superuser. Please send a log of the error to the developer."
I didn't have SuperSU before, I've installed it right now and he tell me
Code:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device.
Then, maybe I just need to update/install the SU binary ? How ? And then did I have my tablet rooted ?

It seems like my tablet is recognized like a GPE GPad when I connected it on my PC, maybe that's why the program won't root my tablet, no
There is a method to reinitialize the tablet (with the build.prop) in factory settings ?

Nobody for my problem ? I find nothing about this

[Q] Lost access to internal storage

Hello,
In the process of rooting and trying to install CWM Recovery in preparation to flash Cyanogenmod, I seem to have denied myself access to the phone's internal storage. In the "File Manager" app, I get the following screen:
Local: /storage
No files
No search results
In addition, any app that requires access to internal memory will not work, instead showing messages such as "Try again after scanning media files" or "Not enough storage". If I plug in the USB cable and set it to "Media sync (MTP)" mode, Windows Explorer will show the device but list the internal storage as having "0 bytes" and no files.
I already tried the following:
- Factory reset
- Flashing the official ROM through the Windows Enabler / UpTestEX tools
In both tries the phone was "reset", as in it returned to the initial Android welcome screen where you set up your Google account, but in each case I still didn't have access to internal storage.
This is what I have in the "About phone -> Software information" option:
Android version: 4.1.2
Baseband version: APQ8064T/MDM9x15M
Kernel version: 3.4.0
Build number: JZO54K
Software version: E98810b
The phone does not have Wi-Fi access either, which is why I was tinkering around with custom ROMs in the first place, so I won't be able to download anything to it as part of the solution.
Is there anything else I can try?

I'm guessing you used FreeGee to install CWM? Perhaps try restoring?
If that didn't work... Id move the EFS backups to my computer. I'd make a NAND backup in CWM. Then I'd get CM and gapps on a micro SD. I'd do a format of system, data, and cache. Then I'd install CM and gapps. Then I'd cross my fingers.
Sent from my LG-E980 using Tapatalk

ackliph,
Since I didn't have Wi-Fi access on the phone, and at the time I didn't know how to reverse tether it to the computer, I was looking for a procedure to install CWM Recovery that didn't involve downloading files directly within the phone (only transfering via USB). Right now I can't find the exact instructions I used, but it was similar to what is described by hkfriends in this thread: http://forum.xda-developers.com/showthread.php?t=2361941, the only difference being that the image I downloaded was not that one.
I rooted the phone with Universal Root, then followed those instructions to install CWM Recovery. It seemed to have worked, but when I rebooted... nothing happened! The phone booted normally, and if I tried entering recovery mode all I got was the stock LG recovery.
I continued looking for another way to install a custom recovery, but instead came upon instructions to flash KDZ files with UpTestEx. Since the immediate problem I was trying to solve was the lack of Wi-Fi access (and not really the custom ROM), I thought it couldn't hurt to try updating the stock ROM. The procedure did update my ROM, but I ended up in my current predicament: no access to internal storage, and still no Wi-Fi access! It even managed to unroot the phone.
So your suggestion would be to try installing CM via a microSD card. OK, I can get a microSD and try that. However, I do believe I will need root access to do anything of the sort. I tried Universal Root again, and got the following messages:
Beginning Root Process
/system/bin/sh: can't create /sdcard/G_security: Permission denied
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
1955 KB/s (1085140 bytes in 0.542s)
mount: permission denied (are you root?)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
You are now properly Rooted.
Click to expand...
Click to collapse
Evidently, that didn't work.
I guess I will need some other method of rooting it.

[Q]Looking for some guidence (zips & updater-binaries)

Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}

Dude360 said:
Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}
Click to expand...
Click to collapse
What is it you are flashing exactly? And which recovery are you using? Could be a problem with the recovery you use

I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.

Dude360 said:
I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.
Click to expand...
Click to collapse
TWRP will not work with older update-binary. Could you upload an example zip which does not flash ?

This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!

Dude360 said:
This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!
Click to expand...
Click to collapse
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.

aWFSuser said:
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
Click to expand...
Click to collapse
That error would make sense then, reverting to an older binary.
From memory, Ive used these binaries myself on:
Desire
CWM 5x, 6x
EXT4 Recovery All versions
Desire HD:
CWM 5x, 6x
EXT4 Recovery All versions
Nexus 4:
CWM 5x (I think it was)
TWRP 2.x to latest
Nexus 7:
TWRP 2.x to latest
Samsung S2
Aman Ra I think its called
Transformer 101
CWM 5x (I think)
Nook Simple Touch:
CWM 5x
OUYA:
CWM 5x
Tesco HUDL
CWM 5x
Several Cheap Chinese Tabs with CWM 5x
And as far as I know they've been used on the rest of the ROMCleaner devices as well, but have no idea about the recoveries as I was on hiatus for some of them.
Sensation
Incredible S
One X
One S
EVO 4G LTE
HTC One (m7)
HTC One (m8)
GNex
TF201
Galaxy S3
Galaxy Note II
Galaxy S4
I remember we did a LOT of testing with updater binaries to find one that was compatible with as many devices as possible but at the time none of us had access to a WFS hence why we were never able to check with them.
We we quite surprised that this one worked with everything we tested and tbh I cant even remember where it came from and Its still running on everything we throw at it!
aWFSuser said:
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.
Click to expand...
Click to collapse
I was using PA at the time, same error with CM11 though.
At the end of the day, the binary can be worked around. The romcleaner binary not working is (child status 4 error) cant!
Im beginning to think its definitely a recovery incompatibility, maybe the way it has to be compiled to run on ARM6 or maybe just particular to the WFS.
The romcleaner binary hasnt changed either and is running on the above devices as well.

[ROM][AOJ6]Moar 1.2.2[Port-Note-5][Aroma][11-21-2015]

[M]other [O]f [A]ll [R]oms ..aka.. MOAR
Take control of your phone​
Under the Hood:
v-1.2.2:
Just added stock kernel, should fix some bugs.
This build is based on the stock Sprint AOJ6 5.1.1 Lollipop build and will run on both OGD and OI6 base firmwares.
We hope you enjoy your MOAR experience. TD
All custom features are controlled through the Moar Control Center application (pictured).
Based on Lollipop AOJ6 firmware // Knox free // ItsOn free
Mod Control with a ton of different mods! //
Added Edge People
On the fly theming // Choose ANY color for a bunch of things!
Deodexed // Optimized and debloated apks & jars
Build.prop, battery, and CSC tweaks // Smooth as silk performance
Hacked Hotspot // Signature verification disabled
Modified and working Private Mode
PRL write enabled // MSL check removed
ASEC package security disabled
Device status "Official" // Syscope dependencies removed
All apps enabled for Multiwindow // All apps NATIVELY enabled!
Music Control // Customizable long press volume skip mod
Phone call and screen recording with toggles!
Tons of unlocked settings // AppOps permission manager, blocking mode, etc.
Modified default Animation Scales
High volume warning disabled
Wireless charging popup disabled
Hotspot wifi warning disabled
Application permissions added
Scrolling cache disabled
Protected features.xml from Xposed writes
Torch enabled volume buttons
Install from unknown sources enabled as default
Custom bootanimation support
Unlocked addition volume items
Max brightness for statusbar
Custom statusbar clock
3minit battery/battery bar/text battery
Custom sound levels
Call/MMS Blocking
Custom carrier texts
Toggles for statusbar icons/charging/notifications and more
Custom button mappings
Back to kill mod
Custom extended power menu
Customize end call delay
Increasing ringtone toggle
System backup/restore feature
NFC always enabled features
Camera modified for use with low battery
Custom rotation toggles
Custom statusbar backgrounds
Custom quickpanel toggle colors
Custom quickpanel view settings
Mokee Listview Animations
Custom two line dateview for pulldown
Customizable third button shortcuts for pulldown
Fontpack with over a 1000 fonts. Credits @Winb33
Custom pulldown backgrounds
Next Alarm mod for lock screen
Expanded from 2 thru 5 viewable notifications on the lockscreen
And much, much, MOAR!
Rom Installation:
Before You Start:
Backup EVERYTHING you want to save from internal and external (SD) storage.
• Copy the downloaded rom.zip file to storage.
This can be internal or external OTG storage device since the TWRP recovery provided in Stage 2 will read from OTG storage.
Stage 1:
** Skip to STAGE 2 if OEM Unlock has already been done **
Preparing the stock rom
** This is REQUIRED
• In the stock rom, turn on developer mode, enable USB debugging and OEM Unlock
• Settings>>>about device>>> scroll to bottom and tap build number 8 times
now press back button once and tap developer options...
• Toggle on both USB debugging and OEM Unlock.
Stage 2:
** Skip to STAGE 3 if already running a custom recovery / TWRP, Philz, Etc **
Install Custom Recovery with Odin
• Download Odin & custom recovery tar
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the recovery file to AP / PDA (depending on version of Odin)
• Make sure re-partition & Auto Reboot are NOT ticked
• Click the start button and let the Odin flash complete
Stage 3:
• Boot the phone into Recovery Mode
- Press and hold volume down+power to reboot and as soon as the phone screen flashes, press and hold Home+Power+Volume Up buttons
to get into recovery. The timing has to be right but I'm sure you'll get the hang of it.
• If TWRP asks, the answer is yes, swipe to allow modifications. It will only ask you this once.
• Do a FULL wipe but do not reboot yet (wipe/advanced wipe)
A full wipe includes:
Dalvik Cache
Cache
Data
System
• Flash rom and reboot.
Known Issues:
Samsung Apps Has a phones not supported error.
** Custom Lollipop ROMs may take about 20 minutes to get to the setup screen, so be patient.
Running UniKernel v9 beta 111215
Everything so far is working including:
Data
Call
Text
Mms
Download:
***DOWNLOAD LINKS REMOVED***
Credit:
tdunham for bring Moar over to the note 5.
Please give thanks to him: Click Here
Gameronone for porting and patching the boot.
​

Niceeee

infamouzwt said:
Niceeee
Click to expand...
Click to collapse
Once I get v4 of darth uploaded, i'll get this one too.
Update: Link UP

Flashing this tonight.

Kstambaugh09 said:
Flashing this tonight.
Click to expand...
Click to collapse
Flashing now

So i can root on oj6 and flash this bad boy

infamouzwt said:
So i can root on oj6 and flash this bad boy
Click to expand...
Click to collapse
Yep

So playing around with this you lose the ability to use Edge and also the samsung market it gone. When i try to open it i get a message saying phones not supported

Great ROM, thank you:beer::beer: Just need stock kernel, Play movies won't work for me otherwise

This firmware includes Russian language?:crying:

Bormotos said:
This firmware includes Russian language?:crying:
Click to expand...
Click to collapse
It might you'd have to check, I'm working on something atm.

GamerOnOne said:
It might you'd have to check, I'm working on something atm.
Click to expand...
Click to collapse
Please, add more locations, including Russian language.

this is the error log
what is the problem ?
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Mother Of All Roms
ROM Version : MOAR v1.2.1 [AOJ6]
ROM Author : <[email protected]>
Device : Galaxy Edge+
Start at : Thu Nov 19 01:05:47 2015
--------------------------------------
--------------------------------------
Mother Of All ROMs
--------------------------------------
---------------------
Setting Mounts...
mount: failed to mount /dev/block/platform/15570000.ufs/by-name/SYSTEM at /system: Device or resource busy
mount: failed to mount /dev/block/platform/15570000.ufs/by-name/USERDATA at /data: Device or resource busy
about to run program [/sbin/busybox] with 3 args
mount: can't find /sdcard in /etc/fstab
run_program: child exited with status 1
Extracting Installation Files...
Preparing Options...
Installing ROM...
Formatting System
Preparing...
Cleaning up...
Installing New Files...
Extracting System
Please Wait...
Writing Data
Creating Symlinks
failed to mkdir /system/bin/busybox: Read-only file system
symlink: failed to symlink /system/bin/busybox to /system/xbin/busybox: making parents failed
symlink: failed to symlink /system/bin/busybox to /system/xbin/busybox: No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
Installer Error (Status 7)
End at : Thu Nov 19 01:05:47 2015

parabola1971 said:
this is the error log
what is the problem ?
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Mother Of All Roms
ROM Version : MOAR v1.2.1 [AOJ6]
ROM Author : <[email protected]>
Device : Galaxy Edge+
Start at : Thu Nov 19 01:05:47 2015
--------------------------------------
--------------------------------------
Mother Of All ROMs
--------------------------------------
---------------------
Setting Mounts...
mount: failed to mount /dev/block/platform/15570000.ufs/by-name/SYSTEM at /system: Device or resource busy
mount: failed to mount /dev/block/platform/15570000.ufs/by-name/USERDATA at /data: Device or resource busy
about to run program [/sbin/busybox] with 3 args
mount: can't find /sdcard in /etc/fstab
run_program: child exited with status 1
Extracting Installation Files...
Preparing Options...
Installing ROM...
Formatting System
Preparing...
Cleaning up...
Installing New Files...
Extracting System
Please Wait...
Writing Data
Creating Symlinks
failed to mkdir /system/bin/busybox: Read-only file system
symlink: failed to symlink /system/bin/busybox to /system/xbin/busybox: making parents failed
symlink: failed to symlink /system/bin/busybox to /system/xbin/busybox: No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
Installer Error (Status 7)
End at : Thu Nov 19 01:05:47 2015
Click to expand...
Click to collapse
Try re-downloading it, I just did a fresh download and no issue here.

Kstambaugh09 said:
So playing around with this you lose the ability to use Edge and also the samsung market it gone. When i try to open it i get a message saying phones not supported
Click to expand...
Click to collapse
I added edge people in 1.2.1. As for Samsung store still needs fix. If I could find a copy of the stock kernel this may fix that issue.

Just flashed the update. On stock rom with custom kernel samsung market works. What would be diff now? I was using unikernel which is the same in this rom. If its just a port should the market just think its the note 5? Wonder if they built it where you had to have the security scripts for it to allow access.

Kstambaugh09 said:
Just flashed the update. On stock rom with custom kernel samsung market works. What would be diff now? I was using unikernel which is the same in this rom. If its just a port should the market just think its the note 5? Wonder if they built it where you had to have the security scripts for it to allow access.
Click to expand...
Click to collapse
When I get free time I'll check it out.

Ok. Ill let you know if i figure it out beforehand

Samsung apps
I'm blocked from downloading add on camera features on this rom. can't download our find anything from Samsung app store. any way to change that?

FingerBlastJ said:
I'm blocked from downloading add on camera features on this rom. can't download our find anything from Samsung app store. any way to change that?
Click to expand...
Click to collapse
Its an issue with the rom right now.