Develop Bugs

[RECOVERY] [OFFICIAL] TWRP 2.2.2.1 for Acer Iconia Tab A100

Teamwin Recovery Project for A100 version 2.2.2.1​ -godmachine81 release-​
SOURCES: Available via Github
Download and Install via the official supported method by TWRP
Install Goo Manager app from Play Store, Open Goo Manager, In the Menu in top right corner go to "Install OpenRecovery Script" Follow Instructions On screen
Download Automated Installer (Windows / Linux):
Linux Installer - 2.2.2.1
Windows Installer - 2.2.2.1
Download IMG:
TWRP v2.2.2.1 main mirror
Download Flashable Zip: (Upgrade Only)
TWRP 2.2.2.1 Flashable Upgrade
Updated TWRP release features:
Uses a custom recovery kernel based off of my v1.5 standard kernel with most unneeded features taken out, i.e. governors, schedulers, networking, misc devices, and most things not needed for recovery operations
Kernel and TWRP includes patches aimed at brick prevention
Resolution is set at native 1024x600
Very fast actions and touch response
Backward compatibility with previous releases of TWRP
Compatibility with all Ice Cream Sandwhich and Jelly Bean ROMs for the A100(HoneyComb should be compatible too, however currently untested)
All previous features from TWRP that you may be familiar with are included
Mount Point Information:
External Storage - mountpoint= /external_sdcard
Internal Storage - mountpoint = /sdcard
Instructions:
Automated Installation (Windows/Linux):
Most importantly you need to have all drivers required for adb and fastboot working on your OS, this shouldn't be a concern for linux users, however it may be for Windows users as it is picky about adb drivers.
Download the above Automated Install .zip file for your operating system
Extract the contents of the Zip to a location on your PC's hard drive
Change to the extracted directory's contents.
Run the installer; On windows you may just double click the install-windows.bat file, on linux you need to run the install-linux.sh script
example linux installation commands:
Code:
cd a100_twrp_installer_linux
Code:
bash ./install-linux.sh
Read the on screen information of the progress. If you get any errors you will need to resolve the issue or try one of the following alternative install methods.
If you need more detailed installation instructions please read the INSTALL file included inside the .zip
Manual installation:
Download the .img file for the recovery
Connect your A100 device to USB on your PC
While your A100 is booted in either Android or Recovery just enter the following into your PCs command prompt/shell:
Code:
adb reboot bootloader
Now flash the image - at the command prompt/shell enter:
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img
Reboot the device - again from the command prompt/shell:
Code:
fastboot reboot
Enter Recovery mode - While tablet shuts off, hold the Vol - (down) button until you see the screen saying "loading recovery kernel"
Checkout the new TWRP build and enjoy!
Flashable Upgrade Instructions: (flash just like you would any other .zip, but here are instructions anyway)
Download the Flashable ZIP above
Save to a location on your tablets internal or external memory
Boot to recovery
Choose the file a100_twrp_upgrade_2.2.2.1.zip in the install menu
Swipe to install
Wait and DO NOT Disconnect your A100!
When finished, go back to Main menu - choose Reboot - and Reboot Recovery
Enjoy the Official 2.2.2.1 TWRP Release!
If you would like to help out with the continuance of my kernel development and other goodies for your Acer Iconia Tab please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
​

.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6

pio_masaki said:
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
And don't forget that i forgot the download link!! lol **fixed haha

Broken links, so you can correct it.

Fransis88 said:
Broken links, so you can correct it.
Click to expand...
Click to collapse
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone

linuxsociety said:
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
Click to expand...
Click to collapse
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.

Fransis88 said:
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Click to expand...
Click to collapse
So let me know how you like it. Also if you happen to be a linux user, I have wrote an automated installer script for linux, Xbow59 is currently writing a windows batch script for installation, I currently have the Linux installation working though if you'd like to test/try it out just let me know. Windows users can look forward to an automated solution within a day or so

help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.

nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
Click to expand...
Click to collapse
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!

linuxsociety said:
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
Click to expand...
Click to collapse
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)

nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
Click to expand...
Click to collapse
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6

nim.whit said:
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
Click to expand...
Click to collapse
yep what pio said:
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
I had forgot all about this, even though it is in my unreleased linux auto installer. If by chance you are using linux, I have an installer that will do this all for you the right way, I just haven't posted it yet because I don't have the windows installer fixed
you can either download the linux installer git repo and just extract it to a directory named twrp_install or similar; just run sudo bash ./install-linux.sh after you are in the install directory. https://github.com/godmachine81/Acer-A100-TWRP-Installer/zipball/linux <<current linux installer for a100 twrp
Or you can clone the repo
Code:
git clone https://github.com/godmachine81/Acer-A100-TWRP-Installer.git
then checkout the linux branch:
Code:
git checkout linux
then install:
Code:
sudo bash ./install-linux.sh
The git method requires you have git installed, you will probably just want to install from the zipball method if you don't already have git

pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause

nim.whit said:
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
Click to expand...
Click to collapse
Once that's removed or renamed it will stop, one time deal.
Tapatalked from my A100 - Jellytime X B6

Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.

linuxsociety said:
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
Click to expand...
Click to collapse
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3

pio_masaki said:
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
Click to expand...
Click to collapse
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol

linuxsociety said:
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
Click to expand...
Click to collapse
The ics Acer zips are known brickers but it happens for a reason I'm not very clear on. HC will also brick it.
Basically there's a chance it will run the zip, attempt to flash everything, however for some reason it will fail to flash system or boot correctly, but does replace the bootloader. What I'm not clear on is why it fails on system or boot but succeeds on bootloader, or why recovery doesn't error flashing it.
Once this situation occurs you get locked out of both recovery and system by the bootloader, no adb or fastboot access to correct it.
Using the information I've gathered on this I've been working on a method to restore to stock if needed, but its going slow as I have to triple check everything before I even test it. Its a long and annoying process but should result in a 100% factory stock system.
Tapatalked from my Galaxy S II.

Installed and working perfectly!

Fransis88 said:
Installed and working perfectly!
Click to expand...
Click to collapse
Great Francis88, mind I ask which method of installation you chose?

[Q] fastboot/recovery/kernel files confussion

I needed fastboot files so i did a little research to find to different files.
1 had only 3 files in the folder(ckpv5's tutorial)
& the other had 6 files(cybervibin's tutorial) so i dont want to mess up flashing kernel.
Since these are important files.
Someone plz help me chose between which fastboot i must copy to c drive

The one with most files just run the fast boot.exe
Sent from my One V using xda app-developers app
---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------
Doesn't have to be on c: drive can be desktop
Sent from my One V using xda app-developers app

u mean i dnt have to cmd/ fastboot flash boot boot.img.
wer do i copy the boot.img i want to flash?

I know 1 way.
Open cmd type fastboot flash boot boot.img(u have too copy its exact location)
then fastboot reboot.
Is that right?
I read somewhere u have to copy boot.img to fastboot folder.
That made me confused like hell.

I found the soltn thread closed.

Why do you need to be confused
The extra files are HTC Driver and TWRP image... those are not part of fastboot
When you want to run fastboot flash boot boot.img - the boot.img file must be in fastboot folder
When you run fastboot flash boot [folder path]/boot.img - the boot.img can be at any folder and put the right path ... but why do you want to do the hard way

ckpv5 said:
Why do you need to be confused
The extra files are HTC Driver and TWRP image... those are not part of fastboot
When you want to run fastboot flash boot boot.img - the boot.img file must be in fastboot folder
When you run fastboot flash boot [folder path]/boot.img - the boot.img can be at any folder and put the right path ... but why do you want to do the hard way
Click to expand...
Click to collapse
No other developer is as calm as you ckpv5.
So flashing kernel is the big deal for me.
As i am doing it for the 1st time.
I wanted to flash some AOSP Roms.
So i was just curious wether i should do it or not.

Nishblueweapon said:
I wanted to flash some AOSP Roms.
So i was just curious wether i should do it or not.
Click to expand...
Click to collapse
Flashing any ROM either Sense ROM or AOSP ROM, you need to flash the boot.img as mentioned on OP. The ROM thread will tell you what kind of kernel/boot.img that you need. Some is on CM9 kernel, some on CM10 kernel and some is using the stock kernel or TK kernel. For CM10 they have two different kernel if I'm not mistaken, so read carefully.
Most basic thing is to flash a boot.img that is meant for that ROM.

ckpv5 said:
Flashing any ROM either Sense ROM or AOSP ROM, you need to flash the boot.img as mentioned on OP. The ROM thread will tell you what kind of kernel/boot.img that you need. Some is on CM9 kernel, some on CM10 kernel and some is using the stock kernel or TK kernel. For CM10 they have two different kernel if I'm not mistaken, so read carefully.
Most basic thing is to flash a boot.img that is meant for that ROM.
Click to expand...
Click to collapse
Thanks ck for your support.
Before flashing Rom i tried back up from recovery but it had some error.

That's too general.
You need to tell what kind of error, what is written for the error then only someone can tell you whether that's an error or something normal

ckpv5 said:
That's too general.
You need to tell what kind of error, what is written for the error then only someone can tell you whether that's an error or something normal
Click to expand...
Click to collapse
It said something failed to create image.
It ocurred during backing up process.The process was completed 50 %(not accurate) & then the error.

Change your CWM to a better version or use TWRP as most people do.

ckpv5 said:
Change your CWM to a better version or use TWRP as most people do.
Click to expand...
Click to collapse
i have the same version u mentioned in your thread how to unlock bootloader.
where do i search for the latest cwm/twrp?
i ll chose after reading reviews

Read again http://forum.xda-developers.com/showthread.php?t=1996665 and follow the links under Recovery Images[PRIMO U/GSM]
When you first started this thread you were confused why he has more files for fastboot and I mentioned he has TWRP there.
I personally use TWRP 2.4.3.0
Gotta go now .... if there is anything further, I'll check later when I'm home

ckpv5 said:
Read again http://forum.xda-developers.com/showthread.php?t=1996665 and follow the links under Recovery Images[PRIMO U/GSM]
When you first started this thread you were confused why he has more files for fastboot and I mentioned he has TWRP there.
I personally use TWRP 2.4.3.0
Gotta go now .... if there is anything further, I'll check later when I'm home
Click to expand...
Click to collapse
the latest is twrp 2.5.0.0 on their main site. can u try & let me know.
how do i uninstall cwm before installing this.

Nishblueweapon said:
the latest is twrp 2.5.0.0 on their main site. can u try & let me know.
how do i uninstall cwm before installing this.[/QUOTE
http://forum.xda-developers.com/showthread.php?t=1721749
I found this on one v orginal development since it is an official twrp recovery it should not have any
Problem...u can also find steps to install it on that thread...so give it a try...
But I personally use cwm no problem so far ....
Don't know about twrp but cwm installing was quite easy...
If u want I can provide u with my recovery.img ..but give twrp a try..
Click to expand...
Click to collapse

Just use the All In One Toolkit for One V
kernel flashing is made so much simpler and easier:good::good:
Never flashed a kernel via ADB(or whatever its called,dunno coz i never used it )

I dont need to remove CWM before installing TWRP through Toolkit right?

Nishblueweapon said:
I dont need to remove CWM before installing TWRP through Toolkit right?
Click to expand...
Click to collapse
dont think so
but to be sure, ask someone with more experienced

Seraz007 said:
dont think so
but to be sure, ask someone with more experienced
Click to expand...
Click to collapse
some1 plz confirm this

[Recovery][FOTA]CWM and TWRP recoveries for custom ROMs

Now we have official TWRP support, so this thread will not be updated anymore. For more info about official TWRP visit this thread.
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.7.0
TWRP 2.8.6.0 (this and next versions are compiled for Xperia M by me)
Older versions and CWM:
TWRP 2.8.5.0 (port from Xperia L)
TWRP 2.8.4.0 (thanks to @Rohan purohit for bringimg it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.

Download
TWRP 2.8.6.0>>>
TWRP 2.8.5.0>>>
TWRP 2.8.4.0>>>

Restoring original image
- You can restore original FOTAKernel flashing it via Flashtool by flashing any firmware (just uncheck everything in "wipe" section and uncheck everything in "exclude" section excluding "FOTA" like in attached screenshot).
- Or install attached zip via recovery or flash FOTAKernel.img from archive as it is written in OP.

cucumber09 said:
TWRP version is 2.8.0.0, because I could not boot 2.8.3.0 this way (maybe due to ramdisk size limitations), I'll look for this later and will try to fix it
Click to expand...
Click to collapse
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea

kh34d said:
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
Click to expand...
Click to collapse
I don't know for sure. Download both recoveries, try to flash one that differs from yours and reboot recovery. If it changes, that means it works on CM11 kernel. BTW, even if it doesn't work on CM11, it will work when you will flash CM12 kernel. So you can flash it to be prepared.

Some one please uploade original fota kernel, i'm forgot to backup them .. thanks

itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Okay, I will upload original FOTAKernel.

itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Everything about restoring is in 3rd post.

cucumber09 said:
Everything about restoring is in 3rd post.
Click to expand...
Click to collapse
Thangs, now all problem will be fixed ..

@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?

KHM90 said:
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
Click to expand...
Click to collapse
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.

cucumber09 said:
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
Click to expand...
Click to collapse
Ok thx, Not needed just wanna know whether it will work or not
btw, FOTA kernel awesome idea:good:

I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...

ndrancs said:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
Click to expand...
Click to collapse
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.

I'm confused, does it work for locked bootloader?

pincheraro said:
I'm confused, does it work for locked bootloader?
Click to expand...
Click to collapse
No way. It even won't work on stock kernel with unlocked BL.

@cucumber09 Which build is the attached FOTA restore zip from? .9?

elmkzgirxp said:
@cucumber09 Which build is the attached FOTA restore zip from? .9?
Click to expand...
Click to collapse
No, it is from earlier build, but also from 4.3. From first 4.3 build, as I remember.

cucumber09 said:
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
Click to expand...
Click to collapse
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?

ndrancs said:
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
Click to expand...
Click to collapse
I read these sources. And 49th line defines size of uncompressed ramdisk. But now I am not sure, which one is used in our kernel. I suppose, that newer one.

Custom kernel Z3+ E6553 - Nuke Verity / Sony RIC and allow SELinux permissive

Introduction
The stock Sony kernels use SONY RIC, SELinux and CONFIG_DM_VERITY that together make it exceptionally hard to root. With the stock kernel, it's impossible to run a modified ROM of any form (incorporating changes to the system partition). Attempting to boot with the stock kernel off a modified system partition results in a kernel stop or panic, manifested either by getting stuck on the Sony screen or a bootloop.
This kernel removes the Sony RIC and CONFIG_DM_VERITY and sets boot and runtime parameters that allow SELinux to be disabled or to be set into permissive mode. Once this kernel is flashed, you can download SuperSU flashable zip and flash it to your phone using the TWRP recovery image I posted in this forum in order to get root on your stock ROM.
This kernel contains no source patches. It's a completely stock kernel from the Sony github repository.
Click to expand...
Click to collapse
Features
SELinux configurable at boot and runtime
Sony RIC disabled
CONFIG_DM_VERITY disabled
Click to expand...
Click to collapse
Installation instructions
This boot image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
Unzip the boot.zip file to extract the boot.img file
Code:
C:\>adb reboot bootloader
C:\>fastboot flash boot boot.img
C:\>fastboot boot recovery.img
C:\>adb push UPDATE-SuperSU-v2.46.zip /sdcard/supersu.zip
Then switch to the TWRP interface, go to the Install menu and flash /sdcard/supersu.zip. Reboot and you're rooted. You can then modify your system partition as you please.
Click to expand...
Click to collapse
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
Binary
28.0.A.8.251 custom kernel for Z3+ E6553
TWRP Recovery Image V0.1 for Z3+ E6553
Sources @ github
Kernel config
Sony kernel-copyleft repository
Click to expand...
Click to collapse
Changelog
Code:
[B]Changelog[/B]
[new] 12 September 2015- Update to 28.0.A.8.251
[old] 10 September 2015 - Initial release
Thanks To
Code:
[url="http://forum.xda-developers.com/member.php?u=631273"]@Chainfire[/url]. What would we do without SuperSU.....
Click to expand...
Click to collapse

Awesome work, works without any issues.

I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!

elladroid said:
I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!
Click to expand...
Click to collapse
"Until Sony releases an open bootloader you need to use this image via fastboot boot mode."

really 28.0.A.8.251?
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy

DHGE said:
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy
Click to expand...
Click to collapse
Correct. The sources on github are old. I dowloaded the archive from the Sony website and compiled it. Yes the boot.img I compiled works perfectly as a replacement. I'm currently running it on my phone.

How to modify system partition
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.

yawo76 said:
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.
Click to expand...
Click to collapse
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.

dl12345 said:
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.
Click to expand...
Click to collapse
Thanks very much. It's true I installed Xposed Framework and didn't wipe cache. I have already reinstalled the Rom so will remember this time not to repeat the same mistake.

dl12345 said:
Introduction
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
[B
Click to expand...
Click to collapse
I'm on .251 (modified system partition) without XPOSED installed. Using the kernel just causes boot loops (Sony Logo then 3 red flashes from the LED) the same way the stock kernel does. Is there something special I need to get SONY RIC / Verity to not run at boot?

This looks like a bad flash. Can you fastboot this kernel?

dl12345 said:
This looks like a bad flash. Can you fastboot this kernel?
Click to expand...
Click to collapse
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it

ChrisJ951 said:
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it
Click to expand...
Click to collapse
Me neither - this bootimage has very few modifications: only CONFIG_DM_VERITY and RIC removed, some options for runtime control of SELinux added and the verity keys removed from the ramdisk. It boots fine on a stock 251 ROM for me. The kernel source is .251 source too...
I have noticed that I occasionally get bad flashes and odd behaviour when flashing ROMs (with everything from fastboot to flashtool to TWRP). I think the platform itself isn't totally stable and bug free. Usually I fix it by just wiping and reflashing

Hi @dl12345, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
EDIT - removed full OP quoted by mistake.

ondrejvaroscak said:
Hi, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
Click to expand...
Click to collapse
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
[UPDATE]
AOSP and copyleft source are different things. You need kernel source for concept rom's kernel, and it won't be published so it's impossible to build custom kernel for concept rom.

AndroPlus said:
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
Click to expand...
Click to collapse
Do I get it right, that I can't justo compile kernel for use with this firmware from AOSP / Sony Copy-left sources?

[CBUMP][BOOT] Bump Your Current Boot Image

BUMP Your Current Boot Partition
Supports all of G2​
Will work for other devices that use BUMP, so long as boot is located at:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Uses:
1) Fix boot partition after flashing SuperSU.
2) Flash any boot.img you want without BUMPing it first. Flash this zip after flashing the non-BUMPed boot.img.
3) Fix boot cert error.**
**This will fix boot cert error as long as you are on JB/KK bootloader. If you broke your phone and got boot cert error by upgrading your bootloader to LP, this won't help.
4) For Dev: The cbump binary in the zip is built static. Feel free to yank it out and use it for your own purposes.
Use: Simply flash in TWRP.
Download:
https://www.gregtwallace.com/
Download is under Miscellaneous.
Credits:
BUMP Team
Open BUMP Team
CBump Dev (who deleted his account, not sure who it was)
--Dev's Source: https://github.com/blastagator/cbump
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal

res 1

Wow! Awesome thing for our G2.
Gonna test it, im impressed, thank you buddy!
Wysłane z mojego LG-D802 przy użyciu Tapatalka

@InsideMuz
ok i tried it again on two different ROMS (AiCP-MM.11.0[030516] and crDroid[030616])
Variant: D802
flash in this order:
Code:
1. ROM
2. GAPPS
3. SuperSU.v2.68
4. CBUMP
@blastagator
thanks for this CBUMP Tool.

fLipz said:
@InsideMuz
ok i tried it again on two different ROMS (AiCP-MM.11.0[030516] and crDroid[030616])
Variant: D802
flash in this order:
Code:
1. ROM
2. GAPPS
3. SuperSU.v2.68
4. CBUMP
@blastagator
thanks for this CBUMP Tool.
Click to expand...
Click to collapse
You're saying that I should install it after clean install?

InsideMuz said:
You're saying that I should install it after clean install?
Click to expand...
Click to collapse
yes sir, 'coz i always do a Clean iNstall everytime i flashed a ROM and that is my routine 1 2 3 4
or try to boot to recovery on your current ROM and try to flash SuperSU.v2.68 1st then followed by CBUMP.

@blastagator thanks for your perfect tool working awesome

fLipz said:
yes sir, 'coz i always do a Clean iNstall everytime i flashed a ROM and that is my routine 1 2 3 4
or try to boot to recovery on your current ROM and try to flash SuperSU.v2.68 1st then followed by CBUMP.
Click to expand...
Click to collapse
Don't work anyway.

Finally worked with SuperSU 2.70!

Did not work with superuser.zip from jan 31 2016. Still get a cert error.

Ummm... Hello @blastagator
I'll try to explain this swiftly...
I made a LG Framework Installer for LG G2 (and finally it installed), also the thread is here
It works by installing all required files to system and then modifies the ramdisk so that LG Framework will be added to BOOTCLASSPATH. The installer is working and changes are verified by re-extracting ramdisk to a connected computer and checking BOOTCLASSPATH on init.environ.rc.
And here is the problem, I know that cert will be broken so I used your CBUMP but booting still gives me secure boot errors... Please help us

xxoscarxx28 said:
Ummm... Hello @blastagator
I'll try to explain this swiftly...
I made a LG Framework Installer for LG G2 (and finally it installed), also the thread is here
It works by installing all required files to system and then modifies the ramdisk so that LG Framework will be added to BOOTCLASSPATH. The installer is working and changes are verified by re-extracting ramdisk to a connected computer and checking BOOTCLASSPATH on init.environ.rc.
And here is the problem, I know that cert will be broken so I used your CBUMP but booting still gives me secure boot errors... Please help us
Click to expand...
Click to collapse
Have you tried saving the new boot.img, using the normal python bump, and then reflashing the python bump version? That will at least tell you if it is CBUMP or some other issue.

blastagator said:
Have you tried saving the new boot.img, using the normal python bump, and then reflashing the python bump version? That will at least tell you if it is CBUMP or some other issue.
Click to expand...
Click to collapse
I tried, and python worked. Maybe it is CBUMP, but well... I looked through the source code of both and then just appended the 6 bytes of lg_magic to the boot.img and it works! Hahahahha
Anyway, thanks for your response
LG Framework is now ready
One down, two to go
Hooks to framework.jar (xposed?)
Upgrade API lvl of lp apps (permission handling rework to make mm happy)

I tried to make a porting of miui 8 from n5 and after flash rom i flashed this script for bumping boot image. In the reboot anyway i got boot security error. Why? (for doing porting i must decompile and recompile kernel)

Hi there guys!
Well it seems there's a lot of stuff around Bump and LG and devs that I do not know.. I read something but I really didn't get the basic stuff, I saw a few bump threads closed but then I find this one..
I have a few question for whom who may know, if you please..
I have an LG G Pad 7 where the latest stock is Lollipop; to root and install TWRP I got to downgrade to KK, as many of LG owers got to; then I can flash ROMs. But what if I need a rooted STOCK? The only Stock available for me are kdz, which completely erase any stuff. If I try to root the Lollipop stock I cannot boot anymore because of boot error!
So I would like to know if I took the boot.img from a rooted KK rom and then bump it, could I flash it back to Lollipop stock so that I'll be able to root it? Also, if it is possible, do I need a "special" version of Bump tool or can I use the G2 one, for example?
Well, I think it's all..
Thanks a lot for paying attention, see you!

Thanks so much!
I tried to install Magisk on my vs985 (G3 verizon) and of course got slammed by the flashing red and blue lights secure boot error.
Little bit of googling led me here, and this fixed it right up.

does any one know if this can be made to work for lg devices such as vs425pp and k120 ?

Hi. Apologies for asking this here. I'm a bit desperate, and I've been searching for ways to get magisk installed on my g3 (f460k - the korean cat.6 variant with snapdragon 805). My search brought me here. Unfortunately, my device is dead dev-wise. I'm wondering if this would work on Nougat? I'd like to flash Magisk then this to avoid secure boot error. Thanks.
Edit:
Flash it after flashing magisk on f460k running Nougat and it works!!! Thank you op for this!

I edited boot.img (came out at 11 mb instead of 16 but contents seems as the original).
Entered TWRP and installed edited img. (Cannot enter fastboot)
Installed your zip. Script seemed to execute correctly.
Reboot (withot wipe cache/dalvik)
Got this error on the top left corner of the screen with LG logo
secure booting error boot certification verify
Had to re-enter recovery and install back original boot.img
Any ideas? Thanks

http://k.japko.eu/boot-img-manipulation.html
used above procedure, just unpacked and repacked, got 16 mb boot.img, installed tru twrp, installed cbump, got into fastboot