[ROM] I337UCUAMF3 Unadulterated [8-19-13] - AT&T Samsung Galaxy S 4 General

Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have is, "Why did you release this - why wouldn't I just use <insert name here>'s stock rom?" It's simple: every other rom in this forum (at this time) has been modified from the original stock rom - whether they've added root, de-odexed it, debloated it, or otherwise. Because the Unadulterated rom is 100% stock (with stock kernel), it is possible for other developers to flash this rom and use it as a platform for attempting to find a root method for the MF3 users out there already. Plus, I like to make my own modifications from a stock base.
UPDATE (8-1-13): a root method has been found for MF3. See thread here. This ROM's purpose has been fulfilled, but your are still welcome to use it, of course!
UPDATE: The MF3 Odin files have been uploaded by @Shockndrop over in his thread here. Remember that the Odin files will flash your bootloader to MF3 (if you allow them), so be careful out there.
Rest assured, this rom will not update your bootloaders, it will not break your custom recovery, and it won't flash your modems. Like most roms, it will simply replace your /system and flash a Kernel. It's also scripted to wipe cache and dalvik for you. It will not wipe your /data partition - you might want to do so if you run into problems, especially when coming from other roms.
Next, you might ask, "How can you say this is 100% stock? How did you construct it?" I'll hide nothing from you - you can build it yourself if you'd like. Here's how I did it:
Rooted with motochopper
Installed TWRP 2.6.0.0
Wiped data & cache
Odin to MDL stock
Allow one full reboot:
Boot script runs (installs CSC - this is REQUIRED for the MF3 update to patch correctly)
Clears up any SysScope flags, etc. that may have persisted from previous rom or root.
"Temporary Root" using motochopper:
Code:
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
NOTE: Possible outcomes of temporary root:
Failure
Success, motochopper exploit hangs, device spontaneously reboots
Success, immediate return to prompt, but adb shell is still not root (indicated by $ prompt)
Success, immediate return to prompt, adb shell is root (indicated by # prompt)
Repeat as needed (usually only twice or so?)
NOTE: Don't both trying to run su. It isn't installed. We're just relying on motochopper to give us a temporary adb root shell.
From adb root shell, installed TWRP recovery:
Code:
dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
Rebooted, checked to be sure system status is still Official. Note that at this point, we've got a 100% stock MDL rom, without root, but with a custom recovery. Woot.
Rebooted into TWRP, installed custom-neutered OTA update (mf3-sys-only.zip), which only does the following:
Verifies all system files
Removes "unneeded" files (as determined by AT&T, not me)
Patches files
Copies new files
Sets permissions
Patches build.prop
Wiped data & cache for good measure
Booted phone, verified ROM works okay, system status = official. Rebooted, checked Odin Mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Booted back to TWRP to begin pulling dumps
... Now, on to the good stuff!
ROM Install Instructions:
Download mf3-stock-rom.zip and place it on your internal sdcard.
Make a nandroid backup of your existing system, data, cache, and anything else you deem important (everything!).
Flash/install the zip using your favorite custom recovery. This part should take several minutes - the file is huge!
Optionally, flash any additional Add-ons that you want (e.g. SuperSU for root)
Optionally, flash a custom kernel (use instructions from the kernel's author!). Note that some custom kernels will need you to flash Loki-Doki. The included kernel does not require Loki patching! It is 100% stock, and your system will accept it as-is.
Optionally, wipe /data. You can skip this, but if you get a ton of force-closes or extreme problems, this would be one of the first troubleshooting steps.
Reboot, and enjoy!
Click to expand...
Click to collapse
Important Recommendation:
You are advised to disable the OTA update applications! If AT&T/Samsung release a new OTA update (beyond MF3), it is theoretically possible to download and install it while using this rom! Accepting such an update could do just as much damage as the original MF3 update did. You can easily disable OTA updates from a root ADB shell using the following commands:
Code:
pm disable com.wssyncmldm
pm disable com.LocalFota
pm disable com.sec.android.fwupgrade
You could also use Titanium Backup Pro to accomplish the same thing. I will later look into the possibility of disabling these using a flashable Add-on zip that otherwise keeps your system as stock as possible.
Known Bugs:
If you do not flash a custom kernel, you will lose WiFi. The WiFi in the MF3 Kernel is expecting the MF3 bootloaders, which we aren't flashing. Therefore it breaks.
If you happen to have the MF3 modem/baseband installed, your WiFi might work, but your sound may stop working completely. This is also a result of not having MF3 bootloaders. A custom Kernel should fix this too.
If you use the "remove-SysScope" Add-on, be careful of any other mods that may poke around with SecSettings.apk - these are rare, but there's some risk of conflict here.
With the custom kernel I installed, I frequently received the "The device has detected an application attempting..." message. This can be pinpointed to the KNOX agent, and can be fixed a different ways (your choice!):
I found this post to be very helpful.
You can also try using the command pm disable com.sec.knox.seandroid from a root ADB shell. This just freezes the app. Personally, I used this method.
@jeboo also mentioned that the KNOXAgent.apk can be patched using smali/baksmali. Check out his post about it.
Also with the kernel I installed, there was a bug regarding updating the camera firmware. I was forced to restore the stock kernel temporarily, open the camera app to update the camera firmware, and then re-flash the custom kernel. The original MF3 kernel is included in the Add-ons.
Any other bugs are likely straight from AT&T/Samsung, otherwise they could be from your custom kernel, if you flashed one.
Be sure to make good backups of everything, and be prepared to use Odin back to stock. One member has reported that after flashing away from this rom to any other rom/kernel, their SIM card would not work until they used Odin to return to stock. After Odin, it worked fine.
It seems most custom kernels are expecting you to have an MDL baseband. Some people are reporting strange issues (such as problems with video streaming) when using MF3 modems and their choice of custom kernels. Check out File #11 for various modems, NON-HLOS modems, and kernels.
Custom Kernels:
Here's a list of custom kernels that are known-working with this rom. Please feel free to test and report other working kernels, and I will gladly add them to the list!
@jeboo's Kernel - built for @shoman94's SHOstock rom. Available in post #3 of their thread.
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me. It appears that the kernels in their thread require Loki-Doki to be flashed after flashing the kernels. However, the one that I downloaded came from here: http://d-h.st/WVs and it was pre-patched for the I337.
@Jamison904's Infamous Kernel works really well, it seems. It also has BusyBox v1.19.3. I'm currently using v4.0, but there are newer versions available on his Dev-Host folder. These are for the M919, so flash Loki-Doki afterwards if you're on I337!
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
File #1 - mf3-stock-rom.zip - CWM/TWRP-Flashable ROM .zip file - created by hand (you are welcome to dissect it if you'd like - take a look inside the updater-script)
Files #2-#7 (individual image files and odin-flashables):
File #2 - system.img.ext4 - EXT4 format copy of the System partition - pulled using make_ext4fs in TWRP:
Used fdisk to obtain partition size:
Code:
# fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Dumped the partition:
Code:
# make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 3192/176704 inodes and 584765/706560 blocks
File #3 - system.img - Binary copy of the System Partition - pulled using dd:
This was much easier to create:
Code:
# dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
File #4 - boot.img - Kernel - pulled from the OTA update file
File #5 - mf3-sys-boot.tar.md5 - "Odin-flashable" tarball - created without any modification:
Using a Linux PC or Cygwin, executed the following:
Code:
$ tar -H ustar -c system.img.ext4 boot.img > mf3-sys-boot.tar
$ md5sum -t mf3-sys-boot.tar >> mf3-sys-boot.tar
$ mv mf3-sys-boot.tar mf3-sys-boot.tar.md5
File #6 - mf3-sys-boot-sgs4ext4fs.tar.md5 - "Odin-flashable" tarball - "bloated" with Chainfire's sgs4ext4fs
Using a Linux PC (I used Ubuntu 13.04 64bit - couldn't get the win32 version to process the file entirely):
Code:
$ mv ./sgs4ext4fs.linux.amd64 ./sgs4ext4fs
$ sudo chmod 755 ./sgs4ext4fs
$ mv system.img.ext4 system.img.ext4.orig
$ ./sgs4ext4fs --bloat system.img.ext4.orig system.img.ext4
Optionally, you can use the "--list" option to view the file before and after the bloating. Once complete, pack it up in a tarball again.
File #7 - mf3-factoryfs.tar.md5 - "Odin-flashable" tarball - created using the system.img instead:
Using a Linux PC or Cygwin, executed the following:
Code:
$ mv system.img factoryfs.img
$ tar -H ustar -c factoryfs.img boot.img > mf3-factoryfs.tar
$ md5sum -t mf3-factoryfs.tar >> mf3-factoryfs.tar
$ mv mf3-factoryfs.tar mf3-factoryfs.tar.md5
Files #8-#11 (Add-ons!):
File #8 - UPDATE-SuperSU-v1.41.zip - ROOT! Flash this to root your new MF3 rom!
Original is found on Chainfire's website.
File #9 - remove-SysScope.zip - Want to stay "Official", even though you rooted? Flash this! It will remove SysScope and customize your SecSettings.apk to not check for SysScope anymore. Must be flashed before first boot, otherwise you'll just be stuck with a "custom" status until you remove it by some other means.
File #10 - mf3-kernel-only.zip - Want to quickly flash back to the MF3 stock Kernel again? Flash this. No need to use Loki-Doki after flashing this - the I337 will accept this just fine and boot.
File #11 - all-kernel-modem-apnhlos.zip - My personal collection of flashable .zip's of all available versions of the stock kernel, stock modem, and stock NON-HLOS modem for the I337 - including MDB, MDL, MF3. Unzip this file first, and flash individual partitions/versions in whatever combination you want.
Disclaimers, etc.:
I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other devices, I can't guarantee anything!
You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.
If you appreciate my work, please use the THANKS button below to let me know!

reserved...

First .. ..... Hey guess u got ur phone up and running huh ?

Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748

as expected...
Aou said:
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have
.......
[*]I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other device, I can't guarantee anything!
[*]You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
[*]I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.[/list]
If you appreciate my work, please use the THANKS button below to let me know!
Click to expand...
Click to collapse
The result was what was expected.
Keeping my fingers crossed for other solutions...

iB4STiD said:
First .. ..... Hey guess u got ur phone up and running huh ?
Click to expand...
Click to collapse
Nope! Ended up needing to replace it, unfortunately. The original is a 100% hard brick. It won't even take the MF3 firmware via JTAG.
jeboo said:
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
Click to expand...
Click to collapse
Awesome - thanks! I'll add that to the list of options. Also, thanks again for your awesome Kernel. v1.4 is exactly what I need for my phone.
SaltyFoam said:
The result was what was expected.
Keeping my fingers crossed for other solutions...
Click to expand...
Click to collapse
This is really unfortunate, but somewhat expected (as you've said). Have you tried the Odin-flooding again (even with the MDL or MF3 Recovery) yet? That was a very interesting accidental discovery you made. I'm going to have to try that myself too! It might have been a fluke, but still worth investigating.
As an update: The last file (mf3-factoryfs.tar.md5) has finished uploading, so I'm adding the link to the OP now.

FINALLY, someone else that respects untouched firmware. Glad to see this.

The odin flooding is not working at this point.
apparently one of the features of the new odin mode (aboot?) is that once it gets the 'failed auth' it stops responding to further pushes. It does not even allow the connection to be setup until a power down and restart.
As you can see in the other thread I submitted a warranty claim and they are replacing the device: as I have no backup device and a family that needs to get in touch with me (i.e. my wife and mother scolding me for not having a phone) I ran out of time...
I still have a few days with the old device before the replacement arrives...
I any case I am off to work.

If anyone wants to help create a flashable-zip that would disable the OTA updates without touching /system, I'm working on it here:
http://forum.xda-developers.com/showthread.php?t=2379517
I just need someone to write something up in a bash script that will make modifications to a file in /data. Should work without rooting the system.

Jah0n said:
FINALLY, someone else that respects untouched firmware. Glad to see this.
Click to expand...
Click to collapse
One thing I've seen in many "stock" roms is: "Completely stock, except for this.... and this.... and this mod I made here.... and this...."
-_-

I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?

We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!

mocsab said:
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
Click to expand...
Click to collapse
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?

Jah0n said:
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
Click to expand...
Click to collapse
Awesome! If the kernel turns out alright, we could add it to the list in the OP.

Aou said:
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Click to expand...
Click to collapse
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -

mocsab said:
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
Click to expand...
Click to collapse
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!

Aou said:
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Click to expand...
Click to collapse
The kernel lies in a separate partition but twrp wipes it away by default so you'd have to unmount the boot partition
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Is boot.img a compressed file?

jortex said:
Is boot.img a compressed file?
Click to expand...
Click to collapse
I did not compress it at all. However it is not a full 10MB either. It's the exact file that came from the MF3 update package. The way that the OTA update .zip installs it is by doing this:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
If you need a full 10MB partition dump (i.e. using dd or a nandroid), I can upload those if you need them for any reason.
UPDATE: I just did a binary comparison of the boot.img that came from the OTA .zip (the one I uploaded), and a nandroid backup I made. It was 100% identical, except the nandroid was padded with zeros at the end (a couple megabytes of zeros...)

Added another kernel to the list:
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me.

Related

[ROM] HTC Magic Vodafone Spain Official Froyo 2.2.1 update aim3 [2011-05-09]

Updated 2011-05-09 (New version aim3)
So now that Vodafone Spain finally released a Froyo OTA upgrade for HTC Magic, I've built a cooked ROM from the official OTA upgrade. The ROM tries to ressemble the stock ROM, but including the following extras:
Version aim1:
/system/etc/install-recovery.sh is removed, so it won't overwrite your recovery on every boot, as the stock ROM does
This ROM is rooted. Superuser.apk is installed on system.
Included apns-conf.xml from Cyanogen, so APNs from all operators are available, not just from Vodafone.
Google applications updated to the latest release: Maps, StreetView, Gmail, Market and Youtube
Replaced keyboard with Gingerbread (Android 2.3) newer keyboard.
Removed the Vodafone Live application and shortcut
Version aim2:
Removed Gingerbread keyboard, better install as separate package if you want it (see link)
Updated Google Maps and Market to latest versions.
Include busybox, it's needed for some root applications
Deodexed (takes some time on first boot, saves space on /system)
Re-signed (needed to include STK)
Included STK (Sim-Toolkit) application ("Servicios SIM" in Spanish). Required for some virtual operatos to work in Roaming
Added Sound Recorder icon in Launcher (application was there, but only accessible from MMS when adding a sound)
Added support for scripts in /system/etc/init.d (useful for adding compcache, swap, etc).
Version aim3:
Removed the "assert shappire" line on installation script. Should allow installation on Dream/G1
Revert some re-signed packages to allow Google applications updated via Market
Load ipv6 module to have Google Goggles working
Replace stock kernel with a custom kernel for better performance and memory tweaks
Enable compcache (compressed in-RAM swap memory) on boot by default, to get some extra free MB on magic 32B, which makes the system much more usable (applications and launcher are not killed all the time). Tweaks can be customized using setprop (see later)
Overclock CPU on boot. Can be tweaked using setprop (see later)
Include support for Live Wallpapers
Please note that this ROM is only for HTC Magic 32B (not for 32A or Dream). You'll need to use the System-Only ROM and a different kernel and/or SPL for 32A or for HTC Dream.
This latest update (version aim3) includes:
Android 2.2.1 (FRG83D)
SPL (HBOOT) version 1.33.0013
Radio 2.22.28.25
Kernel 2.6.35.13 from Farmatito (http://forum.xda-developers.com/showthread.php?t=1010932)
About the SPL and Radio: This is a perfect SPL, so it won't allow you to flash unsigned images from fastboot. Please make sure you have a custom recovery image. The new 2.22.28 radio won't work with other older SPLs, but it's worth the additional RAM (15MB). Also, if you want to install another kernel, it must be compatible with this radio version.
Requeriments and pre-installation
You'll need a custom recovery that allows you to flash the update.zip file. Clockworkmod recovery or AmonRA should do the job.
Make sure you have a good battery level, and make a full backup before installing.
Disclaimer: I won't take any responsibility if this bricks or damages your device.
Upgrading
Due to resigning, you can't update from previous version. A full wipe is required, sorry. However, if you backup your data and apps with Titanium Backup, and then restore them, it should work if coming from a previous version of this ROM, or if coming from the stock versions. There are no guarantees if coming from other non-official ROMs
Installation (Two-step)
This is the way the official OTA is done. First, the HBOOT (SPL) is updated to 1.33.0013. Then, the system, kernel and radio are updated. If you want to make the installation this way:
1. SPL Update. First download http://dl.dropbox.com/u/3658919/android/vf_magic_froyo_aim1/vf_magic_frg83d_hboot_0013.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_hboot_0013.zip?dl=1) and apply update from recovery (copy to the SD Card, then choose Apply .zip from SDCard, and choose the zip file). It will reboot a few times during the upgrade. Finally it should boot the system with the previous version, but the SPL will be upgraded.
2. System+Radio+Kernel update. Download http://dl.dropbox.com/u/3658919/android/vf_magic_froyo_aim3/vf_magic_frg83d_aim3_nohboot_s.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_aim3_nohboot_s.zip?dl=1) and from recovery wipe Data and Cache. Apply update from recovery, the same way. It should reboot a few times and finally boot the system, updated to Froyo.
Installation (System-only installation)
If you already have SPL 1.33.0013 or 1.33.0013d, and radio 2.22.27.08 or 2.22.28.25, and want to install only the system files, then download http://dl.dropbox.com/u/3658919/and...m3/vf_magic_frg83d_aim3_noradio_nohboot_s.zip (Mirror: http://content.wuala.com/contents/airadier/Android/vf_magic_frg83d_aim3_noradio_nohboot_s.zip?dl=1), and apply update from Recovery.
If you have an 32A, you should be able to use the System-only installation, and when finished, flash an appropiate kernel (the included kernel is for Magic 32B).
Tweak configuration
Latest version includes some performance tweaks which are applied on boot. There's no GUI for changing these settings, but they can be easily changed using a command line (for example adb shell).
First, get a root shell (adb shell, then su). Then you can use the command:
getprop propertyname
Click to expand...
Click to collapse
to get the current value of a setting, and the command:
setprop propertyname newvalue
Click to expand...
Click to collapse
to set a new value. The available setting parameters (Replace propertyname are:
persist.tweaks.ramzenabled: Enabled (if 1) or disabled (if 0) the compressed RAM swap. If not set, it defaults to 1 (enabled).
persist.tweaks.ramzsize: The size of the compressed in RAM swap memory, in KB. If not set, it defaults to 32768 (32MB). Don't try anything higher than the amount of memory in your system. I wouldn't recommend more than 65536 (64M).
persist.tweaks.swappiness: The swappiness parameter. A avlue between 0 and 100, defaults to 10. Tells the system how agressively try to move memory pages to the swap. I keep it to a low value, so pages are not swapped until more free RAM is needed.
persist.tweaks.cpuminfreq: The minimum CPU frequency. If not set, it defaults to 245760 (245Mhz). See the list of available frequencies with command:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Click to expand...
Click to collapse
persist.tweaks.cpumaxfreq: The maximumCPU frequency. If not set, it defaults to 595200 (595Mhz). That's a bit overclocking, but I find it perfectly stable. With higher frequencies (614Mhz) I get random reboots.
persist.tweaks.cpugovernor: The CPU frequency governor. Defaults to interactive, but you can try ondemand too.
Any change will require rebooting the system. If you get stuck with a change (phone can't boot), try using adb shell from recovery, mount /data partition, and remove the offending setting file from /data/property/persist.tweaks.xxxx
Add-ons
Gingerbread keyboard is not included anymore. You can install Gingerbread keyboard along with the Froyo keyboard. See this post.
Alternative kernels: For 32A or HTC/Dream you can try with other non-stock kernels. I would recommend trying Farmatito Kernel or the latest Magic 32B kernel from ezterry, search in Doid Basement. Here is the direct link to the latest ezterry version for Magic 32B/32A
Versions and updates
aim1 - 2010/12/25 (Christmas gift) - Initial release
2010/12/27 - Added "Revert to Froyo keyboard" add-on
2010/12/27 - Added mirrors for files
2011/01/09 - Removed one-step install, seems it's not working
aim2 - 2011/05/01 - New version
aim3 - 2011/05/09 - New version
Hmm,sounds good,how about some screenshots?
But i'm a bit skeptical about the SPL and Radio flash-ing,cuz i almost once bricked my phone
Bad First Try
airadier said:
Installation (Two-step version)
This is the way the official OTA is done. First, the HBOOT (SPL) is updated to 1.33.0013. Then, the system, kernel and radio are updated. If you want to make the installation this way:
Click to expand...
Click to collapse
So after many attempts of trying to get my phone back to "factory" for OTA updates, I gave up very very late in the night and decided I'd just try this new ROM. I know I'm crazy since no one else has written of their attempts to try it - meaning I'm probably the first - and I'm a little worried at what I'm seeing. I followed your instructions for the 2-step version using Clockworkmod recovery and my right now my phone is stuck in the black loading screen that says "ANDROID". Its been on this screen for over half an hour. I'm pretty sure it shouldn't take that long so I thought I'd go ahead and ask for tips now so I can work in it tomorrow. My T-Mobile myTouch 3G original (HTC Magic 32 B) phone was on CM6 (Froyo 2.2) before I revered it to factory 1.6 because of frustrations with Cyanogen's slow mod. T-Mobile's OTA updates weren't working because of recovery image issues so I figured I'd give you version a go. Yes, I realize this is the Vodafone version. Hablo español.
So should I try to reset my phone? Take the battery out? Am I bricked?
I don't think it's bricked, it just seems to be failing to boot the system. A logcat (adb logcat command) would help to diagnose the problem.
You should be able to boot to recovery. Did you wipe data and cache partitions?
Did the previous version boot after flashing first step? You can check the SPL on this step was correctly flashed by entering fastboot (vol down + power) and checking if Hboot version is 1.33.0013
I've tried the 2 step version successfuly in 2 htc magic by now.
Let me know about any progress.
Greets.
Sent from my HTC Magic using XDA App
I can't download any chance. Can you post them in another way?
I can't download from phone neither.
Sent from my HTC Magic using XDA App
I finally download it from computer, but I can't flash it. I've got this error:
Code:
E:Failure at line 6: assert getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "saphire"
It works!
It works! Here's how...
It had been 6 hours and it was still stuck on the loading screen, so I pulled the battery.
I wipped my data and cache partitions again using the bootloading, although I'm pretty sure I had already done this. I must have needed to do it again.
The logcat seemed to have tons of errors, more than I could list here. A small copy-paste:
W/PackageManager(30347): Permission com.noshufou.android.su.RESPOND from package com.noshufou.android.su ignored: no gro
up null
I/PackageManager(30347): /system/app/TelephonyProvider.apk changed; collecting certs
D/dalvikvm(30347): GC_FOR_MALLOC freed 5701 objects / 392080 bytes in 124ms
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435ad3a8 android.uid.phone/1001}
E/PackageManager(30347): Package com.android.providers.telephony has no signatures that match those in shared user andro
id.uid.phone; ignoring!
I/PackageManager(30347): /system/app/UserDictionaryProvider.apk changed; collecting certs
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435f7a48 android.uid.shared/10010}
E/PackageManager(30347): Package com.android.providers.userdictionary has no signatures that match those in shared user
android.uid.shared; ignoring!
W/PackageManager(30347): Permission com.android.vending.CHECK_LICENSE from package com.android.vending ignored: no group
null
W/PackageManager(30347): Permission com.android.vending.BILLING from package com.android.vending ignored: no group null
I/PackageManager(30347): /system/app/VpnServices.apk changed; collecting certs
W/PackageManager(30347): Signature mismatch for shared user : SharedUserSetting{435ad158 android.uid.system/1000}
E/PackageManager(30347): Package com.android.server.vpn has no signatures that match those in shared user android.uid.sy
stem; ignoring!
Anyway, after restarting twice the phone loaded! Froyo who-hoo! And I love the Gingerbread keyboard addition! This ROM is elegant - almost official OTA with just a touch of fixes. Cyangen's ROMs are over the top for me.
The only thing we've noticed after 30 minutes of testing is that it suggests Gmail be installed in the market, even though its already installed. Obviously this is because we have the newer version of gmail. But does this mean we will no longer get updates for Google applications? This concerns me - I don't want to have to rehack my phone every month - especially since I'm giving this to my brother.
Thanks for the great work and cool simple ROM.
waffleguy4 said:
It works! Here's how...
I wipped my data and cache partitions again using the bootloading, although I'm pretty sure I had already done this. I must have needed to do it again.
The logcat seemed to have tons of errors, more than I could list here. A small copy-paste:
Click to expand...
Click to collapse
Strange. I'm quite sure a Data + Cache wipe is needed except if you're coming from stock 1.6. The errors in the logcat seem to confirm this.
waffleguy4 said:
It works! Here's how...
The only thing we've noticed after 30 minutes of testing is that it suggests Gmail be installed in the market, even though its already installed. Obviously this is because we have the newer version of gmail. But does this mean we will no longer get updates for Google applications? This concerns me - I don't want to have to rehack my phone every month - especially since I'm giving this to my brother.
Click to expand...
Click to collapse
I think you should get the updates anyways. The only difference is, instead of having Maps 4.6 in SYSTEM partition, you have 5.0. The day Maps 5.x is out, it should show an update is available. I think showing it in the market as "Installed" is the normal behavior since the google apps were extracted in Froyo, or Eclair, I can't remember
I might be adding some optional packages (as updates.zip) soon. For example, I'm thinking of adding a patched version of Google Maps to force using Vector and 3D graphics instead of bitmap tiles. Also, maybe an update to revert to the standard Froyo keyboard.
I hope you enjoy it.
jvmonjo said:
I finally download it from computer, but I can't flash it. I've got this error:
Code:
E:Failure at line 6: assert getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "saphire"
Click to expand...
Click to collapse
The update script is checking that the installed ROM device or product is "sapphire", and it's failing. Maybe the ROM you're using right now uses another device identifier?
I could remove the check, but it was included in the original updater, and I think it's safer this way. You could try flashing cyanogenmod or the stock vodafone 1.6 first, then updating.
Greets.
maverickcri said:
I can't download any chance. Can you post them in another way?
Click to expand...
Click to collapse
I've added a mirror for all files.
Greets.
I tried two step version but after successful spl update i can't boot recovery anymore:
FAILED (remote: not allow). What should I do next?
kurjak said:
I tried two step version but after successful spl update i can't boot recovery anymore:
FAILED (remote: not allow). What should I do next?
Click to expand...
Click to collapse
How are you booting recovery? Are you using "adb reboot recovery" command? If so, it looks like the perfect SPL won't allow you to run that command.
You must enter recovery by powering the phone off, and then pressing Home + Power On button. Keep pressing them until you're on recovery.
Greets.
i tried fastboot boot recovery. I tried home + power on several times but all i get is exclamation mark screen, with some kind of recovery where i can update from sd:update.zip and this also fails: verification fails
kurjak said:
i tried fastboot boot recovery. I tried home + power on several times but all i get is exclamation mark screen, with some kind of recovery where i can update from sd:update.zip and this also fails: verification fails
Click to expand...
Click to collapse
Ok, don't panic, the fix is easy. The exclamation mark screen is the stock recovery, that allows you to flash only HTC signed update.zip file. As this update is not signed by HTC, it throws the "verification fails" error.
So, how to fix it? You need to flash a custom recovery (ClockworkMod or AmonRA, for example), because the SPL won't allow you to boot the recovery from fastboot.
You need to have your current ROM rooted, if it's not already. If not rooted, check SuperOneClick Root in here: http://forum.xda-developers.com/showthread.php?t=803682
Once rooted, you can flash the recovery using flash_image command from an adb shell, or easier, install RomManager from the market and install recovery from there.
Just make sure the recovery is for Magic 32B or Dream. I think last time I used ROM Manager I choose "HTC Magic", and a recovery for Magic 32A was installed, so the recovery wouldn't boot. I discovered I had to choose "HTC Dream" instead, as the recovery for Dream works for HTC Magic 32B too.
Once installed, using the "Home + PowerOn" you should boot into the new recovery (clockwork or AmonRA), and it should allow you to flash the update. If you get "verification failed" error, check that "signature verification" is toggled off (there's an option in the recovery to enable/disable it).
I hope it hellps. Greets.
Radio Installation didnt work
i just tried this rom because CM6.1 is still to slow for me somehow.
it stopped after unpacking radio pack and tried to installe it..aborted installation.
All wiped and partitioned before.
Sry, would really like to give it a try.
Have German 32b Vodafone.
Cheers..
Hi!
I have some questions:
1. are there any differences between the Spanish 2.2.1 OTA ROM and the 2.2.1 UK ROM? What are the languages supported?
2. I come from spl 1.33.0013d and radio 2.22.27.08: what are the drawbacks of installing a perfect spl such as the 1.33.0013?
Thank you!
maxpower_303 said:
i just tried this rom because CM6.1 is still to slow for me somehow.
it stopped after unpacking radio pack and tried to installe it..aborted installation.
All wiped and partitioned before.
Sry, would really like to give it a try.
Have German 32b Vodafone.
Cheers..
Click to expand...
Click to collapse
What was the error when the installation aborted?
Puddux said:
Hi!
I have some questions:
1. are there any differences between the Spanish 2.2.1 OTA ROM and the 2.2.1 UK ROM? What are the languages supported?
2. I come from spl 1.33.0013d and radio 2.22.27.08: what are the drawbacks of installing a perfect spl such as the 1.33.0013?
Thank you!
Click to expand...
Click to collapse
1. I don't know, as I haven't checked the UK ROM, but probably they are both the same. In the spanish vodafone update there's support for english too.
2. SPL 1.33.0013d should work too. It's a modified version of 0013 to allow some additional operations. No need to install 0013. Radio 2.22.27.08 works too, but latest version, the one shipped with the vodafone update, is 2.22.28.25.
Greets.
For those who don't want to upgrade to a perfected spl (Want to stick to engineering spl) and are willing to accept the lower ram count I added ezterry's biffmod kernel/wifi module (oh and also added News and Weather app).
You can download it @ http://dl.dropbox.com/u/7812800/Android/vf_magic_frg83d_eng-signed.zip
Also if you want to use it without sim flash this after the main zip.. http://dl.dropbox.com/u/7812800/Android/Froyo_Provision.zip
Hope this helps anyone.
Btw.. Tested on Google Ion (Yes i got one lol)

[Direct Download] Latest Bootloaders & Modems

I can't keep my mirror up due to increasing need for more space with all the projects I'm working on, sorry guys.
DOWNLOAD
You can find Odin at:
https://build.nethunter.com/samsung-tools
I am no longer hosting firmware for the Note 3. fw.updato.com provides an alternative, and allows wget/curl. (with --referer="link to the download page"))
Example:
N900W8VLU2DPG1 - MTA clicked on at http://updato.com/firmware-archive-select-model?q=N900W8
Code:
wget "http://fws01.updato.com/GALAXYNOTE3/SM-N900W8/BMC/SM-N900W8_1_20160729160241_v4dg1gvbce.zip" --referer="http://updato.com/firmware-archive-select-model?record=3C39D6E6701111E69B2DFA163EE8F90B"
READ INSTRUCTIONS BELOW, OR IT WON'T STICK AFTER FLASHING!
Each zip file contains a _HOME.tar.md5 containing each flashable partition of your device. You can flash the entire tar.md5 for a complete factory restore, or you can extract individual partitions and re-tar them to make individual flashable partition files. There's a tool for tarring them here:
https://build.nethunter.com/samsung-tools/img2tar.zip
GETTING YOUR FIRMWARE TO STICK
When flashing bootloaders (BL) and modems (CP), you must cold boot your phone for the flash to succeed.
To perform a cold boot into Odin, follow these instructions carefully:
Power down your phone
Unplug any cables from your phone
Pull the back cover off and remove the battery completely
Place the battery back in your phone (there is no need to wait)
Place 1 finger on volume down key, and 1 finger on home key
While holding those keys down, place another finger on the power key
Release the finger from the power key when you feel a vibrate
Release your other fingers once you see the Odin warning screen
You may plug your phone cable back into the phone now, or after the next step
Press volume up key to enter Download mode
SOME ODIN OPTIONS EXPLAINED
Auto Reboot - Once the firmware finishes flashing, the phone will attempt to reboot into your current ROM
Re-Partition - Used to flash a PIT file over the current one. See more information below.
F. Reset Time - Enabled by default. Not entirely sure what it does yet.
Nand Erase All - May have different effects on other devices. On the Note 3, it wipes the just the userdata partition to zeros. (your ROM settings, apps, and internal storage)
Phone Bootloader Update - Doesn't seem necessary to select when flashing bootloaders from cold boot, so unsure of purpose.
Phone EFS Clear - Reformats your EFS partition. This deletes calibration data and some small caches, you will want to flash full stock ROM when using this so it can properly restore itself. It's safe to use, and won't wipe your IMEI.
I advise not touching the other options!
When flashing firmware, you can and should leave the default options selected. Confirm that it is just Auto Reboot and F. Reset Time.
RE-PARTITIONING
Re-partitioning may be necessary in the rare scenario that updating to a newer firmware requires more storage than is available in the current layout.
It is possible to back up your PIT file (partition layout) for flashing in Odin later on or sharing with others that are having trouble flashing firmware that you were able to successfully flash.
PIT files are model specific!
Do not flash a PIT file for N9005 on an N900W8 for example. The partition layout will end up pointing to the wrong locations and you'll end up with a blank IMEI / EFS partition or worse.
If you want to back up your PIT file, you must have a rooted phone or be in TWRP which is an environment already running with root privileges.
Executing these commands will back up your PIT to a file (your-device-name.pit) on your internal storage:
su
dd if=/dev/block/mmcblk0 of="/sdcard/$(getprop ro.product.name).pit" bs=16 skip=1088 count=257
You can open the PIT file in a text editor and make sure it starts with v˜4 to be ensure validity.
Restoring a PIT file is as simple as using the PIT tab in Odin and putting it in the box there, then selecting the Re-Partition checkbox in Options tab. Re-Partitioning will not delete any data, however if your PIT file varies from your previous then partition locations may point to completely different places resulting in a no longer functioning modem or worse, a bricked phone.
WIPING YOUR DATA FOR RESALE
You can use the Nand Erase All option in Odin to make your Userdata partition unrecoverable. When the Userdata partition is nand secure erased, all data on it becomes zeros.
In order for Nand Erase option to work, you need to fill an Odin slot. Flashing your bootloader in the BL slot is usually a safe method.
Most ROMs (kernel boot images actually) can't recover from this and will not boot. In order to fix this you have to boot into a recovery.
In TWRP: Go to Wipe -> Format Data -> type "yes" -> Go
In stock recovery: Use the "factory data reset" option
Both of these perform identical procedures that restore a proper format and ext4 layout to your Userdata partition.
ROMs should now be able to boot.
You can confirm through TWRP that your userdata partition has indeed been secure erased by typing in adb or terminal:
hexdump /dev/block/platform/msm_sdcc.1/by-name/userdata
It should display:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
After a few minutes it should complete. The asterisk means that hexdump found that same last row of data (0000...) repeating.
CHANGES
2016-02-26 - Add Nordic SM-N9005XX firmware N9005XXUGPOK2
2016-01-12 - Add SM-N9005XX firmware N9005XXUGBOL3 and N9005XXUGBOJ2 (modem)
2016-01-01 - Add Mexican SM-N900W8UB firmware N900W8UBU2DOL1 and N900W8UBU2DOK1 (modem)
2016-01-01 - Add T-Mobile SM-N900T firmware N900TUVUFOL1
2016-01-01 - Add Exynos SM-N900XX firmware N900XXUEBOL2
2015-12-18 - Add Exynos SM-N900UB firmware N900UBUEBOK1
2015-12-15 - Add Exynos SM-N900XX firmware N900XXUEBOK7 and N900XXUEBOK3 (modem)
2015-12-15 - Add Exynos SM-N900ZS firmware N900ZSUEBOK3 and N900XXUEBOK3 (modem)
2015-12-15 - Add SM-N9005DX firmware N9005DXUGBOK3
2015-12-15 - Add SM-N9005XX firmware N9005XXUGBOK9 and N9005XXUGBOD3 (modem)
2015-12-15 - Add SM-N9005ZS firmware N9005ZSUGOK2
2015-12-15 - Add KT Corporation SM-N900K firmware N900KKKU0GOK3 & N900KKKUGOJ4 (modem) (thanks to Freyelis)
2015-12-11 - Add SK Telecom SM-N900S firmware N900SKSU0GOK3 & N900SKSU0GOJ4 (modem)
2015-12-11 - Add LG Uplus SM-N900L firmware N900LKLU0GOK3
2015-12-02 - Add Sprint SM-N900P firmware N900PVPUEOK2
Why
fingerprinted said:
Why
Click to expand...
Click to collapse
Maybe I just wanna fit in with everybody else!!!!!!!!11
It just seems like a better idea to make all the latest modems and bootloaders for every variant easily available for people who don't want to wipe their custom ROMs or in case of emergencies.
Everything seems to be spread out among multiple threads, and some variants don't even have firmware threads.
Also this post gives me somewhere to send people to when I need it, regardless of what Note 3 variant they have!
Your profile made me chuckle, interests :single females
fingerprinted said:
Your profile made me chuckle, interests :single females
Click to expand...
Click to collapse
Its kinda look cute and honest. Btw,Thanks for a great work.
You are a very organized man, amazing work. Thank you
+1 very neat thread and you can get the files easily. Oh almost forgot to mention that your guide is very detailed.
There are numerous threads regarding Bootloader and Modems, but none as good as this .
Thanks for the effort mate, while this is supposed to be for Note 3, some information inside has a lot of stuff inside worthy of forwarding people to, pretty much a lot of general Samsung stuff explained.
:good:
EDIT: just wanted to add one thing. Sammy tends to confuse us, and we tend to inherit that confusion to other users. I.e, CP and BL are not consistently the same, we have right now K6 as a BL, but the modem seems still to be K1.
We should have a way to identify the real internals through *OUR* naming conventions.
guys
I am facing very low gsm signals after installing a custom rom
I cleaned flashed it wiping al that was needed
Anyway to check if i am using a wrong modem where i am located?
Question
I am having SM-n900k. Can I flash bootloaders from another model? I am sick of korean language in the download mode.
5.1.1 BL and CP?
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!
HazeMC said:
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!
Click to expand...
Click to collapse
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!
Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5
sajmon1983 said:
Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5
Click to expand...
Click to collapse
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)
is there any reason to update to the latest bootloader/modem?
(I use XSP firmware. haven't been able to find or make my own BL or CP files)
jcadduono said:
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)
Click to expand...
Click to collapse
I cant find the link for the differences, but apparently they do actually differ, if i'm not wrong, it has something to do with a different development tree. People have reported issues flashing non-nordic roms after the nordic ones itself, but only when the values change.
jcadduono said:
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!
Click to expand...
Click to collapse
Thanks for a very complete response!
I've realised that the front camera has the same issue recording video, so as far i understand you response, i will try to update the kernel, or try a different rom.
Thanks mate.
I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?
yes ok
jorioux said:
I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?
Click to expand...
Click to collapse
If you are on 5.0 LL you have to use DOI2

[RECOVERY]TWRP 3.1.0.0 - FIsH for FLEX 2

TWRP 3.1.0.0 with FIsH for our FLEX 2
Tested on h955 and it's still a BETA
Requirements
Here are the pre-requirements you have to met!
If you can't get them: Close this page and FORGET it (until the day you met those reqs)!
Here are the 2 simple requirements you have to met:
1. root by SuperSU >=v2.76 (greater or equal v2.76)
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
--> for many devices - if not all - this means you HAVE TO downgrade/install LL. It also means that you have to upgrade your SuperSU to this version by e.g. FlashFire if you have a lower version installed!
--> SU by phh is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> Magisk is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> I will NOT provide downgrading guides there are plenty of them so search and read.
--> I will NOT provide any guides in rooting your device
--> Before you think about downgrading to LL read about ANTI-ROLLBACK protection some devices and may have! Anti-Rollback means you CAN NOT downgrade - it would HARD-BRICK your device (wtf thinking the vendors who we are?? Is this even legal?!)! Check that before!!
2. you have to be able to disable SELinux in your booted Android
--> You do NOT need to set SELinux permanently to permissive. Just CHECK if you COULD get it MANUALLY. If you can get it OK. If not.. you obviously have not full root access but check the forums maybe there is something you can do about this.
--> I will NOT provide any guides enabling SELinux but some lines later you will see how u can execute the very simple check
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
Those above are hard facts so it may NEVER work with MM. Google has changed the way on how the boot chain will be verified and that means changes in /system will void it from now on.
If MM can get fully rooted somehow/somewhen on your device with SuperSU installed and you are able to disable SELinux the method will work there as well.
If you can not meet ALL of the above 2 requirements lay down and cry.
For the others: calm down and read on!
You can simply test those both requirements by downloading the FIsH package and execute the installer with the following test parameter:
./install.sh --check
This way nothing get installed but you will see if it would work on your device or not.
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader!
That means with TWRP-in-FIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = SOFT-BRICK)
Install a custom Kernel (this will modify boot = SOFT-BRICK)
Install a custom recovery (this will modify recovery = may SOFT-BRICK)
In short: do nothing which modifies boot or recovery partitions. Those changes will BREAK your boot signing chain.
You can of course flash everything which is modifying /system /data only (e.g. xposed, Audio mods, etc...)
You're able to backup and restore as well of course and doing any other modifications which you may can't while the Android system is running.
Download
READ THE REQUIREMENTS above before proceeding!
Then UNDERSTAND the requirements before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
READ THE LIMITATIONS above before proceeding!
Then UNDERSTAND the limitations before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
... and NEVER ask for ETA's!
if you can say:
Yes! I have read and totally understood the limitations AND the requirements!
then proceed. Otherwise read again until you got it.
Keep in mind that this is a HACK. It may soft-brick your device. you have been warned!
The concept is the same for all models but again no guarantees here for anything.
There is ALWAYS a risk and you should better backup what you do not want to loose before starting downloading this.
Download
Installation (Linux)
You can just install any newer version over an old one.
boot Android and connect USB cable
download the newest version to your PC and open a terminal in that directory
tar xzf TWRP-in-FIsH*.tgz
cd android_FIsH
./install.sh
check the output of that script. you should not see any errors there (hopefully)
Installation (Windows)
use FWUL or be patient.. maybe i or someone else release an installer... maybe...
First run (no PC required)
This FIsH gets installed PERMANENTLY! That means:
You can boot up TWRP the same way as described here again without re-installing.
If you re-install your STOCK image you have to re-install TWRPinFIsH as well.
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH has done it's job well!
This is a good time to do a full backup isn't it ? Manually mount the SYSTEM partition as it gets not auto mounted atm and do a full backup
reboot from here (safely ignore the msg "no OS installed" and reboot anyways) and you should see Android booting (hopefully ... if not see bottom)
Daily Usage (no PC required)
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH is doing it's job still very well
AGAIN: keep your mind up! You HAVE to ensure that whatever you do and whatever you flash -> NEVER TOUCH BOOT/RECOVERY! If you flash a ZIP ensure first that it do not modify them! Otherwise you WILL softbrick. You have been warned (several times now)
Trouble / Bootloop fix
if you encounter a bootloop (should never happen but who knows) you have 3 choices at least:
Option 1a: (TWRP-Bootloop) Within TWRP open Advanced -> File Manager -> Goto: /system/su.d and click "select" button -> Delete
Option 1b: (TWRP-Bootloop) From your PC: adb shell rm -rf /system/su.d/
Important: Catch the fish log (see next topic)
Option 2 (this works also for a bootloop without twrp): boot into download mode and use LGLaf to get a shell
then:
setenforce 0 <-- if that doesn't work you may have to do a FULL restore to stock
mount -oremount,rw /system
rm -rf /system/su.d/
reboot. You are out of the bootloop.
Important: Catch the fish log (see next topic)
Option 3: Last resort: Reflash STOCK. sorry.. there is always a risk..
Catch the FIsH logs
when in TWRP (or other ramdisk providing adb shell):
adb shell "cat /cache/fish/fish.log"
adb shell "cat /tmp/recovery.log"
OR - when in Android:
adb shell "su -c cat /cache/fish/fish.log"
adb shell "su -c cat /cache/fish/fish.log.old"
adb shell "su -c tar cvzf recoverylogs.tgz /cache/recovery"
adb pull recoverylogs.tgz
Upload the output to https://paste.omnirom.org and paste the link in the IRC channel (see next topic)
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support here only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you will be asked for a server network choose: freenode
Known issues (may never get fixed)
Due to the fact that FIsH is a BRUTAL hijack of the booting process several things may not work as expected.
This will normally not harm anything but you have to know about.
ZIP / ROM flashing:
omg really you wanna hear that again? OK: DON'T TOUCH BOOT / RECOVERY. And you be safe.
When you try to install a ROM it will modify at least BOOT. That means soft-brick!
When you try to install a custom Kernel.. omg really? It will definitively SOFT-BRICK! Maybe you should read the limitations again??
When you try to install a ZIP like xposed, supersu, Vipermod and others ensure that those are not modifying BOOT or RECOVERY partitions. For those mentioned it would be very unlikely but who knows.
FIRMWARE partition:
cannot be mounted - even not manually. You have to live with it.
Double Tap to wakeup (in TWRP):
Unfortunately this cannot work in TWRP-in-FIsH due to the nature of this hijack. You have to live with it.
Credits (without them - no FIsH!!!)
If you feel that someone / you is missing on this list lemme know!
Chainfire for SuperSU! This is the main part of FIsH.
TeamWin for TWRP
@cray_Doze, @dssmex, @Aaahh and @KeiranFTW for their hijack implementations (e.g. https://forum.xda-developers.com/showthread.php?t=2608408, first steps to a G4 hijack)
steadfasterX for the android FIsH !
Here is the h955 device tree for building TWRP with omnirom minimal sources - https://github.com/jarno83/android_device_lge_h955
Here are TWRP logs from backups and restoring if anyone interested - https://github.com/jarno83/twrp_logs
Changelog
29.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA3.zip
Latest FIsH source code and fixes.
3.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA2.zip
Fixed the RESTORE issue - thanks to SteadfasterX
Used latest FIsH source code.
Went to zip format, now a pit smaller.
2.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL.tar.gz
The fishfood is TWRP 3.1.0.0 it uses 15c stock kernel for now. And has a problem with restoring.
What is TESTED
BACKUP and RESTORING /system and /data partitions - OK
Xposed V87 - flashes ok with twrp and works - http://dl-xda.xposed.info/framework/sdk22/arm64/
Tested Device List
H955 running 5.1.1 15c ROM
H950 running 5.1.1 PR ROM - thanks to iDefalt
Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok, thanks Didn't saw that
So anyone tested it yet ? TWRP booting ?
I have my phone in repair center atm cant test anything.
Yes, I have it on my h955 and twrp boots fine. I tested system backup and restore, now working. Flashed xposed also ?
Sent from my LG-H955 using XDA-Developers Legacy app
/data backuped and restored with success ?
Sent from my LG-H955 using XDA-Developers Legacy app
Ok so now what? What is the next step? On road To install custom rom or custom kernel.
dadaa1 said:
Ok so now what? What is the next step? On road To install custom rom or custom kernel.
Click to expand...
Click to collapse
SteadfasterX is developing some stuff... so maybe on day we will have a possibility to use full custom roms.
But for now we have a custom recovery
If someone is willing to cook something interesting that can work with not touching the boot or recovery partitions... then well I would call it a custom rom
In theory it should work on a H950PR? So I can at least test it
maucvs said:
In theory it should work on a H950PR? So I can at least test it
Click to expand...
Click to collapse
Hi, I think it will work. You'll need to be rooted and You can give it a try ?
Sent from my LG-H955 using XDA-Developers Legacy app
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Seams like the twrp I build is not liking h950
Sent from my LG-H955 using XDA-Developers Legacy app
I'll try to make h950 tree and build a test twrp.
Sent from my LG-H955 using XDA-Developers Legacy app
adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Can you test this... made a h950 test tree. The twrp boots on my h955 also.
ergo911 said:
Seams like the twrp I build is not liking h950
Click to expand...
Click to collapse
I had a similar issue for the g4 and here it was FIsH because it was too slow for some devices . I will release a new FIsH release which improves speed dramatically asap.
.
Sent from my LG-H815 using XDA Labs
Thanks ?
ergo911 said:
Thanks ?
Click to expand...
Click to collapse
Ok so please use git pull to get the latest updates!
Lemme know if you have any trouble.
.
Sent from my LG-H815 using XDA Labs
ergo911 said:
Can you test this... made a h950 test tree. The twrp boots on my h955 also.
Click to expand...
Click to collapse
Works like a charm on my H950. Thanks! The only issue is TWRP booting time, but it's should be right that, if I understand correctly.
Thank you!

[Patch] Persistent automatic disabling SELinux in any kernel

Warning: SELinux – important security feature.
After disabling it you obliviously make Android less secure. Use it on your own risk.
Why it needed?
SELinux can prevent work some mods, like Viper. Or you can have own reasons.
Executing in Terminal "setenforce 0" or via scripts / apps turns SELinux off only after booting: this is not good.
This solution disables SELinux directly in kernel.
Compatible with any MIUI or custom ROM.
How it works
After flashing ZIP creates kernel dump, then it repacks with new command line androidboot.selinux=permissive and writes back.
Into /system/bin copied script.sh and two binaries: mkbootimg and unpackbootimg plus auto-restore script (addon.d)
Last required for keeping and launching that files at every ROM update. This works only on custom ROM's, on MIUI you need re-apply patch manually.
Note: on previous phone at some rare unknown conditions after updating ROM kernel repackaging ended with error and device can't boot.
In this case enter recovery and restore boot from backup or flash boot.img from ROM via fastboot / TWRP.
How to install
1. Once flash attached ZIP
2. Then flash required mods
How to delete
1. Delete file /system/addon.d/99-selinux.sh (and other, that belong to mods that not work with SELinux)
2. Flash current ROM
P.S. This patch probably will work on any device (at least with custom ROM because stock kernel can use different structure).
Rare, but may be required change path to boot partition in script.sh: /dev/block/bootdevice/by-name/boot, twice.
Hi does this method still work in Android 10 and newer?
Great job. This is exactly what I was searching for!
lebigmac said:
does this method still work in Android 10 and newer?
Click to expand...
Click to collapse
Very likely, don't know for sure because still on Pie. Try yourself and share result
When I run this command:
Code:
cat /proc/cmdline
I get this result:
Code:
BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=XXXXX-XXXX-XXXX-XXXX-XXXXXXXXX ro quiet splash vt.handoff=1
Maybe in Android 10 and newer they moved the androidboot.selinux=permissive parameter to somewhere else kind of like how they moved the system partition into the super image?
lebigmac said:
Maybe in Android 10 and newer they moved parameter to somewhere else
Click to expand...
Click to collapse
Parameter not present by default.
It's not clear if you tried to flash ZIP. If yes and got no result: probably script can't handle changes in boot.img structure because it was created 4 years ago. Try some tool on PC to unpack boot and add line manually.

[PX5][Android 10] Patched recovery

This is the Android 10 recovery image by HCT (version 10.3.1) patched to skip signature checking on .zip files
Tested on MTCE_LM (Eunavi). Use at your own risk
It can be flashed from a root shell (either adb or via terminal emulator) by performing the following steps
1. upload recovery via adb
Code:
adb push hct_recovery_patched.img /sdcard/
2. flash recovery
Code:
# backup current recovery
dd if=/dev/block/by-name/recovery of=/sdcard/recovery_backup.img
# write new recovery
dd if=/sdcard/hct_recovery_patched.img of=/dev/block/by-name/recovery
NOTE: If you do not disable the "flash_recovery" service in /init.rc, AND you have a stock kernel, recovery will be restored to the original version after rebooting.
There are 3 ways to avoid this:
- Flash magisk (or a modified kernel) while in recovery. The patch will then fail to apply and recovery won't be overwritten
- Disable "flash_recovery" by doing "adb remount" and editing /init.rc (comment out the following)
Code:
service flash_recovery /system/bin/install-recovery.sh
class main
oneshot
- Neuter the service by either:
- removing /system/bin/install-recovery.sh​- replacing /system/bin/install-recovery.sh with a dummy script​- removing /system/recovery-from-boot.p​
Woo-hoo, after hundreds of rubbish posts in the MTCD forums, we have a real development post!
Great work and thanks for sharing this, these forums need more like you.
Thanks for the kind comment!
I have to admit that it was frustrating to see the lack of information sharing on this forum, and the pervasive pay-per-use model.
I spent a lot of time just getting Android 10 installed (starting from Android 9), and i had to bring the head unit to my desk as working in the car was rather hard and all i achieved was a brick.
I unfortunately had to bring it back in the car now (can't sit on my desk forever) but, now that i figured out how to make bootable recoveries, i was wondering how hard it could be to have TWRP or at least a hassle-free recovery to install Android 10 from Android 9.
As a first step, this recovery makes it possible to install Magisk or other zip files without doing it manually within adb.
Cheers!
Your work is really good!
Thanks a lot for it.
Now you can also modify ROM's without signatur errors when installing.
Wouldn't it be good if we had an app like the ModInstaller ?
So a one click installation of the recovery without shell or adb.
I have now built an app.
And now need help.
Namely, in the app is the recovery and the script.
Unfortunately, the flash process is not started.
It always comes only the first message from the script.
The app is open source and the script and the recovery are in res/raw.
In the attach you will find the finished app and pictures.
If someone has a solution, he can write me or make a pull request on Github.
Source code:
GitHub - jamal2362/RK33XX-Custom-Recovery-Installer: Application for flashing custom recovery on Rockchip Android Head-Units.
Application for flashing custom recovery on Rockchip Android Head-Units. - GitHub - jamal2362/RK33XX-Custom-Recovery-Installer: Application for flashing custom recovery on Rockchip Android Head-Units.
github.com
The script:
RK33XX-Custom-Recovery-Installer/script at master · jamal2362/RK33XX-Custom-Recovery-Installer
Application for flashing custom recovery on Rockchip Android Head-Units. - RK33XX-Custom-Recovery-Installer/script at master · jamal2362/RK33XX-Custom-Recovery-Installer
github.com
First of all, congrats for the work!
DISCLAIMER:
I don't own ModInstaller, i have never bought a copy of it and i don't intend to do so.
Analysis is purely done from Youtube videos, open source code analysis and existing and openly available binary images.
I was working to figure out how to make a FLOSS alternative to ModInstaller.
The issues i found in all my attempts are the following:
- A6 recovery is the only one that can boot from SD Card (which can then be used to flash A9 -> A10 with the 2SD trick)
- (it took me a long time to pull these information together and unbrick my unit)​- The A6 recovery is unable to directly flash A10 RKAF/RKFW images (sdupdate.img) due to the code being too old
- a failure will be observed while writing super.img. This happens because the device needs to be repartitioned, and the A6 recovery is not doing it correctly​- A9 recovery is buggy. Booting it with no system installed will result in a black screen.
- it will only boot succesfully after being written by the A6 flash tool, which writes the "misc" partition with the recovery commands to run (the "hint" i get from this is that the misc partition is important)​- A10 recovery can't be loaded by the A6 recovery. I always got a black screen after flash. Is it a flash issue? is it an issue with the recovery itself? hard to know
Theory: maybe the recovery could be written over the kernel partition? ("boot")
This way, the recovery will always run after being flashed instead of requiring an explicit "enter recovery" trigger (buttons, misc partition, etc.)
Besides these experiments, in parallel, i did some bug fixing to this repository: https://github.com/liftoff-sr/rockchip-tool/commits/master (i'm "smx-smx")
That allows me to unpack nad repack "sdupdate.img" , "reduced recovery images" and "full IMG files".
With those tools. i tried to swap "recovery.img" in the A6 image, but i always got the black screen upon booting from SD.
Either A9/A10 breaks sdboot or the bootloader crashes before it gets there.
Since this also happens when being flashed, this could either be a bug in the flashing program or a bug in the boot stack (which fails to run recovery perhaps due to a dirty state of the internal flash). It's hard to know for sure without having a UART connection with the board.
BUT, we have an alternative, in the form of the recovery built-in ISP flash tool.
This is the code that reads "sdupdate.img" from the SD Card and flashes it
After reading the recovery source code, i realised that this code can only be triggered correctly when booting from the SD card.
It detects this state by reading /proc/cmdline and probing for specific values (https://github.com/rockchip-android...6f72b7d3123dab27135ac41d55029/sdboot.cpp#L206)
This means the bootloader can (and will) pass those arguments under specific conditions (https://github.com/rockchip-linux/u...c873f178c/arch/arm/mach-rockchip/board.c#L358)
If you check here https://github.com/rockchip-linux/u...3f178c/arch/arm/mach-rockchip/boot_mode.c#L47 you can see the magic word that needs to be written to the "misc" partition in order to trigger that code.
Note that, besides the well known "sdboot", "usbboot" is also possible.
I'm not sure if the ROM can physically boot from USB, but the bootloader and recovery do support (according to code) passing the flag to enable flashing from USB.
So, recapping, there are these ways we can try:
a - try to overwrite "boot" with "recovery" (but it might not work due to the partitioning layout, e.g. jumping from A6 -> A10)
- note: uboot might also need to be written when doing this.
b - making a modified "sdupdate.img" that flashes recovery on top of boot, and all the other core partitions like "misc", "uboot", "trust", "vbmeta"
c - writing "misc" from android in order to triggers the "rkfwupdate" mode
d - taking a dump of the first portion of the flash in various states (A6, A8, A9, A10), and having a "dd" that writes it back to the beginning of the flash (i suspect this is how ModInstaller does it)
Considering cases "b" and "c" depend on a recovery that can write them correctly (and the A6 one is buggy), this leaves us with "a" and "d"
Considering that ModInstaller does it in one shot, and doesn't seem to matter about the partitioning layout, i believe "d" might be the most viable option...
Using the "rockchip-tool" repository i linked from github, the partition table can be dumped from any .img file
You can observe "Image/parameter.txt" from the extracted firmware
This is the partition table from A6's recovery:
[email protected](uboot)
[email protected](trust)
[email protected](misc)
[email protected](resource)
[email protected](kernel)
[email protected](dtb)
[email protected](dtbo)
[email protected](vbmeta)
[email protected](boot)
[email protected](recovery)
[email protected](backup)
[email protected](security)
[email protected](cache)
[email protected](system)
[email protected](metadata)
[email protected](vendor)
[email protected](oem)
[email protected](frp)
[email protected](userdata)
And this is the partition table from A9's recovery
[email protected](uboot)
[email protected](trust)
[email protected](misc)
[email protected](resource)
[email protected](kernel)
[email protected](dtb)
[email protected](dtbo)
[email protected](vbmeta)
[email protected](boot)
[email protected](recovery)
[email protected](backup)
[email protected](security)
[email protected](cache)
[email protected](system)
[email protected](metadata)
[email protected](vendor)
[email protected](oem)
[email protected](frp)
[email protected](userdata)
Notice how uboot, trust, misc, resource, kernel, dtb, and others live in the same space. (2000, 4000, 6000, 8000, 10000, ...)
What we could do is create a raw blob that spans that address range, and "dd" it directly to /dev/mmcblk0 at the right offset.
So i would focus on converting recovery images to raw blobs, with recovery-as-kernel so it boots straight away on the first try.
Bump a real thread.
Is it possible to convert it to a file installed by SDDiskTool?
marchnz said:
Bump a real thread.
Click to expand...
Click to collapse
I created a flashing tool to flash recovery within Android, using Rockchip's own code: https://forum.xda-developers.com/t/...chip-firmware-flash-tool-for-android.4458299/
blala said:
I created a flashing tool to flash recovery within Android, using Rockchip's own code: https://forum.xda-developers.com/t/...chip-firmware-flash-tool-for-android.4458299/
Click to expand...
Click to collapse
This file hct_recovery.patched.img does not appear to be installed via rkupdate
sadaghiani said:
Is it possible to convert it to a file installed by SDDiskTool?
Click to expand...
Click to collapse
It needs to be converted, yes
I'll take a look this afternoon
blala said:
It needs to be converted, yes
I'll take a look this afternoon
Click to expand...
Click to collapse
Is it possible to create a boot image that includes moded recovery & magisk and moded kernel ?
If by image you mean firmware image then yes, it can be done with https://github.com/liftoff-sr/rockchip-tool
But what i would recommend is the modded recovery only, with the magisk .zip to use in Recovery
Otherwise you risk flashing a kernel that doesn't match with kernel modules or is otherwise not fully compatible with the installed system
blala said:
If by image you mean firmware image then yes, it can be done with https://github.com/liftoff-sr/rockchip-tool
But what i would recommend is the modded recovery only, with the magisk .zip to use in Recovery
Otherwise you risk flashing a kernel that doesn't match with kernel modules or is otherwise not fully compatible with the installed system
Click to expand...
Click to collapse
boot.img file included recovery+magisk+kernel
Flashing a boot.img (Kernel, for example) in an Android mobile phone via adb shell
Flashing a boot.img (Kernel, for example) in an Android mobile phone via adb shell - script.sh
gist.github.com
MTCD has separate boot and recovery partitions.
Perhaps you can adapt both recovery/kernel to be in the same image but the bootloader won't know about that (and will always boot from "recovery" partition)

Categories

Resources