Database Info

[ROM][DEV][Jan-24-2012]Rooted Telus 3.13.661.4 Sense3.0 100% Inspire compatible.

Hackers/kangers only!
I managed to get the OTA that HTC is currently sending down to Telus customers using the Canadian DHD. I patched it to the current Telus ROM an packaged it up for Inspire. This DHD is 100% compatible with the Inspire so this ROM works without any modifications to audio or graphics.
This is for experienced ROM users/developers and not intended for general use yet due to the new lib.img partitioning scheme. It will NOT work completely with ClockWorkMod recoveries. I don't know if there are any recovery images that mount and backup the new lib partition. We're working on a new recovery for this, but you'll need to manually backup/restore the lib partition after a CWM backup for now
This ROM installs a new HBOOT that WILL rearrange your partition table! If you istall this, you'll have to downgrade your hboot to install any older ROMs.
This is a PD98IMG installation zip and is only installable through your current bootloader. It WILL wipe out everything currently on your device by repartitioning the NAND memory to include the new lib.img partition. Backup!
This is the direction HTC is moving and it is already how the DHD WWE ROMs do things and if we see any Sense3 update to Inspire from AT&T, it will most likely have this partitioning scheme so it's a good idea to get used to it now.
If you've made it this far and still want to play with this, then be my guest, but I'm not going to assume any responsibility for anything that happens. As I've explained, it repartitions your device, deletes all existing data, and has an incomplete recovery (won't backup /system/lib).
I'm currently working on a more user oriented ROM that will incorporate a proper CWM recovery with bloat removed, etc. but it's a few days off.
This ROM is essentially the Telus ROM with a properly rooted system partition and a ro.secure=0 boot.img. It includes the radio and rcdata from the current Telus OTA (which works fine with Inspire). I've replaced the recovery image with a CWM recovery from the latest cyanogenmode kang source and it will do everything you need in a recovery EXCEPT backup the lib partition (I'm working with ATTN1 to modify CWM recovery to do this).
It is a PD98IMG style install and will not install from your current recovery. Download the file below, rename it to exactly PD98IMG.zip on your SDCard and reboot to hboot and follow the prompts. If you don't know how to do this, then you probably shouldn't be installing this ROM. It will install the new bootloader first, then reboot to the new bootloader to install the rest.
http://hoxnet.com/droid/RUU_Ace_Sen...61.4-2.43.661.1_R_release_rooted_unsigned.zip
MD5: 47d532199ec3e4f638622fd7d3cfcb5a
File List:
Code:
unzip -v RUU_Ace_Sense30_S_TELUS_WWE_3.13.661.4-2.43.661.1_R_release_rooted_unsigned.zip
Archive: RUU_Ace_Sense30_S_TELUS_WWE_3.13.661.4-2.43.661.1_R_release_rooted_unsigned.zip
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
74 Stored 74 0% 12-15-2011 04:04 242b7893 android-info.txt
2902016 Defl:N 2883345 1% 01-23-2012 22:29 c656e133 boot.img
1048576 Defl:N 233535 78% 12-15-2011 03:51 e7bf8e92 hboot_7230_Ace_2.00.0027_110907.nb0
159383552 Defl:N 51646690 68% 01-23-2012 15:07 7c23a0ba lib.img
585101312 Defl:N 283384857 52% 01-23-2012 23:01 f5ede6ba system.img
3741696 Defl:N 3734895 0% 01-23-2012 22:30 141db616 recovery.img
25559040 Defl:N 11697885 54% 12-15-2011 02:43 cc964593 radio.img
124 Defl:N 104 16% 12-15-2011 03:51 6fb0a433 rcdata.img
1420752 Defl:N 933921 34% 08-31-2011 08:50 8ae782ee dzdata.img
-------- ------- --- -------
779157142 354515306 55% 9 files

Very interesting.

I should have a normal ROM later today. I've managed to strip out enough bloat to fit the new bigger system and lib on the same partition.

Awesome Gene
Keeping updated upon rom release.
Thanks

mateusm said:
Awesome Gene
Keeping updated upon rom release.
Thanks
Click to expand...
Click to collapse
I recycled my earlier 3.06 based ROM and posted it there. Download here:
http://forum.xda-developers.com/showthread.php?t=1269864
This one WILL wipe data. I couldn't find any way around that. The good news is that Titanium Backup restored all my previous settings just fine (except the wallpaper).

[Q] Invisiable backups

I seem to have dug myself into a hole. I tried to test KitKat on my Galaxy Mega (GT-I9205). I found two roms that said they supported the Mega, so I made a backup of my current rom and flashed the first rom I found, played around with it and decided to go back to Jelly Bean, backup restored, no problems, all normal.
Then I tried the second rom (cm11 unofficial). Installed, no problems, played around with it and decided it wasn't for me and tried to revert to the JB rom backup. No chance. The recovery environment (which used to be cwm but somehow is now twrp v2.7.0.5 - don't ask me how? ) cannot even see any of the backups I have (and I have plenty, some of which were made by cwm and some by twrp - although probably not the same twrp version, not sure on that).
What I have tried.
Renaming the backups, moving the backups to different folders, using twrp to do a backup of the new rom to see where it saved it and then moving the backups to that folder, but it simply refuses to see them. So I can't go back. I even tried flashing a cwm recovery zip from within twrp - ok, I realise that is not likely to work, and sure enough it didn't..
My next thought was that I will have to continue using the cm rom that I have installed, but it has a problem too. When gapps is not installed every single application runs normally, but as soon as I install gapps both Titanium Backup (6.1.5.6) and Rom Manager (5.5.3.7) crash. I have tried this three times (two different gapps versions) and including cache and dalvik wipes before flashing gapps, absolutely no change.
So in short I have a perfect backup that can't be seen, I have a cm11 rom without gapps that works perfectly normally and I have a cm rom with gapps where two of my most important applications constantly crash.
I would really like to go back to JB - but if anyone can tell me how to fix titanium and rom manager on the present install, that would be fine, I would stick with cm11.
Another complication is that I don't use windows (linux only) so Odin is not an answer for me.
Help!
Edit: Here is another thought. I can easily do without Rom Manager, since Twrp took over my recovery it does nothing anyway, but is there a replacement out there for Titanium Backup? Even something half as capable I would be able to cope with until TB maybe issues an update that works with gapps on cm11.
Edit2: It seems there is such a tool. Jrummy Ultimate Backup seems to have the same functions as Titanium and it runs perfectly so far whereas Titanium still crashes all the time. This might be the answer to continuing to use Cm11.

Well here is a clue. When I look at the backups in the Ultimate backup interface, it actually identifies them by type and it appears that the backups I thought were twrp backup (I even included the letters 'twrp' in the backup name) are in fact cwm backups not twrp. This may be why twrp can't see them!!
Don't think I will ever be able to go back to these now unless I force another recovery onto the phone (cwm of course) - without Odin that is none too easy.
However, the good news is that at the moment (early days still) the CM11 rom with Ultimate Backup on it is running very smoothly so maybe I don't have to go back at all, we will see.

I finally solved this after 4 days puzzling over it. I will tell you how even though I received absolutely no help from anyone on the forum.
All my backups (which used to work) look like this:
Code:
/h/c/b/c/2014-08-10-lite> ls -l
total 2235668
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 boot.img
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 cache.ext4.tar
-rw-r--r-- 1 manjaro 1000 19456 Feb 1 2013 cache.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 data.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 data.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 41370112 Feb 1 2013 data.ext4.tar.b
-rw-rw-r-- 1 manjaro 1000 492 Aug 15 15:39 nandroid.md5
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 recovery.img
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 system.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 system.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 226939392 Feb 1 2013 system.ext4.tar.b
You can see from the fourth column that I have three zero byte files in there - don't ask me how, it is just how the backups were written, I didn't interfere with the process and all five backups were the same and they had been used to restore the image before without problem.
What I did was to change it to this:
Code:
/h/c/b/c/2014-08-10-lite-COPY> ls -l
total 2235672
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 boot.img
-rw-r--r-- 1 manjaro 1000 19456 Feb 1 2013 cache.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 data.ext4.tar
-rw-r--r-- 1 manjaro 1000 41370112 Feb 1 2013 data.ext4.tar.a
-rw-rw-r-- 1 manjaro 1000 339 Aug 16 11:45 nandroid.md5
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 recovery.img
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 system.ext4.tar
-rw-r--r-- 1 manjaro 1000 226939392 Feb 1 2013 system.ext4.tar.a
Removed the zero byte files, renamed the other files appropriately and then regenerated the nandroid.md5 file with the correct values, cd to the backups folder and run:
Code:
md5sum *>nandroid.md5
(on Linux that is)
The amended backup restored at the first attempt.
This process was much complicated by the fact that these backups were done in CWM and my running ROM had TWRP. Thanks to the writers of Heimdall for solving that problem for me - nothing windows or android possessed was capable of doing so.
Having succeeded in restoring the backup I then flashed TWRP onto the Jelly Bean rom so it is now a simple rom flash to switch from one the other.

[MTK][TOOL][APP]MTKTransfROM, port your ROM directly from phone!

Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Code:
[B]system/bin/vold [/B] (Copy this file from your device)
[B]system/etc[I]/[/I][/B] (Copy entire directory, replacing existing files)
[B][I]-[/I]system/etc/ [/B] (First delete ROM folder and then copy entire folder)
[B]system/lib/libaudio[I]*[/I][/B] (Copy all files that starts with libaudio...)
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.​

Can you add support for MT6752 devices?

You can add it yourself putting your custom files in the folder I explained in the tutorial

RacerOttavio97 said:
You can add it yourself putting your custom files in the folder I explained in the tutorial
Click to expand...
Click to collapse
Thanks, I will try it and see if it works :fingers-crossed:

I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.

HypoTurtle said:
I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.
Click to expand...
Click to collapse
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.

RacerOttavio97 said:
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.
Click to expand...
Click to collapse
MTKsplit can/does run on android itself - thats why I wrote it. It's a sh - primarily using dd to split the boot/recovery. I removed the #! at the top so the same script can be run fron recovery and system (making it default to the shell that calls it - /sbin/sh in recovery and /system/bin/sh in system).
Just tested the MTKsplit against a 6592 recovery.img and it works fine:
Code:
[email protected]_phone:/tmp # ls -la
ls -la
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
[email protected]_phone:/tmp # MTKsplit recovery-6592 unpack
MTKsplit recovery-6592 unpack
Unpacking recovery-6592 - will only take 30 seconds
All Done...
Command line: f30"
Ramdisk unpacked to /tmp/work
[email protected]_phone:/tmp # ls -la
ls -la
-rw------- root root 4265472 2015-10-05 16:24 kernel
-rw------- root root 512 2015-10-05 16:23 kernel_header
-rw------- root root 2048 2015-10-05 16:23 mtk_header
-rw------- root root 1598976 2015-10-05 16:24 ramdisk.cpio.gz
-rw------- root root 512 2015-10-05 16:24 ramdisk_header
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
drwx------ root root 2015-10-05 16:24 work

Android sdk
Is it necessary to be the port rom is the same android sdk level of my mobile stock rom ?!

RacerOttavio97 said:
Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.
Click to expand...
Click to collapse
playstore-item not found
what ca i do..??

link not work

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 !?