[Q&A] [v9.52] Online Nandroid / Nandroid Backup without re-booting [CWM + TWRP + 4EX
Q&A for [v9.52] Online Nandroid / Nandroid Backup without re-booting [CWM + TWRP + 4EXT]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [v9.52] Online Nandroid / Nandroid Backup without re-booting [CWM + TWRP + 4EXT]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hey everybody,
I was setting up online Nandroid on my S4Mini LTE (I9195) and everything looks good so far. Except that preload is not being backup-ed. I also installed the the required recognition script. When using TWRP via recovery I am able to backup the preload partition.
Any ideas why I cannot backup the preload partition online?
Thanks,
Sebastian
bjacke said:
Hey everybody,
I was setting up online Nandroid on my S4Mini LTE (I9195) and everything looks good so far. Except that preload is not being backup-ed. I also installed the the required recognition script. When using TWRP via recovery I am able to backup the preload partition.
Any ideas why I cannot backup the preload partition online?
Thanks,
Sebastian
Click to expand...
Click to collapse
Which recognition script did you install?
ameer1234567890 said:
Which recognition script did you install?
Click to expand...
Click to collapse
Hey,
I used "Samsung Galaxy S IV Mini LTE GT-I9195" ->serranolte. Is this the correct one?
Basti
bjacke said:
Hey,
I used "Samsung Galaxy S IV Mini LTE GT-I9195" ->serranolte. Is this the correct one?
Basti
Click to expand...
Click to collapse
Could you post the log file inside one of the backup folders?
Hey.
I've got problem. Lg l7II, sock kk rom rooted. I can't make backup on my external_SD, set in onb settings backup location external_SD, but backup still is created ie my internal memory. I know, that android kk not allow save files external micro sd card for third-party apps, but i've installed sd fix. but without result. So where is wrong?
Here's log:
Starting backup...
Running with the following commands: -o --custom kk_rooted --storage /external_sd -pd -r
Using Default Shell
##########################################
Online Nandroid Backup v9.52
* A tool to perform a nandroid backup
without booting into recovery.
* It is fully compatible with nandroid.
* Type 'onandroid --help' for usage
instructions.
* Created by Ameer Dawood
##########################################
14:30:44 Using busybox from: /data/data/com.h3r3t1c.onnandbup/files/busybox
14:30:44 Checking for root permissions...
14:30:44 Root permissions acquired!
14:30:44 Analysing battery level...
14:30:44 Sufficient battery available!
14:30:44 Checking version of BusyBox installed...
14:30:44 BusyBox version 1.20 or above installed!
14:30:44 Searching for SD card...
14:30:44 SD card found!
14:30:44 This device has a patch file installed!
14:30:44 Checking for required tools...
14:30:45 All required tools available!
14:30:45 Checking disk space...
14:30:45 SD Card Free Space: 1186 MB
14:30:45 Required Space: 1719 MB
14:30:46 Not enough disk space! Exiting...
exitcode [86]
Kura pazurem to wydrapała, a Xperia Neo V Tapatalkiem 4 wysłała
Ok, problem solved. It was mistake with backup save location. After changing to /storage/external_SD instead external sd, it working as it should.
Wysłano przy użyciu LG L7 II (P710) Tapatalkiem
Patch or No Patch - That Is the....
Help!
Folks, I have one, perhaps-challenging question, and I am hoping that there will be a fairly straightforward answer from one or more of the obviously-above-average-intelligence contributors to XDA.
I recently purchased a Foxconn house-branded phone, an 'InFocus M512'. I had only.moderate expectations - you usually get what you pay for - but, it has exceeded my expectations from almost every angle. However, it arrived already-rooted. And now that I've invested some hours (I'm embarrassed to admit how many) investigating and installing security/privacy apps and mods, and debloating it, I'm really satisfied and it's no longer the cheap throwaway I had originally purchased... and given how many changes I've already made, it's pure luck that I haven't bricked it; I'm waaaay overdue for a full NAND backup.
But, I have no recoveries for it, I have no idea how it was rooted or what magic was thrown at it before it landed in my inexperienced hands. It's KK 4.4.2 - that much I do know. And the launcher is a lightly themed MIUI, as far as I can tell.
I installed Online Nandroid, looking like my best / only option to create a recovery.
I clicked on the 'Get Device Identified' button in Nandroid, which returned a device code MC2_CN - not in the downloaded patch list, of course. So, then I clicked on the 'Request a patch from Santa Claus' button...
I'm not holding my breath, waiting for Ameer to come up with a patch for me; I'm sure he has bigger fish to fry, and this phone is just one in the sea of obscure Chinese mutations (that's an actual place, I think).
So... here it is... finally... my question:
What's my next step?
Is there one? (Oh crap, that's two questions) Have I been too wordy? (Damn, that's three... and don't answer it - you'll hurt my feelings.
Any informed advice would be hugely appreciated.
Thanks. :fingers-crossed:
Is this app currently maintained? I thought I would help out and sent in a patch weeks ago for my device (LG Realm) and never heard anything back. I also never got a response as to whether or not I can somehow load and use my own patch with the correct partition layout instead of having to download it.
????
codebot said:
Is this app currently maintained? I thought I would help out and sent in a patch weeks ago for my device (LG Realm) and never heard anything back. I also never got a response as to whether or not I can somehow load and use my own patch with the correct partition layout instead of having to download it.
????
Click to expand...
Click to collapse
It is still being maintained. The pace is, however, a bit slower.
Nandroid Backup for UBIFS
Sir regarding for NANDROID BACKUP it could be work in this UBIFS device?
ameer1234567890 said:
It is still being maintained. The pace is, however, a bit slower.
Click to expand...
Click to collapse
I'm willing to do any testing for an updated SM-N910T. Please just let me know.
Sent from my Note 4 with Tapatalk
SJMarty said:
I'm willing to do any testing for an updated SM-N910T. Please just let me know.
Sent from my Note 4 with Tapatalk
Click to expand...
Click to collapse
Yikes...has the script been abandoned? That would stink.
Does Online Nandroid Backup work for Alcatel OT 5020D?
I tried to restore some apps with a Nandroid Manager and even if the app didn't show any error, none of the restored apps worked. After trying to run them they always crashed.
Not boot found not recovery found
Hi, i tried these script for my Xperia Neo mt15i, in your site in the list of supported devices says that no need of path file for my hallon but during the backup appears this message, and i don't know what is wrong, Online Nandroid makes appslog .android_secure system data cache, but it's strange no boot, recovery, and bootloader. It's something wrong?
elasca said:
Hi, i tried these script for my Xperia Neo mt15i, in your site in the list of supported devices says that no need of path file for my hallon but during the backup appears this message, and i don't know what is wrong, Online Nandroid makes appslog .android_secure system data cache, but it's strange no boot, recovery, and bootloader. It's something wrong?
Click to expand...
Click to collapse
Can you post the log file inside backup folder?
ameer1234567890 said:
Can you post the log file inside backup folder?
Click to expand...
Click to collapse
Online Nandroid v9.52
Started at Sun May 3 00:58:58 CEST 2015
###########################
Run with options:
###########################
Busybox: BusyBox v1.21.1-jb static (2013-07-25 21:23 +0100) multi-call binary.
###########################
File System Layout:
rootfs on / type rootfs (ro,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock0 on /system type yaffs2 (ro,seclabel,relatime)
/dev/block/mtdblock3 on /data type yaffs2 (rw,seclabel,nosuid,nodev,relatime)
/dev/block/mtdblock1 on /cache type yaffs2 (rw,seclabel,nosuid,nodev,relatime)
/dev/block/vold/179:1 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /storage/sdcard0/.android_secure type tmpfs (ro,seclabel,relatime,size=0k,mode=000)
###########################
Device Details:
ro.product.model=MT15i
ro.product.brand=SEMC
ro.product.name=MT15i
ro.product.device=hallon
ro.product.board=mogami
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony Ericsson
###########################
Recovery:
CWM-based Recovery v6.0.4.6
###########################
Language File:
Not found!
###########################
00:58:59 Using busybox from: busybox
00:58:59 Checking for root permissions...
00:58:59 Root permissions acquired!
00:58:59 Analysing battery level...
00:58:59 Sufficient battery available!
00:58:59 Checking version of BusyBox installed...
00:58:59 BusyBox version 1.20 or above installed!
00:58:59 Searching for SD card...
00:58:59 SD card found!
00:58:59 This is an MTD based device!
00:59:00 Checking for required tools...
00:59:00 All required tools available!
00:59:01 Checking disk space...
00:59:02 SD Card Free Space: 4159 MB
00:59:02 Required Space: 839 MB
00:59:02 Necessary disk space available!
00:59:02 Detecting mountpoints to exclude...
00:59:02 Backing up to /storage/sdcard0/clockworkmod/backup/2015-05-02.22.58.59
00:59:02 /boot not found! Skipping backup of /boot!
00:59:02 Consider installing patch file for your device, for a complete nandroid!
00:59:02 /recovery not found! Skipping backup of /recovery!
00:59:03 Backing up /appslog...\c
00:59:05 Backing up /system...\c
01:04:01 Backing up /data...\c
01:11:01 Backing up /cache...\c
01:12:02 Backing up /.android_secure...\c
01:12:12 Generating md5sum...\c
01:13:04 Verifying md5sum...\c
01:13:05 Online Nandroid Backup Completed in 14 minutes 6 seconds!
###########################
Files Backed-up:
"----rwxr-x 1 1536 May 3 01:12 .android_secure.vfat.tar
----rwxr-x 1 6291456 May 3 00:59 appslog.img
----rwxr-x 1 96431808 May 3 01:12 cache.yaffs2.img
----rwxr-x 1 373038336 May 3 01:10 data.yaffs2.img
----rwxr-x 1 258 May 3 01:13 nandroid.md5
----rwxr-x 1 421466496 May 3 01:04 system.yaffs2.img"
@elasca This is common among Xperia devices. Your backup should just be fine. Your custom recovery (CWM / TWRP) would also not backup boot and recovery.
ameer1234567890 said:
@elasca This is common among Xperia devices. Your backup should just be fine. Your custom recovery (CWM / TWRP) would also not backup boot and recovery.
Click to expand...
Click to collapse
Do you know an alternative method to back up these partitions? I don't see these partitions even on terminal, it should be showed using "cat /proc/partitions" command, but only shows system, cache, appslog, data, and sdcard, no recovery, boot, bootloader, and other partitions showed in my Wolder tablet with Allwinner chipset.
I have also the question for these tablet, i can backup recovery and boot partitions manually but with nandroid appears "boot not found" and "recovery not found", are you working for a patch file for this tablets?
Thank you.
ameer1234567890 said:
@elasca This is common among Xperia devices. Your backup should just be fine. Your custom recovery (CWM / TWRP) would also not backup boot and recovery.
Click to expand...
Click to collapse
Hi ameer just wanted to thank you for still supporting the app . And for uploading the patch for my Lg tribute aka e2nas. I thought it was a dead issue ,im glad you brought it back to life!!
sent from my VM LGLS660 rooted on zv5
Related
This is a Custom CWM-Based Recovery 5.0.2.7 for HTC FlyerCredits and special thanks to Koush and everyone else involved in Cyanogenmod project!
{
"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"
}
for more screenshots check attachments
[ info ]
This Recovery will reside on the /recovery partition of the device and will give you lots more features than any existing recoveries for this device...
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
Team Revolutionary - for the initial CWM4 recovery... i have used the recovery.fstab and HTC charger from their recovery-ramdisk
Napstar - my teammate (Team UtterChaos) for his work on implementing touch based interface
sztupy - for his work on SteamMOD recovery (the core touch interface is based on his work)
[ Requirements ]
S-OFF device
HoneyComb version
WiFi Flyer only????
CWM4 Recovery (by Team Revolutionary)
[ features ]
now featuring Touch based navigation interface!
features derived from CWM5
ability to backup & restore to/from internal SDCARD
ability to flash custom update.zip from internal SDCARD
faster .TAR backups (backups created using this new recovery MAY NOT BE COMPATIBLE with older CWM4)
my additions
changes to graphics (ported some graphics from CWM5.5 ICS edition)
revamped layout for recovery menu (to improve navigation) [renamed few options and changed their order]
changed "wipe data/factory reset" option to just "factory reset", and detailed the partitions which will be wiped
added reboot options
reboot into system
reboot into recovery
reboot into fastboot mode
some modification in "Partition SDCard" section:
put up a confirmation to warn the user that this option will wipe sdcard
added ability to select filesystem when creating new layout
add confirmation to "backup" option in Nandroid menu... it used to keep getting pressed by mistake and start making backups immediately... now it will ask u before starting backup
removed tons of "NO"s from some menus...
[ WARNING ]
THIS RECOVERY IS STILL IN TESTING... MAKE SURE THAT U HAVE UR COMPLETE DATA BACKED-UP (INCLUDING SDCARD DATA)...
and incase this doest work correctly make sure that u can restore to factory condition...
"Partition SDCard" option in CWM5 WILL WIPE UR EXTERNAL SDCARD!!!
I have only tested it to work on my WIFI Flyer... please check if it works for the 3G version... if 3G version uses a different partition table THEN DO NOT USE IT ON 3G VERSION!
[ how to install this recovery ]
download the recovery package (its an update.zip)
place the downloaded package on external SDCARD
reboot into recovery and flash this package
thats it! new recovery will now be installed
[ how to get back to Team Revolutionary's CWM4 Recovery ]
download the Team Revolutionary's CWM4 Recovery package (its an update.zip)
place the downloaded package on external SDCARD
reboot into recovery and flash this package
thats it! old recovery will now be installed
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ download links ]
[FLYER][HC] CWM-Based Touch Edition Recovery 5.0.2.7 by DooMLoRD (v02)
MD5HASH: c05da93ec4744eaffcc6f440691c8790
[Flyer][GB] CWM-Based Touch Edition Recovery 5.0.2.7 by DooMLoRD (v02)
MD5HASH: 91bf21aa8ddb4fc8504b8103942c957f
[FLYER] CWM-Based Recovery 5.0.2.7 by DooMLoRD (v01) < OLD NON-TOUCH >
MD5HASH: 68470906ea654d6c9cff88930d5e7480
Team Revolutionary's CWM4 Recovery
KINDLY DO NOT MIRROR MY FILES
please do intensive testing and let me know!
enjoy!!!
reserved for later
i need people to test this recovery out and give me feedback asap.. because i am working on a TouchEdition recovery which will be based on this...
so do let me know how this works out!
DooMLoRD, can you confirm that you have off-mode charging working properly? Having a recovery that doesn't is not a good situation to get into in a device with no removable battery.
globatron said:
DooMLoRD, can you confirm that you have off-mode charging working properly? Having a recovery that doesn't is not a good situation to get into in a device with no removable battery.
Click to expand...
Click to collapse
the necessary files for that are already in place...
may be someone can help test that...
additionally: is the partition layout on GB different? and waht abt the 3G version?
Reserved for me at the moment
Will give it a try and post here + stuff from other posts
Thanks a lot... Great idea
Sent from my HTC Flyer P510e using xda premium
EDIT:
OK just chose to install your zip in CWM - successful
Phone is rebooting... to android, not back to recovery - booting since 5 minutes
(no bootloop - HTC quietly brilliant logo visible)
EDIT2:
pressed power - powered down (vibrated once) booting again
Coolexe´s rom with your kernel just successfully started
will reboot soon to bootloeader check your stuff
EDIT3:
got into your recovery... old backups still there
Rebooted from recovery to Androd without problems now
just the first boot after installing your recovery was a hangup solved by pressing power button untill manual reboot
ALL OK
HTC Flyr 32GB 3G
globatron said:
DooMLoRD, can you confirm that you have off-mode charging working properly? Having a recovery that doesn't is not a good situation to get into in a device with no removable battery.
Click to expand...
Click to collapse
i think its charging:
i just need the recovery.img from GB (wifi/3g) & HC (3g) versions to add support for them...
I have a 3G Flyer running HC; how might one find the partition layout information you need?
Dunno if this is any help:
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p29 /data ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p30 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p31 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/data/d /data/d debugfs rw,relatime 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=0202,
allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=
0202,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:65 /mnt/sdcard/ext_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmas
k=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.robotinvader.knightmare-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=
0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/mainwood.android.rushhourfree-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmas
k=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
fdisk -l shows exactly nothing; /proc/mtd is empty. :S
DooMLoRD said:
the necessary files for that are already in place...
may be someone can help test that...
additionally: is the partition layout on GB different? and waht abt the 3G version?
Click to expand...
Click to collapse
On the GB (2.23.405), 3G device it didn`t start, i got a white screen.
---------- Post added at 07:46 PM ---------- Previous post was at 07:42 PM ----------
DooMLoRD said:
i think its charging:
i just need the recovery.img from GB (wifi/3g) & HC (3g) versions to add support for them...
Click to expand...
Click to collapse
Here is the recovery that works with GB (http://www.multiupload.com/0X989UZK3J )
porcupineadvocate said:
I have a 3G Flyer running HC; how might one find the partition layout information you need?
Click to expand...
Click to collapse
i need the recovery.img which works for ur device...
mohamed_moscow said:
On the GB (2.23.405), 3G device it didn`t start, i got a white screen.
---------- Post added at 07:46 PM ---------- Previous post was at 07:42 PM ----------
Here is the recovery that works with GB (http://www.multiupload.com/0X989UZK3J )
Click to expand...
Click to collapse
the version u quoted is for 3G GB version of flyer right?
DooMLoRD said:
i need the recovery.img which works for ur device...
the version u quoted is for 3G GB version of flyer right?
Click to expand...
Click to collapse
yes. that is for GB 3G/Wifi version.
mohamed_moscow said:
yes. that is for GB 3G/Wifi version.
Click to expand...
Click to collapse
so there is a common recovery for 3g/wifi versions in GB?
yes, i think so.
DooMLoRD said:
so there is a common recovery for 3g/wifi versions in GB?
Click to expand...
Click to collapse
Yes, layout is the same, sizes may differ, but that doesn't matter so log as the partitions reside at the same device path.
---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------
additionally: is the partition layout on GB different? and waht abt the 3G version?
Click to expand...
Click to collapse
The partitions are the same layout but the kernel offsets are different, you'll need a GB kernel for GB and HC for HC.
ok so from what i see, comparing the 3G-GB with WIFI-HC versions of CWM4 recovery from Team Revolutionary, is that the ramdisk (recovery.fstab i.e. partition table info) is the same on both these versions...
so i think..
3G/WIFI versions use same partition table
to have GB/HC versions i just need corresponding zImage
can someone confirm this?
if the above is true then the version i have posted in 1st post (HC-WIFI version) will work on HC-3G too...
DooMLoRD said:
i think its charging:
i just need the recovery.img from GB (wifi/3g) & HC (3g) versions to add support for them...
Click to expand...
Click to collapse
Sorry, I wasn't very clear on what I said earlier. I meant off-mode charging. Device powered off and charger plugged in. The recovery is used to handle this charging mode. The use case which is of particular concern is what happens if the battery goes completely flat. I'd suggest the test is to be charged about 50% power off and plug into wall charger for 30 minutes or so and then check the charge level. I can't test it myself right now because I'm working on other things on my flyer.
globatron said:
Yes, layout is the same, sizes may differ, but that doesn't matter so log as the partitions reside at the same device path.
---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------
The partitions are the same layout but the kernel offsets are different, you'll need a GB kernel for GB and HC for HC.
Click to expand...
Click to collapse
oh ok...
i use the offset: 0x14400000 for the HC recovery/kernel
whats the offset for GB?
globatron said:
Sorry, I wasn't very clear on what I said earlier. I meant off-mode charging. device powered off and charger plugged in. The recovery is used to handle this charging mode.
Click to expand...
Click to collapse
that isnt directly related to recovery...
that should be taken care by bootloader or main kernel...
ALL OK
Flyer 32GB 3G Honeycomb
more details in post 6 -LINK
DooMLoRD said:
oh ok...
i use the offset: 0x14400000 for the HC recovery/kernel
whats the offset for GB?
Click to expand...
Click to collapse
0x4400000 ( same without the 1 )
---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------
DooMLoRD said:
that isnt directly related to recovery...
that should be taken care by bootloader or main kernel...
Click to expand...
Click to collapse
Nope, it's recovery on HTC devices, we had loads of problems with pyramid and a few others when revolutionary was first released.
globatron said:
0x4400000 ( same without the 1 )
---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------
Nope, it's recovery on HTC devices, we had loads of problems with pyramid and a few others when revolutionary was first released.
Click to expand...
Click to collapse
okay i will post test GB kernel with new recovery
and if its related to recovery then its already working... please verify it urself when u get time
ROM is discontinued for VIEW, use YNC's latest update
DextersJB
i would test it out but i gotta charge my view its been dusty since i got my N7 lol
Thank you!
first.. thank you for trying to save VIEW.. there is no much going on here. but if you can save our dying VIEW, even slight attempt is greatly appreciated.
I will test this. I am kind of new on tablet but I will test and report back to you. here we go..:good:
Dexter_nlb said:
i would like to see if i can utilize the JB on View.
for this i have changed the kernel and partitions(removed those i do not know atm).
and uploading my test image for someone to test. Download it here MD5 06096eea121b5ec534830fcf97072fc4
HC hboot is required here, GB boot is not supported.
please if someone can help and test it, it will be great.
REMEMBER to factory reset, before installing this rom
I would also like to see a "mount" output run in as shell. so i know what partitions are different, besides /system i know for now.
Click to expand...
Click to collapse
myowin said:
first.. thank you for trying to save VIEW.. there is no much going on here. but if you can save our dying VIEW, even slight attempt is greatly appreciated.
I will test this. I am kind of new on tablet but I will test and report back to you. here we go..:good:
Click to expand...
Click to collapse
it if dos not boot at first try (showing a X after 20-30 seconds)..
maybe change the /system/build.prop in the zip.
replace everything you see in th build.prop with "flyer" with "express" .
save it and copy it back into the zip and replace the original one.
in the /system/lib/hw , rename files you see with "flyer" in the name, replace that with "express" too. ie lights.express.so
flash it once more and see if it helps.
Pulled, will try in about an hour when she charges back up. Apparently I left my wifi on..seems to drain a little more in ICS.
Will report back
Dexter_nlb said:
I would also like to see a "mount" output run in as shell. so i know what partitions are different, besides /system i know for now.
Click to expand...
Click to collapse
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p26 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /data ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p31 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p34 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/data/d /data/d debugfs rw,relatime 0 0
/dev/block/vold/179:65 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:36 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:36 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
and during installation:
Code:
AROMA INSTALLER version 2.00
(c) 2012 by amarullz xda-developers
ROM Name : FlyerJB-view
ROM Version : 1.0
ROM Author : dexter_nlb
Device : view/express-3g
Start at : Fri Jul 27 16:36:10 2012
script aborted: file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
Installer Error (Status 7)
End at : Fri Jul 27 16:36:10 2012
install finished, rebooted, stuck on white HTC bootscreen.
adb detects the device
Code:
$ ./adb devices
List of devices attached
HT16THY00941 device
but can't connect
Code:
$ ./adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
thanks,
just what i needed here.
Sounds cool. From what I have read we will lose Flash if we go to JB. Is this correct?
Stopping support for Flash by Adobe now in favor of HTML5 is sort of like closing all gas stations in favor of electric. Great idea, terrible timing. HTML5 is nowhere near ubiquitous.
** Ring up yncconsulting. I'm sure he would want to help on this.
boastt said:
and during installation:
Code:
AROMA INSTALLER version 2.00
(c) 2012 by amarullz xda-developers
ROM Name : FlyerJB-view
ROM Version : 1.0
ROM Author : dexter_nlb
Device : view/express-3g
Start at : Fri Jul 27 16:36:10 2012
script aborted: file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
Installer Error (Status 7)
[/QUOTE]
can you replace META-INF\com\google\android\updater-script
in the zip you downloaded first with the updater-script in the zip attached to this post and try again.
the reboot is because it probably only wiped, but not unpacked anything to the partition.
Click to expand...
Click to collapse
Dexter_nlb said:
can you replace META-INF\com\google\android\updater-script
in the zip you downloaded first with the updater-script in the zip attached to this post and try again.
the reboot is because it probably only wiped, but not unpacked anything to the partition.
Click to expand...
Click to collapse
Done. Install went smooth. Theres a long delay waiting for a sim card, then the "Insert SIM card" shows up with a "skip" button.
Overall, it seems pretty solid for what it should be.
Compared to your thread for the flyer: mic doesn't work, GPS seems to not even exist on the device, using that UMS doesn' work, if scrolling in chrome is part of the 2d hardware acceleration then it feels slow
boastt said:
Done. Install went smooth. Theres a long delay waiting for a sim card, then the "Insert SIM card" shows up with a "skip" button.
Overall, it seems pretty solid for what it should be.
Compared to your thread for the flyer: mic doesn't work, GPS seems to not even exist on the device, using that UMS doesn' work, if scrolling in chrome is part of the 2d hardware acceleration then it feels slow
Click to expand...
Click to collapse
thanks for the confirmation, no matter if its good or bad.
i believe its possible to make a generic edition and let the installer detect which parts belong to which hardware.
ill look into that.
the hardware issues, probably relate to the files /system/lib/hw where light/sensor/gps is for the flyer and probably differ from the view edition.
for the mic part, i believe those files are for flyer, which needs to be view specific as well.
anyways, thanks, its good to know it can be made working on view as well.
quick search on google, shows that Chrome is not as fast as stock browser, which might be was regular chrome users experience? JB is new and not all apps are adapted? maybe thats why this keeps coming back as being a problem, but might not be a build problem, but Chrome being less compatible.
mitchellvii said:
Sounds cool. From what I have read we will lose Flash if we go to JB. Is this correct?
Stopping support for Flash by Adobe now in favor of HTML5 is sort of like closing all gas stations in favor of electric. Great idea, terrible timing. HTML5 is nowhere near ubiquitous.
** Ring up yncconsulting. I'm sure he would want to help on this.
Click to expand...
Click to collapse
You can still use flash. You just cannot download it from the market but the ICS version works just fine.
In what ways is JB significantly better than ICS or GB in order to sacrifice some functionality to run it in your opinion? Not snarking here - I really would like to know.
In my personal experience, GB on this tablet is just fine. It can be overclocked and everything works, but of course I'd love the latest and the greatest if there is some noticeable performance pop.
"Not snarking here" - ehum.
mitchellvii said:
In what ways is JB significantly better than ICS or GB in order to sacrifice some functionality to run it in your opinion? Not snarking here - I really would like to know.
In my personal experience, GB on this tablet is just fine. It can be overclocked and everything works, but of course I'd love the latest and the greatest if there is some noticeable performance pop.
Click to expand...
Click to collapse
its all just a challenge and development tests/teasers.. for some it can easily be a daily driver, for others too much is definately not working.
I do not have it for the pen, so thats no priority personally.
but media playback for me, can be important, for now i just switch to SD when im on youtube.
but generally, there is alot of difference in the drivers and how framework and JB differs, i do not want to repeat , but it is for better, if just we can make more work better.
JB/ICS is alot better experience especially comparing our less good HC adaption.
JB kills GB. i'm running JB on my nexus and it's SO quick!
thanks for your hard work here, i hope we can get something running! we sort of have an ICS rom, but JB is what ICS should have been from the start..i'm pumped!
Yeah HC was pretty lame. Its really too bad the way HTC just completely abandoned what was an expensive device at the time.
I have a pen but really don't use it much anymore anyway. 7 inch tablet is just a little too small to comfortably write on anyway. I guess for me fast internet browsing and solid Netflix are the most important things.
Sent from my SPH-D710 using Tapatalk 2
Great work. I'm interested in testing once I can flash in a normal fashion (not sure how to switch out the zip file etc.)
Sent from my PG41200 using xda app-developers app
Thanks for the development of JB on the view, been thinking of trying to port some of the roms from the flyer lately. I'm not much of a developer so the fresh thread here is greatly appreciated.
Sent from my PG86100 using xda app-developers app
Runs great so far! A few minor issues but won't take much to iron out.
Device: Arnova Gbook (ereader)
OS: Android 4.0.3
Kernel version: Linux 3.0.8
I was using my tablet at an airport and everything was fine before I shutoff my phone for the flight to take off. I turned it back on once the plane reached cruising altitude. I got an indicator that my SD card was damaged, which makes no absolutely no sense. also, my apps disappeared...
Problems are:
-When I connect to PC, tapping "Turn on USB storage" nothing happens, only the lile circle indicates that it is doing something but it does nothing...
-Settings>Storage: "Unfortunately, Settings has stopped."
next to the clock it says "Damaged SD card. SD card damaged, you may have to reformat it." There is not SD card in the slot, but it still says this.
-Cannot push an SD card into the slot: It doesnt stay there even if i push it to the maximum inside. No "click sound" either.
-Cant do anything only using the internet, internal storage is not reachable in any way thus i cant install newer rom too.
Did a factory reset (Settings>factory reset) but couldnt help, still the same... I beg you guyz for your help!
Anyone?
up
...having the Same Problem
dyingsoulwow said:
up
Click to expand...
Click to collapse
So it looks like I'm having the same problem with the same gear. I tried several cures to no avail.
But First the Tech Specs of my Arnova GBook:
Manufactor: VIMICRO
Model: ANGB
CPU: ARMv 7 rev 2 (v7l)
Memory: RAM 337, ROM 0.91, SDCard 0 MB (at the Moment more to that later)
Android: 4.0.3
BuildID: generic_vortex-userdebug 4.0.3 IML74K 1.0 test-keys
Linux Version: 3.0.8-vimicro([email protected]) (gcc Version 4.4.3)
I copied some files to the mounted exSDCard (4gb noname) when my tablet suddenly died and the only way to reanimate it was by factory resetting it.
The Problem istself seems to relate to the inability to mount a Nonformated SDCard that i can not format because it is not proberly mounted.
I have no clue how to root the tablet. I tried a set of instruction from a french website, but since i don't speak french i'm not sure if the google translator gave me the right directions.
I tried to mount it the SDCard via terminal. Format it connecting the gbook to an ubuntu box and a lot of system tools available via googles play store.
USB connection shows the drives but I'm not abel to mount or list the contents of it. In general the System is booting up and i am able to install apps from Google Play. Since i can't mount any external devices i am not abel to transfer files via other means because the gbook wants to copy them to the interna SDCard (wich is not available ).
I am looking for any possible solution. If there is an alternate Frimware i will try it.
Thanks in advance for any offered Help!
Lanman99
Still trying...
Any solution i found using Google, Bing and DuckDuckGo seems to require Root Access. Has somebody successfully rooted an Arnova GBook?
Or is there really no possibel solution for a dummy user to fix this problem. It seems to boil down that i cannot mount device mmcblk0 to sdcard because "access denied".
Did anybody face a similar problem and fixed it without root?
Tried several SDCard tools to no avail...
ES File Explorer is showing me that everthing i need is there but still, every try to mount the internal storage is leading to permission denied. I'm stating to love Android
Well if there is no root, is it possible to write a shell script to revive the internal SDCard and run that with elevated rights?
ES File manager is showing the directory entry with 0 MB. Since i am a novice in Android Systems i am just not sure if that means anything.
Maybe i'm wasting my time on a piece of chinaware but this nut i still too tempting to ignore. It's just that with my limited Linux knowlegde it seems that mounting a device and formating it afterward sounds not to troublsome or am i completely lost. After asking Google, bing and some other SEs it is not that uncommon but none of the cures i found worked for my GBook.
What am i missing?
Stil no answer from Arnova on my request for a stockrom Download. Somebody got an Idea where elsee i could find a ROM image for an Arnove GBook or does anybody know if there is an alternative Firmware available?
I was able to connect to my Device via ADB
mount is delivering the following:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
ubi0_0 on /system type ubifs (ro,noatime,no_chk_data_crc,compr=lzo)
ubi1_0 on /data type ubifs (rw,nosuid,nodev,noatime,bulk_read,no_chk_data_crc,compr=lzo)
ubi2_0 on /cache type ubifs (rw,nosuid,nodev,noatime,bulk_read,no_chk_data_crc,compr=lzo)
none on /proc/bus/usb type usbfs (rw,relatime,devmode=666)
The list under /dev/block/vold has three entries:
179:0 179:1 and 7:0
Cat /proc/partitions delivers:
31 0 10240 mtdblock0
31 1 12288 mtdblock1
31 2 120832 mtdblock2
31 3 45056 mtdblock3
31 4 524288 mtdblock4
31 5 1048576 mtdblock5
31 6 262144 mtdblock6
31 7 2169856 mtdblock7
179 0 3909632 mmcblk0
179 1 3905536 mmcblk0p1
Please I am a complete Android Noob. Is there somebody able to guide me to a Point where i can start to patch all this together.
I am able to find pieces here, but i'm not getting the broad picture.
Next try...
using Root Many by Bin4ry http://forum.xda-developers.com/showthread.php?t=1886460 to get into my device I got following results:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.04.2013) v29 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Above file not found warning ARE NOT ERRORS, it is intended to be this way!
Normal Mode enabled!
.
Pushing busybox....
2207 KB/s (1085140 bytes in 0.480s)
Pushing su binary ....
2185 KB/s (380532 bytes in 0.170s)
Pushing Superuser app
2309 KB/s (1468798 bytes in 0.621s)
Making busybox runable ...
.
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
After reboot the gbook is throwing "unfortunately UI has stopped" and "unfortunately settings has stopped". Nothing works until i factory reset it again (at least something i am growing really good at) and I'm back to square one.
Other means of editing files within the system via ADB are only leading to access denied or system is in read only mode.
Any other ideas?
By using Archtablet.com's method: "http://www.arctablet.com/blog/forum/firmware-development/dumping-firmware-on-arnova-g2-arnova-g3-and-other-rockchip-based-tablets/" i tried to get an Firmwareimage. They tried to Help me out but again disaster struck. Ubuntu 13.04 with usblib installed failed to even recognize the GBook. Trying it with Windows and adb i need (what a surprise) root rights.
So next question is: Is there any general way to read out a tablet firmware without rooting or is it always up to the vendor to just screw things to their Liking ?
I know i should quit this beast, but stubborn as ever i keep banging my head against the wall .
Lanman99
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
munjeni said:
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
Click to expand...
Click to collapse
and probably now guys with locked bootloader can boot roms requiring custom kernels
DevSwift1 said:
and probably now guys with locked bootloader can boot roms requiring custom kernels
Click to expand...
Click to collapse
NO because kernel need enabled kexec and reguire some other modifications whick is not exist on stock kernel!!!
Tried to boot stock kernel but failed, seems not stable kexec by now! Need help!
Here is kernel changes (3 commits by Aug.09.2013) -> https://github.com/munjeni/android_kernel_xperiago/commits/jb-dev seems there is problem with clean reboot! Got kexec working with usind zImage from the same kernel version but seems when there is another kernel version its fail! I think it fail on my reboot function implementation! Need help to solve these things!
Got ansfer by self. Stock kernel and everyother without kexec patch ca not be loaded more info here -> http://forum.xda-developers.com/showthread.php?p=44077327
Tomorow will make it better, hope perfectly working.
Ok, lets go multiboot development!
My experience using kexec:
- since hard reboot owerwrite new kernel and ramdisk, I disabled hard reboot. So we need shutdown cpu instead of using function reboot! Since we have no shutdown cpu function we have very slow boot after executing new kernel and ramdisk (curently I am satisfied with slow boot because kexec can boot new kernel and ramdisk, yes its slow but working )
What is needed for kexec boot:
- kexec can not boot non kexec based kernels
- kexec can boot only kexec enabled kernel which mean only kernel which have my kexec patch (you can patch your kernel using kexec patch from my git)
- suported phones by now is only Sola and Go
My idea for multiboot by now:
- making boot menu based on modified CWM recovery
Modified CWM recovery plan:
- create new recovery and add new sub menu for multiboot feature
CWM multiboot menu idea:
- here we can write kexec multiboot functions
CWM kexec function idea:
- mount system, cache, userdata partition from external sdcard EXT4 partitons and mount them (only if these partions is created by you on your sdcard !!! We can create an small submenu for creating these partitons if these partitons not exist, but not now, we can do it later after creating simple kexec main menu))
- after mounting these partitions we can:
- boot android from allready installed android from these partitions
- ability to install new android to these partiton and boot them
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
munjeni said:
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
Click to expand...
Click to collapse
I cannot think of a way to do this without involving CWM. But we could make use of the volume buttons to select the ROM on boot (by mounting the appropriate partition based on the volume button that has been pressed down when the bootsplash screen is displayed). However this would limit us to the number of ROMs that can be installed to two (or max 3, if we have an option to set a default ROM to boot if no button is pressed).
Brilliant work by the way. You are Godlike! :victory:
itachilinux said:
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
Click to expand...
Click to collapse
Simple not supported!
First of all we need to create ramdisk which will boot android located on external sdcard, than if we get it working we can play with kexec. I need your help! If some one get android working from external sdcard than I will continue further. I am allso playing now with new ramdisk and trying to get external android booting!!
Our multiboot is not ready. Only ready is kexec tool and kexec kernel. Our multiboot feature is not yet implemented. Our multiboot is in plan and our multiboot need ideas!
can this be of any help?
http://forum.xda-developers.com/showpost.php?p=42057833&postcount=1
github:
https://github.com/tux-mind/tf201-dev
Changed fstab, recovery.fstab and sony fstab device paths to point to the external sdcard partition, modified updater_script paths, rebooted to the recovery, installed rom to the external sdcard partitions, rebooted, after abnormaly slow boot system booted but is abnormally unresponsive, so I deleted and reverted back to the emmc boot. Sory guys I am stopping here until some one get android booted from sdcard! I have no free time to play with external boot. When you done it I will continue
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
./fota-ua --help
FOTA-UA May 21 2013 18:05:10
ERROR [181] Parameter Error
Info [745] No status file
Total physical memory: 407695360 bytes
Total available physical memory: 8314880 bytes
Configuration information at runtime:
The number of pages of physical memory SC_PHYS_PAGES: 99535
The number of currently available pages of physical memory _SC_AVPHYS_PAGES: 203
0
Info [88] The number of processors configured _SC_NPROCESSORS_CONF: 2
The number of processors currently online (available) _SC_NPROCESSORS_ONLN: 2
Size of a page in bytes _SC_PAGESIZE: 4096
Logging of resource usage measures:
Maximum resident set size ru_maxrss: 172 KB
Page reclaims ru_minflt: 84
Page faults ru_majflt: 0
Block input operations: 0
Block output operations: 0
Info [468] No sdcard found in mounts
Info [757] Update Failed
WARN [48] Failed to remove /sbin/fota-ua, Read-only file system
WARN [52] Failed to remove /sbin/fota-mke2fs, Read-only file system
WARN [56] Failed to remove /sbin/rb_repart, No such file or directory
Click to expand...
Click to collapse
What we can do with these tools???
Or another tool:
./rb_repart
Repartitioning Tool
(C) Copyright 1999-2011 Red Bend Ltd.
4 Hacharash St. Hod-Hasharon, Israel
Version: 7.0.15.5514
Usage: ./rb_repart
-r [OPTIONAL, DEFAULT] - Run full operation
-t [OPTIONAL] - Run in test mode. Do not perform writes
-c config_file [OBLIGATIONAL] - Configuration file
Click to expand...
Click to collapse
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
XperianPro said:
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
Click to expand...
Click to collapse
When I tried on Xperia Go to update trought fota it was not worked! I never seen anything related to the fota recovery! Is recovery exist on fota kernel??? Have any menu???
Found some logs:
/data/local/tmp/sbin/fotatools # find / | grep fota
find / | grep fota
/cache/recovery/fota
/cache/recovery/fota/executed
/cache/recovery/fota/report
/cache/recovery/fota/status
/system/bin/fota-snoop
find: /proc/2652: No such file or directory
find: /proc/3172: No such file or directory
find: /proc/3554: No such file or directory
find: /proc/3610: No such file or directory
find: /proc/3723: No such file or directory
find: /proc/3884: No such file or directory
/data/local/tmp/sbin/fota-tad
/data/local/tmp/sbin/fotatools
/data/local/tmp/sbin/fotatools/rb_repart
/data/local/tmp/sbin/fotatools/vold.fstab
/data/local/tmp/sbin/fotatools/toolbox
/data/local/tmp/sbin/fota-mke2fs
/data/local/tmp/sbin/fota-ua
/dev/.fota_ui_down
/dev/.fota_ui_shutdown
/data/local/tmp/sbin/fotatools # ls /cache/recovery
ls /cache/recovery
fota
last_log
/data/local/tmp/sbin/fotatools # ls /cache/recovery/last_log
ls /cache/recovery/last_log
/cache/recovery/last_log
/data/local/tmp/sbin/fotatools # cat /cache/recovery/last_log
cat /cache/recovery/last_log
MR: Master reset starting Sat Aug 10 20:26:26 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /data ext4 /dev/block/mmcblk0p11 (null)
2 /cache ext4 /dev/block/mmcblk0p12 (null)
3 /modemfs ext4 /dev/block/mmcblk0p6 (null)
MR: Got content --wipe_data from /cache/recovery/command
MR: Formatting /cache
Creating filesystem with parameters:
Size: 262144000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 1024
Label: /cache
Blocks: 64000
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16000 inodes and 2065/64000 blocks
MR: Formatting /data
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label: /data
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
MR: Unlocking gesture
MR: Resetting RFHAL parameters
MR: Cleaning dir /modemfs/RFHAL
MR: Leaving dir /modemfs/RFHAL
MR: Master reset done
/data/local/tmp/sbin/fotatools #
Click to expand...
Click to collapse
I hope it will work on Xperia™ U, I don't know if it could be possible as I don't know how many differences are between Sola's and U's ramdisk and stuff. :/
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
How you load recovery from ota partition? Seems you have something like LK bootloader???
munjeni said:
How you load recovery from ota partition? Seems you have something like LK bootloader???
Click to expand...
Click to collapse
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
mirhl said:
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
Click to expand...
Click to collapse
Thats good idea, but thats not ideal solution in comparation with phones which have separated recovery/boot partition and bootloader ui like HTC devices which have direct recovery load trought bootloader, these solution only working if primary boot partition is modified and added "few lines" for booting recovery from seccond partition (like ota partition). Will be perfect solution if we make LK bootloader for separating recovery/boot partition, allso with LK we will be able to create custom emmc layout, by now I can not see any small bootloader for NovaThor on google search, seems thats not public. Searching for a way for creating bootloader based on kernel. How we can modify curent kernel and make them bootloader??? We can modify recovery and make them bootloader kexec based, but I am not happy with kexec because we need to fix them first because loading an kernel trought current kexec patch is very slow! I will be happy if some one look into my git and find a solution for fixing them!
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
munjeni said:
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
Click to expand...
Click to collapse
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
---------- Post added at 04:59 PM ---------- Previous post was at 04:44 PM ----------
bobthecooldad said:
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
Click to expand...
Click to collapse
just read this about fota
http://forum.xda-developers.com/showpost.php?p=12615775&postcount=1
and the orginal file is checked and if it isnt the correct one the phone wont boot
[Q&A] [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11
Q&A for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
denizyildizi345 said:
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
Click to expand...
Click to collapse
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
carliv said:
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
Click to expand...
Click to collapse
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
denizyildizi345 said:
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
Click to expand...
Click to collapse
No, for checking recovery root you need to look here: CM11-0/out/target/product/msm8226/recovery/root . But anyway that folder looks strange (I see a perl script there)....
Check my screenshot below.
And type a
Code:
make clobber
before stating a new build, or
Code:
make clean
between repetitive builds.
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
george676 said:
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
Click to expand...
Click to collapse
You need to be more specific: what recovery you try to build, in what environment (if it's not cm-11), and post a link to your device folder tree. That error means that the compiler can't find an init.rc file to add in ramdisk.
Compiler stops after a few segments
This is shown in my terminal:
Code:
cp: cannot stat ‘/home/paul/cm-10.2/out/target/product/Ultra/root/init.recovery.*.rc’: No such file or directory
make: [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1 (ignored)
mkdir -p /home/paul/cm-10.2/out/target/product/Ultra/recovery/root/system/bin
cp -rf device/CherryMobile/Ultra/recovery/root /home/paul/cm-10.2/out/target/product/Ultra/recovery/
cp: omitting directory ‘device/CherryMobile/Ultra’
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1
[email protected] ~/cm-10.2 $ make clobber
And you wrote about the problem:
During the build process you may encounter some errors or warnings.
*********************
Code:
Code:
cp: cannot stat `/home/carliv/CM11-0/out/target/product/P780/root/init.recovery.*.rc': No such file or directory
make: [/home/carliv/CM11-0/out/target/product/P780/recovery/root.ts] Error 1 (ignored)
This will not stop the build, and it appears if you don't use a init.recovery.{hardware}.rc file. Can be ignored, as the build process does.
Though in my terminal it just stopped at that part so I had to rename mine which was originally init.recovery.qcom.rc to init.recovery.*.rc
--edit--
And yet it still would not continue ... Any ideas on how to fix this?
--edit # 2--
Here's the pastebin link just in case ->biQ7kjV8 add that to pastebin...(I can't post links)
--edit # 3--
I fixed it... Turns out that it was just a BoardConfig.mk parameter that I forgot to complete
Calculate proper BoardConfig.mk partition sizes
I have this log:
Code:
----- Making recovery image ------
/home/paul/cm-10.2/out/target/product/Ultra/recovery.img maxsize=8380416 blocksize=135168 total=8409088 reserve=270336
error: /home/paul/cm-10.2/out/target/product/Ultra/recovery.img too large (8409088 > [8650752 - 270336])
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery.img] Error 1
make: *** Deleting file `/home/paul/cm-10.2/out/target/product/Ultra/recovery.img'
Meaning I have wrong sizes for the partitions so I need help on it...
When I ran the following:
cat /proc/mtd
cat /proc/emmc
they both return: No such file or directory...
Now If I run the command: cat /proc/partitions
it comes up with this:
As far as I know.... mmcblk1p1 is my external sd card which is about 32 GB...
My system image is about 1 GB and more(confirmed) when I used the dd command(to dump it) and is located at mmcblk0p16
Userdata reaches more than 4 GB as reported by the dd command(file size too large) and is located at mmbblk0p25
here(recovery.fstab):
/boot mtd /dev/block/mmcblk0p10
/cache yaffs2 /dev/block/mmcblk0p18
/data yaffs2 /dev/block/mmcblk0p25
/misc mtd /dev/block/mmcblk0p20
/recovery mtd /dev/block/mmcblk0p19
/system yaffs2 /dev/block/mmcblk0p16
-- edit --
I solved this already
Help required for compiling CWM for android 4.4.2 version only?
I am on Ubuntu 14.0.4 and I am trying to build a CWM recovery for Celkon Q 5009android 4.4.2, Broadcom processor). I have set up build environment and currently working on syncing repo. I have heard that it takes too much time and disk space to complete this process. I am interested to know in the following particular scenario : want to build only CWM recovery from source for an android running on version 4.4.2. So do I have to download all repositories or is there any shortcut that would enable me to not download all, but a certain part that is required for android 4.4.2? If yes, how to go about it? please help.
Please help. I do not undertstand why 'repo sync' always fails at a particular stage, though I have 30+ GB of disk space available in my working folder named 'cm12'. Following is the last screen message :
Fetching project platform/external/ant-glob
Fetching projects: 8% (40/495) Receiving objects: 86% (2389/2771), 26.68 MiBerror: RPC failed; result=56, HTTP code = 200iB | 124.00 KiB/s
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
remote: Sending approximately 1.94 GiB ...
remote: Counting objects: 85, done
remote: Finding sources: 100% (85/85)
error: RPC failed; result=56, HTTP code = 200iB | 88.00 KiB/s
fatal: The remote end hung up unexpectedly
Now should I run 'repo sync' again or should I use 'repo sync -j1' ?
fatal: early EOF
fatal: index-pack failed
error: Cannot fetch device/lge/mako-kernel
error: Exited sync due to fetch errors
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Black Manta said:
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60297989&postcount=51
Somewhere around that post you will find your answer.
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
4javier said:
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
Click to expand...
Click to collapse
First let me ask you where did you find a cwm for lollipop to build it? I'm interested to see that.
Second in recovery fstab you may want to add emmc partitions like boot, recovery... Check my github and look at elephone p6000 device folder (it's close enough to understand). If internal sdcard is on data/media you don't have to add it at all in fstab (at least that was the rule for kitkat... again I need to see the source for that lollipop cwm to tell you exactly). In elephone device recovery fstab you can see that usb and external sdcard are defined as auto for type not vfat because it is better to let minivold manage that.
Normaly for cm12.1 ther is no need to copy any rc file in root, only the fstab. {hardware}, which you said you did.
Again I can tell more if I will see the source code for the recovery, and last thing my guide is quite old now but I'm glad you found it useful.
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
4javier said:
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
Click to expand...
Click to collapse
I did understand it's cm12.1, but that was my question since there is no cwm for cm12.1 only cyanogenmod recovery which is different. At the moment I only recommend twrp for cm12.1+ and for that you have to use a different fstab, easy to find on github or here on xda in twrp threads.
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
4javier said:
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
Click to expand...
Click to collapse
Yes for all and for twrp fstab I think you can study device folders from twrp github (few are mediatek).
My kitchen now detects if image has mtk header and will repack it the same way (it stores a variable in unpacked folder which will tell that it must add a mtk header).
I decided to follow this guide to integrate the changes needed to build twrp instead of cwm: http://forum.xda-developers.com/showthread.php?t=1943625
It doesn't cover all the preparation steps like yours do. Do you think there are changes to be made to make your guide suitable for cm12 and twrp, or I can follow it until the " Build a CWM-based Recovery " paragraph?