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.
Dear all,
Currently my WhatsApp is behaving strange. After a forced or manual reboot I often get this message (see attachment) when I open WhatsApp. Earlier I tried to backup and restore my history but with over 1000 new messages a day this isn't going to work at all.
EDIT: I had 4 backups:
15:00 - Whatsapp - GOOD
15:00 - TB - Whatsapp - GOOD
16:50 - NAND (before reboot) - GOOD
16:51 - Phone \data\data\com.whatsapp\databases (after reboot) - BAD
16:51 - TB - Whatsapp (after reboot) - BAD
I found out that my phone at \data\data\com.whatsapp\databases was almost empty (mgstore.db (1kb), axolotl.db, wa.db) while the NAND backup showed more files and a very large mgstore.db file. I restored it and it works again. But can anyone tell me what happened?
I'm using a Google Nexus 5 with the following:
ROM: Pac Man Rom
PAC: KK RC-3 dev
Android: 4.4.4
Baseband: M8974A-2.0.50.1.16
kernel: 3.4.0-cyanogenmod-gb4379ab [email protected] #1 tue nov 4 07:55:41 CET 2014
Buildnr: pac_hammerhead-userdebug 4.4.4 KTU84Q eng.build.20141104.74602 test keys
Hi,
Just with accident I've downloaded (probably) latest Allview X2 Xtreme OTA Update, some props:
Code:
ro.build.version.incremental=1447143781
ro.build.version.security_patch=2016-02-01
ro.build.date=Thu Jul 7 19:18:13 CST 2016
ro.build.flavor=full_gionee6795_lwt_l1-user
ro.build.description=full_gionee6795_lwt_l1-user 5.1 LMY47I 1447143781 release-keys
ro.build.fingerprint=ALLVIEW/X2_Soul_Xtreme/X2_Soul_Xtreme:5.1/LMY47I/1447143781:user/release-keys
ro.gn.extvernumber=X2_Soul_Xtreme_0301_V5894
scatter (just in case for someone):
Code:
preloader 0x0
pgpt 0x0
proinfo 0x80000
nvram 0x380000
protect1 0x880000
protect2 0x1280000
seccfg 0x1c80000
lk 0x1cc0000
boot 0x1d20000
recovery 0x2d20000
secro 0x3d20000
para 0x4320000
logo 0x43a0000
frp 0x4ba0000
expdb 0x4ca0000
tee1 0x56a0000
tee2 0x5ba0000
system 0x6800000
cache 0xba000000
userdata 0xd4800000
flashinfo 0xFFFF0084
sgpt 0xFFFF0004
Download Link: https://mega.nz/#!U4FUyASA!uiFckL5WhK81W8cIDdo2qFp7WWYM9UA-9zkPVKBVlk8
Not updated yet, first unofficial twpr recovery for my phone shows ro.product.device as BLU Pure XL so it wont start
Code:
getprop("ro.product.device") == "X2_Soul_Xtreme" || abort("This package is for \"X2_Soul_Xtreme\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Just flashed latest twpr 3.0.2.0 - it shows "x2xtreme" -.-
@bemolx setprop has no effect in twpr btw!
Time to go to work, I'll try flash it later.
Hey I have the same problem. When I try to flash I get the error "This package is for "X2_Soul_Xtreme" devices, this is a "BLU_PURE_XL".
My phone is an Allview X2 Soul Xtreme !
I've edited the zip and changed everywhere I've found "X2_Soul_Xtreme" with "BLU_PURE_XL", but I still get that error.
What should I do?
Ok, found the answer on some one plus thread dealing with a this issue (I can't copy paste the link)
you have to change the update-script with a notepad.
unzip the boeffla kernel .zip archive, find out the file "update-script" and edit it using a notepad.
replace all "OnePlus2" instances with "oneplus2", save the file, zip it again and flash it.
Click to expand...
Click to collapse
Good morning, can i flash this rom to my blu pure XL? I am rooted, as i understand, i just need to modify the text file, correct? Is this the original chinese rom?
Should i flash using twrp? I have the twrp that is on the root guide in the general thread.
Best Regards.
Gnufan
Hi Cyrax2008,
Short questions related to your X2 Soul Xtreme:
- how many hours/days is your phone/battery able to sustain?
- how would you define your phone usage on a 0 to 5 scale: 0 being mostly calls and some web browsing, 5 being heavy YouTube and games usage?
I'm asking this because my brand new phone can handle 20 hours of phone calls + some google searches and web browsing. If I would watch YouTube it would handle about 4.5 - 5 hours.
Also did you tried to install a more later Android image, like 7.1 or 8.0? If yes: was it successful?
Thank you! Razvan.
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 !?
Hello guys,
I recently encountered a problem regarding creating scatter file for my Android device through mtk droid root and tools v2. 5
3
My device specifications: -
Micromax canvas tab P681
Hardware: - MT8321(CPU-Z detects it as MT6580)
Baseband version: - MOLY. WR8. W1449. MD. WG. MP. V61, 2016/03/10
Android version: - 6.0
Build number: - MMX_P681_SW_V2.2_HW_V1.2_10092016
Kernel version: - 3. 18. 19
[email protected] #2
sat Sep 10 15: 59 CST 2016
Serial number: - PX06X67260101238
I want to create a scatter file for this device. Mtk droid tools detect my device as unstable ROM and cannot backup. I need it because to create CWM recovery for my device. My device does not allow to root, I tried kingroot, kingoroot, iroot, mtk droid tools and everything failed to root. So I need help to create scatter file or if there are any other ways to root it. Thx in advance
Find here: usehelp.org/%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D1%8B-%D1%81%D0%BE%D1%84%D1%82-%D0%B8%D0%BD%D1%81%D1%82%D1%80%D1%83%D0%BA%D1%86%D0%B8%D0%B8/%D0%B8%D0%BD%D1%81%D1%82%D1%80%D1%83%D0%BA%D1%86%D0%B8%D0%B8/scatter-%D1%84%D0%B0%D0%B9%D0%BB%D1%8B-%D0%B4%D0%BB%D1%8F-%D1%81%D0%B1%D1%80%D0%BE%D1%81%D0%B0-frp-%D0%BD%D0%B0-%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0%D1%85-mtk/