Database Users

[RECOVERY] A500 Public Recovery v0.2 based on CWM v5.5.0.4 for ICS [May 21st 2012]

[Size=+2]A500 Public Recovery v0.2 based on Koush's CWM v5.5.0.4[/Size]
Here is a new Clock Work Mod for the ICS unlocked bootloaders only.
Features:
* cleanup tab option: shortcut to try to fix forcequits after updates, return to recovery and select on the main screen (Wipes Cache, dalvik, and fixes permissions)
* Standard options to backup and restore to either the SD card or internal storage
* Mount points match those of most running roms
* adb shell works as root (with or without system mounted)
* set boot mode menu to select the boot partition (hidden on know non-multiboot bootloaders)
* setbootmode and itsmagic command line tools for advanced users
* /data/linux directory is not deleted on erase userdata, nor backed up on nandroid backup (just like /data/media) to allow a space for linux files for dual boot and chroot linux installes.
While there may not be much fantastic yet about the recovery it appears funcitonal at this point. (Features such as touch ui may appear in the future)
Why is it called Public: its public in the sense that all the scripts and code required for anyone to build it have been made avalible. (note some linux knowledge may be needed to build it yourself)
[Size=+2]Installation[/Size]
There are to main ways to install
1) using fastboot or nvflash you can install the image
A500PubRecovery_v0.2.img MD5: 0e40a494cd066b1c8e1a8d01493f1452
2) using a any exiting recovery (as long as you have one of the unlocked bootloaders) you can install with an update.zip
A500PubRecovery_v0.2_update_S.zip MD5: 349d0d6284fc6d1e071827a37a8a55e5
** (FYI the fastboot command to run on your computer is 'fastboot flash recovery A500PubRecovery_v0.2.img')
[Size=+2]Developers Additional Information:[/Size]
Build instructions (including how to fetch the source code) is here:
https://github.com/ezterry/AcerRecovery/blob/recovery_manifest/README.mkdn
(Thanks yous/Credits are also included)
Kernel:
as of version 0.2 the kernel is built from source (see above for information on fetching the build tree including the linux kernel)
the kernel in v0.1 was a patched for system r/w acer ICS Stock kernel
additional information can be seen on the commit:
https://github.com/ezterry/AcerRecovery/commit/402da6f73e752e80312318e177035ee02e4fbf89
The biggest thanks is as manythings in the Android World to Koush, and the CyanogenMod team. (They did the hard part, I've just tweaked it for the A500 configuration)
[Size=+2]Version List[/Size]
v0.2:
A500PubRecovery_v0.2.img 0e40a494cd066b1c8e1a8d01493f1452
A500PubRecovery_v0.2_update_S.zip 349d0d6284fc6d1e071827a37a8a55e5
v0.1:
A500PubRecovery_v0.1.img 4414bdbdd3aa7b7d7d1166595e6ccb2a
A500PubRecovery_v0.1_update_S.zip f45e7e3b640b42a68ec9bb08bd4b88ce
for details on the source commits used in the builds please see:
https://github.com/ezterry/AcerRecovery/blob/recovery_manifest/VERSIONS.mkdn

I will put it in the guide ,so when you flash the unlocked boot loader you can chose to install this with it , the more options for the user the better.
Thanks for the hard work.

Awesome !!! im curious to look at source so thanks for this
Sent from my SCH-R760 using XDA

btw,
The a501 is a very similar device.. is some more advanced user wishes to test things out and let me know if and changes is needed or if its good as is (fastboot boot may be useful if you wish to boot it without actually saving it to the tab)
Other Acer devices probably need slight modifications, if you help I can look into adding it to the codebase/builds..but I can only test the a500 as it's the only tab I own.
Just try to make sure you have a link to the source code of any kernel..and failing that that it Lisa stock kernel from an official OTA image.

I have a A500 with the Build.Number "1.033.00_EMEA_DE".
I have Problems to get the CWM with that Tutorial:
http://www.brutzelstube.de/2012/acer-iconia-a500-mit-android-4-0-ics-rooten/
Its all running fine but when i want to boot into the CWM it seems to work but then the Android Guy with open Stomach and the Red ExclamationPoint is showing.
I wonder if i can use this Public Recovery v0.1??
Maybe someone can help me that.

Basian Mile said:
Its all running fine but when i want to boot into the CWM it seems to work but then the Android Guy with open Stomach and the Red ExclamationPoint is showing.
Click to expand...
Click to collapse
If you are running a stock ICS rom you need to make sure you don't have the recovery patch still installed, otherwise the stock recovery will be installed on reboot if any other recovery is installed.
If you have the script and patch.. this recovery as any other custom recovery will be overwritten.
Sent from my Galaxy Nexus using Tapatalk 2

The CWM (v5 from Thor2002ro) is running now. I was using the wrong CPUID. That was my falut. But now its ok.
So i can flash this new Recovery just in this right?

If you have one of the the unlocked ics bootloader you can flash this recovery.. either directly or with the update.zip from a working custom recovery.
Sent from my Galaxy Nexus using Tapatalk 2

Great Job!
If you want to build an A510 version, just change the data partition to point to /dev/block/mmcblk0p10. Everything else stays the same. If it doesn't boot, i may need to have the A510 recovery kernel.
BTW.. the recovery kernel doesn't really need to be patched for r/w, because /system never gets mounted as readonly, so it never does a remount to r/w. I've repacked recoveries with stock ICS kernels and they work fine. == Although, it doesn't hurt to patch them. ==

Euclid's Brother said:
BTW.. the recovery kernel doesn't really need to be patched for r/w, because /system never gets mounted as readonly, so it never does a remount to r/w. I've repacked recoveries with stock ICS kernels and they work fine. == Although, it doesn't hurt to patch them. ==
Click to expand...
Click to collapse
Part of it is I intend the kernel for my own ics rom. (Safer anyway in my opinion to not find any surprises as a user but not the biggest issue)

Tested it and installed fine , it's barebones recovery but I think A lot will love it , clean and simple. I used fastboot to install it .
Thanks Ez.

BTW I'm working on the next release
1) Some minor bug fixes (partitioning sdcard and full wipe are a bit strange at present.. in most cases we don't re-partition sdcards.. and wipe if you are installing a rom after will fix its self)
2) Now that acer has released their source, I've dropped the pre-built tweaked stock kernel, and added a source build, mostly still stock but I've changed to lZMA to allow some more space for the recovery ramdisk. (also system remount is allowed by default in this kernel so no postbuild acrobatics .. ie KPatch script)
3) add setbootmode/itsmagic binaries to the system. A500 (this is in github as is the kernel so building from synced source will give you a recovery with these pre-installed)
4) hopefully add an interface to call said binaries
Also I have an A510 test version I need someone (with the tab) to try.. PM me
Edit (Feature Idea):
whould anyone be interested in recovery when wiping not only skiping /data/media (internal /sdcard) but also skiping /data/linux ?
The idea is dual boot people bootling linux could use a ramdisk to run some bindmount/piviot root hackery to make /data/linux the root directory
also anyone using chroot to run a linux distro along side android could use the /data/linux directory as the chroot jail
let me know and I'll look into making APR here support such a feature

Is it posible to add app cwm for install.zip,backup,restore since rom ?
For exemple,the same app into sgs2 with siyha kernel or another kernel ??? Big thanks
Envoyé depuis mon A500 avec Tapatalk

ezterry said:
3) add setbootmode/itsmagic binaries to the system. A500 (this is in github as is the kernel so building from synced source will give you a recovery with these pre-installed)
Click to expand...
Click to collapse
Ehm, definitely don't put itsmagic next to setbootmode, it corrupts the kernel image in AKB.
ezterry said:
Edit (Feature Idea):
whould anyone be interested in recovery when wiping not only skiping /data/media (internal /sdcard) but also skiping /data/linux ?
The idea is dual boot people bootling linux could use a ramdisk to run some bindmount/piviot root hackery to make /data/linux the root directory
also anyone using chroot to run a linux distro along side android could use the /data/linux directory as the chroot jail
let me know and I'll look into making APR here support such a feature
Click to expand...
Click to collapse
Yeah I'm actually thinking to install linux to /data/linux and chroot there, too, exactly the same way.

micky387 said:
Is it posible to add app cwm for install.zip,backup,restore since rom ?
For exemple,the same app into sgs2 with siyha kernel or another kernel ??? Big thanks
Click to expand...
Click to collapse
I'm not exactly sure what you are talking about,
If you want to use this recovery with RomManager (as an unofficial 3.x+ recovery) you may. (In rom manager select flash recovery, select a500, select that you have manually installed a CWM recovery, select 3.x) To make it "official" koush needs to update his repo.. and I'm not going to poke that until I fix some minor outstanding bugs.
Actions will by default happen on the /data/media partition (as that is usually /sdcard) and no roms are yet in the system.. but I may work on fixing that after I make the next release. Currently running a backup myself.
If you want some other app to do this.. it needs to be compatible with the clockwork mod API.
Skrilax_CZ said:
Ehm, definitely don't put itsmagic next to setbootmode, it corrupts the kernel image in AKB.
Click to expand...
Click to collapse
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.

ezterry said:
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
Very clever... i was worried myself at first when i saw you mention itsmagic... i'm so happy we have an open bootloader now with no tricks... oh, except the original hacking
Thanks so much for your work on this!

ezterry said:
I'm not exactly sure what you are talking about,
If you want to use this recovery with RomManager (as an unofficial 3.x+ recovery) you may. (In rom manager select flash recovery, select a500, select that you have manually installed a CWM recovery, select 3.x) To make it "official" koush needs to update his repo.. and I'm not going to poke that until I fix some minor outstanding bugs.
Actions will by default happen on the /data/media partition (as that is usually /sdcard) and no roms are yet in the system.. but I may work on fixing that after I make the next release. Currently running a backup myself.
If you want some other app to do this.. it needs to be compatible with the clockwork mod API.
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
OK.
I want to know if it's possible to add the same app (a part of recovery)
Thanks

ezterry said:
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
Yeah that's ok, I meant next to as in GUI, that would bring only problems.

v0.2 is out (see op)
Bugfixes:
~ wipe full data fix
~ fix on formating the external sdcard
~ cleaned up some warnings
Features:
~ added multiboot support (select boot partition)
~ added itsmagic binary (command line only)
~ switch to kernel source build rather than pre-built kernels
~ added /data/linux support (skip on wipe data, and nandroid backup)
kernel was built from:
https://github.com/ezterry/AcerTabKernel/commit/a6312764aa19ea7fe581b9931723c206a12b11ef
config file: apr_a500_defconfig
besides the configuration the kernel source is thus far unchanged from the acer a500 ICS drop
The kernel is built along with the recovery, see developer notes in OP for a link to the build instructions.

v0.2 doesn't boot for me.
Using Skrilax v6 bootloader I can't boot v0.2 while v0.1 works fine, both flashed from fastboot.
I also tried flashing v0.2 from v0.1 recovery, same results.

Pac-Rom + Pink kernel 20140319: WiFi not working: workaround

Hello,
Sorry, I have to post this workaround here because I'm new on xda and I can't post an answer on the development forums. So if someone see that, please post a link to this thread on PAC ROM or pink kernel topic
It seems there is a new file in the modules directory which is a symbolic link named wlan.ko. As an easy workaround, simply replace this file (/system/lib/modules/wlan.ko) by this one: /system/lib/modules/pronto/pronto_wlan.ko (move this file to the parent directory and rename it). Then reboot, you should have the WiFi working now
PS: I guess it's maybe better to modify the symlink or load the correct module but it's harder to write command lines with a smartphone

According to some people, this bug should be fixed now.

Doesn't work!
Sadly, doesn't work on PA/C-RoM.
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.

Mycroft-Dev said:
Sadly, doesn't work on PA/C-RoM.
Click to expand...
Click to collapse
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko

matttbe said:
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
Well, Wi-Fi still refuses to work after removing the symlink!
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Cheers, mate!

Mycroft-Dev said:
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Click to expand...
Click to collapse
No :-/
Maybe you can try to reinstall the latest nightly version of your rom (released after March 20th -- I think it's the case for C-RoM), reboot and check if the WiFi is working. If yes, don't disable it now then reinstall the latest version of Pink kernel.
But if the WiFi is still not working, it's annoying... You can reformat /system where kernel modules are installed but I think it's automatically done when installing a rom. Maybe they are not using the latest version of the kernel?

Mycroft-Dev said:
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Click to expand...
Click to collapse
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").

Clarification
matttbe said:
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Click to expand...
Click to collapse
As in, I repacked the kernel, and then flashed it.
I'll try tweaking a bit here and there, and let you know how it goes.
And yes, I flashed the latest C-RoM.

[DEV][RECOVERY] TWRP Recovery 2.7.0.0

TWRP Recovery
For Galaxy Ace
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
Me: For compiling it for Galaxy Ace.

CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.

DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!

About the current build:
STABLE

Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app

aurisltu said:
Nice job. Is it working on Cm9?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
I think, I should remind you: Recovery is independent of ROM.
It can flash everything which the new kitkat update-binary allow.
If anything fails to flash, just replace /META-INF/com/google/android/update-binary file inside that zip from cm11 or omni4.4 and it will flash.

well im using this recovery for a while and its responding better than the normal recovery , plus the other features in it , thanks for you great work
keep it up
sent from my kitkat ACE

works great, but if formatting or installing and you accidentaly bump the back button it stops what it is doing, can also corrupt the partition, installs ALL roms from cm9 through to cm11 and all scripts/mods install too,, thanks for this version,, i didnt like the other versions they were a yuck colour, i like the black and gray theme

I just had some look today on your device's development forum and found that @Mardon has already made this recovery for your device (Because, I was confused as I didn't receive a single THANK on any of my posts).
Please note that my TWRP has no relation with @Mardon's TWRP. He has used omniarmv6 sources while I've used official omni sources and the androidarmv6 sources.
I've worked hard enough and researched on everything and have made this recovery. This build is the closest one to an official build unlike little buggy build of @Mardon: Bad colors (not official colors), maybe brightness settings are missing, maybe you can't flash some zips with that recovery, etc.
And...ofcourse, you won't be able to flash stock rom using this recovery because it uses samsung's crappy rfs.

Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.

Thanks Bro for the recovery.
Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse

Bhargav97 said:
Here's something I need you guys to test:
[ROOT]TWRP Coordinator
It's a newly released app (released just before 10-15 minutes) by TeamWin.
I just need a report if everything's working as it should or not.
WARNING: Don't use the option to update TWRP because we are using an unofficial build. Other than that, everything should work but the app is still BETA...Try at your own risk.
What to do?
-Install my TWRP.
-Remember, app needs root.
-Then, start using app's features and report here if found any bugs.
Your report would be appreciated! Thanks.
Click to expand...
Click to collapse
Work fine bro.. good job.. :fingers-crossed:

Thanks for this recovery, really works great, with CM9 too!

Bhargav97 said:
DOWNLOAD:
http://www.upload.ee/files/3991497/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)

Bhargav97 said:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
Click to expand...
Click to collapse
not working ... failed with error: -1

GalaxyAce User said:
I follow the above steps, but nothing happens.I am on same recovery as before using the above steps.BTW thanks for recovery. I am currently using AOSP GingerBread 2.3.7 [COOPER] V3 by SpaceCaker (http://forum.xda-developers.com/showthread.php?t=2375459)
Click to expand...
Click to collapse
Busybox is needed for flash_image command to work. If you are using any Stock Based ROM, I doubt you have Busybox. If you can't manage to get it done this way (I don't get, why?) then you can replace recovery.img inside any recovery flashable zip file (of recovery, i.e. CWM-x.x.x.x.zip) from the one given in the link of first post. Now flash that zip file using your current recovery.
kjub6 said:
not working ... failed with error: -1
Click to expand...
Click to collapse
What I said above, also applies to you.

Thank you
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.

sdembiske said:
Installed over Mardon's latest version as I was having issues with his (failure to flash certain files etc). Will test over next while and report if I find any issues.
Thanks again.
S.
Click to expand...
Click to collapse
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM

Thank you ...
Viper The Ripper said:
it´s not compatible with android 4.4. but it´s working great with CM9/10/10.x, for kitkat roms you need the latest TWRP or CWM
Click to expand...
Click to collapse
Yes, found that out - neither this nor Mardon's TWRP version worked on Mardon''s CM11 latest. Took the recovery.image file out of CWM-6.0.5.3-cooper and flashed it using terminal command:
su
flash_image recoveryonly /sdcard/recovery.img
Worked like a charm and all's well now. Would like to know though what settings you recommend on SuperchargerV6 on Mardon's CM 11 with your patch for it installed - have not successfully managed to get it past the Samsung boot screen at 50% Supercharged the two times I have tried.
Thanks again, Steve

Link to dowload
Hi Bhargav97,
I don't found link for to dowload, it's possible that can u send me this link?
Many thaks!

testing AOSP Marshmallow 6.0 for Z2 following Ev3rtH's

I tried to make rom working modem following Ev3rtH's result "AOSP Marshmallow 6.0 for Z1 Compact"
when i test in my z2, modem works (IMEI,SIM,Data,call...)
and the working and not working are same as Ev3rtH's posting
Working and Not working :
Working:
-Boots
-Screen
-Brightness
-Orientation sensor
-Ambient light sensor
-Wifi
-Bluetooth
-IMEI shows up, still have to test with SIM
Not working:
-Camera
-NFC
-GPS (haven´t tested yet)
-Internal SD doesn´t mount right - As pointed out by tgascoigne, if you´re playing around with the mount points and Android asks you to format it, DON´T. You will wipe the boot and system partitions.
It is not official build and unstable
Is there any problem in this post, please give a comment
contributors and reference
Ev3rtH, nickholtus
Download :
dropbox:
IMGs : https://www.dropbox.com/sh/yb3l8j5gjtx0zo6/AACT8LdwfiXGKxo29VxNd5oQa?dl=0
IMGs zip : https://www.dropbox.com/sh/yb3l8j5gjtx0zo6/AACT8LdwfiXGKxo29VxNd5oQa?dl=1
flashable .zip (cannot use because of error) : https://www.dropbox.com/s/lbdm3vxiikqzp3n/aosp_d6503-ota-eng.choirakwon.zip?dl=0
Google drive:
IMGs : https://drive.google.com/folderview?id=0ByjmFQapr1xqOWY0ZmM2aHUxaU0&usp=sharing
flashable .zip (cannot use because of error) : https://drive.google.com/file/d/0ByjmFQapr1xqWk5wLVZQYkF5eDg/view?usp=sharing
Changelog :
Adding /vendor/sony/sirius/proprietary/etc/firmware/modem.bxx from 23.4.A.1.232
Modify /vendor/sony/sirius/sirius-partial.mk
Modify /vendor/sony/sirius/proprietary/Android.mk
Modify /vendor/qcom/prebuilt/proprietary/common/vendor/lib/libaudcal.so
It is almost same as https://github.com/tg-togari-marshmallow in http://forum.xda-developers.com/xpe...marshmallow-6-0-z-ultra-t3224321/post63278643

That's only a preview version, or a Concept version? all the Marshmallow features are working?

stayawake said:
That's only a preview version, or a Concept version? all the Marshmallow features are working?
Click to expand...
Click to collapse
It is same build as sony developer world's AOSP build instruction Android6.0.0_r1 except modem fix
I have not tried all the features, after trying i'll comment about that

nakwonelec said:
It is same build as sony developer world's AOSP build instruction Android6.0.0_r1 except modem fix
I have not tried all the features, after trying i'll comment about that
Click to expand...
Click to collapse
I was thinking it was the same build from this topic
http://forum.xda-developers.com/z3/general/sonys-android-concept-marshmallow-t3229030

i think that is not, Sony's Android™ Concept is official test build but this is unofficial build
and there is no Concept build for Z2 as i know

Is there a way to flash imgs with multiROM? I mean install the ROM on the internal storage without screwing up my other two installations.

Well, I tried this build, but gapps doesn't work... btw root is working (Booted a custom kernel with TWRP, install SuperSU 2.52, then back to original Kernel)...
Can't test permissions per app
System UI Tuner is working.
another new function, when you login with your google account (at least this was possible with gapps), a new menu appear on your settings, called "Google" or something like that, it shows and let you configure in a simple way lots of settings from your google acccount, like, youtube historic, location, voice commands, etc

Could someone please mirror the download... the links are not working for me

paxy97 said:
Is there a way to flash imgs with multiROM? I mean install the ROM on the internal storage without screwing up my other two installations.
Click to expand...
Click to collapse
i'm sorry for late, i make flashable zip also (using 'make otapakage' instead of just 'make')
https://www.dropbox.com/s/lbdm3vxiikqzp3n/aosp_d6503-ota-eng.choirakwon.zip?dl=0
maybe .zip version, it can be used in MultiRom.
after flashing 23.4.0.A.232 and AndroPlus ROM and testing this flashable .zip, i comfirm about that

nicholasknicks said:
Could someone please mirror the download... the links are not working for me
Click to expand...
Click to collapse
IMGs :
https://drive.google.com/folderview?id=0ByjmFQapr1xqOWY0ZmM2aHUxaU0&usp=sharing
flashable .zip :
https://drive.google.com/file/d/0ByjmFQapr1xqWk5wLVZQYkF5eDg/view?usp=sharing

nakwonelec said:
IMGs :
https://drive.google.com/folderview?id=0ByjmFQapr1xqOWY0ZmM2aHUxaU0&usp=sharing
flashable .zip :
https://drive.google.com/file/d/0ByjmFQapr1xqWk5wLVZQYkF5eDg/view?usp=sharing
Click to expand...
Click to collapse
Flashable zip not working
"Error executing updater binary in zip"

nicholasknicks said:
Flashable zip not working
"Error executing updater binary in zip"
Click to expand...
Click to collapse
Yes, i confirmed. When I tested in my phone. It make same result.
It maybe related with sdcard problem. So i will find solution. Thanks

nakwonelec said:
Yes, i confirmed. When I tested in my phone. It make same result.
It maybe related with sdcard problem. So i will find solution. Thanks
Click to expand...
Click to collapse
nicholasknicks said:
Flashable zip not working
"Error executing updater binary in zip"
Click to expand...
Click to collapse
But is not a flashable zip, Its just compacted to be easier to download

stayawake said:
But is not a flashable zip, Its just compacted to be easier to download
Click to expand...
Click to collapse
There are both just compacted zip and flashable zip also
"Error executing updater binary in zip" in this case, using just compacted zip
And when i test flashable zip, it make md5 error

nakwonelec said:
There are both just compacted zip and flashable zip also
"Error executing updater binary in zip" in this case, using just compacted zip
And when i test flashable zip, it make md5 error
Click to expand...
Click to collapse
oh you're right, I didnt saw the Updates on the OP

[Utility] Android Image Kitchen & Flasher APK

Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis

atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
Click to expand...
Click to collapse
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk

Yes, you can try

tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.

Well I use in my apk AIK.mobile tools proposed by osm0sis.

atoxyd said:
Well I use in my apk AIK.mobile tools proposed by osm0sis.
Click to expand...
Click to collapse
https://github.com/osm0sis/AnyKernel2/ ?
from http://forum.xda-developers.com/showthread.php?t=2670512

bigsupersquid said:
tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.
Click to expand...
Click to collapse
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.

atoxyd said:
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.
Click to expand...
Click to collapse
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.

nero curin said:
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk
Click to expand...
Click to collapse
Hi, did my apk work for you?

atoxyd said:
Hi, did my apk work for you?
Click to expand...
Click to collapse
only unpacking and repacking,didnt help on my device but yet again nothing else helps me compile kernel for this idol 3 so i guess this app works just not for me, bad luck :/
Sent from my 6045X using Tapatalk

Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay

atoxyd said:
Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay
Click to expand...
Click to collapse
The scope of my tools is for Google's Android image standard as defined in the bootimg.h header from AOSP/CM. My tool forks have the widest support available for images which are standards compliant, supporting all commonly used ramdisk compression formats.
Supporting Sony's ELF, MTK's labeled and Samsung's headerless image formats along with the standard images (not to mention Samsung's and others' various deviations based on the standard header) and having the script/app differentiate between them would be a very large and difficult undertaking indeed. If that's your plan then I wish you the best of luck in your efforts.

hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well

atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis
Click to expand...
Click to collapse
Thank you for adding the appropriate credit back to your post. Patching, cross-compiling and scripting has taken significant work. :good:
The only other thing that I'd ask is that you do not use the name of Android Image Kitchen or AIK in the title of your app. I'd like to suggest maybe "Image Editor and Flasher" as a snappy alternative?

bigsupersquid said:
hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well
Click to expand...
Click to collapse
Thank you my friend , you are the only one who supported me , and from the beginning.

atoxyd said:
Thank you my friend , you are the only one who supported me , and from the beginning.
Click to expand...
Click to collapse
it's a useful project, definitely worth a little testing and feedback.
besides, i remember what a pain it was getting my xda account eligible for posting the project i was all gung-ho about sharing (optimus v boot from sd card if i remember correctly)
sharing is cool, but a lot of the feedback tends to be annoying when there's no logs or other usable information, just "it's broken" or "can you implement for me on device XYZ."

bigsupersquid said:
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.
Click to expand...
Click to collapse
Did you have an unlocked bootloader ?

nothing changed on the device, unlocked and still s-on, I'm not sure what went wrong the first try.
PEBKAC error probably
(problem exists between keyboard and chair)

I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.

atoxyd said:
I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.
Click to expand...
Click to collapse
Please use a different name for your app as I have requested.