Database Info

[Q] Go back to stock kernel?

Hi all
I have been experimenting with Bricked and faux123 kernels but I've had terrible stability with both of them.
Now I want to go back to stock kernel but I'm unable to find it, is it available somewhere?
An alternative is of course to flash an entire RUU but if that's not necessary I'd like to avoid it. Also my nand-backup is now a bit out of date so I don't want to go back to that either.
The phone is original HTC Sensation w/ SW 1.45.401.3.
Thanks

Konstigt said:
Hi all
I have been experimenting with Bricked and faux123 kernels but I've had terrible stability with both of them.
Now I want to go back to stock kernel but I'm unable to find it, is it available somewhere?
An alternative is of course to flash an entire RUU but if that's not necessary I'd like to avoid it. Also my nand-backup is now a bit out of date so I don't want to go back to that either.
The phone is original HTC Sensation w/ SW 1.45.401.3.
Thanks
Click to expand...
Click to collapse
Extract rom from original RUU first. Then you can extract boot.img from rom package.

I suppose you don't have backup with original kernel?
I think the best way is to find custom ROM based on this RUU and look into adoons section. Very often stock kernel is provided by ROM author.

Insomnis said:
I suppose you don't have backup with original kernel?
I think the best way is to find custom ROM based on this RUU and look into adoons section. Very often stock kernel is provided by ROM author.
Click to expand...
Click to collapse
I have a nandroid backup. I looked around in it but was unable to find the kernel. The most interesting file was boot.img (16MB) but I could not find how to open that image-file.
I looked at Bricked/faux123 threads but could not find the stock kernel there.

Aha, is boot.img the image that I should flash?
Then I will try do do that with fastboot..

Yep boot.img has kernel & ramdisk

Fuses said:
Yep boot.img has kernel & ramdisk
Click to expand...
Click to collapse
It was the file size that tricked me... 16MB compared to ~ 3-4MB for just zImage. But I guess it's the ramdisk that adds on size.

nandroid backup has done so called raw backup from boot partition. If you extract that 16 MB partition dump, you propably get ~3.5MB zimage and ~1 MB ramdisk.

Fuses said:
nandroid backup has done so called raw backup from boot partition. If you extract that 16 MB partition dump, you propably get ~3.5MB zimage and ~1 MB ramdisk.
Click to expand...
Click to collapse
Aha... thanks for setting me straight.

I did this operation today. Did the restore via fastboot (./fastboot flash boot.img) but after that I had one problem, no WiFi.
I remembered that I'd seen a bcm4329.ko in the custom kernel zip's so I also replaced that from a nandroid-backup (first went to recovery, then adb shell).
Now also WiFi worked.
/system/lib/modules # ls -al
drwxr-xr-x 2 root root 4096 Mar 3 12:18 .
drwxr-xr-x 8 root root 12288 Oct 6 18:54 ..
-rwxrwxrwx 1 root root 278688 Mar 3 12:18 bcm4329.ko <-- Stock module
-rw-r--r-- 1 root root 279875 Aug 1 2008 bcm4329.custom <-- Included with faux123 kernel, now renamed by me
-rwxrwxrwx 1 root root 154871 Mar 3 12:18 kineto_gan.ko <-- Some other module which was present in the nandroid-backup which I also restored

Konstigt said:
I did this operation today. Did the restore via fastboot (./fastboot flash boot.img) but after that I had one problem, no WiFi.
I remembered that I'd seen a bcm4329.ko in the custom kernel zip's so I also replaced that from a nandroid-backup (first went to recovery, then adb shell).
Now also WiFi worked.
/system/lib/modules # ls -al
drwxr-xr-x 2 root root 4096 Mar 3 12:18 .
drwxr-xr-x 8 root root 12288 Oct 6 18:54 ..
-rwxrwxrwx 1 root root 278688 Mar 3 12:18 bcm4329.ko <-- Stock module
-rw-r--r-- 1 root root 279875 Aug 1 2008 bcm4329.custom <-- Included with faux123 kernel, now renamed by me
-rwxrwxrwx 1 root root 154871 Mar 3 12:18 kineto_gan.ko <-- Some other module which was present in the nandroid-backup which I also restored
Click to expand...
Click to collapse
Me too. please guide me . Thaks

Custom Recovery for rooted 6th Gen Fire HD 8 Tablets? (Exploratory Discussion)

I was just wondering if the partition structure on the 5th gen fire hd tablet was the same as the 6th gen.
Looked at
HTML:
https://developer.amazon.com/public/solutions/devices/kindle-fire/specifications/01-device-and-feature-specifications
to compare hardware. It does bear same chipset manufacture as Fire HD 6 (2014)<KFARWI>,Fire HD 10 (2015)<KFTBWI>, and Fire (2015)<KFFOWI>, so maybe they retain the same partitioning structure/scheme, which would be nice. Now that root is possible, can anyone advise if they have had any luck with flashing a custom recovery. I was about to cancel this post because I realize the bootloader is locked. However I was wondering if this might provide some pathways: https://forum.xda-developers.com/fire-hd/development/bootloader-unlock-t3129630 and apply to the 6th gen unit.
Food for thought. I might try it and see what happens. Unless someone more braver than me wants to try it, please advise. I'll look into it later.
TWRP on this would be sweet.
I did run this real quick:
Code:
C:\dump\adt-bundle\sdk\platform-tools>adb shell
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 79688 loop0
179 0 15388672 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 500 mmcblk0p6
179 7 16268 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 6144 mmcblk0p9
179 10 512 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 40320 mmcblk0p16
179 17 1024 mmcblk0p17
179 18 1024 mmcblk0p18
179 19 1653024 mmcblk0p19
179 20 434176 mmcblk0p20
179 21 512 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 4320 mmcblk0p23
179 24 13138927 mmcblk0p24
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 33 2 mmcblk0boot0p1
179 34 2 mmcblk0boot0p2
179 35 256 mmcblk0boot0p3
179 36 747 mmcblk0boot0p4
[email protected]:/ #
15388672 mmcblk0 might be the recovery partition as noted from that other thread linked above.
eh...scratch that..i guess based on older rsa bug which later fire OS fixed. oh well.might still try it though since have more powerful permissions now (su).

For Reference <or enlightenment>
MT8163
CPU ISA CPU CPU cache GPU Memory technology Wireless radio technologies Released
ARMv8 1.3 GHz quad-core ARM Cortex-A53 Mali-T720 MP2 @ 520 MHz Wi-Fi, Bluetooth, FM, GPS Q2 2015
Acer B3-A20-K8UH
BQ Aquaris M10
Asus ZenPad 10 (Z300M)
Asus ZenPad 8.0 (Z380M)
Amazon Fire HD (6th generation)
from: https://en.wikipedia.org/wiki/List_of_devices_using_Mediatek_tablet_processors
https://www.asus.com/zentalk/thread-88877-1-1.html
https://forum.xda-developers.com/android/general/guide-bq-aquaris-m10-freezerhd-twrp-root-t3523833
I found bootimg.exe and extracted the boot.img from the .bin file to take a peek...but I think if any changes were made and file recreated and flashed over would presumably fail due to locked bootloader. Not sure if this unit is unlocked, just had the same chipset..I dunno.Just looking at things.lol.

smokejumper76 said:
For Reference <or enlightenment>
MT8163
CPU ISA CPU CPU cache GPU Memory technology Wireless radio technologies Released
ARMv8 1.3 GHz quad-core ARM Cortex-A53 Mali-T720 MP2 @ 520 MHz Wi-Fi, Bluetooth, FM, GPS Q2 2015
Acer B3-A20-K8UH
BQ Aquaris M10
Asus ZenPad 10 (Z300M)
Asus ZenPad 8.0 (Z380M)
Amazon Fire HD (6th generation)
from: https://en.wikipedia.org/wiki/List_of_devices_using_Mediatek_tablet_processors
https://www.asus.com/zentalk/thread-88877-1-1.html
https://forum.xda-developers.com/android/general/guide-bq-aquaris-m10-freezerhd-twrp-root-t3523833
I found bootimg.exe and extracted the boot.img from the .bin file to take a peek...but I think if any changes were made and file recreated and flashed over would presumably fail due to locked bootloader. Not sure if this unit is unlocked, just had the same chipset..I dunno.Just looking at things.lol.
Click to expand...
Click to collapse
I'm thinking it's definitely locked. I ran a few commands from adb while in fastboot mode and always get back that the commands aren't allowed on locked hw.

unlock
try fastboot getvar all
it will shows an unlock_code

emas73 said:
try fastboot getvar all
it will shows an unlock_code
Click to expand...
Click to collapse
yes. However, is this the public key? They (mediatek <chipset manufacture SOC>/amazon <brand name>/quanta computer <the actual manufacturer> might use 2 key firmware signing. So, they will have a master private (secret) key. and each device has a generated public key unique to each device. Those 2 keys get crypto'd together to sign the firmware/bootloader. So, as a result only firmware signed by the master key can be loaded on the device. I can be totally wrong. But the more people asking questions, researching, arguing (lol), etc., the closer we may get to trying to find a way to unlock the bootloader. I hope a way will be found. I will give the first person to find a way a big shinny nickel (I'm a cheap bastard).

Under developer options is a setting called OEM unlocking.
I tried enabling it, but it will not stick.
I wonder where this is located in the code...
Sent from my KFGIWI using Tapatalk

I don't have this tablet, but I have the Asus Z380M (same chipset). I was just wondering, has anyone even tried to build and flash a custom recovery onto this device? We just made a TWRP build for the Z380M and it boots and works perfectly. Best part: you don't even have to unlock the bootloader! Everyone's just assuming that a locked bootloader will refuse to boot unofficial images. But has this been tested? It should at least be able to boot self-signed images. Since you have root already, it shouldn't be too hard to flash a recovery. See this thread here for some information that might help you. There's even a method to flash stuff onto a locked MediaTek device from a PC that might work for this Fire HD.

diplomatic said:
I don't have this tablet, but I have the Asus Z380M (same chipset). I was just wondering, has anyone even tried to build and flash a custom recovery onto this device? We just made a TWRP build for the Z380M and it boots and works perfectly. Best part: you don't even have to unlock the bootloader! Everyone's just assuming that a locked bootloader will refuse to boot unofficial images. But has this been tested? It should at least be able to boot self-signed images. Since you have root already, it shouldn't be too hard to flash a recovery. See this thread here for some information that might help you. There's even a method to flash stuff onto a locked MediaTek device from a PC that might work for this Fire HD.
Click to expand...
Click to collapse
You win the internet today! I looked at that thread:
https://forum.xda-developers.com/android/development/twrp-custom-recovery-asus-zenpad-8-0-t3588765
You need a scatter file (partition structure file) for the particular device. However making a scatter seems to be pretty easy <and i wouldn't be surprised if the partition structure is somewhat similar due to being same the same chipset..but I'd rather have one for the actual device..lol> I'm sure there is a thread here on XDA too on how to make a scatter file. Then just apply those instructions to that that zenpad thread. Very interesting indeed!
:
https://androidmtk.com/create-scatter-file-for-mtk-devices
So, maybe this is theoretically possible. I might try it, but someone else I'm sure will beat me to it (hint hint)...<and maybe do a write up>. I'll hmm and haw and look into it. Good work!

diplomatic said:
I don't have this tablet, but I have the Asus Z380M (same chipset). I was just wondering, has anyone even tried to build and flash a custom recovery onto this device? We just made a TWRP build for the Z380M and it boots and works perfectly. Best part: you don't even have to unlock the bootloader! Everyone's just assuming that a locked bootloader will refuse to boot unofficial images. But has this been tested? It should at least be able to boot self-signed images. Since you have root already, it shouldn't be too hard to flash a recovery. See this thread here for some information that might help you. There's even a method to flash stuff onto a locked MediaTek device from a PC that might work for this Fire HD.
Click to expand...
Click to collapse
So I tried creating a scatter file, but I'm not having much luck. I don't think MTK Droid Tools works with later MediaTek Chipsets like the mt8163.
It brings up the following info when I load it up USB debugging enabled and phone connected and device shows up via "adb devices" command:
Code:
Hardware : MT8163
Model : KFGIWI
Build number : LVY48F
Build date UTC : 20160918-002858
Android v : 5.1.1
Baseband v: -----
Kernel v : 3.18.19-g9fc382b ([email protected]) (gcc version 4.9 20140514 (prerelease) (GCC) ) #1 SMP Sun Sep 18 00:32:41 UTC 2016
But clicking on the "Blocks Map" button just shows
Code:
bmtpool scatter/00000000 byte size 0
And that's it.
Then, I tried to "manually" create it. In an ADB shell there are tutorials that show you to issue the command:
Code:
cat /proc/mtd
but I don't get anything:
Code:
[email protected]:/ $ cat /proc/mtd
dev: size erasesize name
Tried it via su and same thing. Any ideas?

Wait, before you bother with creating the scatter file and what not, have you checked to see if your tablet exposes the MediaTek USB interface that Flashtool can use? When you plug in the USB cable with the tablet powered off, do you get a Mediatek Preloader USB VCOM device (VID 0E8D, PID 2000) on your PC? What about when you hold the volume up or volume down as you plug in? Do you see a Mediatek USB Port (VID 0E8D, PID 0003)? If you get the first one, that's good. If you get the latter one, that's very good, because that's the boot ROM that's built into the SoC. It's independent of any code on the EMMC, so may be able to flash stuff even to a bricked unit.
When I made the scatter file for the Z380M, I did it the cowboy way. The droid tools didn't work for me either, of course. All the information you need to make the scatter file is already on the GPT. You just need to read back the first few sectors of the "disk" and save it on your computer. Then use your favorite hex editor and a hex calculator to crunch the LBA numbers into partition addresses and sizes. This is the information that every scatter file boils down to.
I believe you don't need to have an accurate scatter file to read back data. You can start with the one from the Z380M, and then see if you can read back anything with SP Flash Tool. At the same time, you can check if your tablet exposes the low-level USB interfaces.
But if you already have root, why don't you just try to build a recovery for your device and flash it with Busybox/dd? I mean, I don't think there's anything that SP Flash Tool can do for you that you can't already do with a root shell...except to serve as an emergency flashing option. That was kind of the point of my last post.

smokejumper76 said:
You need a scatter file (partition structure file) for the particular device. However making a scatter seems to be pretty easy <and i wouldn't be surprised if the partition structure is somewhat similar due to being same the same chipset..but I'd rather have one for the actual device..lol> I'm sure there is a thread here on XDA too on how to make a scatter file. Then just apply those instructions to that that zenpad thread. Very interesting indeed!
Click to expand...
Click to collapse
Did you or anyone else ever get anywhere with this? I didn't mean to say you have to do it all yourself. I can help you build the scatter file, etc. if you send me the GPT (i.e. first 4KB or so of mmcblk0).

diplomatic said:
Did you or anyone else ever get anywhere with this? I didn't mean to say you have to do it all yourself. I can help you build the scatter file, etc. if you send me the GPT (i.e. first 4KB or so of mmcblk0).
Click to expand...
Click to collapse
So far as I know, it's not possible to make a scatter file for the HD 8...at least not possible for UNROOTED ones. Amazon has several security and locking features in place which lock that information on the other side of the bootloader. So programs such as MTK Droid Tools, won't be able to read the code to create a scatter file. Unfortunately this is the case with nearly every phone with a locked bootloader, unless your provider or manufacturer allows it to be unlocked through official channels.
Looking on the deepweb I've seen posts in forums in China (where a significant portion of one click rooting software comes from) and there is supposedly exploits for the newest MTXXXX's, but I have yet to find anything. There are very few exploits for the MT8XXX types. Most exploits are for the MT6XXX types.

DragonFire1024 said:
So far as I know, it's not possible to make a scatter file for the HD 8...at least not possible for UNROOTED ones. Amazon has several security and locking features in place which lock that information on the other side of the bootloader. So programs such as MTK Droid Tools, won't be able to read the code to create a scatter file. Unfortunately this is the case with nearly every phone with a locked bootloader, unless your provider or manufacturer allows it to be unlocked through official channels.
Click to expand...
Click to collapse
Well, I'm talking about creating the scatter file manually, like I did for my locked/unrooted Asus ZenPad 8.0. No root tools or any special apps necessary. I'm not sure you understand what a scatter file contains. It is simply the partition layout of the device's flash memory and some parameters of each partition relevant to SP Flash Tool. If you have root and busybox you already have everything you need to make one. Just read back the GPT (dd if=/dev/block/mmcblk0 of=gpt.bin bs=4K count=1) and open with a hex editor and do some number crunching. It might even be possible to read the flash memory of a locked device with SP Flash Tool.

diplomatic said:
Well, I'm talking about creating the scatter file manually, like I did for my locked/unrooted Asus ZenPad 8.0. No root tools or any special apps necessary. I'm not sure you understand what a scatter file contains. It is simply the partition layout of the device's flash memory and some parameters of each partition relevant to SP Flash Tool. If you have root and busybox you already have everything you need to make one. Just read back the GPT (dd if=/dev/block/mmcblk0 of=gpt.bin bs=4K count=1) and open with a hex editor and do some number crunching. It might even be possible to read the flash memory of a locked device with SP Flash Tool.
Click to expand...
Click to collapse
I'm just saying. Plug my Fire HD 8 into the PC> load MTK Droid Tools> Click blocks map> bmtpool 00000000 000000 size: 0

DragonFire1024 said:
I'm just saying. Plug my Fire HD 8 into the PC> load MTK Droid Tools> Click blocks map> bmtpool 00000000 000000 size: 0
Click to expand...
Click to collapse
Did you get a chance to try the dd method above, sounds like that should work to get a peek at the partitions?

growlre said:
Did you get a chance to try the dd method above, sounds like that should work to get a peek at the partitions?
Click to expand...
Click to collapse
I have not.

Gear S3 Root and Kernel Source! (Android Wear Port Thread)

Hey guys! Some of you might know me from the LG G5 scene, but I have since moved on from there and am hoping to make some progress with the Gear S3
After doing some digging and paying zero attention in class today, I came across the kernel source files for the Exynos 7270 and the combination firmwares for the Gear 3 Classic and Frontier versions.
If you don't know what combination files are here (link removed) is a great explanation but the TL;DR is that this is the internal firmware Samsung uses to reset devices, so it gives you full read/write access to the device including root access. So basically this is a pre-rooted firmware, and I assume that it is bootloader unlocked as it appears to flash an engineer sboot (bootloader), so I believe this would be the first step towards porting Android Wear/TWRP!
The kernel source is what we will actually use to port over AW/TWRP. It does not seem to have been posted before, and took me a few hours of digging to find. My watch comes in tomorrow, and after I flash this firmware I will pull the boot.img and start making a device/vendor tree to attempt and make a kernel!
Here is the kernel source for the Exynos 7270: https://github.com/HonestlyAnnoying/tizen_kernel_exynos7270
Here is the kernel source for the Gear S3 (all versions) (will upload to GitHub in the morning): Samsung Opensource
Here is the SM-R770 (Classic) combination firmware [R770XXU2BQC2]: link
Here is the SM-R760 (Frontier) combination firmware [R760XXU2BQC2]: link
The road to porting Android Wear is going to take a lot of work, and any help developing (not testing for now!) would be EXTREMELY appreciated (looking at you guys @cipherswitch @biktor_gj !). If you would like to help with development or would like to contribute in any way, please PM me or hit me up on Skype (honestly.annoying)!
Here is a Google Drive folder with all files I have for this, it will be updated as new things are found

The one thing that might persuade me to try a sammy product! Thanks for your efforts @Honestly Annoying

Update: have flashed this, can confirm it has root access!! Pulling images now

Wow!!! Fingers crossed!!

@Honestly Annoying
Please, can you tell us what you see on Screen?
Maybe screenshot if posible...
I have flashed just for fun the older Z1 Combination I have... AOC1... and my SM-Z130H shows testmode Icons...
Later I can upload Screenshot... I have to remove something...
But in this Firmware I can enter all testmode Codes via Keys... like:
*#197328640#
And more... this is blocked in normal Firmware...
Cool. su work nice...
I can enter su in Shell and Super User is active... instead SDB Command:
sdb root on
Best Regards
Edit 1.
Screenshot from Combination Firmware AOC1 I have added in this Post:
https://forum.xda-developers.com/showpost.php?p=71744490&postcount=413

adfree said:
@Honestly Annoying
Please, can you tell us what you see on Screen?
Maybe screenshot if posible...
I have flashed just for fun the older Z1 Combination I have... AOC1... and my SM-Z130H shows testmode Icons...
Later I can upload Screenshot... I have to remove something...
But in this Firmware I can enter all testmode Codes via Keys... like:
*#197328640#
And more... this is blocked in normal Firmware...
Cool. su work nice...
I can enter su in Shell and Super User is active... instead SDB Command:
sdb root on
Best Regards
Edit 1.
Screenshot from Combination Firmware AOC1 I have added in this Post:
https://forum.xda-developers.com/showpost.php?p=71744490&postcount=413
Click to expand...
Click to collapse
I'm just going to start dumping information I find in this thread

this is the partition scheme
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13

Honestly Annoying said:
Update: have flashed this, can confirm it has root access!! Pulling images now
Click to expand...
Click to collapse
Did it erase the serial number of the device?

10urshin said:
Did it erase the serial number of the device?
Click to expand...
Click to collapse
nope

Honestly Annoying said:
nope
Click to expand...
Click to collapse
How about knox trip?

10urshin said:
How about knox trip?
Click to expand...
Click to collapse
how can I check?

Honestly Annoying said:
how can I check?
Click to expand...
Click to collapse
Good question. I don't know. I thought it might show on download mode but it doesn't.

This is the boot.img and recovery.img. The Tizen does not seem to extract like an Android kernel, will have to look into this more...
Also, they are both 16.8MB in size, possibly the same image?

Check this path:
/home/developer
Here is device-profile.xml inside...
This allow Privileges of all 3 Levels:
Public
Partner
Platform
But for now only if this Combination Firmware is flashed... it ignores Serial Number/DUID... maybe by these 0 Byte Flag file(s) in CSC...
Best Regards
Edit 1.
... seems my fault...
All Certs are inside...
Code:
usr/share/cert-svc/certs/code-signing/tizen
So fingerprint should be similar like in Reference devices...
Code:
usr/share/wrt-engine
Will later check with open eyes... now better sleep...

adfree said:
Check this path:
/home/developer
Here is device-profile.xml inside...
This allow Privileges of all 3 Levels:
Public
Partner
Platform
But for now only if this Combination Firmware is flashed... it ignores Serial Number/DUID... maybe by these 0 Byte Flag file(s) in CSC...
Best Regards
Click to expand...
Click to collapse
here ya go

Thank you for device-profile.xml...
Should be same here...
https://forum.xda-developers.com/showpost.php?p=71737611&postcount=18
And maybe in all FTMA Combination files... all Gear... all Z-Mobiles...
But reason for working seems not this file...
Sorry, my fault...
But difference in these 2 folders...
Code:
usr/share/wrt-engine/fingerprint_list.xml
and in commercial devices... Certs missing...
Code:
usr/share/cert-svc/certs/code-signing/tizen
This is what I did long time ago in my rooted Zseries Firmware...
By "mistake"... :laugh:
I have nuked device-profile.xml... because I was tooo lazy to register my Email and Certs...
Best Regards

Currently trying to extract the boot.img... should be studying for the SAT but screw it

I did lose Samsung Pay, but to me that is not a big deal. Waiting for a USA firmware to be released to reflash
EDIT: JUST KIDDING. It's still there! I'm an idiot lol

This is great to see! Good luck guys, hope you get this all worked out. Android Wear on the Gear S3 would be the perfect combination! :good:
I have the S3 Frontier, but not all that knowledgeable with Android dev unfortunately.

the_scotsman said:
This is great to see! Good luck guys, hope you get this all worked out. Android Wear on the Gear S3 would be the perfect combination! :good:
I have the S3 Frontier, but not all that knowledgeable with Android dev unfortunately.
Click to expand...
Click to collapse
Honestly at this point any help would be greatly appreciated. Do you have any interest/time available to help out?

[Multiboot][Recovery][ha3g] Boot Multiple Roms v1.0 - (twrp3.1.1.0)

Hi all,
Here you will find modded TWRP recovery file with multiboot feature for Galaxy Note 3 Exynos (ha3g).
With it, you can have multiple ROMs on your device, test new roms without touching your principal rom, etc...
The method used is based on kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827) with a lot of adaptations to make it work on our device (different kernel patches and usersapce program).
Generic demo of booting multiple roms from internal and external storages (https://www.youtube.com/watch?v=d9ekjWaUHYU)
Here is a simple video to show basically how to create and install a ROM. It shows also how to upgrade the rom with another zip after installation (https://youtu.be/B0cGRY4vwy0).
Very important recommendations before using multiboot :
BACKUP all your data first !
Please watch and follow video.
Use only if you have at least 5.5G available on your internal sdcard.
Installation :
Download here : https://www.androidfilehost.com/?fid=673368273298984528
Install zip in recovery mode
Informations :
- Your principal ROM is not affected at all by ROMS installed with multiboot
- Each ROM created sit in a subdirectory of your card : (Internal Storage)/multiboot/roms/NAME_OF_ROM
# ls -al /data/media/0/multiboot/roms/
drwxrwxrwx 2 root root 4096 Sep 8 03:32 Angelo-A7
drwxrwxrwx 2 root root 4096 Sep 9 00:10 DILSHAD-V10UX
drwxrwxrwx 2 root root 4096 Sep 8 02:05 Lineage14.1
drwxrwxrwx 2 root root 4096 Sep 8 03:33 RR-N-v5.8.4
drwxrwxrwx 2 root root 4096 Sep 8 02:21 aicp_ha3g_n-12.1​
- Each ROM directory contains 5 image files (boot, system, data, cache and modem) with fixed size for the moment
# ls -al /data/media/0/multiboot/roms/Lineage14.1
-rw------- 1 root root 20971520 Sep 6 19:45 mmcblk0p13_modem.img
-rw------- 1 root root 329252864 Sep 8 21:10 mmcblk0p19_cache.img
-rw------- 1 root root 2554331136 Sep 7 05:59 mmcblk0p20_system.img
-rw------- 1 root root 3221225472 Sep 8 21:10 mmcblk0p21_data.img
-rw------- 1 root root 8388608 Sep 6 20:13 mmcblk0p9_boot.img​
- Image files system, data and cache are sparsed so dont necessarely take all their size
# du -sh /data/media/0/multiboot/roms/Lineage14.1/
1.4G /data/media/0/multiboot/roms/Lineage14.1/​
- Because android installation method with system.new.dat failed on external sdcard with vfat FS, I disabled option to install ROMs on external sdcard.
- You can copy /sdcard/multiboot/roms/NAME_OF_ROM to external/multiboot/roms/NAME_OF_ROM, il you want to boot ROM from external storage (only sdcard vfat supported). Copy can be done diretly from your PC with copy/paste of the folder.
- All kernels tested are working fine, except Aurora kernel which seems to work but takes long time to load (~1 minute). I recommend another kernel if you want to boot quickly.
- If you want to access your real internal sdcard, look at /multiboot/intsdcard
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : https://twrp.me/
jcadduono : TWRP porting developper - https://forum.xda-developers.com/ga...elopment/recovery-official-twrp-ha3g-t3406899
All ROMs developpers
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2017-09-09
Created 2017-09-09
Last Updated 2017-09-09
Philippe,

reserved

Hi,
First post updated with multiboot v1.0 released.
Please watch this video https://www.youtube.com/watch?v=B0cGRY4vwy0 and read carefully first post before using multiboot.
Philippe,

Ok...i'll try
Sent from my SM-A9100 using Tapatalk

Twrp nandroid
how to backup or restore twrp backup?

Thanks for the Multiboot option on Android
:good: Excellent option for trying out ROM without affecting the Usage ROM.
Tried out and it woks.
Thanks a lot Phil for providing this option.

First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.

Is there a way to have my actual storage for every rom?

nalbantoglu.mehmet said:
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Click to expand...
Click to collapse
TW roms dont need gapps
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app

buick1356 said:
how to backup or restore twrp backup?
Click to expand...
Click to collapse
You can simply copy all the ROM folder (internal card/multiboot/roms) with your PC on another drive.
Maybe a next version will include nandroid backup for those without computer.
nalbantoglu.mehmet said:
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Click to expand...
Click to collapse
I did not notice any trouble installing 6.0 gapps (pico) with AngeloA7 rom.
DontBrickYourPhone said:
Is there a way to have my actual storage for every rom?
Click to expand...
Click to collapse
Inside a multibooted rom, I already mentionned it on first post : If you want to access your real internal sdcard, look at /multiboot/intsdcard ( need a file explorer with root permission I guess)
Inside TWRP, when set to a ROM, your real storage is accessible in /sdcard2.
Philippe,

Phil_Suz said:
You can simply copy all the ROM folder (internal card/multiboot/roms) with your PC on another drive.
Maybe a next version will include nandroid backup for those without computer.
I did not notice any trouble installing 6.0 gapps (pico) with AngeloA7 rom.
Inside a multibooted rom, I already mentionned it on first post : If you want to access your real internal sdcard, look at /multiboot/intsdcard ( need a file explorer with root permission I guess)
Inside TWRP, when set to a ROM, your real storage is accessible in /sdcard2.
Philippe,
Click to expand...
Click to collapse
Thanks I noticed but I was wondering if I can have my data on that Rom as well, or is that not possible since they get sepereated?

DontBrickYourPhone said:
Thanks I noticed but I was wondering if I can have my data on that Rom as well, or is that not possible since they get sepereated?
Click to expand...
Click to collapse
Unfortunately no, I don't think that it could be possible with the way I separated the roms.
Philippe,

Backup and restore
Please add backup and restore options in multiboot for second ,.....roms

Can u write steps of how to do this ???
Pls

mehal123 said:
Can u write steps of how to do this ???
Pls
Click to expand...
Click to collapse
Please view the video post for the same purpose. if you still have a clarification, I will be glad to support.

well I've notice after adding ROM internal storage is just 8GB ,well is this default for TWRP? or there is option to choose exact space taken by each ROM?
check picture:
HTML:
https://ibb.co/inAtW5

Phil_Suz said:
Hi all,
Here you will find modded TWRP recovery file with multiboot feature for Galaxy Note 3 Exynos (ha3g).
With it, you can have multiple ROMs on your device, test new roms without touching your principal rom, etc...
The method used is based on kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827) with a lot of adaptations to make it work on our device (different kernel patches and usersapce program).
Generic demo of booting multiple roms from internal and external storages (
)
Here is a simple video to show basically how to create and install a ROM. It shows also how to upgrade the rom with another zip after installation (
).
Very important recommendations before using multiboot :
BACKUP all your data first !
Please watch and follow video.
Use only if you have at least 5.5G available on your internal sdcard.
Installation :
Download here : https://www.androidfilehost.com/?fid=673368273298984528
Install zip in recovery mode
Informations :
- Your principal ROM is not affected at all by ROMS installed with multiboot
- Each ROM created sit in a subdirectory of your card : (Internal Storage)/multiboot/roms/NAME_OF_ROM
# ls -al /data/media/0/multiboot/roms/
drwxrwxrwx 2 root root 4096 Sep 8 03:32 Angelo-A7
drwxrwxrwx 2 root root 4096 Sep 9 00:10 DILSHAD-V10UX
drwxrwxrwx 2 root root 4096 Sep 8 02:05 Lineage14.1
drwxrwxrwx 2 root root 4096 Sep 8 03:33 RR-N-v5.8.4
drwxrwxrwx 2 root root 4096 Sep 8 02:21 aicp_ha3g_n-12.1
- Each ROM directory contains 5 image files (boot, system, data, cache and modem) with fixed size for the moment
# ls -al /data/media/0/multiboot/roms/Lineage14.1
-rw------- 1 root root 20971520 Sep 6 19:45 mmcblk0p13_modem.img
-rw------- 1 root root 329252864 Sep 8 21:10 mmcblk0p19_cache.img
-rw------- 1 root root 2554331136 Sep 7 05:59 mmcblk0p20_system.img
-rw------- 1 root root 3221225472 Sep 8 21:10 mmcblk0p21_data.img
-rw------- 1 root root 8388608 Sep 6 20:13 mmcblk0p9_boot.img
- Image files system, data and cache are sparsed so dont necessarely take all their size
# du -sh /data/media/0/multiboot/roms/Lineage14.1/
1.4G /data/media/0/multiboot/roms/Lineage14.1/
- Because android installation method with system.new.dat failed on external sdcard with vfat FS, I disabled option to install ROMs on external sdcard.
- You can copy /sdcard/multiboot/roms/NAME_OF_ROM to external/multiboot/roms/NAME_OF_ROM, il you want to boot ROM from external storage (only sdcard vfat supported). Copy can be done diretly from your PC with copy/paste of the folder.
- All kernels tested are working fine, except Aurora kernel which seems to work but takes long time to load (~1 minute). I recommend another kernel if you want to boot quickly.
- If you want to access your real internal sdcard, look at /multiboot/intsdcard
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : https://twrp.me/
jcadduono : TWRP porting developper - https://forum.xda-developers.com/ga...elopment/recovery-official-twrp-ha3g-t3406899
All ROMs developpers
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2017-09-09
Created 2017-09-09
Last Updated 2017-09-09
Philippe,
Click to expand...
Click to collapse
I tried and installed 3 different roms . It is working perfectly.
The minus points which i noted are,
we dont have enough internal space in the secondary roms(We have only 2 gb per rom)
If i restart the phone the original rom will be replaced the secondary roms ( without booting it via twrp)

Principal ROM
Sorry if I missed it in the OP.
How to get back to the original (primary/principal) rom which is parent to multiboot folder? set rom only shows the newly created roms.

notagamer said:
Sorry if I missed it in the OP.
How to get back to the original (primary/principal) rom which is parent to multiboot folder? set rom only shows the newly created roms.
Click to expand...
Click to collapse
Just restart or clear cache it will automatically revert to primary rom.

Can I give a working link to download !?

Is there any way to see date of last factory reset/installation date for android?

Hello, thank you for your help!
I'm trying to see if there Would be a way to see the date on which the operating system was installed.
In particular, I have a Phone that may have been factory reset. I Would like to Know if its possible to check wether or not this Phone has been factory reset, and in which date it has been reset.
Any Kind of tool Will be of help, even if I have to root the device or something.
Thank you very much for your help!

How to find a date when Android OS is installed
I need to find information about when the particular android OS is installed on mobile device.Is there any way to find that info?Thanks
www.forensicfocus.com

jwoegerbauer said:
How to find a date when Android OS is installed
I need to find information about when the particular android OS is installed on mobile device.Is there any way to find that info?Thanks
www.forensicfocus.com
Click to expand...
Click to collapse
Thank you very much, this can be useful. So, there isn't an option to be sure when the phone was initialized? I mean, if there was no account used in the setup and the user logged into an account later, that file would display the latter date, right?

IDK, never had to figure that out.

you could check /data/misc/bootstat/factory_reset
Code:
# ls -l /data/misc/bootstat
total 6
drwx------ 2021-07-07 20:33:25.000000000 +0200 .
drwxrwx--t 1971-04-02 22:24:49.000000000 +0100 ..
-rw------- 2021-05-06 15:26:07.000000000 +0200 build_date
-rw------- 2021-07-03 14:22:23.000000000 +0200 factory_reset
-rw------- 2023-03-18 23:01:57.000000000 +0100 factory_reset_current_time
-rw------- 2021-07-03 14:22:23.000000000 +0200 factory_reset_record_value
-rw------- 2023-03-18 23:01:57.000000000 +0100 last_boot_time_utc