Related
Hello,
Been wrestling some time with different firmwares / mods and kernels. I had many problems and currently re-visiting my 900 apps long list in Google Play.
Currently I'm very happy with [ROM] Android Revolution HD 17.1 | High Quality & Performance | AROMA | Android 4.1.2 - especially after the many problems I had with my previous Franco kernel
BUT, again, I've chosen a custom kernel, advised by Revolution HD: Perseus-alpha27.1-i9300.tar . This kernel (?) seems to have very bad wifi performance. And I mean really really really bad Upgrading to Perseus-alpha29.1-i9300.tar did not fix, although Change Log mentioned improved wifi performance.
After having spend changing kernels and stuff many times with Odin 3.04 (I still don't understand how it knows WHAT to flash when 'an image' is offered... Must be in the tar itself, but still I thought I could easily download the Samsung Galaxy Siii official stock kernel (NOT ROM, but KERNEL). Should be a small file (<10MB), not a >700MB download with the ROM included.
I've browsed many threads on xda and beyond, but downloading JUST the OFFICIAL kernel... SIGH I cannot find it?!!
What am I missing here??
Very curious if anyone can point me to a download link for the official kernel.tar I need? Or kernel.zip? I don't feel like re-installing everything, I just want to re-install the kernel alone. OR is this impossible? Please advise, I don't like feeling like a newbie
One of the few downloads I could find (like forums . androidcentral . com /verizon-galaxy-s-iii-rooting-roms-hacks/191375-guide-restore-back-clean-factory-stock-update-10-23-a.html) do not work - when flashed my phone ends up bricked (tested many times:0).
Anyway, thank you for a great forum!
Phone info: Samsung Galaxy Siii International GT-i9300
Android Version: 4.1.2
Baseband: i9300xxelkc
Kernel 3.0.36-Perseus-alpha29
Build Android Revolution HD 17.1 by mike1986
Peace!
Devvie
~~~ [email protected] ~~~
Cuisvis hominis est errare, nullius nisi insipientis in errore persevare
——
All spelling mistakes are my own and may only be distributed under the GNU General Public License! – (© 95-1 by Coredump; 2-012 by DevNullius)
See your other post I have replied to that one.
Sent from my GT-I9300 using xda premium
Trying to solve it myself - part xxx ;p
The following Google search brought some light to the end of the tunnel, I hope: http://www.google.com/search?q=stock+zimage+i9300+samsung&oq=stock+zimage+i9300+samsung&ie=UTF-8 .
It first brought me to this page: http://androidromupdate.com/2012/06/05/how-to-install-stock-rom-on-samsung-galaxy-s3-s-iii-gt-i9300/ .
There I learned the following (quote):
" Stock ROMs contains the binary and image files of the whole software packaged, like these:
* Sbl.bin
* cache.img
* factoryfs.img
* hidden.img
* modem.bin
* param.lfs
* zImage "
So I figured to let 7zip extract the stock firmware I downloaded (>700MB). Except for unexpected archive header warning, 7zip extracted just fine. I ended up with:
* boot.img
* cache.img
* hidden.img
* modem.img
* recovery.img
* system.img
From the chapter "For some reasons how to root the device info is here" (http://forum.gsmhosting.com/vbb/f200/galaxy-s3-i9300-flashing-root-guide-1483155/), I learned the following:
Quote: " According to Chainfire, the modification of the kernel was not as easy as done for the SGS I, SGS II, and SG Note, because, “…this time around, Samsung is using the standard boot.img format, instead of the zImage format used for SGS1, SGS2, SGNote, etc, that is much harder to repackage.”
This time around, the SGS III also has a separate Recovery partition, and unlike its predecessors, a custom recovery can now be flashed independent of the kernel."
So zImage is boot.img on i9300 - finally I learn something :> Also see: http://forum.xda-developers.com/showthread.php?t=2022181 .
I was hoping that I could just flash this file with Odin. I have not tried it yet, for I first wanted to make sure that boot.img === kernel-to-flash
http://www.google.com/search?q=what+is+a+zimage brought me to http://www.embeddedarm.com/support/faqs.php?item=2 and especially http://forum.xda-developers.com/showthread.php?t=1284986 . And brought many more questions - just flashing does not seem to be the trick?
So googling some more:
http://www.google.nl/search?q=is+the+(zimage.img+OR+boot.img)+the+same+as+the+kernel??&ie=UTF-8 brought me to: http://forum.xda-developers.com/showthread.php?t=1477845 where there are instructions on how to split the kernel :s SIGH - why is this so hard??? Grmbl.
Quote: " At this point, we need a boot.img file to play with.
Pick your favorite custom kernel and get the .img.
Place it in a folder along with the 2 perl scripts from the attached package.At this point, we need a boot.img file to play with.
Pick your favorite custom kernel and get the .img.
Place it in a folder along with the 2 perl scripts from the attached package. "
And: " Can I do this on Windows? - Not that I know of, no. " SIGH!!
At this point, I'm about to give up again. One more page? http://www.freeyourandroid.com/guide/extract-edit-repack-boot-img-windows .
Quote: " boot.img is a small(ish) file that contains 2 main parts, the kernel (the brain of the Android system) and the ramdisk (a core set of instructions and binaries that begins the boot process and controls base aspects of the system, such as mountpoints, memory management and startup services). "
This looks promising! This solution works on Windows by installing Cygwin (Linux for Windows) and the for-mentioned scripts. I learned more AND I see confirmation for what I already learned...
Quote: " boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk. "
This is something I definitely will try out tonight when I'm home - light again?
Peace!
devnullius
--
Some further technical info and background reading with some nice tools: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images (from: http://forum.xda-developers.com/showthread.php?t=1831027 ).
Partial solution for my stalled wifi connection due to custom kernel (gs3)
I'll will investigate the splitting-process one day for sure. For now, I have solved it, although I expect problems...
To manage the phone, I downloaded SGS3_International_ToolKit_v6.0.exe (>100MB). After installation this gives C:\Samsung Galaxy S3 ToolKit\root . This folder contains many boot images (stock or insecure). I chose for boot-insecure-xxdlj4-i9300.tar (for Android 4.1.1).
After flashing it with Odin, my wifi problems with slow to stalled network traffic was instantly solved Now my phone reads as follows:
GT-i9300 / 4.1.2 / i9300XXELKC / 3.0.31-368423 [email protected] #1 SMP PREEMPT Fri Oct 19 18:17:48 KST 2012 / Android Revolution HD 17.1 by mike1986.
LAST QUESTION, for now, is: is it pure luck that the kernel made for 4.1.1 works with 4.1.2? Or does that have nothing to do with it???
Peace!
devnullius
Actually the new boot.img is a lot easier to decompile and recompile compared to the SGS1/2's zImage format
Sent from my GT-I9300 using xda premium
I can provide the boot.img from xxelkc
Actually I use franco.kernel updater app in which I can either backup or restore my kernel
That's how I got the boot.img
Sent from my GT-I9300 using xda premium
freddy1991 said:
I can provide the boot.img from xxelkc
Actually I use franco.kernel updater app in which I can either backup or restore my kernel
That's how I got the boot.img
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yeah, that's how all my troubles started I first did Franco kernel, then I switched to ClockworkMOD. I had problems and wanted to reverse kernel with the backup I made with Franco Kernel Updater app. It failed and gave me bricked phone
I really start to think all those custom kernels are to be AVOIDED ;p
Thank you, merry christmas and... Peace!
devnullius
i'm trying to build an aosp rom for my samsung galaxy s duos(gt-s7562). what modifications do i do so that the rom can work on my phone.
i've downloaded one file from samsung open source website this files contain two things called platform.tar.gz and kernel.tar.gz
how do i go about this.
i'm running the latest firmware update and the phone is rooted and has clockworkrecovery mod on it
For all those who aren't yet ready to upgrade to Lollipop but would like to close this vulnerability on their device, I have built the latest CM11 i9100 source as of 9/1/15 (since CM11 nightlies for this device are no longer released for download). This build is unofficial but I have not modified it in any way**. It includes all StageFright fixes that the CM development team has implemented.
All required downloads are located here.
Works well as a daily driver with Lanchon's i777 Crossflash Kernel on my device.
Installation instructions can be found on CM's website or on Lanchon's kernel thread (above).
I recommend wiping cache/system/data prior to flashing (dirty flash with only a cache wipe did not work on my device when upgrading from the last public nightly).
Good luck!
** I did manually modify the updater-script to allow this ROM to be flashed on any device (because i9100 ROMs refuse to flash on the i777/S959G). Flashing this ROM on anything other than an i9100/i777/S959G WILL brick your device.
XDA:DevDB Information
CyanogenMod 11 [UNOFFICIAL] for i777 with Stagefright Fix, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
dimoochka
ROM OS Version: 4.4.x KitKat
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-08-31
Last Updated 2015-08-31
Apparently the crossflash kernel is incompatible with this build (not sure why - was working ok on my device). A compatible version was rebuilt by Lanchon on 9/4/15 (can be found on his thread or in the download link in the first post).
Very considerate, and good of you to take the time to present this. Cheers, and build-on!
-Cyril
Stagefright bug still present
Flashed it yesterday.....all works fine.....except bug isn't fully patched
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
I just started a rebuild. Will try to upload when it's finished tonight - maybe that vulnerability has been patched since the last time I built this (months ago).
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
dimoochka said:
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
Click to expand...
Click to collapse
i just dirty flash it. right?
mmystere68 said:
i just dirty flash it. right?
Click to expand...
Click to collapse
If you're coming from a prior version of CM11 dirty flash should be fine.
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Edgarhighmen said:
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Click to expand...
Click to collapse
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
dimoochka said:
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
Click to expand...
Click to collapse
Thanks dimoochka, i'm probably going to give it a go this weekend.
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Rhaegon said:
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Click to expand...
Click to collapse
Glad this helped! Just so you're aware I haven't rebuilt this ROM for a good 9 months (and I am not even sure if the CM team is still patching old bugs in versions 11/12). If you're unable to get CM13 on the i777, I would definitely suggest buying a newer device for the sake of security. Nexus devices are basically the only option I'm aware of here since none of the other manufacturers actively maintain their ROMs. I retired my i777 in leiu of a Nexus 5X about 6 months ago.
Best of luck!
This rom is a port of the Stock Touchwiz Marshmallow beta build
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
I'm searching for Contributors, if you are interested, please send me a PM
Current Status: Released first Alpha (v0.1a)
Next Release ETA: ~ January 2016
Known Issues:
Stuck On Boot Logo
Click to expand...
Click to collapse
Install Guide:
Download the compressed file
Decompress the file
Reboot phone in download mode
Open the folder called "Odin + flash files"
Open Odin, flash the pit file (i9100-3GB) and the kernel (i9100-kernel)
Copy the continuingM flashable zip file into an sd card
Insert the SD card in the phone
reboot the phone in recovery mode
Wipe data/factory reset
Flash the continuingM Zip
Fix permission
reboot phone
Click to expand...
Click to collapse
Changelog:
v0.1a
Initial Release
Click to expand...
Click to collapse
Downloads:
Alpha 1
Click to expand...
Click to collapse
XDA:DevDB Information
ContinuingM Touchwiz Edition, ROM for the Samsung Galaxy S II
Contributors
firepenguin
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2015-12-29
Last Updated 2015-12-29
Interesting project. Keep it up!
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
firepenguin said:
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
Click to expand...
Click to collapse
hi,
something like this ?
http://forum.xda-developers.com/showpost.php?p=63855358&postcount=122
http://forum.xda-developers.com/showpost.php?p=63854846&postcount=113
wel wel wel... rely intersting project keep up
Interesting,
I am waiting to test your rom.You know if we gonna have this function available ?
Call record
Code:
Voice call uplink + downlink audio source
Constant Value: 4 (0x00000004)
Interesting .......
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
GreekDragon said:
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
Click to expand...
Click to collapse
Yes bro but I guess device needs official marshmallow, Because i don't have much faith in Touchwiz when it comes to updates
And personally i believe stockis better than port in Touchwiz ROMs
Placeholders aren't allowed on XDA.
edi194 said:
Placeholders aren't allowed on XDA.
Click to expand...
Click to collapse
Actually, since this thread is clearly labeled "WIP" this is allowed. Ongoing development.
Thanks for your concern.
The_Merovingian
Forum Moderator
I will test to help development
I'm currently deodexing the dump and removing all arm64 libs/binaries. I think that the first alpha will be ready for the 2nd January
I've done the first build, Now i'm uploading it. It won't boot, it gets stuck on Galaxy SII logo, I don't know why. To flash it you need to repartition the phone. The file i will upload is a 7z file, so you need to decompress it to flash. The file contains odin, the pit file and the rom
Clean CM13 kernel can't boot TouchWiz rom. You need to modify it.
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
firepenguin said:
I've done the first build, It won't boot, it gets stuck on Galaxy SII logo, I don't know why.
Click to expand...
Click to collapse
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
i confirm , no boot , sorry for s2.
I think S2 would be ported on S3 JB 4.3 stock firmware rather than this.
This is almost impossible... 64bit firmware is not compatible with 32bit device.
FaserF said:
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
Click to expand...
Click to collapse
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
PolishVodka said:
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
Click to expand...
Click to collapse
Thank you so much. I will try your method
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- Touchscreen failure (sometimes occurs, if touch works after reboot it will work till next reboot);
- Camera (both);
- Dock special keys (top row);
- GUI crashes; - occure less often
Currently, I'm only one from Unlegacy Team, who has TF device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Latest information about OREO builds can be found HERE.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Eee Pad Transformer Prime
Contributors
Clamor, Ziyan, Narkolai
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
TF201 users know well what is repartition. While flashing 4.2BL from HB internal storage is reformatted. This thing is exactly the same.
I worked on it for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY!
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash HB bootloader or Bootloader 4.2 attached in Downloads section.
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
MalibuKoKo said:
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
Click to expand...
Click to collapse
Actually you can't build fully working ROM from my source for now. If you would like to help in developing - PM me.
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
goosebickel said:
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
Click to expand...
Click to collapse
Based on latest 4.2 bootloader (like Hairybean). I'll provide a bootloader + new TWRP and separate TWRP as soon as I get a stable recovery build.
General Feedback
Finally got around to flashing your ROM a week ago, following your instructions, everything went fine. I installed your UA-bootloader and flashed _that16 kernel.
Running pretty smooth with Pico gapps installed, after a week, the usual happens, slow loading apps etc, but that is not the ROMs fault, the very slow memory that Asus put into it and Google is slowing it down with constant syncs etc.
Was wondering if you had added compatibility for using MicroG?
Thanks for keeping this old tablet going.
@goosebickel sorry for such a long silence. MicroG are supported as I can say (I installed them but didn't test much).
P.S. If you are still on UA rom there is an update.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs from O for now. I know already about all major issues.
Thank you!
Great to see some development for the Transformer Prime
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Clamor said:
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Click to expand...
Click to collapse
Are you planning to work on Pie as well once 8.1 is somewhat stable?
shinzz said:
Are you planning to work on Pie as well once 8.1 is somewhat stable?
Click to expand...
Click to collapse
I'm planing to bring up P as well. If O works, P should work as well.
Can the ROM be installed by using the latest KANG TWRP 3.2.3 or do I need to use the TWRP found in the download section?
@shinzz TWRP from download section
any update?
shinzz said:
any update?
Click to expand...
Click to collapse
Noticed the link to the ROM is 404'ed also. - NP
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Clamor said:
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Click to expand...
Click to collapse
My 201 is on KANG's - TWRP 3.2.1-0 and KatKiss, if this ROM just a simple wipe and flash with KANG's - TWRP 3.2.1-0 and the Harry Bean bootloader on my 201 or will I need a different recovery console, bootloader ext. ext? - NP