Related
After i try to flash kernel boot.img on CWM recovery
BootLoop
I found this from CWM recovery
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
then I try restore my rom with CWM
i found like this
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk03
Error while formatting /system!
Can Anyone help me for resolve this.
My Device
Indonesian Polytron Crystall Wizard II (w3430)
Hardware : MT6577
Model : W3430
Build number : W3430
Build date UTC : 20121228-035645
Android v : 4.0.4
Baseband v: MAUI.11AMD.W12.22.SP.V5.P2, 2012/08/31 18:02
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Fri Dec 28 11:51:14 CST 2012
Uboot build v : MAIN2.2.ubt.2073
This Device Like Micromax A90s
8Mpix Camera
512 RAM
1Ghz Dual Core Processor
Now I stuck on On Bootloop and CWM
Try hard for Flashing new Rom, kernel etc.
The fact i can't do Anything with my Phone.
Help Me Guys.///:crying:
Sory My Bad English
before doing anything make sure you make a backup,like nandroid backup you could have made,now what you can do is, flash stock boot.img if boot.img is creating this error,else flash stock rom,then next time make sure you make nandroid backup,so if something goes wrong you can restore from backup.
aksingh05 said:
before doing anything make sure you make a backup,like nandroid backup you could have made,now what you can do is, flash stock boot.img if boot.img is creating this error,else flash stock rom,then next time make sure you make nandroid backup,so if something goes wrong you can restore from backup.
Click to expand...
Click to collapse
I have Nandroid BackUp But Only Can Restore Boot On advance Restore
Try Restore Other but Failed
Mount System Ext4 /dev/block/mmcblk0p3 failed
Mount Data Ext4 /dev/block/mmcblk0p5 failed
Mount Cache Ext4 dev/block/mmcblk0p4 failed
Maybe my partition goes wrong..
Are You Have Different way to fix this?
I Have Many Backup Files
Hope My Backup from MTK Droid Tools Are Helping Me
Can You Help Me Create Edify Script for some File like this
- boot.img
- DSP_BL
- files.md5
- firmware.info
- logo.bin
- MBR
- nodl_expdb
- nodl_misc
- nodl_pmt
- nodl_seccfg
- nodl_secro.bin
- nvram.bin
- phone.info
- preloader_and_dsp
- recovery.img
- uboot.bin
- userdata_nvram_only.ext4.tar
Or Can I Fix this With Terminal on Aroma File Manager?
Because i only can open CWM recovery And Aroma File Manager on my phone.
i'm So stupid make mistake this think...:crying:
kemasrio said:
I have Nandroid BackUp But Only Can Restore Boot On advance Restore
Try Restore Other but Failed
Mount System Ext4 /dev/block/mmcblk0p3 failed
Mount Data Ext4 /dev/block/mmcblk0p5 failed
Mount Cache Ext4 dev/block/mmcblk0p4 failed
Maybe my partition goes wrong..
Are You Have Different way to fix this?
I Have Many Backup Files
Hope My Backup from MTK Droid Tools Are Helping Me
Can You Help Me Create Edify Script for some File like this
- boot.img
- DSP_BL
- files.md5
- firmware.info
- logo.bin
- MBR
- nodl_expdb
- nodl_misc
- nodl_pmt
- nodl_seccfg
- nodl_secro.bin
- nvram.bin
- phone.info
- preloader_and_dsp
- recovery.img
- uboot.bin
- userdata_nvram_only.ext4.tar
Or Can I Fix this With Terminal on Aroma File Manager?
Because i only can open CWM recovery And Aroma File Manager on my phone.
i'm So stupid make mistake this think...:crying:
Click to expand...
Click to collapse
where is the system img?????????
better download the original stock rom,containing all flashing files,then flash via sptool
---------- Post added at 08:53 AM ---------- Previous post was at 08:32 AM ----------
kemasrio said:
I have Nandroid BackUp But Only Can Restore Boot On advance Restore
Try Restore Other but Failed
Mount System Ext4 /dev/block/mmcblk0p3 failed
Mount Data Ext4 /dev/block/mmcblk0p5 failed
Mount Cache Ext4 dev/block/mmcblk0p4 failed
Maybe my partition goes wrong..
Are You Have Different way to fix this?
I Have Many Backup Files
Hope My Backup from MTK Droid Tools Are Helping Me
Can You Help Me Create Edify Script for some File like this
- boot.img
- DSP_BL
- files.md5
- firmware.info
- logo.bin
- MBR
- nodl_expdb
- nodl_misc
- nodl_pmt
- nodl_seccfg
- nodl_secro.bin
- nvram.bin
- phone.info
- preloader_and_dsp
- recovery.img
- uboot.bin
- userdata_nvram_only.ext4.tar
Or Can I Fix this With Terminal on Aroma File Manager?
Because i only can open CWM recovery And Aroma File Manager on my phone.
i'm So stupid make mistake this think...:crying:
Click to expand...
Click to collapse
This usually happens by the incompatibility of this kernel3 with some SD cards, the installation is correct, but the internal card is not recognized at boot, no partitions are mounted system, data, cache. This is causing the boot not last rom and this error in cwm.
At this time the only solution to this problem is to change the internal SD.
Alternative solution is possible, this is a summary of my experience:
- Testing with several sd cards, some work well, others reproduce this problem.
- Sd card format with the problem, with
SDFormatter4,
now the SD card is working well!
- After a few reboots and install rom again reproduces the problem, boot logo stuck, and does not mount cache recovery. Surprisingly I turn off the tablet 2 min with on-off switch, restarting everything works fine.
This takes a little research to find a solution, possibly related to a correct SD card format.
found on google,try may it will help
I Can't Mount Via USB
now I have found alternative how to fix it, but i'm still confuse.
I use Console Terminal from Aroma File Manager.
i write
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0: 3905MB
Sector size (logical/physical): 512/512B
Partition table: msdos
but i dont know what a format partition for :
mmcblk0p1 EBR1 (?)
mmcblk0p2 sec_ro (?)
mmcblk0p3 Android (system) (ext2 Convert to ext4)
mmcblk0p4 Cache (ext2 Convert to ext4)
mmcblk0p5 UserData (data) (ext2 Convert to ext4)
mmcvlk0p6 fat (?)
kemasrio said:
I Can't Mount Via USB
now I have found alternative how to fix it, but i'm still confuse.
I use Console Terminal from Aroma File Manager.
i write
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0: 3905MB
Sector size (logical/physical): 512/512B
Partition table: msdos
but i dont know what a format partition for :
mmcblk0p1 EBR1 (?)
mmcblk0p2 sec_ro (?)
mmcblk0p3 Android (system) (ext2 Convert to ext4)
mmcblk0p4 Cache (ext2 Convert to ext4)
mmcblk0p5 UserData (data) (ext2 Convert to ext4)
mmcvlk0p6 fat (?)
Click to expand...
Click to collapse
please visit here may this will work,
http://forum.xda-developers.com/showthread.php?t=1745601
& please go here for info on mmcblocks
http://forum.xda-developers.com/showthread.php?t=1665123
mmcblk0p1 qcsbl_cfg part of radio.img
mmcblk0p2 qcsbl <empty>
mmcblk0p3 osbl part of radio.img
mmcblk0p4 extended part of radio.img elf-header of rex/amss
--------- --------- -------
mmcblk0p5 modem part of radio.img
mmcblk0p6 adsp part of radio.img
mmcblk0p7 htc rcdata.img Radio settings (IMEI,CID,S-OFF)
mmcblk0p8 rf_nv <empty>
mmcblk0p9 nv_mfg <empty>
mmcblk0p10 cdma_user_data <empty>
mmcblk0p11 rf_delta <empty>
mmcblk0p12 reserved <empty>
mmcblk0p13 modem_fs1
mmcblk0p14 modem_fs2
mmcblk0p15 htc_data <empty>
mmcblk0p16 htc_reserved <empty>
mmcblk0p17 misc device info
mmcblk0p18 appsbl hboot
mmcblk0p19 splash1
mmcblk0p20 wifi WiFi module
mmcblk0p21 recovery
mmcblk0p22 boot kernel & ramdisk
mmcblk0p23 mfg device config ?, contains WiFi MAC-address and Serial number
mmcblk0p24 splash2 <empty>
mmcblk0p25 system
mmcblk0p26 data userdata
mmcblk0p27 cache
mmcblk0p28 devlog
Is Dead,... I format wrong Partition
now my phone only show up 1st bootloader Vol+ Power just restart Phone
Vol- Power same,...
Last Chance,.. bootloader + CWM from sdcard or SdCard android
maybe anyone can help me for make SD CArd bootable CWM or SD card Android?
i have download many SCDcard CWM on Xda but won't Work,..
Ignore this comment
you can install temporary recovery via temp recovery if adb shows your device
download this,if your phone supports fastboot,then it may help
http://forum.xda-developers.com/attachment.php?attachmentid=2303287&d=1380965873
lolerpro8 said:
Nope.. You can't have recovery on sd-card with an h-boot, sorry dude. And what partition did you formated, when you bricked your phone so the bootloader restarts?
Click to expand...
Click to collapse
To bad,... for the first I install other kernel,.. then my device only have CWM recovery because my partition error, my plan to repartition,.. and then i use Aroma File Manager Terminal for parted partition manual,.. maybe i wrong repartition mmcblk0p1 > 3 because mmcblk0p4 and mmcblk0p5 workfine with Ext4, on parted is only 4 primary partition, i got stuck because the real partition on my device mmcblk0p1 > 6.
at last on terminal i format mmcblk0p1,2,3, so i cannot format other partition 4 and 5 because partition can't unmount, i try unmount but fail to unmount... i think maybe must reboot.. after reboot,... i lost my recovery.. and only 1st boot...
if i format my partition succes maybe my phone will be work normaly.
@aksingh05 : No man,...... ADB cannot Detect my device... T_T..
My last chance is only on SDCard..
kemasrio said:
To bad,... for the first I install other kernel,.. then my device only have CWM recovery because my partition error, my plan to repartition,.. and then i use Aroma File Manager Terminal for parted partition manual,.. maybe i wrong repartition mmcblk0p1 > 3 because mmcblk0p4 and mmcblk0p5 workfine with Ext4, on parted is only 4 primary partition, i got stuck because the real partition on my device mmcblk0p1 > 6.
at last on terminal i format mmcblk0p1,2,3, so i cannot format other partition 4 and 5 because partition can't unmount, i try unmount but fail to unmount... i think maybe must reboot.. after reboot,... i lost my recovery.. and only 1st boot...
if i format my partition succes maybe my phone will be work normaly.
@aksingh05 : No man,...... ADB cannot Detect my device... T_T..
My last chance is only on SDCard..
Click to expand...
Click to collapse
I'm sorry to say this, but even an sd card recovery won't help... That is becouse you probably broke some partitions during the proces. The only 2 stuff i could think of is to use the j-tag box to repartition your mmcblk's, or somehow do it over h-boot Etheir way you have a big problem.
kemasrio said:
After i try to flash kernel boot.img on CWM recovery
BootLoop
I found this from CWM recovery
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
then I try restore my rom with CWM
i found like this
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk03
Error while formatting /system!
Can Anyone help me for resolve this.
My Device
Indonesian Polytron Crystall Wizard II (w3430)
Hardware : MT6577
Model : W3430
Build number : W3430
Build date UTC : 20121228-035645
Android v : 4.0.4
Baseband v: MAUI.11AMD.W12.22.SP.V5.P2, 2012/08/31 18:02
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Fri Dec 28 11:51:14 CST 2012
Uboot build v : MAIN2.2.ubt.2073
This Device Like Micromax A90s
8Mpix Camera
512 RAM
1Ghz Dual Core Processor
Now I stuck on On Bootloop and CWM
Try hard for Flashing new Rom, kernel etc.
The fact i can't do Anything with my Phone.
Help Me Guys.///:crying:
Sory My Bad English
Click to expand...
Click to collapse
I have the same issue with cwm on my galaxy s3. If youre rooted download goomanager and install TWRP recovery. TWRP is better in every way!
Sent from my SPH-L710 using xda app-developers app
To late,.... now my device at service center,... hahahahahaha
fastboot is not working anymore,..
Lot of Tool For MTK device i already use it ,... but no one can detect my device....
hahaha,... i Must wait for one week back to my own..
^_^
Stessa cosa
anche a me è successa la stessa cosa dopo un memory test andato a male su sp flash a quanto pare nel mio dispositivo ho un bootloop e funziona solo la cwm e quando provo a montare le partizioni sd-ext e emmc mi da errore da parte di /dev/block/mmcblk0p7 invalid argument si può sbrikkare
Adb FUNZIONA!!
CWM RECOVERY (v5.0.4) FUNZIONA
Backup OK (manca il file system.img)
tutto l'altro ok
Hi guys, yesterday I tryied for the first time to update franco kernel's last update via FKU Beta and as a resoult my phone won't start anymore. When i power it on it get stuck on the boot logo (the one right after the cyanogen logo with powered by android). I can access to TWRP and i can access to adb but usb debugging it's turned off I think (is it possible to verify it?).
Inside the phone there is a very recent TWRP backup (yes, I tryied already to restore it from TWRP but no changes) and a Titanium Backup of all my apps. Is it possible to save it somewhere? What can I do to fix my phone?
Pleeeease help me Thanks in advice!
Which partitions are backed up in your TWRP backup?
Transmitted via Bacon
ok I flashed my phone from scratch so now I have r33 on it.
I restored an old backup but now I can't update to r38!
That's the log of twrp
Installing '/sdcard/Download/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
about to run program [/tmp/otasigcheck.sh] with 1 args
failed to stat "/system/bin/thermal-engine": No such file or directory
script aborted: assert failed: apply_patch_check("/system/bin/thermal-engine","b94fc36a478b73d2d44133a4369d10e1b060bf5e","605b06e559abced4cdbafe02dc5ea14d69c89cd9")
assert failed: apply_patch_check("/system/bin/thermal-engine","b94fc36a478b73d2d44133a4369d10e1b060bf5e","605b06e559abced4cdbafe02dc5ea14d69c89cd9")
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip'
Error flashing zip '/sdcard/Download/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip'
Updating partition details...
I:mount '/data/media/0' '/sdcard' process ended with RC=0
Iata backup size is 6070MB, free: 42239MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:mount '/data/media/0' '/sdcard' process ended with RC=0
Click to expand...
Click to collapse
You had Franco kernel installed at some point? The remnants are screwing with the OTA. You need to clean flash with a full wipe.
Transmitted via Bacon
yes I had franco so i made a clean flash of r33, wiped cache and dalvik then i tryied to flash r38 with that error
Wiping cache and dalvik isn't enough, you need to wipe system/data/cache/dalvik cache, then install clean 33R, then you can take the 38R update. Or you could just flash the full recovery flashable version of 38R after wiping system/data/cache/dalvik cache, that's probably the easier solution.
Transmitted via Bacon
Good afternoon,
I am wondering how to do this...
i built latest TWRP for nexus 5 with full F2FS support added (recovery kernel does support F2FS) : i can format /system + /data + /cache to F2FS and mount them from recovery once done... :good:
i tweaked a homebuilt CM 12.1 installer in order to install it on my device's F2FS partitions : i replaced boot.img by an ALL-F2FS enabled boot.img (kernel + fstab) + a modified updater-script...
... BUT when i flash my new ALL-F2FS CM 12.1 installer onto my D821 then /system goes back to EXT4. I know that the data packed into system.new.dat is contained in a RAW EXT4 FS.
Is there any way to modify this line from any LP updater-script :
Code:
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
... in order to extract system.new.dat as F2FS or without modifying target /system partiton ?
Or any other solution ?!
Thanks for your comments and answers !
PS : attached screenshot shows my current FS types for /system + /data + /cache...
How to convert NAND ROM to SD-EXT ROM for MultiBootloader
Code:
After following this guide, your ROM can be use with [URL="http://forum.xda-developers.com/nokia-x2/development/sbl-multibootloader-v1-00-04-10-2015-t3217360"]MultiBootloader[/URL]
THIS GUIDE IS NOT FOR NOOBs
Requirements
Knowledge about Android Image Kitchen
Notepad ++
A nand ROM extracted
Instructions
Delete the RED COLOR
Add the BLUE COLOR
Step 1: Modifying boot.img (FOR STOCK KERNEL ONLY) - Check post #2 to download the modified boot image, you don't need to edit it yourself.
Use Android Image Kitchen's unpackimg command to unpack the boot.img file from the ROM your want to port.
Go to Android Image Kitchen\ramdisk folder, edit these files:
fstab.qcom
Change like this:
Code:
# Android fstab file.
# 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
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
[COLOR="Red"]/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check,encryptable=footer[/COLOR]
[COLOR="Blue"]/dev/block/platform/msm_sdcc.1/by-name/userdata /nanddata ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check,encryptable=footer[/COLOR]
/devices/msm_sdcc.2/mmc_host /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard:auto
#/dev/block/mmcblk0p11 /system ext4 ro,barrier=1 wait
#/dev/block/mmcblk0p12 /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,check,encryptable=footer
init.rc
- Find this event:
Code:
on fs
- Change like this:
Code:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
[COLOR="Red"]mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
mount yaffs2 [email protected] /data nosuid nodev[/COLOR]
[COLOR="Blue"] mount ext4 /dev/block/mmcblk1p2 /system
mount ext4 /dev/block/mmcblk1p2 /system ro remount
mount ext4 /dev/block/mmcblk1p3 /data nosuid nodev[/COLOR]
mount yaffs2 [email protected] /cache nosuid nodev
[COLOR="Blue"]#mount nand data for sharing data/app
mkdir /nanddate 0771 system system
mount yaffs2 [email protected] /nanddata nosuid nodev
# mount sdcard
wait /dev/block/mmcblk1p1
wait /dev/block/mmcblk1p1
mount vfat /dev/block/mmcblk1p1 /storage/sdcard1[/COLOR]
init.target.rc
- Find this event:
Code:
on fs
- Change like this:
Code:
on fs
mount_all fstab.qcom
# Keeping following partitions outside fstab file. As user may not have
# these partition flashed on the device. Failure to mount any partition in fstab file
# results in failure to launch late-start class.
wait /dev/block/platform/msm_sdcc.1/by-name/cache
mount ext4 /dev/block/platform/msm_sdcc.1/by-name/cache /cache nosuid nodev barrier=1
wait /dev/block/platform/msm_sdcc.1/by-name/persist
mount ext4 /dev/block/platform/msm_sdcc.1/by-name/persist /persist nosuid nodev barrier=1
wait /dev/block/platform/msm_sdcc.1/by-name/modem
mount vfat /dev/block/platform/msm_sdcc.1/by-name/modem /firmware ro shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337
[COLOR="Red"] wait /dev/block/platform/msm_sdcc.1/by-name/custom
mount ext4 /dev/block/platform/msm_sdcc.1/by-name/custom /custom nosuid nodev barrier=1 ro[/COLOR]
[COLOR="Blue"] wait /dev/block/mmcblk1p4
mount ext4 /dev/block/mmcblk1p4 /custom nosuid nodev barrier=1 ro[/COLOR]
Repack boot.img and copy to the ROM folder.
Step 2: Modifying updater-script
Open ROM-name\META-INF\com\google\android\updater-script
Find:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p19", "/system");
or
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
Add these lines above it:
Code:
[COLOR="blue"]ui_print(" Mounting Partitions ");
mount("ext4", "MMC", "/dev/block/mmcblk1p2", "/system-ext");
mount("ext4", "MMC", "/dev/block/mmcblk1p4", "/custom-ext");
mount("ext4", "EMMC", "/dev/block/mmcblk0p20", "/cache");
mount("ext4", "MMC", "/dev/block/mmcblk1p3", "/data-ext");
ui_print(" Formatting Partitions ");
delete_recursive("/system-ext");
delete_recursive("/custom-ext");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data-ext");[/COLOR]
Find this line:
Code:
package_extract_file("boot.img", "/tmp/boot.img");
Change like this:
Code:
[INDENT][COLOR="Red"]package_extract_file("boot.img", "/tmp/boot.img");
run_program("/system/xbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p10");
delete("/tmp/boot.img");[/COLOR][COLOR="Blue"]
package_extract_file("boot.img", "/emmc/kernels/[I]your_rom_name[/I].img");[/COLOR][/INDENT]
Find and change all /system/ to /system-EXT/
Find and change all /custom/ to /custom-EXT/
Save.
Step 3: Create the ZIP
Make sure you have copy the modified boot.img to the ROM folder
Select all the files and folders in the ROM folder (custom, system, META-INF, boot.img,etc..)
Compress into ZIP file.
Done.
<EDITTING>
I have modifed the boot.img to boot into sdext ROM:
For stock based ROM: stock_ext.img - thanks to @symbuzzer for adding some features and fixing the ril & sdcard bugs
modified_stock_insecure-kernel.img - (Maybe I've made some mistake in this file. I don't recommend to use this, it can cause some bugs with sdcard0. Better modify it yourself.)
For CM11 based ROM: ext_cm11.img
Great ! Im waiting for this
Bro how can intsall the rom
I m try but couldn't with me
Plz help ??
@SonnySimon this method doesnt work on Stock Kernel/Rom. I will attach stock kernel on XDA today. You can compare mine with yours and update this post. Thanks
symbuzzer said:
@SonnySimon this method doesnt work on Stock Kernel/Rom. I will attach stock kernel on XDA today. You can compare mine with yours and update this post. Thanks
Click to expand...
Click to collapse
It works. I tried and it boots successfully into ext stock ROM but have some bugs with ril and sdcard.
SonnySimon said:
It works. I tried and it boots successfully into ext stock ROM but have some bugs with ril and sdcard.
Click to expand...
Click to collapse
I meant yours have bugs Thanks anyway
[HOW TO] BOOT FROM SD CARD [SUCCESSFULLY] on QMobile Z8 with BRICKED/DEAD eMMC
SimonVN said:
How to convert NAND ROM to SD-EXT ROM for MultiBootloader
Click to expand...
Click to collapse
I have been successfully able to boot from SD card on QMobile Z8 by partitioning SD card on a Ubuntu machine using 'parted' and 'fdisk' commands, replicating eMMC partition table and then flashing factory firmware images to these newly created partitions using 'dd' command. Then I modified "fstab.qcom" & "init.tegra.rc" files in kernel (boot.img) and "recovery.fstab" and "uneventd.rc" files in twrp recovery to initiate mounting and booting from sd card instead of internal memory. It was successful after some experiments. Details can be found here:
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171
But I have still a few queries to be answered. Please have a look. Any help, comments, information or suggestions will be appreciated.
Hello,
I'm not able to build (repackage) correctly system.img for SM-G361F, output is always rejected by both Odin (10.3.7) and Heimdall
I'm trying to repackage (pre-root) system.img taken from "G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5" (taken from ETL factory image named ETL-G361FXXU1APA2-20160202095551.zip )
Step-by-step:
1) tar xvf G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5 system.img
2) simg2img system.img system.img.raw
3) mount system.img.raw /mnt
4) made changes
5a) make_ext4fs -s -g 32768 -b 4096 -T -1 -S file_contexts -f -l 1843M system.repack.img /mnt/
5b) mkuserimg.sh -s /mnt system.repack.img ext4 system 1843M file_contexts
6) tar --owner 0 --group 0 --numeric-owner -H ustar -c system.img > G361F_SYSTEM.tar
7a) Load either system.img through Heimdall (PIT file downloaded through Heimdall is here: http://forum.xda-developers.com/showpost.php?p=65779994&postcount=146 )
7b) Load G361F_SYSTEM.tar in Odin v3.10.7 in AP tab and flash it
On ODIN/Download screen I can see that
1) FRP LOCK: OFF
2) KNOX: 0x0
3) System status: official
4) RP SWREV: S1, L1, M1
Notes
1) I have checked the box "OEM Unlock" in Developers settings to enabled
2) "file_contexts" is taken from booted up device through ADB (adb pull /file_contexts)
3) I've tried repackage the image without making any changes
4) When I compare original and repackaged images ("ls -lsaR" outputs), it seems like owner:group permissions are not persisted
5) I've tried both simg2img/make_ext4fs/mkuserimg.sh from CM12.1 repository (up to date today) and from https://github.com/ASdev/android_img_repack_tools (branch android-5.1.1)
6) I'm not sure about size 1843M, however flashing fails in the same manner when I go with 1536M and 2048M and anything between those two
7) Heimdall fails at about 6% of flashing single (sparse system.img) file with error "Failed to unpack received packet"
OSS Kernel for SM-G361F is here: https://github.com/smarek/G361F-Kernel
OSS Platform for SM-G361F is here: https://github.com/smarek/G361F-Platform
Questions are:
1) Is there anything special to be aware of when building for Samsung devices?
2) Did I miss or misunderstood any step in system.img repackaging process?