Develop Bugs

[Q] Boot loop into TWRP / TWRP does not flash image (solved)

I rooted a LG V500 and installed Malladus 1.2.5. Did work fine. Then I made the mistake to flash the dyn.Kernel r2. The device did not start anymore.
After going around with the tricky hardware keys I can get back to TWRP recovery and flash again an image ZIP (tested it with the already working Maladus Zip as also with CM11 nightly). Flashing did not show any errors but after rebooting to system it does not start the image instead it goes back to recovery or hangs at the LG screen (did also wait over an hour there). ADB does also not connect anymore also the drivers did work fine before.
Does anyone have a clue what I can do or what I have missed?

Meanwhile I upgraded TWRP to the newest version and changed recovery also to Philz CWM "Secure Booting Error! Device UnLock" is also shown. But Boot loop does still occur also after triggering all sorts of wipe and reflashing again.
ADB, Fastboot or sideload is still not available. Windows device driver does only show "LGE AndroidNET Serial Port".
The mentioned recovery methods do fail since the GPAD does not connect regardless if already in download mode or not.
Anyone some hints what I can try next?

Have you tried flashing cm11 or mahdi, just to check it's not a rom thing?

Both the newest CM11 and MAHDI ROMs show up with the boot loop. Its unclear for me why the recovery mode is still forced also after flashing a ROM. Did also try CMWs "Clean to Install a new ROM" which should wipe everything but no luck.

Weird, there shouldn't be any problem...
As far as I can tell - but I might be wrong - your only way out would be to go back to stock. I haven't tried it myself, cause my installs always got right, but this thread might do the job :
http://forum.xda-developers.com/showthread.php?t=2543350

Tried already to recover. With LGMobile Support tool no connection can be established no matter if in download mode or in recovery.
With Software Update or Flash Tool for KDZ also no luck since KDZ is there is an error after successful unpacking:
[R&D Test Tools Log File]
11:16:48 : Launching SW update
11:16:48 : Unpacking KDZ
11:19:46 : KDZ file extraced
11:19:46 : Extract file error
11:19:48 : ===FINISHED===

I can suggest two things,
One is a complete clutching at straws idea and the other is a bit scary if it doesn't work.
First is to extract the boot.img and try to flash just that and see what happens. I'm not sure if you would have to lokify it, I'm just brainstorming.
The other is to download quick adb and fastboot (from xda) several roms and twrp 2.3.0 first to your pc and then completely wipe your tablet. Then reinstall your drivers on your pc.
Then install twrp 2.3.0 on your tablet through adb. Then flash a rom.
Then hopefully boot up and then flash twrp 2.3.2 zip
I'm not shouting but I want to emphasise this
If you wipe the tablet and adb is still not working YOU MAY END UP WITH A BRICK.
I'm not confident, it would be great if someone with more experience could chip in.
Sent from my LG-V500 using XDA Premium HD app

Already gone through all of this.
Recovery is not the problem, I can flash and use TWRP 2.6.3.1/2.6.3.2 or Philz CWM. LOKI should also be working since the "Secure Booting Error" is shown.
ADB is NOT possible. I can not connect to ADB since in recovery both TWRP and CWM do not respond on ADB and the download mode does not support ADB in general. Drivers should be fine since the GPAD could be rooted via ADB before I flashed the dyn. Kernel.
Since ADB does not work that might be also the problem I can´t start the recovery.
To flash the original kernel or recovery I would need Flashify since those are only available as image files (.IMG) but I can´t do this from recovery.

Boot log from TWRP after it looped again into recovery and not into system:
Code:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 2.6.3.2 on Sun Feb 22 05:53:00 1970
BOARD_HAS_NO_REAL_SDCARD := true
I:Single storage only -- data/media.
I:Device has /data/media defined.
I:Mount: Unable to find partition for path '/data'
TW_NO_REBOOT_BOOTLOADER := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
Starting the UI...Pixel format: 1200x1920 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (1200 x 1920)
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/modem'
I:Processing '/sbl1'
I:Processing '/sbl2'
I:Processing '/sbl3'
I:Processing '/rpm'
I:Processing '/tz'
I:Processing '/modem_st1'
I:Processing '/modem_st2'
I:Processing '/aboot'
I:Processing '/boot'
I:Processing '/system'
I:Processing '/data'
I:Created '/sdcard' folder.
I:mount '/data/media' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/TWRP/BACKUPS/08faffb79c96eb46'
I:Settings storage is '/data/media'
I:Processing '/cache'
I:Processing '/recovery'
I:Processing '/external_sd'
I:Created '/external_sd' folder.
Updating partition details...
I:Data backup size is 0MB, size: 11304MB, used: 0MB, free: 11175MB, in data/media: 0MB.
I:Unmounting main partitions...
Partition Logs:
/modem | /dev/block/mmcblk0p1 | Size: 64MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: modem
Storage_Name: modem
Backup_Path: /modem
Backup_Name: modem
Backup_Display_Name: modem
Storage_Path: /modem
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl1 | /dev/block/mmcblk0p2 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: sbl1
Storage_Name: sbl1
Backup_Path: /sbl1
Backup_Name: sbl1
Backup_Display_Name: sbl1
Storage_Path: /sbl1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl2 | /dev/block/mmcblk0p3 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p3
Display_Name: sbl2
Storage_Name: sbl2
Backup_Path: /sbl2
Backup_Name: sbl2
Backup_Display_Name: sbl2
Storage_Path: /sbl2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl3 | /dev/block/mmcblk0p4 | Size: 2MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p4
Display_Name: sbl3
Storage_Name: sbl3
Backup_Path: /sbl3
Backup_Name: sbl3
Backup_Display_Name: sbl3
Storage_Path: /sbl3
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/rpm | /dev/block/mmcblk0p6 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p6
Display_Name: rpm
Storage_Name: rpm
Backup_Path: /rpm
Backup_Name: rpm
Backup_Display_Name: rpm
Storage_Path: /rpm
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/tz | /dev/block/mmcblk0p8 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p8
Display_Name: tz
Storage_Name: tz
Backup_Path: /tz
Backup_Name: tz
Backup_Display_Name: tz
Storage_Path: /tz
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modem_st1 | /dev/block/mmcblk0p10 | Size: 3MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p10
Display_Name: modem_st1
Storage_Name: modem_st1
Backup_Path: /modem_st1
Backup_Name: modem_st1
Backup_Display_Name: modem_st1
Storage_Path: /modem_st1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modem_st2 | /dev/block/mmcblk0p11 | Size: 3MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p11
Display_Name: modem_st2
Storage_Name: modem_st2
Backup_Path: /modem_st2
Backup_Name: modem_st2
Backup_Display_Name: modem_st2
Storage_Path: /modem_st2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/aboot | /dev/block/mmcblk0p5 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p5
Display_Name: aboot
Storage_Name: aboot
Backup_Path: /aboot
Backup_Name: aboot
Backup_Display_Name: aboot
Storage_Path: /aboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/boot | /dev/block/mmcblk0p7 | Size: 24MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p7
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/system | /dev/block/mmcblk0p23 | Size: 2113MB Used: 1727MB Free: 386MB Backup Size: 1727MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p23
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/data | /dev/block/mmcblk0p36 | Size: 11304MB Used: 0MB Free: 11175MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p36
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/cache | /dev/block/mmcblk0p24 | Size: 788MB Used: 15MB Free: 773MB Backup Size: 15MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p24
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/recovery | /dev/block/mmcblk0p27 | Size: 24MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p27
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/external_sd | /dev/block/mmcblk1p1 | Size: 1933MB Used: 1778MB Free: 154MB Backup Size: 1778MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: Micro SDcard
Storage_Name: Micro SDcard
Backup_Path: /external_sd
Backup_Name: external_sd
Backup_Display_Name: Micro SDcard
Storage_Path: /external_sd
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
I:Loading package: TWRP (/script/ui.xml)
I:Loading package: TWRP (/data/media/TWRP/theme/ui.zip)
I:Loading package: TWRP (/res/ui.xml)
I:Loading resources...
I:Loading variables...
I:Loading pages...
I:Loading page main
I:Loading page main2
I:Loading page install
I:Loading page flash_confirm
I:Loading page flash_zip
I:Loading page flash_done
I:Loading page clear_vars
I:Loading page confirm_action
I:Loading page action_page
I:Loading page singleaction_page
I:Loading page action_complete
I:Loading page filecheck
I:Loading page rebootcheck
I:Loading page wipe
I:Loading page advancedwipe
I:Loading page formatdata
I:Loading page formatdata_confirm
I:Loading page backup
I:Loading page backupname1
I:Loading page backupname2
I:Loading page backupencryption
I:Loading page backupencryption2
I:Loading page checkbackuppassword
I:Loading page backup_run
I:Loading page restore
I:Unable to open '/data/media/TWRP/BACKUPS/08faffb79c96eb46'
I:Loading page restore_read
I:Loading page restore_decrypt
I:Loading page try_restore_decrypt
I:Loading page restore_select
I:Loading page renamebackup
I:Loading page restore_run
I:Loading page selectstorage
I:Loading page mount
I:Loading page usb_mount
I:Loading page usb_umount
I:Loading page reboot
I:Loading page settings
I:Loading page timezone
I:Loading page screen
I:Loading page advanced
I:Loading page partsdcard
I:Loading page htcdumlock
I:Loading page lock
I:Loading page filemanagerlist
I:Loading page filemanageroptions
I:Loading page choosedestinationfolder
I:Loading page filemanagerrenamefile
I:Loading page filemanagerrenamefolder
I:Loading page filemanagerchmod
I:Loading page filemanagerconfirm
I:Loading page filemanageracction
I:Loading page decrypt
I:Loading page trydecrypt
I:Loading page terminalfolder
I:Loading page terminalcommand
I:Loading page sideload
I:Loading page installsu
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
SELinux contexts loaded from /file_contexts
E:Cannot load volume /misc!
E:Cannot load volume /misc!
Startup Commands: ro.boot.hardware=awifi
ro.boot.emmc=true
ro.boot.serialno=08faffb79c96eb46
ro.boot.baseband=apq
ro.serialno=08faffb79c96eb46
ro.bootmode=unknown
ro.baseband=apq
ro.bootloader=unknown
ro.hardware=awifi
ro.revision=11
ro.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JLS36I
ro.build.display.id=cm_v500-eng 4.3.1 JLS36I 256a257cdc test-keys
ro.build.version.incremental=256a257cdc
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3.1
ro.build.date=Tue Dec 31 09:34:19 CST 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=drgravy
ro.build.host=drgravy-i7
ro.build.tags=test-keys
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=cm_v500
ro.product.device=v500
ro.product.board=awifi
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=v500
ro.build.description=cm_v500-eng 4.3.1 JLS36I 256a257cdc test-keys
ro.build.fingerprint=lge/cm_v500/v500:4.3.1/JLS36I/256a257cdc:eng/test-keys
ro.build.characteristics=default
ro.cm.device=v500
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.root_access=1
ro.cm.version=10.2-20131231-UNOFFICIAL-v500
ro.modversion=10.2-20131231-UNOFFICIAL-v500
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.opengles.version=196608
persist.audio.handset.mic.type=digital
persist.audio.dualmic.config=endfire
persist.audio.fluence.voicecall=true
persist.audio.handset.mic=dmic
persist.audio.fluence.mode=endfire
persist.audio.lowlatency.rec=false
af.resampler.quality=4
persist.hwc.mdpcomp.enable=true
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
media.aac_51_output_enabled=true
debug.egl.recordable.rgba8888=1
ro.qc.sensors.wl_dis=true
ro.qualcomm.sensors.smd=true
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.sf.lcd_density=480
ro.bt.bdaddr_path=/data/misc/bdaddr
ro.telephony.default_network=9
telephony.lteOnGsmDevice=1
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.r_buffer_cache_size=4
ro.hwui.path_cache_size=24
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=5
ro.hwui.texture_cache_flushrate=0.5
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.kernel.android.checkjni=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Running boot script...
/sbin/postrecoveryboot.sh: line 5: can't create /sys/class/leds/button-backlight/brightness: nonexistent directory
/sbin/postrecoveryboot.sh: line 6: can't create /sys/class/leds/R/device/led_blink: nonexistent directory
I:/sbin/postrecoveryboot.sh process ended with ERROR=1
Finished running boot script.
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/TWRP/.twrps'.
I:Backup folder set to '/external_sd/TWRP/BACKUPS/08faffb79c96eb46'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Switching packages (TWRP)
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log

In over 15 years of R&D testing of STBs and embedded devcies I´ve never seen such a f***ing flawed recovery design.
First of all it should never happen that connection to first stage bootloader is not possible anymore via ADB or (USB)serial. Then all recovery images lack of a real erase function, removing really all data and file rights by zeroing the sectors.
Damn, that bricked device was a real tricky one.
So here my solution for the boot loop (I don´t know if it does work for others but I will not go try this again....)
Install the LG Mobile Tools and start them. There is no need to set to Korea as country as described in some manuals (later more). Now install the offered device drivers if they (or newer drivers) are not already installed on your PC.
Boot into recovery whether it does it on itself, by "adb reboot recovery" or with the hardware key combination.
In recovery mode swipe system, data, cache, dalvik etc. Swipe really EVERYTHING your recovery does allow you to swipe.
In recovery call the boot-to-system function. Some recovery images may now offer to root the device, ignore this.
When the reboot started press both volume keys together and hold them until the download mode is activated (screen will be almost black with a very faded infobanner which signalizes download mode is enabled).
Connect the pad to the PC. The LG Mobile tools will automatically identify the device if connection can be established and show up if a software upgrade is available. Therefore no need to set up before to Korea as country since it does switch itself to the correct settings. If a software upgrade is offered then start it, if it says you have already the newest version then go to option and start a recover/repair update. In case a connection is not established try another USB port. For me it worked for e.g. with an USB3.0 port but it should also work with USB 2.0 ports. In some cases an active USB hub may help since they are powered externally.
Hope this might help others with the same problem.
Some words from me regarding the dyn.Kernel: do not flash it if it is not already confirmed that it will work together with your installed ROM version. I don´t know what really went wrong with it, but in my personal opinion there is a high risk to get this boot loop again which is really hard to break since normal swiping/reflashing did not work anymore on my device and LG recovery and ADB were affected, too.

I just found this thread after I had a similar experience.
In matter of fact the LG mobile tool helped. Since the mobile tool deletes and overrides everything is it easy to recover:
Turn of the device
Start LG Mobile tool (check that LG driver is installed)
Push volume up and down at the same time (not power button)
Plug into USB port
Release volume buttons
Now you can continue with LG Mobile tool
Do want to have the procedure again, took me a long time to get it fixed...
My mistake: Started OTA update with root which brought into situation above. I thought it would be worth to try with only deleting via SuperSu but root is not removed completely...
Gesendet von meinem LG-V500 mit Tapatalk

dummy1001 said:
I just found this thread after I had a similar experience.
In matter of fact the LG mobile tool helped. Since the mobile tool deletes and overrides everything is it easy to recover:
Turn of the device
Start LG Mobile tool (check that LG driver is installed)
Push volume up and down at the same time (not power button)
Plug into USB port
Release volume buttons
Now you can continue with LG Mobile tool
Do want to have the procedure again, took me a long time to get it fixed...
My mistake: Started OTA update with root which brought into situation above. I thought it would be worth to try with only deleting via SuperSu but root is not removed completely...
Gesendet von meinem LG-V500 mit Tapatalk
Click to expand...
Click to collapse
Thank you! This worked beautifully for me. I, too, took the OTA with root and got stuck in the TWRP boot loop. Was hopeful of a successful install even if losing root because of other's saying that they did without unrooting first. Lesson learned.

Thanks, you saved me. Power off GPad and after downloading driver press vol up and down at the same time. choose recovery from options in LG mobile support tool.

thanks
dummy1001 said:
I just found this thread after I had a similar experience.
In matter of fact the LG mobile tool helped. Since the mobile tool deletes and overrides everything is it easy to recover:
Turn of the device
Start LG Mobile tool (check that LG driver is installed)
Push volume up and down at the same time (not power button)
Plug into USB port
Release volume buttons
Now you can continue with LG Mobile tool
Do want to have the procedure again, took me a long time to get it fixed...
My mistake: Started OTA update with root which brought into situation above. I thought it would be worth to try with only deleting via SuperSu but root is not removed completely...
Gesendet von meinem LG-V500 mit Tapatalk
Click to expand...
Click to collapse
i registered the forum just for thank you. thank you my friend

Broken internal SD card

The partitioning of my internal SD card seems to be horribly broken, I haven't been able to find any solution that works.
When I run fdisk, and press p, this is what is shown:
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 4097 32768 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 4097 4225 1024 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 4225 4353 1024 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 4353 88064 669695+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 5121 5248 1024 47 Unknown
/dev/block/mmcblk0p6 6145 6784 5120 45 Unknown
/dev/block/mmcblk0p7 7169 7808 5120 4c Unknown
/dev/block/mmcblk0p8 8193 9472 10240 48 Unknown
/dev/block/mmcblk0p9 10241 10368 1024 46 Unknown
/dev/block/mmcblk0p10 11265 11648 3072 4a Unknown
/dev/block/mmcblk0p11 12289 12672 3072 4b Unknown
/dev/block/mmcblk0p12 13313 14336 8192 83 Linux
/dev/block/mmcblk0p13 14337 16384 16384 60 Unknown
/dev/block/mmcblk0p14 16385 20480 32768 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p15 20481 20864 3072 59 Unknown
/dev/block/mmcblk0p16 21505 21888 3072 5a Unknown
/dev/block/mmcblk0p17 22529 22912 3072 5b Unknown
/dev/block/mmcblk0p18 23553 23936 3072 58 Unknown
/dev/block/mmcblk0p19 24577 24704 1024 5d Unknown
/dev/block/mmcblk0p20 25601 26624 8192 83 Linux
/dev/block/mmcblk0p21 26625 28672 16384 83 Linux
/dev/block/mmcblk0p22 28673 37888 73728 83 Linux
/dev/block/mmcblk0p23 37889 38912 8192 83 Linux
/dev/block/mmcblk0p24 38913 41984 24576 76 Unknown
/dev/block/mmcblk0p25 41985 43008 8192 77 Unknown
/dev/block/mmcblk0p26 43009 43136 1024 78 Unknown
/dev/block/mmcblk0p27 44033 109568 524288 83 Linux
/dev/block/mmcblk0p28 109569 150528 327680 83 Linux
/dev/block/mmcblk0p29 150529 150912 3072 83 Linux
/dev/block/mmcblk0p30 151553 438272 2293760 83 Linux
/dev/block/mmcblk0p31 438273 440320 16384 83 Linux
/dev/block/mmcblk0p32 440321 440576 2048 83 Linux
when I try parted /dev/block/mmcblk10 and type print I get
Code:
Error: Unable to satisfy all constraints on the partition.
Any ideas, preferably a solution that doesn't cost money?

Wow.....if you were trying to format the 16 gb card that came with the phone first you need to Google SDFORMAT, it's a free download. Then pull the memory card it of your phone, put it in a micro sd to sd adapter, insert into a laptop and use the utility that you downloaded. However, those look like android partitions and under no circumstances are you to use Windows fdisk. Unless you want to brick your phone, hopefully you haven't already. If you have a custom recovery use the built in utility to handle the internal memory. Good luck.
Sent from my LG-D800 using XDA Free mobile app

[Q&A] [MOD][NOV 21] MultiROM v30

Q&A for [MOD][NOV 21] MultiROM v30
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 [MOD][NOV 21] MultiROM v30. 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!

Kernel: does not have kexec-hardboot patch
Guys, help me, please, solve the problem. I updated to Android 5.0.1 and now the program writes to me: "Kernel: does not have kexec-hardboot patch". There is a patch for 5.0.1?

FalseTrue said:
Guys, help me, please, solve the problem. I updated to Android 5.0.1 and now the program writes to me: "Kernel: does not have kexec-hardboot patch". There is a patch for 5.0.1?
Click to expand...
Click to collapse
You need a kernel with kaxec hardboot patch. Try elemental x. Or see if there is a stock one with the patch.

madbat99 said:
You need a kernel with kaxec hardboot patch. Try elemental x. Or see if there is a stock one with the patch.
Click to expand...
Click to collapse
Thanks for the reply. And how fast is usually a new version of the patch will released?

FalseTrue said:
Thanks for the reply. And how fast is usually a new version of the patch will released?
Click to expand...
Click to collapse
As soon as a new stock kernel comes out, someone usually immediately makes one with kaxec

Thanks you
madbat99 said:
As soon as a new stock kernel comes out, someone usually immediately makes one with kaxec
Click to expand...
Click to collapse
Thank you very much for your answer. Thought so.

Error MultiROM mr_update A0001
Hi, I have a big problem...
I have a 1+1 with cm11s 44S in primary ROM. I use MultiROM for testing new ROM's... I have AK35 cm12 kernel
I have installed 5 or 6 custom ROM cm12, without problem..
since lastest Rom's of multiple Dev, I can't install new version of their rom...
Exemple: I can install LiquidSmooth v4.0.0 of 21/11/2014... but i can't install the version of 27/11/2014 and newer..
Other custom ROM have same problem..
Install doesn't work because this problem: E:Error executing updater binary in zip '/tmp/mr_update.zip'
It comes only with newer versions..
Only AICP and Euphoria ROM are good and want to install...in their newer version
Installing ROM LS-LP-v4.0-2014-12-06-liqu...
Creating folders and images for type 1
Flashing ZIP file /sdcard/Download/LS-LP-v4.0-2014-12-06-liquid_bacon.zip
ROM: LS-LP-v4.0-2014-12-06-liqu
Preparing ZIP file...
rm: can't remove '/tmp/mr_update.zip': No such file or directory
Copying ZIP to /tmp...
updating: META-INF/com/google/android/updater-script
zip warning: Local Entry CRC does not match CD: META-INF/com/google/android/updater-script
(deflated 74%)
Changing mounts to ROM LS-LP-v4.0-2014-12-06-liqu...
I:Mount: Unable to find partition for path '/data'
I:Backup folder set to '/realdata/media/0/TWRP/BACKUPS/5e7b4ef6'
I:mount '/realdata/media/0' '/sdcard' process ended with RC=0
Irocessing '/data_t'
I:Created '/data_t' folder.
Irocessing '/system'
Irocessing '/cache'
I:Recreating /cache/recovery folder.
Partition Logs:
/modem | /dev/block/mmcblk0p1 | Size: 64MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: modem
Storage_Name: modem
Backup_Path: /modem
Backup_Name: modem
Backup_Display_Name: modem
Storage_Path: /modem
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl1 | /dev/block/mmcblk0p2 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: sbl1
Storage_Name: sbl1
Backup_Path: /sbl1
Backup_Name: sbl1
Backup_Display_Name: sbl1
Storage_Path: /sbl1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/rpm | /dev/block/mmcblk0p6 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p6
Display_Name: rpm
Storage_Name: rpm
Backup_Path: /rpm
Backup_Name: rpm
Backup_Display_Name: rpm
Storage_Path: /rpm
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/tz | /dev/block/mmcblk0p8 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p8
Display_Name: tz
Storage_Name: tz
Backup_Path: /tz
Backup_Name: tz
Backup_Display_Name: tz
Storage_Path: /tz
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modem_st1 | /dev/block/mmcblk0p10 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p10
Display_Name: modem_st1
Storage_Name: modem_st1
Backup_Path: /modem_st1
Backup_Name: modem_st1
Backup_Display_Name: modem_st1
Storage_Path: /modem_st1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modem_st2 | /dev/block/mmcblk0p11 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p11
Display_Name: modem_st2
Storage_Name: modem_st2
Backup_Path: /modem_st2
Backup_Name: modem_st2
Backup_Display_Name: modem_st2
Storage_Path: /modem_st2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/static_nv_bk | /dev/block/mmcblk0p13 | Size: 10MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p13
Display_Name: static_nv_bk
Storage_Name: static_nv_bk
Backup_Path: /static_nv_bk
Backup_Name: static_nv_bk
Backup_Display_Name: static_nv_bk
Storage_Path: /static_nv_bk
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/oppodycnvbk | /dev/block/mmcblk0p12 | Size: 10MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p12
Display_Name: oppodycnvbk
Storage_Name: oppodycnvbk
Backup_Path: /oppodycnvbk
Backup_Name: oppodycnvbk
Backup_Display_Name: oppodycnvbk
Storage_Path: /oppodycnvbk
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/aboot | /dev/block/mmcblk0p5 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p5
Display_Name: aboot
Storage_Name: aboot
Backup_Path: /aboot
Backup_Name: aboot
Backup_Display_Name: aboot
Storage_Path: /aboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/boot | /dev/block/mmcblk0p7 | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p7
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/realdata | /dev/block/mmcblk0p28 | Size: 56189MB Used: 1710MB Free: 39907MB Backup Size: 1710MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /realdata/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p28
Display_Name: Realdata
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /realdata/media/0
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/misc | /dev/block/mmcblk0p21 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p21
Display_Name: misc
Storage_Name: misc
Backup_Path: /misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: /misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p17 | Size: 16MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p17
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/logo | /dev/block/mmcblk0p22 | Size: 16MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p22
Display_Name: logo
Storage_Name: logo
Backup_Path: /logo
Backup_Name: logo
Backup_Display_Name: logo
Storage_Path: /logo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/reserve4 | /dev/block/mmcblk0p27 | Size: 64MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p27
Display_Name: reserve4
Storage_Name: reserve4
Backup_Path: /reserve4
Backup_Name: reserve4
Backup_Display_Name: reserve4
Storage_Path: /reserve4
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/data | /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/data | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Use_Rm_Rf Can_Be_Backed_Up IsPresent Ignore_Blkid
Primary_Block_Device: /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/data
Display_Name: Data
Storage_Name: data_t
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data_t
Current_File_System: ext4
Fstab_File_System: ext4
Bind_Of: /realdata
Backup_Method: files
/system | /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/system | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Use_Rm_Rf Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Ignore_Blkid
Primary_Block_Device: /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/system
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Bind_Of: /realdata
Backup_Method: files
/cache | /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/cache | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Use_Rm_Rf Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Ignore_Blkid
Primary_Block_Device: /realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/cache
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Bind_Of: /realdata
Backup_Method: files
I:Running cmd "dd if="/dev/block/mmcblk0p7" of="/realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/boot.img""
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.786623 seconds, 20.3MB/s
Current boot sector was used as base for fake boot.img!
I:Running cmd "echo '/dev/block/mmcblk0p7' > /tmp/mrom_fakebootpart"
I:Running cmd "mv "/dev/block/mmcblk0p7" "/dev/block/mmcblk0p7-orig""
I:Running cmd "ln -s "/realdata/media/0/multirom/roms/LS-LP-v4.0-2014-12-06-liqu/boot.img" "/dev/block/mmcblk0p7""
ZIP uses block updates
Creating system.img...
I:Creating image with cmd: make_ext4fs -l 1333M -a "/system" -S /file_contexts "/realdata/media/0/multirom/system.img"
Creating filesystem with parameters:
Size: 1397751808
Block size: 4096
Blocks per group: 32768
Inodes per group: 7760
Inode size: 256
Journal blocks: 5332
Label:
Blocks: 341248
Block groups: 11
Reserved block group size: 87
Created filesystem with 11/85360 inodes and 11226/341248 blocks
I:Running cmd "losetup "/dev/block/loop0" "/realdata/media/0/multirom/system.img""
I:Running cmd "mv "/dev/block/mmcblk0p14" "/dev/block/mmcblk0p14-orig" && ln -s "/dev/block/loop0" "/dev/block/mmcblk0p14""
I:Running cmd "rm "/realdata/media/0/multirom/system.img""
I:Running cmd "echo "/dev/block/mmcblk0p14" > /tmp/mrom_fakesyspart"
Installing '/tmp/mr_update.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.
line 2 col 6: syntax error, unexpected ENDIF, expecting $end
line 12 col 5: syntax error, unexpected ELSE, expecting $end
line 17 col 6: syntax error, unexpected ENDIF, expecting $end
3 parse errors
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/tmp/mr_update.zip'
rm: can't remove 'META-INF/com/google/android': No such file or directory
Failed to install ZIP!
I:Running cmd "busybox umount -d /tmpsystem"
umount: can't umount /tmpsystem: No such file or directory
I:Running cmd "rm "/dev/block/mmcblk0p14""
I:Running cmd "mv "/dev/block/mmcblk0p14"-orig "/dev/block/mmcblk0p14""
I:Running cmd "rm "/dev/block/mmcblk0p7""
I:Running cmd "mv "/dev/block/mmcblk0p7"-orig "/dev/block/mmcblk0p7""
Restoring mounts...
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /realdata: Device or resource busy
losetup: /dev/block/loop1: No such device or address
losetup: /dev/block/loop2: No such device or address
losetup: /dev/block/loop3: No such device or address
losetup: /dev/block/loop4: No such device or address
losetup: /dev/block/loop5: No such device or address
losetup: /dev/block/loop6: No such device or address
losetup: /dev/block/loop7: No such device or address
Iartition /realdata is mounted during TWPartitionManager:op_Context()
Updating partition details...
I:mount '/data/media/0' '/sdcard' process ended with RC=0
Iata backup size is 1710MB, free: 39893MB.
...done
I:Unable to find storage partition '/realdata/media/0'.
I:mount '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/5e7b4ef6'
Erasing incomplete ROM...
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'multirom_add'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Click to expand...
Click to collapse
Sorry for my very very bad English.
Pleaaase! HELP me!
Thanks for regarding!

Wifi stops working after install
I've tried 3 separate times to install multirom and each time it installs fine but once installed my wifi is automatically turned off. I go into settings and try to turn it back on, and it says it's turning it on but then it sits indefinitely without ever actually turning it back on. I'm using a Nexus 7 (2013) with 5.0.1 Any ideas?

Losing wifi
Everytime I install Multirom, I seem to lose wifi -- the indicator won't light up when I press it, and though I can slide the button to the right on the Wi-Fi Settings page,
This Nexus 7 arrived yesterday & I wasted little time trying to get Multirom on it, basically with the intent of booting Ubuntu. I'm not exactly a hacker, but I have managed to root my Nexus 4, so I'm not completely useless.
Twice now I've done this with the same result:
1. Successfully gain root with the device using Chainfire's "one-click script."
2. Use the MultiROM Manager app to do its stuff, which it successfully completes.
3. Reboot.
The reboot process completes successfully as far as I can tell, and everything seems to work, except wifi.

So here's my problem: I really want to install Multirom, but I can't unless it's rooted. As far as I can tell, the easiest way to root the device is flashing Chainfire's rom, but apparently doing so kills wifi. I guess I could proceed to install Multirom at that point and then install a different rooted rom but that's a little complicated, especially since I'm afraid of bricking in my ignorance.
Is there a simpler way for me to proceed? Or am I missing something.
Please note I am on Ubuntu only so cannot use Wug's windows thing.

Okay, so I used a buddy's Windows machine to root the N7 with Wugfresh's toolkit. Got home and used the Multirom Manager app to install, and watched it reboot and then add the kexec patch. I rebooted, and now have lost wifi, so I don't know what to do next. Did I miss a step somewhere? Should I copy a third-party rom and flash that?

So, let me try again: is this a known issue? It's the second time I've lost wifi after installing Multirom using the app. after rooting -- first with Chainfire's rom and then using Wugfresh's toolkit. I'm pretty sure I followed directions to the letter. Is there a fix I can try?

More information just in case: this is a Nexus 7 (2013), brand new
Android version 5.0.1
Kernel version
3.4..0-g20f5923
[email protected] #66
Wed Sep 25 22:02:11 CEST 2013
Build number LRX22C
Glad to provide more information if needed.

Hello All,
I am currently running multirom v30 on my 2013 Nexus 7.
Edit: I have an extfat formatted usb stick. I installed a cm12 nightly to the usb drive via multirom. When it boots the rom now hangs on the Google screen while the light on the usb drive flashes slowly. I am currently at a loss at what to do. Any and all help is appreciated!!!

ray field said:
More information just in case: this is a Nexus 7 (2013), brand new
Android version 5.0.1
Kernel version
3.4..0-g20f5923
[email protected] #66
Wed Sep 25 22:02:11 CEST 2013
Build number LRX22C
Glad to provide more information if needed.
Click to expand...
Click to collapse
Don't think it related to multirom. I have all the same as you and WiFi is fine. Have you tried forgetting that network and retyping the password? Make sure frequency is set to auto. WiFi is fine on multirom on nexus 7(2013) 5.0.1.

Calendar and book reader
I have been playing with multirom since I got my nexus 7 (2013). I installed it first thing. I installed several roms and I was wondering if there were any way to synch my calendar and my book reader across the roms. Calendar especially.

I'm running Paranoid 4.6 Beta 6 with patched Franco Kernel r17 as primary and want to flash latest CM 12 nightly as secondary. I followed the steps to add the custom ROM but when I flash the zip file it says something like "error executing binary file /tmp/mr_update.zip" What I'm trying to do is not possible? Should I try another CM 12 nightly? Is there any other good custom rom based on lollipop and compatible with multiROM that you could recommend?
BTW, my device is a Nexus 7 2013 (flo)

problems with my 3 rom in nexus 7 2013
Hello and thanks for any help. + sorry for my bad english.
I have nexus 7 2013 with sim and i just install multirom and flashed the second rom without any problems. The first rom is the original 4.4.4 and the second is ubuntu touch. I download kali linux for nexus 7 2013 and flash it from TWRP as new rom. It has installed successfuly but i gut an error trying to boot to that rom. Im attaching picture with the screen when it got the error.
Can some one help plz?
Cheers

The Latest Multirom v30 Seems Unstable
Hi all, I 'm a Multirom user. since I found I can`t boot into AICP rom after it`s ota update, I backed up and erased everything. Then I downloaded google`s factory image and runned flash-all.bat file smoothly. After that, I did: boot system (seccess) and reboot into bootloader --> flash twrp_multirom_20150115.img --> install kernel_*_501.zip&&multirom_v30.zip --> add previous rom backups --> reboot system ,till now,everything seems OK . I can boot into any of the secondary roms.
Ａ．But Problems happened after I renamed the secondary roms in the recovery, like "bckp--DATE--AICP“ ->"AICP", "bckp--DATE--CM_Games" -> "CM_Games". It tends to boot into the PRIMARY ROM when I tap the First SECONDARY ROM ;when I tap other secondary roms , it stuck at Google Logo. If I give the Secondary ROMs long-names back , it can boot into the 1st secondary rom , stuck at Google Logo if I tap other Secondary rom I backed up before.
Ｂ．Besides, after I installed firefox_OS_1.3.zip,CM_20150125.zip,AICP_20150125.zip individually as secondary rom ,I failed booting into them. １.Firefox_OS:stuck at Google Logo,２.CM&&AICP:stopped at boot animation.(I am bored to and don`t try the "swap" option or rename)
Anyone who knows any temp solution(s) about those bugs?Should I upload the log file?
It seems that the short-name bug exits for a long time. Anyway , thanks for your multirom @Tasssadar !
Sorry for my bad English.

running X applications in Xmir in Ubuntu Touch
Finally I figured out a way to run X applications in Ubuntu Touch using clues from here:
www dot youtube dot com/watch?v=XfMLzlki9XE
www dot phoronix dot com/scan.php?page=news_item&px=Ubuntu-Unity-8-Pre-MWC-Demo
1. Install Ubuntu Touch Vivid Proposed via MultiROM
2. Increase the disk image size for Ubuntu
3. boot Ubuntu
4. enable developer mode
5. connect via adb
6. mount image writable
Code:
mount / -o rw,remount
touch /userdata/.writable_image # to keep rw after reboots
7. install Xmir
Code:
wget 'https://launchpad.net/~mlankhorst/+archive/ubuntu/ppa//+files/xserver-xorg-xmir_1.17.1-0ubuntu1%7Eppa1%2Bsa7_armhf.deb'
wget 'https://launchpad.net/~mlankhorst/+archive/ubuntu/ppa//+files/xserver-xorg-core_1.17.1-0ubuntu1~ppa1+sa7_armhf.deb'
wget 'https://launchpad.net/~mlankhorst/+archive/ubuntu/ppa//+files/xserver-common_1.17.1-0ubuntu1%7Eppa1%2Bsa7_all.deb'
dpkg --install *.deb
8. place a script like this in your home
Code:
#!/bin/bash
DISPLAY=:1
Xmir $DISPLAY
sleep 1
xeyes
9. make it executable
Code:
[email protected]:~$ chmod +x test.sh
10. place a file like this in ~/.local/share/applications/test.desktop
Code:
[Desktop Entry]
Name=Test
Type=Application
Terminal=false
Icon=/usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/Themes/Ambiance/artwork/[email protected]
X-Ubuntu-Touch=true
Exec=/home/phablet/test.sh
11. pull down on the "Apps" home screen in Ubuntu Touch, now you should see the Test icon appear
12. launch Test and see xeyes appear
It seems to work with all applications I tried so far (xeyes, xterm, icewm, libreoffice-writer). A keyboard plugged in via USB OTG works ok, touch works, external mouse kinda works. The mouse cursor doesnt show, so that makes for awkward usage, also xeyes only seems to register the position upon click, not upon moving around.

After repartitioning /dev/block/mmcblk0p15 is missing - mount /data (invalid argument

Hello,
I wanted to flash Android 6 on my Xperia S (32GB).
Bootloader + root are unlocked.
I downloaded the image and extracted the .zip file.
=> new cmd:
Code:
fastboot flash boot recovery.img
fastboot reboot
Now the TWRP 3.0 screen appeared.
The problematic part was now the reparitioning.
Here you can see the full output (I followed this steps: http://forum.xda-developers.com/showpost.php?p=64862885&postcount=2)
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 973824.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-954240, default 769): 42945
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
Using default value 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
The next step was
Code:
Now we will convert /data and /cache to F2FS.
Ext4 is not supported anymore on nAOSProm. You don't need to take care about the 16384 byte to reserve for encryption. TWRP will do it for you.
Wipe => Advanced Wipe => select Data => Repair or Change File system => Change File System =>F2FS =>Swipe to Change
Code:
Mount Point /data
File system: f2fs
Present: Yes
Size: 0MB
Free: 0MB
Used: 0MB
Changing the file system results in:
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Failed to mount /data (Invalid argument)
MTP Enabled
Failed to mount /data (Invalid argument)
If I execute
Code:
fdisk -l /dev/block/mmcblk0
I see that /dev/block/mmcblk0p15 is missing.
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Can anyone help me out please?
Thanks in advance.

Kesandal said:
Hello,
I wanted to flash Android 6 on my Xperia S (32GB).
Bootloader + root are unlocked.
I downloaded the image and extracted the .zip file.
=> new cmd:
Code:
fastboot flash boot recovery.img
fastboot reboot
Now the TWRP 3.0 screen appeared.
The problematic part was now the reparitioning.
Here you can see the full output (I followed this steps: http://forum.xda-developers.com/showpost.php?p=64862885&postcount=2)
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 973824.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-954240, default 769): 42945
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
Using default value 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
The next step was
Code:
Now we will convert /data and /cache to F2FS.
Ext4 is not supported anymore on nAOSProm. You don't need to take care about the 16384 byte to reserve for encryption. TWRP will do it for you.
Wipe => Advanced Wipe => select Data => Repair or Change File system => Change File System =>F2FS =>Swipe to Change
Code:
Mount Point /data
File system: f2fs
Present: Yes
Size: 0MB
Free: 0MB
Used: 0MB
Changing the file system results in:
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Failed to mount /data (Invalid argument)
MTP Enabled
Failed to mount /data (Invalid argument)
If I execute
Code:
fdisk -l /dev/block/mmcblk0
I see that /dev/block/mmcblk0p15 is missing.
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Can anyone help me out please?
Thanks in advance.
Click to expand...
Click to collapse
What You have done is correct, The problem is since there is no space available at end of data partition for encryption, it is giving the error. Are You sure the TWRP version is 3.0? Try rebooting to TWRP once and converting the file system. If that doesn't work, I would recommend using recovery from latest version of nAOSP.
Also, /dev/block/mmcblk0p15 is supposed to be missing. This command
Command (m for help): d
Partition number (1-15): 15
deletes the partition.
p14 is the data partition and p15 was the internal storage.
In Marshmallow version, a different type of storage structure is used. There is no concept of separate internal storage in it, the storage is merged with data partition.
Here, p14 is the

How to make cache partition in recovery? want to install factory ROM via adb.

Hi xda.
My fire phone keeps power off itself a few weeks ago. so I did factory reset and installed google play store related apps as I used to use. PLUS only this time I disabled some amazon apps that I don't use at all to save ram. (calendar, home right panel, wallet and all Whispernet apps ) after that it freezing and power off again like before the reset. and do that more often.
I thought its because I didn't factory reset thoroughly. and this time did 'wipe cache partition' first. I pretty sure that's my mistake.
after that the phone won't boot up. and even get hard to get in Fire System Recovery menu. after so many tries I managed to get to recovery . and it says...
{
"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"
}
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/dropbox_last_kmsg
E:Can't open /cache/recovery/dropbox_last_kmsg
E:failed to mount /cache (Invalid argument)
the cache partition deleted totally. and 'wipe data/factory reset' not worked.
still I try to sideload 'update-kindle-35.4.6.6_user_466001420.bin' via ADB. the bin file could transferred to the phone but can't be installed due to the same reason.
Now send the package you want to apply
to the device with "adb sideload <filename>"...
E:failed to mount /cache (Invalid argument)
E:failed to set up expected mounts for install; aborting
Installation aborted.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/dropbox_last_kmsg
E:Can't open /cache/recovery/dropbox_last_kmsg
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/dropbox_last_kmsg
E:Can't open /cache/recovery/dropbox_last_kmsg
E:failed to mount /cache (Invalid argument)
If I make the missing cache partitions, can I install the ROM? To doing that I did adb shell commands and it returns 'error:closed'. the phone is not rooted.
Please reply anything you know about it. clue, ideas
Thank you very much. :good:

Will Custom ROM helpful?
Can Installing custom rom will make it easier then using stock rom ?
like Fire Nexus ROM - KTU84Q [09 June 2016]
http://forum.xda-developers.com/fire-phone/orig-development/rom-fire-nexus-rom-ktu84q-t3316848

bricked forever?
or should I ask help to Amazon?

Can I get root permission at this situation ?

here's my updated status
after full charging . connect to my desktop (windows server 2012 R2)via USB. it shows green battery gauge middle of the screen.
turn on. > Shows Amazon logo then Fire animation then Stop, off itself. during this computer recognize it 'Android'
when keep pressing power button the phone vibrate little but showing nothing on screen . during this computer recognize it 'QHSUSB_BULK' and appear some disks on computer explorer .
some partition is reachable on computer explorer
here's the list of ALL partitions
Disk 3: \Device\Harddisk3\DR3
BusType: USB
Media Type: RAW
DiskGeometry Layout:
BytesPerSector = 512
SectorsPerTrack = 63
TracksPerCylinder = 255
Cylinderst = 3801
MediaType: Fixed
Partition Numbers: 19
Partition Type: GPT
StartingOffset: 17408
PartitionLength: 2048
MountPoints: (D
Partition Type: GPT
StartingOffset: 19456
PartitionLength: 1024
MountPoints:
Partition Type: GPT
StartingOffset: 20480
PartitionLength: 8192
MountPoints:
Partition Type: GPT
StartingOffset: 28672
PartitionLength: 32768
MountPoints:
Partition Type: GPT
StartingOffset: 67108864
PartitionLength: 32768
MountPoints:
Partition Type: GPT
StartingOffset: 67141632
PartitionLength: 67108864
MountPoints: (F
Partition Type: GPT
StartingOffset: 201326592
PartitionLength: 524288
MountPoints:
Partition Type: GPT
StartingOffset: 201850880
PartitionLength: 524288
MountPoints:
Partition Type: GPT
StartingOffset: 202375168
PartitionLength: 524288
MountPoints:
Partition Type: GPT
StartingOffset: 202899456
PartitionLength: 1572864
MountPoints:
Partition Type: GPT
StartingOffset: 204472320
PartitionLength: 1572864
MountPoints:
Partition Type: GPT
StartingOffset: 268435456
PartitionLength: 1572864
MountPoints:
Partition Type: GPT
StartingOffset: 270008320
PartitionLength: 33554432
MountPoints: (G
Filesystem: EXT4
codepage:utf8
Size: 33554432
Free: 18194432
Partition Type: GPT
StartingOffset: 335544320
PartitionLength: 2097152
MountPoints:
Partition Type: GPT
StartingOffset: 402653184
PartitionLength: 10485760
MountPoints:
Partition Type: GPT
StartingOffset: 413138944
PartitionLength: 10485760
MountPoints:
Partition Type: GPT
StartingOffset: 423624704
PartitionLength: 2147483648
MountPoints: (H
Filesystem: EXT4
codepage:utf8
Size: 2147483648
Free: 120090624
Partition Type: GPT
StartingOffset: 2571108352
PartitionLength: 1717986304
MountPoints: (I
Partition Type: GPT
StartingOffset: 4289094656
PartitionLength: 26979424768
MountPoints: (J
Volume: \Device\HarddiskVolume5:
Filesystem: RAW
Mountpoints: (D
Volume status: Online
size: 2048
free space: 2048
Extent: 0
DiskNumber: 3
StartingOffset: 17408
ExtentLength: 2048
Volume: \Device\HarddiskVolume6:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 1024
free space: 1024
Extent: 0
DiskNumber: 3
StartingOffset: 19456
ExtentLength: 1024
Volume: \Device\HarddiskVolume7:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 8192
free space: 8192
Extent: 0
DiskNumber: 3
StartingOffset: 20480
ExtentLength: 8192
Volume: \Device\HarddiskVolume8:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 32768
free space: 32768
Extent: 0
DiskNumber: 3
StartingOffset: 28672
ExtentLength: 32768
Volume: \Device\HarddiskVolume9:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 32768
free space: 32768
Extent: 0
DiskNumber: 3
StartingOffset: 67108864
ExtentLength: 32768
Volume: \Device\HarddiskVolume10:
Filesystem: FAT
Mountpoints: (F
Volume status: Online
size: 67059712
free space: 10059776
Extent: 0
DiskNumber: 3
StartingOffset: 67141632
ExtentLength: 67108864
Volume: \Device\HarddiskVolume11:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 524288
free space: 524288
Extent: 0
DiskNumber: 3
StartingOffset: 201326592
ExtentLength: 524288
Volume: \Device\HarddiskVolume12:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 524288
free space: 524288
Extent: 0
DiskNumber: 3
StartingOffset: 201850880
ExtentLength: 524288
Volume: \Device\HarddiskVolume13:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 524288
free space: 524288
Extent: 0
DiskNumber: 3
StartingOffset: 202375168
ExtentLength: 524288
Volume: \Device\HarddiskVolume14:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 1572864
free space: 1572864
Extent: 0
DiskNumber: 3
StartingOffset: 202899456
ExtentLength: 1572864
Volume: \Device\HarddiskVolume15:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 1572864
free space: 1572864
Extent: 0
DiskNumber: 3
StartingOffset: 204472320
ExtentLength: 1572864
Volume: \Device\HarddiskVolume16:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 1572864
free space: 1572864
Extent: 0
DiskNumber: 3
StartingOffset: 268435456
ExtentLength: 1572864
Volume: \Device\HarddiskVolume17:
Filesystem: EXT4
Mountpoints: (G
Volume status: Online,codepage:utf8
size: 33554432
free space: 18194432
Extent: 0
DiskNumber: 3
StartingOffset: 270008320
ExtentLength: 33554432
Volume: \Device\HarddiskVolume18:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 2097152
free space: 2097152
Extent: 0
DiskNumber: 3
StartingOffset: 335544320
ExtentLength: 2097152
Volume: \Device\HarddiskVolume19:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 10485760
free space: 10485760
Extent: 0
DiskNumber: 3
StartingOffset: 402653184
ExtentLength: 10485760
Volume: \Device\HarddiskVolume20:
Filesystem: RAW
Mountpoints:
Volume status: Online
size: 10485760
free space: 10485760
Extent: 0
DiskNumber: 3
StartingOffset: 413138944
ExtentLength: 10485760
Volume: \Device\HarddiskVolume21:
Filesystem: EXT4
Mountpoints: (H
Volume status: Online,codepage:utf8
size: 2147483648
free space: 120090624
Extent: 0
DiskNumber: 3
StartingOffset: 423624704
ExtentLength: 2147483648
Volume: \Device\HarddiskVolume22:
Filesystem: RAW
Mountpoints: (I
Volume status: Online
size: 1717986304
free space: 1717986304
Extent: 0
DiskNumber: 3
StartingOffset: 2571108352
ExtentLength: 1717986304
Volume: \Device\HarddiskVolume23:
Filesystem: RAW
Mountpoints: (J
Volume status: Online
size: 26979424768
free space: 26979424768
Extent: 0
DiskNumber: 3
StartingOffset: 4289094656
ExtentLength: 26979424768
I have researched with this condition.
what I got so far is using EMMCRAW_1.4.0.0 to restore partitions
OR QPST follow this guide http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/
thing is I am not sure this guide can be applied with my Fire phone without problem.
and I couldn't find good guide to restoring partitions.
any experience with this will helpful

@pure7258
http://forum.xda-developers.com/fire-phone/help/bricked-firephone-t3268133/post64876520#post64876520
http://forum.xda-developers.com/fire-phone/help/bricked-firephone-t3268133/post64939562#post64939562
http://forum.xda-developers.com/fire-phone/help/bricked-firephone-t3268133/post64932890#post64932890

Kramar111 said:
@pure7258
http://forum.xda-developers.com/fire-phone/help/bricked-firephone-t3268133/post64876520#post64876520
http://forum.xda-developers.com/fire-phone/help/bricked-firephone-t3268133/post64939562#post64939562
http://forum.xda-developers.com/fire-phone/help/bricked-firephone-t3268133/post64932890#post64932890
Click to expand...
Click to collapse
Thank you~
I saw this thread and now you gave me confidence .
----
my EMMCRAW_1.2.1.0 partition structure result is same to @duxbak99 's
before doing your step
installed Qcomm_Drivers, QHSUSB_BULK turns to Qualcomm HS-USB QDLoader 9008 and a disk drive.
I wrote files only except "NON-HLOS.bin >> modem" it gives error over again
so I was going to charge the phone more and try again.
after disconnect the phone and charged. It won't turn on at all. connect to the desktop only shows Qualcomm HS-USB QDLoader 9008 but not the drive.
I did Power and Vol +
I keep pressed power button nearly 5 minutes
press all buttons
not working all
so frustrating....