Database Info

[Question]OrDroid 6.0.0 install issue - Solved

Solved. EXT4 recovey is a must Shame on me.
Hi, does anyone have an idea what could be my problem?
Tried to install OrDroid 6.0.0
On aroma only the wipe was displayed (fortunately the wipe was not performed). Then I was told that the install is complete...
Afterwards I did verify again the md5 hash, it's correct does match.
Currently CoinDroid with Sense 4 V1.5.2 is installed from the same developer shnizlon...
Saved the log :
AROMA INSTALLER version 2.00
(c) 2012 by amarullz xda-developers
ROM Name :
OrDroid
ROM Version : 6.0.0
ROM Author : Shnizlon & Baadnewz
Device : HTC Sensation
Start at :
Wed May 16 10:32:41 2012
Executing Full Wipe
-> Erasing & formatting /cache as EXT4
about to run program [/sbin/erase_image] with 2 args
Creating filesystem with parameters:
Size: 125787136
Block size: 4096
Blocks per group: 32768
Inodes per group: 7677
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 30709
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/7677 inodes and 1518/30709 blocks
error: file_write: write: I/O error
Installer Error (Status 1)
End at : Wed May 16 10:32:41 2012

SzosszeNET said:
Hi, does anyone have an idea what could be my problem?
Tried to install OrDroid 6.0.0
On aroma only the wipe was displayed (fortunately the wipe was not performed). Then I was told that the install is complete...
Afterwards I did verify again the md5 hash, it's correct does match.
Currently CoinDroid with Sense 4 V1.5.2 is installed from the same developer shnizlon...
Saved the log :
AROMA INSTALLER version 2.00
(c) 2012 by amarullz xda-developers
ROM Name :
OrDroid
ROM Version : 6.0.0
ROM Author : Shnizlon & Baadnewz
Device : HTC Sensation
Start at :
Wed May 16 10:32:41 2012
Executing Full Wipe
-> Erasing & formatting /cache as EXT4
about to run program [/sbin/erase_image] with 2 args
Creating filesystem with parameters:
Size: 125787136
Block size: 4096
Blocks per group: 32768
Inodes per group: 7677
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 30709
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/7677 inodes and 1518/30709 blocks
error: file_write: write: I/O error
Installer Error (Status 1)
End at : Wed May 16 10:32:41 2012
Click to expand...
Click to collapse
Are you using 4ext?
Sent from my Sensation using Tapatalk 2

Man use 4ext... That will do the trick
Sent from my Sensation using Tapatalk 2

matt95 said:
Are you using 4ext?
Click to expand...
Click to collapse
Sure, almost since available.
I have the latest 5.8.0.9 touch clockworkmod also

matt95 said:
Man use 4ext... That will do the trick
Click to expand...
Click to collapse
This is my current ROM : Coindroid v1.5.2
As far as I know it's also EXT4.
Same developer.

I mean flash the rom with 4ext recovery not with clockwork
Sent from my Sensation using Tapatalk 2

matt95 said:
I mean flash the rom with 4ext recovery not with clockwork
Click to expand...
Click to collapse
Sure, I'll give a try.

matt95 said:
Man use 4ext... That will do the trick
Click to expand...
Click to collapse
Rocks, that really did the trick.
It's now installed.
Btw is that normal that after install on "Senstaion" boot screen the only way to get through is to go into "safe mode" for the first boot?
Left previously the phone for 1 hour and only "htc sensation" bootscreen was displayed (when I was on CoinDroid). Then I pushed my phone into safemode and since boots normally.

SzosszeNET said:
Rocks, that really did the trick.
It's now installed.
Btw is that normal that after install on "Senstaion" boot screen the only way to get through is to go into "safe mode" for the first boot?
Left previously the phone for 1 hour and only "htc sensation" bootscreen was displayed (when I was on CoinDroid). Then I pushed my phone into safemode and since boots normally.
Click to expand...
Click to collapse
Well, I think that it's not normal... Have you got the latest 3.32 firmware installed? You need The ics hboot to boot these roms
Sent from my Sensation using Tapatalk 2

matt95 said:
latest 3.32 firmware installed?
Click to expand...
Click to collapse
Regarding this I have no idea...nor where to check it. Could you please advise?
HBOOT is 1.27.0000
Radio : 11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
That's all what I see at the bootloader.

Found it, for me that's OrDroid 6.0.0...

What radio/firmware works best with this ROM?
I currently have the tmo 11.69A.3504.00u_11.23.3504.07_m2.
3.32.531.14CL356011

wogeboy said:
What radio/firmware works best with this ROM?
I currently have the tmo 11.69A.3504.00u_11.23.3504.07_m2.
3.32.531.14CL356011
Click to expand...
Click to collapse
The firmware must be the 3.32 which is hboot 1.27.1100 and the radio depens on different areas... You choose the best in less words
Sent from my Sensation using Tapatalk 2

[Tut][I9001] How To Repartition Brocken Partitioned I9001 devices

Hi every one !
Our Odin version doesn't support repartition , so we can't do any thing while we have a Brocken partition ! Brocken partition are software related or hardware related , If you used the method bellow with no success your problem is hardware related and you need to at least replace your EMMC ic . OK I will describe more on method , the alternative method is flashing whole of empty partitions on +8 partitions except some partitions such as efs and ...
1- you need to check out which partitions are Brocken ! Choose format/wipe option in recovery mod to find out which are brocken , mostly data or cache partitions are Brocken , or in harder situation may system !
2- you need to create empty partitions for Brocken ones , you need terminal emulator to run this ( for data and cache )
Code:
su
dd if=/dev/zero of=/data.img.ext4 count=1413120
dd if=/dev/zero of=/cache.img.ext4
count=102400
# ... do Like this for other brocken partitions
continue for every Brocken partitions
3- tar every empty partitions you have created in step 2
4- flash tar file by Odin in one package
5- When your device boots up check out Brocken partitions are fixed or not if yes wipe them in recovery if not your problem is hardware related and you need to change EMMC ! I hope all Brocken partitions fix by this method and you won't need to hardware fixing .
# Do At Your Own Risk ! # I'm not responsible any more ! #
Just do this when you have Brocken partitions ! This can cause some problems to non damaged devices !(thanks to Broodplank for reminding )
Credit:
BroodPlank1337 - Helping me
Cheers
AliReza

Ok some additional info:
You can get the block size by looking at the /proc/partitions table
Code:
major minor #blocks name
7 0 2111 loop0
179 0 7757824 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5230592 mmcblk0p28
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
254 0 2110 dm-0
Also our odin has no default repartition box idd, but I made a package a while ago which resets "all" partitions:
Code:
adsp.mbn (mmcblk0p5)
amss.mbn (mmcblk0p6)
boot.img (mmcblk0p8)
cache.img.ext4 (mmcblk0p19)
data.img.ext4 (mmcblk0p17)
dbl.mbn (mmcblk0p1)
EMMCBOOT.MBN (mmcblk0p4)
emmcparam.bin (mmcblk0p14)
osbl.mbn (mmcblk0p2)
partition.bin (mmcblk0p0)
persist.img.ext4 (mmcblk0p12)
preload.img.ext4 (mmcblk0p18)
recovery.img (mmcblk0p13)
system.img.ext4 (mmcblk0p15)
oh and a global message to all, if you don't have to use dd, don't use it. when you have non corrupted partition that you want to wipe use "cd /partition && rm -Rf *" its always the safest option. (unless executed in root hehe)

AW: [Tut][I9001] How To Repartition Brocken Partitioned I9001 devices
Thats very usefull! Thanks to you both!
Sent from my GT-I9000 using xda app-developers app

XeLLaR* said:
Thats very usefull! Thanks to you both!
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thanks for supporting ... but I wish you won't ever need to use this

alireza7991 said:
Thanks for supporting ... but I wish you won't ever need to use this
Click to expand...
Click to collapse
Idd hehe, I've had some crazy moments that I accidentally removed a partition (when having over 50 windows open, and 10 of them are a commandline), but when flashing broodROM RC5 it was restored anyways ;p

broodplank1337 said:
Idd hehe, I've had some crazy moments that I accidentally removed a partition (when having over 50 windows open, and 10 of them are a commandline), but when flashing broodROM RC5 it was restored anyways ;p
Click to expand...
Click to collapse
Hehe
You were in the software damaged case , so you could restore but if you had hardware damaged emmc you had to change it ! Some thing like Buffo had done to its device was hardware Brocken emmc

UP !

Hi! Is this useful if my SGS+ always freezes when I wanna make a factory reset? And it freezes at the Samsung galaxy screen.... I tried to format with a few recoveries but always the same problem. It started after I failed to flash the newest CM 10b4.
I tried already to flash a few stock-roms over odin and other custom roms over CWM / FeaMod / TeamWin recovery.... Nothing helped. How can I find out if that emmc is brocken?

Imanidiot said:
Hi! Is this useful if my SGS+ always freezes when I wanna make a factory reset? And it freezes at the Samsung galaxy screen.... I tried to format with a few recoveries but always the same problem. It started after I failed to flash the newest CM 10b4.
I tried already to flash a few stock-roms over odin and other custom roms over CWM / FeaMod / TeamWin recovery.... Nothing helped. How can I find out if that emmc is brocken?
Click to expand...
Click to collapse
Did you flash the CM10 with a to old version of CWM? (it needs to be 5.4.0.4 atleast). this could have caused it, if not, did you do excessive rom flashing? (sometimes when im hours and hours of trying to flash things on my phone it seems to get "tired" and the formatting/installing goes so slow that you almost manually pull the batter)
Have you tried to flash broodROM RC5? don't want to advertise for it but it's generally known that it "unbricks" devices because of the large number of partitions
Have you tried the CWM bootloop solution btw? http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330

I tried the bootloop solution but it didn't work... And I don't think that my phone went "tired" cuz cache formating is still working...but the phone turns automatically off after a few seconds.
No i never tried the other rom solution cuz someone other with the same problem tried it already but it didn't work... Well I'll try it anyway.
And thanks for the fast answer! I would give you a "thanks" but i gave already 8 sorry..
Edit:
I can't remember which CWM I used before... but after I saw the "Symlinks failed" "Status 7" error I flashed the latest CWM but there it was just the same :/

How can i know about broken partitions ?
Because i have ~7 months left to change my phone, and i don't want to brick my phone which i love much <3

AW: [Tut][I9001] How To Repartition Brocken Partitioned I9001 devices
DiKei said:
How can i know about broken partitions ?
Because i have ~7 months left to change my phone, and i don't want to brick my phone which i love much <3
Click to expand...
Click to collapse
If your device is booting and running fine, you dont have to worry about these things at all.
Sent from my GT-I9001 using xda app-developers app

Okay, i flashed the broodROM RC5 over Odin, but i can't still boot the phone.
And i can't make a factory reset / deleting data. The phone just freezes while the process ... Any ideas? Please :/

R: [Tut][I9001] How To Repartition Brocken Partitioned I9001 devices
Imanidiot said:
Okay, i flashed the broodROM RC5 over Odin, but i can't still boot the phone.
And i can't make a factory reset / deleting data. The phone just freezes while the process ... Any ideas? Please :/
Click to expand...
Click to collapse
Flash stock ROM via odin. Then flash broodROM again. Make sure you followed the instructions in the thread.
Grammar™ is freeware; this means you can use it without paying anything. Though, Grammar™ is not open-source; this means you can't edit source code.

edisile said:
Flash stock ROM via odin. Then flash broodROM again. Make sure you followed the instructions in the thread.
Grammar™ is freeware; this means you can use it without paying anything. Though, Grammar™ is not open-source; this means you can't edit source code.
Click to expand...
Click to collapse
I know about my grammar, sorry. And yes okay, I'll try this one
Edit:
Factory reset is still not working...so how can I follow the instructions? :/

Imanidiot said:
I know about my grammar, sorry. And yes okay, I'll try this one
Edit:
Factory reset is still not working...so how can I follow the instructions? :/
Click to expand...
Click to collapse
Can you stil mount /data & /cache ??
Can you go in /data partition via twrp file manager or aroma file manager ?

Yes I can mount data and cache over the FeaMod recovery.
Well...should I flash twrp again?

Imanidiot said:
Yes I can mount data and cache over the FeaMod recovery.
Well...should I flash twrp again?
Click to expand...
Click to collapse
You can use aroma file managed too !
just check out that you can enter in /data and remove or.copy files there !

Phone is finally dead now...I got a reset.md5 to reset all partitions, but now it won't even start...I think I can trow it now out of the window

Okay a short summary please.
What are the thing you have done to try to get your phone back to life?

Xoom 2 backup solution?

Hi! I have an european Xoom 2 MZ 616 stock, rooted and I want to know how can I make a backup, like linux dd or something to have it just in case. The main problem might be that the european model doesn't have a card slot, I think. Could you recommend me some methods?
And another question: Will the non-US ones get the JB update? Come on, is it faire that only one carrier in US to get it?
Thanks
Sent from my XOOM 2 using xda app-developers app

Partition layout
I did
Code:
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
, I pulled it on my computer, opened it with an hex editor and saw this:
Code:
console=/dev/null rw [email protected] vram=8004K,0x81800000 omapfb.vram=0:[email protected],1:[email protected] init=/init ip=off mmcparts=mmcblk1:p1(mbmloader),p2(mbm),p3(mbmbackup),p4(cdt.bin),p5(pds),p6(utags),p7(logo.bin),p8(sp),p9(devtree),p10(devtree_backup),p11(boot),p12(recovery),p13(cdrom),p14(misc),p15(cid),p16(kpanic),p17(system),p18(cache),p19(preinstall),p20(userdata)
Then I see all these 20 partitions:
- p1(mbmloader)
- p2(mbm)
- p3(mbmbackup)
- p4(cdt.bin)
- p5(pds)
- p6(utags)
- p7(logo.bin)
- p8(sp)
- p9(devtree)
- p10(devtree_backup)
- p11(boot) 8 MB
- p12(recovery) 9 MB
- p13(cdrom) 212 MB
- p14(misc)
- p15(cid)
- p16(kpanic)
- p17(system)
- p18(cache)
- p19(preinstall)
- p20(userdata)
What these every partitions do? CDROM probably is the one it boots in case it can't boot normally, just like a safe mode, SYSTEM is the partition with the main files, but what about the hidden ones?
Almost all these partition start with hex offset 41 4E 44 52 4F 49 44 21 or ANDROID! What filesystem is this? How can I mount these images on Windows or Linux?
Do I need to backup all these partitions (except userdata, probably) ?
Thanks!

Sir,
Same concern any JB update I'm stock in ice cream sandwich,Any master's help?
Regards,
Akihiro
Sent from my XOOM 2 using xda app-developers app

Samsung General Galaxy Core LTE SM-G386F knowledge base

In this thread I would like to gather all information about custom roms, recoveries, kernels and root methods suitable for the Samsung Galaxy Core LTE SM-G386F, so that people don't have to look up every single thread in order to find (or, which is true in most of the cases, to not find) their desired solutions. Also this may get developers interested which would be good since there is nearly no developing going on at the moment. It would be very kind of the mods if they'd made this thread a sticky so that everybody can easily access the information.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEVICE SPECIFICATIONS
Display - PLS capacitive touchscreen, 16M colors; 540 x 960 pixels, 4.5 inches (~245 ppi pixel density)
Internal Memory - 8 GB, 1 GB RAM
Connectivity - GPRS; EDGE; HSPA; LTE, Cat4, 50 Mbps UL, 150 Mbps DL; Wi-Fi 802.11 b/g/n, Wi-Fi Direct, DLNA, Wi-Fi hotspot; Bluetooth v4.0, A2DP; NFC;
Camera - Back: 5 MP, 2592 х 1944 pixels, autofocus, LED flash; Front: 0,3 MP
CPU - Renesas MP5232 dual-core SoC (1,2 GHz)
Graphics Chip - PowerVR SGX544
Sensors - Accelerometer, proximity, compass
GPS - with A-GPS, GLONASS
LATEST STOCK ROM
Android OS, v4.2.2
Release date: August 2014
Country: Italy
PDA: G386FXWUANG1
CSC: G386FITVANH1
Download: http://rapidgator.net/file/6a9315a968157e27400354cc6850bfcd/XEF-G386FXWUANG1-20140805095652.zip.html
HOW TO ROOT
First of all: I am NOT responsible for any damage the following guides may do to your phones. Use them at your own risk! If you don't know what you're doing - stop! You have been warned.
Currently there is only one working root method (thanks to freb123 for letting me know!).
Root via Chimera tool
EDIT: You can now manually root your devices!
The necessary files can be downloaded from here: sendbox.fr/pro/yagmbf4ke22i/g386froot.zip.html (thanks to freb123 again for providing us with the files! )
These files can be flashed through ODIN and/or adb. The only thing you need to do is to change the file extension from .md5 to .tar (thanks to mstefanski1987 for figuring that out!)
Note: You still need to install supersu from Google Play after flashing.
Again: Use this at your own risk and only if you're completely aware of what you're doing.
Download ODIN 3.07: http://www.mediafire.com/download/khxp78iwthsukji/Odin+3.07+BY+taringuero_d+.rar
Download Samsung USB driver: http://developer.samsung.com/board/download.do?bdId=0000000700&attachId=0000000001
Requirements - Computer running Windows XP or above; Chimera Tool: https://chimeratool.com/application/142; All-in-one driver package: https://pics.chimeratool.com/drivers/chimera_drivers.exe; USB debugging enabled in phone
1. Download the linked packages
2. Install the drivers first and the program itself afterwards
3. Launch chimera tool
4. You will have to log in in order to proceed. To do so you'll need to sign up for a free chimera account here: https://chimeratool.com/register (this account expires after three days)
5. Connect your phone via USB with USB debugging enabled
6. If the phone is recognized correctly, the program will display your device model and five options (Info, Repair, Root/Unroot, Firmware Update and Factory Unlock)
7. Click "Root/Unroot"
8. The rooting process is automated so everything from 7. on should happen automatically. However, the program prompted me to manually enter download mode. If that's the case, simply disconnect your phone from USB, turn it off and enter download mode by following the on-screen instructions. After entering download mode reconnect your phone via USB and rooting should finish.
9. Since the program does NOT install supersu, you'll have to manually install it via Google Play.
10. That's it - your device is rooted!
CUSTOM ROMS & KERNELS
None yet
CUSTOM RECOVERY (TWRP,CWM)
None yet
Note: This thread will be updated as soon as I receive new information about the listed sections. If there is anything you wish to add or contribute (I'd love you to do that, believe me ) feel free to comment!

Thx for this thread.
Could we use the root.tar.md5 downloaded by chimera and root directly with adb or odin ?

freb123 said:
Thx for this thread.
Could we use the root.tar.md5 downloaded by chimera and root directly with adb or odin ?
Click to expand...
Click to collapse
It should work, I'll give it a try when I'm on my Windows PC and report back.
Btw: You can also use the thanks-button if you want to thank me

Thx for this thread, my Core LTE will appreciate :good:

freb123 said:
Thx for this thread.
Could we use the root.tar.md5 downloaded by chimera and root directly with adb or odin ?
Click to expand...
Click to collapse
Do you know where chimera tool puts the downloaded files? I can't seem to find them.
If they can be taken from any directory, flashing via ODIN or adb should be no problem, since that's what the tool does as well.

bchzmlsn said:
Do you know where chimera tool puts the downloaded files? I can't seem to find them.
If they can be taken from any directory, flashing via ODIN or adb should be no problem, since that's what the tool does as well.
Click to expand...
Click to collapse
Yes, in the directory where you launh chimera (/backup/gm-386), but files are deleted after root. You can get them just after chimera asks you to put the phone off.
If you are already rooted, you need to unroot your phone to see them again ! (voodoo ota root keeper can help you...)
I send you the link to the file in PM (can't include a link, not enough posts in the forum).
sendbox.fr/pro/yagmbf4ke22i/g386froot.zip.html

freb123 said:
Yes, in the directory where you launh chimera (/backup/gm-386), but files are deleted after root. You can get them just after chimera asks you to put the phone off.
If you are already rooted, you need to unroot your phone to see them again ! (voodoo ota root keeper can help you...)
I send you the link to the file in PM (can't include a link, not enough posts in the forum).
sendbox.fr/pro/yagmbf4ke22i/g386froot.zip.html
Click to expand...
Click to collapse
Thank you!
I've updated the initial post and attached the files.

When i try to use attached file with Odin 3.07 I get this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> sm-g386f_root.tar.md5 is invalid.
<OSM> End...
What am I doing wrong?
I am trying to get root so I can dump recovery image and start working on it. Any help is appreciated.
EDIT:
Figured it out, I had to change extension from .tar.md5 to .tar.
MANUAL ROOT METHOD IS WORKING.
EDIT 2:
I've added CWM to builder queue: builder-clockworkmod-com/done?build_id=16f0aab3c75f41c0a46f1aa4fdb4b407

There is a recovery.img file in the archive (open the .tar with winrar).

it made my day, can confirm that manual root works

By uploading this file I can void some flag or triangle or it is with samsung signature ?
PS I know root is nonlegal

I've dumped boot.img and I'll try to create recovery later today.
Partition table for reference:
Code:
major minor #blocks name
253 0 153600 zram0
179 0 7634944 mmcblk0
179 1 1024 mmcblk0p1
179 2 20480 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 2048 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 10240 mmcblk0p9 - kernel
259 2 10240 mmcblk0p10 - recovery
259 3 2048 mmcblk0p11
259 4 6144 mmcblk0p12
259 5 32768 mmcblk0p13
259 6 6144 mmcblk0p14
259 7 6144 mmcblk0p15
259 8 256 mmcblk0p16
259 9 2048 mmcblk0p17
259 10 204800 mmcblk0p18
259 11 1510400 mmcblk0p19 - system
259 12 51200 mmcblk0p20
259 13 5730304 mmcblk0p21 - data
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
Well, I tried. Any idea why I get this after trying to boot freshly compiled recovery? Is bootloader locked or what?
Normal boot logo byt with red exclamation mark in the top left corner and then nothing.
i-imgur-com/32XyqR5.jpg
EDIT: Trying again, will post results. Here is my recovery.fstab:
Code:
# mount point fstype device [device2]
/tmp ramdisk
/efs ext4 /dev/block/mmcblk0p2
/boot emmc /dev/block/mmcblk0p9
/recovery emmc /dev/block/mmcblk0p10
/cache ext4 /dev/block/mmcblk0p18
/system ext4 /dev/block/mmcblk0p19
/preload ext4 /dev/block/mmcblk0p20
/data ext4 /dev/block/mmcblk0p21
/sdcard vfat /dev/block/mmcblk1p1

mstefanski1987 said:
I've dumped boot.img and I'll try to create recovery later today.
Partition table for reference:
Code:
major minor #blocks name
253 0 153600 zram0
179 0 7634944 mmcblk0
Well, I tried. Any idea why I get this after trying to boot freshly compiled recovery? Is bootloader locked or what?
Normal boot logo byt with red exclamation mark in the top left corner and then nothing.
i-imgur-com/32XyqR5.jpg
Click to expand...
Click to collapse
Maybe because your recover is not valid ( samsung signature )
Like in my question above.
If you upload sm-g386f_root.tar you will have red exclamation ? or something else ?

No, everything worked ok.

After uploading of this file all work fine, root working, but in samsung phone info app we have "Bootloader version: unknow". But I think, after reflash of original ROM it will be overwrited.

freb123 said:
There is a recovery.img file in the archive (open the .tar with winrar).
Click to expand...
Click to collapse
There is but flashing it won't get you to CWM recovery (or I am doing something wrong). That's why I am trying to compile ClockWorkMod on my own.
I have little to none experience with compiling anything for android (built sony xperia j kernel from sources once). So far I've managed to fail once - compiled CM11 CWM instead of CM 10.1 and without modyfing recovery.fstab, which I presumed would be autogenerated from boot.img. I've fixed thoe mistakes and I will try to compile it again today.
In the meantme I've found that little red exclamation mark signifies that the device has been rooted at least once, so I guess it is not a problem to boot custom recovery once I get compiling it right.
Many fails are inbound, as I learn all the things along the way. Wish me luck.

mstefanski1987 said:
Figured it out, I had to change extension from .tar.md5 to .tar.
MANUAL ROOT METHOD IS WORKING.
Click to expand...
Click to collapse
Thank you very much, manual root method is really working if you rename the file ! For me this is the only root method that works :good: (root method with chimera tool does not work for me (device is listed as "unknown") )

mstefanski1987 said:
Figured it out, I had to change extension from .tar.md5 to .tar.
MANUAL ROOT METHOD IS WORKING.
Click to expand...
Click to collapse
Thank you very much!
I've put this into the initial post

Core 4G - Best price now
In France the Samsung Core 4G is at 119 euros
Compared to Wiko Kite or Archos 45 HELIUM 4G, I'd like to buy that one.
But, the best configuration would be with the last kitkat OS.
So, I'd like to root, install if possible CyanogenMod...
If I understand all the discussion, it seems to be possible to root it (possible for France ?)
Can we install CyanogenMod ?

eleger91 said:
If I understand all the discussion, it seems to be possible to root it (possible for France ?)
Can we install CyanogenMod ?
Click to expand...
Click to collapse
Salut. Oui le root est possible (la méthode manuelle semble bien marcher), par contre il n'y a pour l'instant ni custom recovery, ni rom kitkat.
Root is possible (manual method is ok) but no custom recovery and no kitkat rom.

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