I achive for now:
!!!! Restore from any softbrick (any partition ful corrupted emmc) almost infalible!!! i have soft bricked bootloaders gpt, more than 10 times and resurrected again
A clowermod recovery
Semi flashed with f70 d315 stock?
I´m working when i can i post my results
Root
root is easy just use Towelroot
Clowermod Recovery
Tanks to OpenBump
put in sdcard and
Code:
adb shell
su
dd if=/sdcard/cwmrecovery_bumped.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery
Clower mod for L31L
Boot loader
The bootloader has some protection in aboot
if you disasemble with idapro is idem to the f70 d315, g2 mini and family the block that you have to patch
but this file is protected if you pach a single bit it bring you a raw disk when conect the phone (Q9006 mode)
-----OLD POST--------
I have a LG F70 D315 from tracfone whit this company the models change to LGL31L but I verify and many references says that is F70 an no other
I wan to flash whit a lesser restrictive firmware that not belong to this company to later flash a custom room, volume down while conet to get DOWNLOAD MODE are removed from this phone
I have KDZ, extracted to , i rooted sucefully the phone, got recovery mode
but the only way I find to flash is via download and this mode dosent apear
I think is rplace with a batery charging becouse that is what I see whit
Code:
adb reboot-bootloader
and others
and when try key conbinations to power up to download mode it bring me to the batery loader again
In the original extracted f70 d315 kdz the download mode is in the laf partition
I have it have a diferent size of the original fone laf
there is a way to push this to get download mode?
Sorry for my bad English and for post in this secction becouse I dont find LG 70 board
thanks
The partition info off the phone is this
Code:
shell># cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 22528 mmcblk0p15
179 16 22528 mmcblk0p16
179 17 22528 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 512 mmcblk0p30
179 31 2097152 mmcblk0p31
259 0 921600 mmcblk0p32
259 1 4220416 mmcblk0p33
259 2 40943 mmcblk0p34
179 32 512 mmcblk0rpmb
shell># ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 20:09 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 20:09 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 20:09 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 20:09 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 20:09 cache -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-02 20:09 drm -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 20:09 eksst -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-02 20:09 encrypt -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 20:09 factory -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 20:09 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 20:09 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 20:09 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 20:09 grow -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-02 20:09 laf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 20:09 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 20:09 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 20:09 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 20:09 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 20:09 mpt -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-02 20:09 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 20:09 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 20:09 rct -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 20:09 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 20:09 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 20:09 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 20:09 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 20:09 sbl1b -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 20:09 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 20:09 sns -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 20:09 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 20:09 system -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-02 20:09 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 20:09 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 20:09 userdata -> /dev/block/mmcblk0p33
shell># parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8389kB 75.5MB 67.1MB fat16 modem
2 75.5MB 76.5MB 1049kB sbl1
3 76.5MB 77.1MB 524kB rpm
4 77.1MB 77.6MB 524kB tz
5 77.6MB 78.1MB 524kB sdi
6 78.1MB 80.2MB 2097kB aboot
7 80.2MB 80.7MB 524kB rpmb
8 80.7MB 81.3MB 524kB tzb
9 81.3MB 83.4MB 2097kB abootb
10 83.4MB 85.5MB 2097kB pad
11 85.5MB 88.6MB 3146kB modemst1
12 88.6MB 91.8MB 3146kB modemst2
13 91.8MB 109MB 16.8MB misc
14 109MB 143MB 33.6MB ext4 persist
15 143MB 166MB 23.1MB laf
16 168MB 191MB 23.1MB boot
17 191MB 214MB 23.1MB recovery
18 214MB 217MB 3146kB fsg
19 218MB 219MB 524kB fsc
20 219MB 219MB 524kB ssd
21 226MB 227MB 524kB DDR
22 235MB 235MB 524kB encrypt
23 235MB 236MB 524kB rct
24 243MB 252MB 8389kB ext4 drm
25 252MB 260MB 8389kB ext4 sns
26 260MB 281MB 21.0MB factory
27 281MB 315MB 33.6MB fota
28 319MB 320MB 1049kB sbl1b
29 320MB 353MB 33.6MB ext4 mpt
30 353MB 354MB 524kB eksst
31 361MB 2508MB 2147MB ext4 system
32 2508MB 3452MB 944MB ext4 cache
33 3452MB 7774MB 4322MB ext4 userdata
34 7776MB 7818MB 41.9MB grow
(parted) q
I copy laf to recovery partition with dd and bring me to Download Mode when I enter to recovery but i dont find a way to flash yet
unlock boot loader
I maybe try to flash via custom recovery but i have to unlock bootloader
This method
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
says change bites in this string 20 00 EB 00 00 50 E3 E0 FF FF 0A
The stock firmware have this string in aboot.img 20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f e5
but the aboot of my phone the string change to
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a
and is the string only string that match to 20 00 eb 00 00 50 e3
20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f ->stock firm
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a ->current room
If i change this with this conditions the phone may not boot anymore?
I am trying to get the download mode for the L31l and am wondering how you copied the files to the recovery partition.
I got the kdz file extracted it and extracted the dz files and have the binfiles.
I have also created an image file by combining the bin files but don't think this will do anything.
I am planning to use the method from:
htt p://ww w.lg-phone s.org/how-to-flas h-unbrick-lg-f70-bac k-to-stoc k.htm l
(Remove spaces)
To flash the kdz file of I can get download mode to work.
Thanks
Download mode
To get download mode:
1-To get download mode I rooted easy with towelroot
2-With dd made a backup of all partitions (nandroid backup)
3-Flash laf partition to recovery (change msm_sdcc I dont know exactly the name because I don´t have phone here and my tools):
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/dev/block/platform/msm_sdcc.1/by-name/recovery
4-Do
Code:
adb shell
reboot recovery
and you will enter to download instead of recovery
but for me was unseful because the firmware is for Lgf70 and is a lgl31l
and any flash sofware detected
I do the last I posted and dead:silly: to usb qualcom mode that see as raw disk
http://forum.xda-developers.com/showthread.php?t=2582142
this mode is easy to recover but intead I fail and dd other partition sbl
and have a mode that is very very triky and dont find how to solve
cause nothing worme form my phone
This a mode who I'am now QDLoader 9008
{
"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"
}
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830/page17#post58460319
I also got into download but couldn't get it to load the F70 rom.
Anybody have any ideas?
Thanks for your work. Have you been able to load the portion of the f70 rom that contains the hidden menu for unlock?
I know there is some information about adding it back to the verizon g2 available.
Thanks again
Any more info to share?
You mentioned a f70 rom. Any more luck getting it to work?
Thanks
f70 rom
1god 1Bad news I flash the f70 but the unlock menu says that not more atemps left (usseless)
Flash f70 room bricks me the phone many times with a backup I can bring back ever I want but may sometimes have to open the phone and make a tespoint
Frist backup all your phone whit dd
I backup all single partition
dd if=/dev/block/platform/msm_sdcc.1/by-name/xxx of=/sdcard/backup
and after backup the GPT partition table
you beter dd all then phone mmc instead
of course copy to a PC or any external
Extract boot.img and system.img of F70 room kdztools etc...
For f70 room you have to bumped boot.img of F70
frist have to repack whit bootimg.exe http://en.miui.com/thread-27657-1-1.html
descompress and compress
and after used open bump
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
Better put frist system.img to sdcard
1)whit dd flash the recovery to the boot img after that youre phone start always in recovery
because no recovery convination
2)flash boot.img to recovery
3) Now when you turn your phone start in the recovery mount /sdcard /system...
conect in and this recovery have adb
flash whit dd system partition
don't exit recovery
4)wipe cache factory reset
5) in avanced revot recovery will boot system (anytimes you power on have to do this)
The gide is not easy and safe i can made a better but flash f70 dosen't worst
yes you have more usb modes enabled, wifi theter and hotspot
but no unock , even any unlock boxes that have f70 direct unlock
all becuse the nvram is not accesible????
i brick my d315 with update v10e
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english
willowlefou said:
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english
Click to expand...
Click to collapse
I resolved my problem ,
I have backup the LAF files so in TWRP I 've restore the laf
Code:
dd if=/sdcard/backup/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
after i reboot in download mode ( power off / button up + plug usb cable )
the LGFlashTool2014 detect my phone i Ican retore the D31510e_00.kdz file with this tools.
my data aren't destroy.
thanks!
Hi guys! My lg f70 phone broken after use flash tool, (Qdloader 9008), i search fixing on internet, and finding them QFIl and qpst.. My phone cpu msm8926, need emmc firehose 8926 file for flashing emmc and fastboot restore file, somebody help? Sorry my bad english!
Related
Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app
Chance77 said:
Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app
Click to expand...
Click to collapse
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.
LG already released source. https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=vk810
edgemaster191 said:
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.
Click to expand...
Click to collapse
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.
prana22 said:
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.
Click to expand...
Click to collapse
I would do something but I have never even compiled CM11 let alone tweaked it to work with a new device. I can work with a developer who doesn't have one, but I don't know enough to do it on my own.
That is where I am as well. I know just enough to get myself in trouble.
Sent from my VK810 4G using XDA Free mobile app
anyone care to share a system dump of the VK810?
boot.img and system partition would be useful
my local verizon store refuses to sell it to me without a contract............ sigh
probably going to get it from amazon
Sure, how do I do that? <-- I am a noob
popezaphod said:
Sure, how do I do that? <-- I am a noob
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2450045
info about the various partitions,good reading: http://www.all-things-android.com/content/review-android-partition-layout
if you have the custom recovery installed, you could do a backup of the device from recovery and share the files
don't share your EFS partition because it contains your unique IMEI/ESN number, and sometimes devices break if you flash someone else's EFS partition. don't share your userdata partition obviously
(if you can't figure out which is the EFS partition from the WAY #2 image, or how to do a system dump, I just need the following partitions and partition layout)
What I need:
1) Following partitions
BOOT - contains ramdisk info necessary to compile a working boot image
RECOVERY - not that necessary, but more info is useful
SYSTEM - probably contains modem libraries not present in the v500 system partition
2) Partition Layout
needed to compile a working ROM
more info is better... so a complete system dump (minus EFS and userdata) would be great
thanks for helping...
Good Amount of Info
ro.product
Code:
[ro.product.board]: [MSM8960]
[ro.product.brand]: [lge]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [altev]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [LGE]
[ro.product.model]: [VK810 4G]
[ro.product.name]: [altev_vzw]
[email protected]:/ # getprop | grep ro.build.
ro.build
Code:
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1392900914]
[ro.build.date]: [Thu Feb 20 21:55:14 KST 2014]
[ro.build.description]: [altev_vzw-user 4.2.2 JDQ39B VK81010C.1392900840 release
-keys]
[ro.build.display.id]: [JDQ39B]
[ro.build.fingerprint]: [lge/altev_vzw/altev:4.2.2/JDQ39B/VK81010C.1392900840:us
er/release-keys]
[ro.build.host]: [LGEARND9B11]
[ro.build.id]: [JDQ39B]
[ro.build.product]: [altev]
[ro.build.tags]: [release-keys]
[ro.build.target_country]: [US]
[ro.build.target_operator]: [VZW]
[ro.build.target_region]: [US]
[ro.build.type]: [user]
[ro.build.user]: [hyungjin.yoo]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [VK81010C.1392900840]
[ro.build.version.release]: [4.2.2]
[ro.build.version.sdk]: [17]
Stock aBoot img
https://www.dropbox.com/s/kf3fysyhvlyw8l0/aboot.img
Boot IMG w/ TWRP Installed(Not sure if that matters or not)
https://www.dropbox.com/s/egm0rp381cahbeo/boot.img
TWRP Recovory
https://www.dropbox.com/s/ypwreq1c07yj36v/VK810_twrp_2.7.0.1.zip
Recovory IMG w/ TWRP Installed
https://www.dropbox.com/s/23xy2o8qydqsunu/recovery.img
Stock build.prop
https://www.dropbox.com/s/4rqciye90mhp1cj/build.prop
Partitions
Code:
7 0 5229 loop0
7 1 22901 loop1
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 2195456 mmcblk0p23
179 24 1392640 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 11247616 mmcblk0p35
259 4 4079 mmcblk0p36
254 0 5229 dm-0
254 1 22900 dm-1
lrwxrwxrwx root root 1970-01-13 12:13 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-13 12:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-13 12:13 bnr -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-13 12:13 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-13 12:13 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-13 12:13 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-13 12:13 eksst -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-13 12:13 encrypt -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-13 12:13 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-13 12:13 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-13 12:13 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-13 12:13 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-13 12:13 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-13 12:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-13 12:13 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-13 12:13 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-13 12:13 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-13 12:13 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-13 12:13 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-13 12:13 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-13 12:13 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-13 12:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-13 12:13 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-13 12:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-13 12:13 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-13 12:13 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-13 12:13 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-13 12:13 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-13 12:13 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-13 12:13 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-13 12:13 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-13 12:13 tzbak -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-13 12:13 userdata -> /dev/block/mmcblk0p35
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You
NICG said:
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You
Click to expand...
Click to collapse
Thanks for posting....
Slightly strange values...
VK810 (LTE):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2248146944 # 2114M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 11517558784 #10984
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
V500 (wifi):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 880803840 # 840M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 6189744128 # 5.9G
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
can you post the output of the below command? Want to verify the BOARD_FLASH_BLOCK_SIZE settings
cat /proc/mtd
EDIT1:
Who wants to be a guinea pig for my first cm-11.0 build? (requires you to have TWRP recovery)
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img is already LOKI patched
<removed>
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....
I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed
traccdma said:
I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed
Click to expand...
Click to collapse
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)
paperWastage said:
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)
Click to expand...
Click to collapse
i think we should stick with v500/v510/vk810 convention.....
http://forum.xda-developers.com/showpost.php?p=48103469&postcount=22
from this, it looks like the recovery image needs to be fixed...
http://forum.xda-developers.com/showpost.php?p=48331517&postcount=10
for now, I've manually edited the META-INF/com/google/android/updater-script to include "altev" as part of the check
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img will be LOKI-patched during the flash (which means don't use my previous upload where I pre-patched the boot.img)
http://d-h.st/tAq
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
hmm, not sure why TWRP is complaining. need to investigate tomorrow. if the update_script failed, then the boot.img wasn't patched, so the new boot image won't boot at all.
were you able to restore from nandroid backup?
you also try replacing the update-binary in the ROM with this
http://forum.xda-developers.com/showthread.php?t=2532300
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
whenever that happens get a recovery log, They are very helpful
traccdma said:
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
Click to expand...
Click to collapse
good to hear...
need two things:
system dump of stock ROM.
The proprietary libs I'm using right now is from v500 which probably doesn't have the radio libs. maybe wifi/bt driver is different too
logs
As Drgravy said, logs are helpful. Recovery log, /proc/last_kmsg from kernel boot, ...
Sorry been a little busy but here you go.
Stock Rooted System IMG
https://www.dropbox.com/s/rpxmbp1lgb5a4k9/system.img
Didn't see this listed yet so thought I would do it. Mods feel free to merge or delete or slap me upside the head if needed ;p
I would assume these to be the same on the EU version but I could be wrong. If someone with the EU version would reply with the partitions to this post then we would have it all in one post
[email protected]_P821A10:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 196608 zram0
179 0 3817472 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 128 mmcblk0p3
179 4 32 mmcblk0p4
179 5 512 mmcblk0p5
179 6 500 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 500 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1536 mmcblk0p11
179 12 786432 mmcblk0p12
179 13 1048576 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 262144 mmcblk0p15
179 16 10240 mmcblk0p16
179 17 1024 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 1 mmcblk0p19
179 20 8 mmcblk0p20
179 21 4 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 4 mmcblk0p23
179 24 933871 mmcblk0p24
179 32 4096 mmcblk0rpmb
[email protected]_P821A10:/ #
[email protected]_P821A10:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-01 01:00 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 01:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 01:00 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 01:00 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 01:00 factory -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 01:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 01:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 01:00 grow -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 01:00 misc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 01:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 01:00 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 01:00 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 01:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 01:00 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 01:00 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 01:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 01:00 safeKeybox -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 01:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 01:00 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 01:00 splash -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 01:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 01:00 system -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 01:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 01:00 userdata -> /dev/block/mmcblk0p13
[email protected]_P821A10:/ #
I was an idiot and attempted to flash the DP4 OTA zip file in TWRP. It started and progressed for a little bit then failed, and then it couldn't see any of my partitions. I tried to reboot into bootloader, but now the phone will literally not do anything (no LED, no screen, no vibrate), except sometimes give me some USB Com3 device in device manager.
Apparently I'm the second one on XDA that this has happened to, but the other guy just RMA'd his phone and didn't try and solve it using QPST or anything. I've got an RMA started with huawei, but they indicate it will take 10-14 business days from the day they receive my phone through UPS ground. Uggghhh...
Any alternatives?
ok, so I believe I could actually fix this myself if I had access to the contents of the bootloader. there are lots of utilities to restore "fastboot ROMs" to qualcomm SoC phones.
would someone mind running this for me on their 6p via an adb shell (then copying and pasting the results here)?
parted /dev/block/mmcblk0
all it does is print out the partition list from your phone
I'm kind of curious about how to solve this, so keep me posted on any updates. I'll do what I can to help.
Running parted in an adb shell isn't going to do anything, as parted is a CLI partition manager that doesn't exist on android. You can run parted on the majority of linux systems, but not on adb shell. What exactly are you trying to find out about the partitions? From the research I've done, it looks like you'd need a particular tool and file to flash from Huawei. According to my understanding, you'd need direct access to the SoC to directly flash firmware to it without a bootloader of any type, but my reading is suggesting that some devices have a backup bootloader. It may be best to go with the RMA, but if you want me to run any tools over here and post the results I can.
Morganmachine91 said:
I'll do what I can to help.
Click to expand...
Click to collapse
Thank you sir.
Morganmachine91 said:
Running parted in an adb shell isn't going to do anything, as parted is a CLI partition manager that doesn't exist on android. You can run parted on the majority of linux systems, but not on adb shell.
Click to expand...
Click to collapse
parted will run just fine in adb shell, just needs to be put in the /system/bin folder and chmod 0755 (see this post)
Morganmachine91 said:
What exactly are you trying to find out about the partitions?
Click to expand...
Click to collapse
I'm trying to possibly extract files from a functional 6p that I can then get on to my bricked device through QPST or another similar utility, as the 6p isn't the only Snapdragon 810 device out there, and a number of manufacturers of other 810 devices have provided flash utilities that utilize the Qualcomm emergency mode serial connection. I haven't found one from huawei yet though (a utility).
Morganmachine91 said:
From the research I've done, it looks like you'd need a particular tool and file to flash from Huawei. According to my understanding, you'd need direct access to the SoC to directly flash firmware to it without a bootloader of any type, but my reading is suggesting that some devices have a backup bootloader.
Click to expand...
Click to collapse
Exactly. So i caved, and went and bought another 6p from Bestbuy as their return policy is very liberal. This way I can try and fix my phone and cancel the RMA I've started (waiting for prepaid label from Huawei/UPS). I think i found the backup bootloader at /dev/block/mmcblk0p16, see my post below for more details.
Following the link I posted above, i learned how to get a partition listing without using parted.
Code:
[email protected]:/dev/block/platform/soc.0/f9824900.sdhci # ls -al by-name
lrwxrwxrwx root root 1970-04-24 07:44 DDR -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-24 07:44 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-24 07:44 abootbak -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-24 07:44 apdp -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-24 07:44 boot -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-04-24 07:44 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-04-24 07:44 cmnlib -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-24 07:44 cmnlibbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-24 07:44 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-24 07:44 dpo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-24 07:44 frp -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-04-24 07:44 fsc -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-04-24 07:44 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-24 07:44 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-24 07:44 hypbak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-24 07:44 keymaster -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-24 07:44 keymasterbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-24 07:44 keystore -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-04-24 07:44 limits -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-24 07:44 metadata -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-04-24 07:44 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-04-24 07:44 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-24 07:44 modemst1 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-24 07:44 modemst2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-24 07:44 msadp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-24 07:44 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-04-24 07:44 oeminfo -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-04-24 07:44 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-04-24 07:44 persistent -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-04-24 07:44 pmic -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-24 07:44 pmicbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-24 07:44 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-04-24 07:44 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-24 07:44 rpmbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-24 07:44 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-24 07:44 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-24 07:44 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-24 07:44 sec -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-24 07:44 ssd -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-04-24 07:44 system -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-04-24 07:44 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-24 07:44 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-24 07:44 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-04-24 07:44 vendor -> /dev/block/mmcblk0p37
here is the parted output:
Code:
[email protected]:/sdcard/download # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8389kB 92.3MB 83.9MB fat16 modem
2 92.3MB 93.3MB 1049kB sbl1
3 93.3MB 93.4MB 98.3kB sdi
4 93.4MB 94.5MB 1049kB tz
5 94.5MB 95.0MB 512kB rpm
6 95.0MB 95.5MB 524kB hyp
7 95.5MB 95.6MB 131kB pmic
8 95.6MB 96.7MB 1049kB DDR
9 96.7MB 96.8MB 131kB sec
10 96.8MB 101MB 4485kB aboot
11 101MB 101MB 131kB pmicbak
12 101MB 102MB 1049kB sbl1bak
13 102MB 104MB 1049kB tzbak
14 104MB 104MB 512kB rpmbak
15 104MB 105MB 524kB hypbak
16 105MB 109MB 4485kB abootbak
17 109MB 109MB 1024B devinfo
18 117MB 122MB 4194kB fsg
19 126MB 126MB 1024B limits
20 134MB 138MB 4194kB modemst1
21 138MB 143MB 4194kB modemst2
22 143MB 143MB 262kB apdp
23 143MB 143MB 262kB msadp
24 143MB 143MB 262kB keymaster
25 143MB 144MB 262kB cmnlib
26 144MB 144MB 262kB keymasterbak
27 144MB 144MB 262kB cmnlibbak
28 144MB 144MB 1024B dpo
29 144MB 144MB 1024B fsc
30 144MB 144MB 8192B ssd
31 144MB 151MB 6806kB oeminfo
32 151MB 159MB 8389kB ext4 persist
33 159MB 176MB 16.8MB metadata
34 176MB 210MB 33.6MB boot
35 210MB 243MB 33.6MB recovery
36 243MB 310MB 67.1MB oem
37 310MB 520MB 210MB ext4 vendor
38 520MB 625MB 105MB ext4 cache
39 625MB 626MB 1049kB misc
40 626MB 627MB 524kB keystore
41 627MB 627MB 524kB frp
42 627MB 628MB 512kB persistent
43 628MB 3849MB 3221MB ext4 system
44 3849MB 31.3GB 27.4GB userdata
Research so far...
http://forum.xda-developers.com/showthread.php?t=1884417&page=2
http://kernel-develop.blogspot.com/2012/05/emmc-partition-tools-usage-for.html
http://kernel-develop.blogspot.com/2012/05/how-to-generate-8660msimagembn.html
http://forum.xda-developers.com/win...ate-rawprogram0-xml-ffu-file-extract-t3385201
If any of you SM-J727R4 users can run and get the output of these 2 commands, I'll create a TWRP build for the device (SM-J727R4).
Code:
adb shell ls -al /dev/block/bootdevice/by-name
Code:
adb shell cat /proc/partitions
adb shell ls -al /dev/block/bootdevice/by-name
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
killertaz17 said:
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
Click to expand...
Click to collapse
Do you have OEM Unlock available in developer settings?
Did not. I will re do it give me a few.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
adb shell ls -al /dev/block/bootdevice/by-name
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
--------------------------------------------------------------------------------------------------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
killertaz17 said:
Did not. I will re do it give me a few.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
adb shell ls -al /dev/block/bootdevice/by-name
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
--------------------------------------------------------------------------------------------------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
Click to expand...
Click to collapse
Oh, I didn't need you to redo it, I wanted to verify if it's present in Developer Settings or not. If you don't have OEM Unlock in Developer Settings, then you can't flash anything.
minz1 said:
Oh, I didn't need you to redo it, I wanted to verify if it's present in Developer Settings or not. If you don't have OEM Unlock in Developer Settings, then you can't flash anything.
Click to expand...
Click to collapse
Yeah i turned it on. I know how to flash with odin. Ive rooted before just dont know how to debug and all that fun stuff. But guide me thru and im sure i can do it.
Are you making one? Because That would be awesome I havent been able to root or anything with this phone
v0idd said:
Are you making one? Because That would be awesome I havent been able to root or anything with this phone
Click to expand...
Click to collapse
Yeah, but currently I'm neck deep in resolving a bug on the other J7 variant. Soon I'll have a build up for ya guys, and if all goes well, we can have an official build for the J727R4.
minz1 said:
Yeah, but currently I'm neck deep in resolving a bug on the other J7 variant. Soon I'll have a build up for ya guys, and if all goes well, we can have an official build for the J727R4.
Click to expand...
Click to collapse
Okay hopefully root will follow right behind it. Just let me know if you need anything
https://www.androidfilehost.com/?fid=746010030569960106
Try this, guys.
minz1 said:
https://www.androidfilehost.com/?fid=746010030569960106
Try this, guys.
Click to expand...
Click to collapse
installed using odin worked gave permission to write rebooted and got into a bootloop opened back up recovery and asked for permission to make writing permissions. i am now stuck in a boot loop will have to use stock rom to fix this. kinda my daily phone. i will try to flash just the stock recovery.
killertaz17 said:
installed using odin worked gave permission to write rebooted and got into a bootloop opened back up recovery and asked for permission to make writing permissions. i am now stuck in a boot loop will have to use stock rom to fix this. kinda my daily phone. i will try to flash just the stock recovery.
Click to expand...
Click to collapse
Format data and flash magisk/superSU and you'll be out of the bootloop. That's normal behavior because of dm-verity
minz1 said:
Format data and flash magisk/superSU and you'll be out of the bootloop. That's normal behavior because of dm-verity
Click to expand...
Click to collapse
i backup up my system with TWRP and flashed magisk. can i restore my backup with twrp? i will downlooad supersu when it boots up.
killertaz17 said:
i backup up my system with TWRP and flashed magisk. can i restore my backup with twrp? i will downlooad supersu when it boots up.
Click to expand...
Click to collapse
Oh I meant either magisk or superSU, but not both. Be sure you format data in twrp, and yes you can restore your system
minz1 said:
Oh I meant either magisk or superSU, but not both. Be sure you format data in twrp, and yes you can restore your system
Click to expand...
Click to collapse
oh okay i did magisk ill delete super su then. and we have root on sm-j727r4! checked with root checker.
killertaz17 said:
oh okay i did magisk ill delete super su then. and we have root on sm-j727r4! checked with root checker.
Click to expand...
Click to collapse
Cool, I'll get this device rolling with official TWRP builds, and I'll build Lineage for it once it's stable on the sprint J7
v0idd said:
Are you making one? Because That would be awesome I havent been able to root or anything with this phone
Click to expand...
Click to collapse
Still need root i can help you get it? Super easy.
I have installed xposed on my j7 works. Little to no bugs that i have found. No random reboots or anything.
killertaz17 said:
Still need root i can help you get it? Super easy.
Click to expand...
Click to collapse
Sorry for such A late response my apologies. For some reason I completely forgot about rooting. If you are around then yes I would love some help I really need to root lol I miss xposed.
v0idd said:
Sorry for such A late response my apologies. For some reason I completely forgot about rooting. If you are around then yes I would love some help I really need to root lol I miss xposed.
Click to expand...
Click to collapse
Supereasy just flash the twrp the link is in this thread then download magisk manger and flash that MAKE SURE TO WIPE DATA AND STUFF AFTER or bootloop will happen. I had to restore my device many times before finally getting it, verify with root checker no need for supersu. Once i booted and had root i backed up my boot and system incase a restore needed but havent had a issue at all since. Its been a while since i did this so ill try to remember if u have problems.
OK. So, not for the first time, LineageOS has managed to completely knacker my Nexus. It's too long and boring to go into in detail but, basically, the situation I'm left with is:
* I can access the device through fastboot
* I can boot TWRP through fastboot
* I can flash Boot & System images
However, I can't install TWRP [or any recovery] for that matter because it seems my Recovery partition has vanished. If I try to flash any Recovery, I get:
````
fastboot flash recovery /path/to/recovery.img
Sending 'recovery' (7598 KB) OKAY [ 0.280s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
````
Same with Data partition. When I boot into TWRP it's showing as 0mb. I've tried the usual tricks of formatting it [from TWRP and Fastboot] but I get 'unable to mount storage' or [from Fastboot] that 'partition table doesn't exist' message again.
I've also tried the trick of changing the format of Data from ext4 to ext2 and back. That just produces the 'unable to mount storage' error again and doesn't do anything.
I've also tried:
```
ls -al /dev/block/platform/msm_sdcc.1/by-name
```
and I don't even seem to have a [user]data or recovery partition any more:
````
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxr-xr-x 2 root root 600 Jan 27 19:06 .
drwxr-xr-x 4 root root 680 Jan 27 19:06 ..
lrwxrwxrwx 1 root root 21 Jan 27 19:06 DDR -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 27 19:06 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 27 19:06 abootb -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 27 19:06 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 27 19:06 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 27 19:06 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 27 19:06 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 27 19:06 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 27 19:06 m9kefs3 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 27 19:06 m9kefsc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 27 19:06 metadata -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 27 19:06 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 27 19:06 modemst1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 27 19:06 modemst2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 27 19:06 pad -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 27 19:06 persist -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 27 19:06 radio -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 27 19:06 rpm -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 27 19:06 rpmb -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 27 19:06 sbl1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl2b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 27 19:06 sbl3b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 27 19:06 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 27 19:06 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 27 19:06 tz -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 27 19:06 tzb -> /dev/block/mmcblk0p21
````
So where can I go from here. Everything I've found online says to flash stock ROM or reflash stock recovery.... etc. etc.
But how can I flash anything when the partitions don't actually exist and I just get 'FAILED (remote: 'partition table doesn't exist')' if I try to do anything with any of those partitions?
Is there anyway I can completely wipe the partition table on the device and set it up again from scratch? I'm not worried about loss of data or anything else. I've everything backed up. But I just need to <somehow> recreate my /data partition [at least] so I can write to the damned thing.
BTW --I had the device repartitioned 'flox' and I believe that LineageOS has encrypted the /data partition, which is why TWRP can't see it. I've tried running 'decrypt' from TWRP but get a 'command not found' error. I understand that this is because the 'decrypt' command only works with TWRP actually installed on the device, not when remote booted via fastboot. And I can't install it on the device because I have no recovery partition!
Similarly, I can actually boot to stock system but am presented with a dialogue asking me to enter my password to decrypt the device. When I do so, I get a message saying [from memory] something along the lines of "The password you entered was correct but your data is corrupted" with a button to do a factory reset. However, when I hit this, the phone just reboots into fastboot again.
Apparently the fix for this is to have the stock recovery flashed, so the factory reset will work. But, again, I have no recovery partition so can't flash stock recovery!
I've been going round in circles with this all afternoon and am on the verge of taking a sledge-hammer to the damned thing. Please someone tell me there's a way to force repartition my Nexus so I can start from scratch again.
Phew! --well, as is so often the case, after spending a day in frustration and getting nowhere and then posting a thread on XDA, I may have belatedly stumbled on a [at least partial] solution:
[Guide] Repartition Nexus7(2013) to increase system partition - Extra Space for Rom
Hi, this is my first time posting here. I noticed there is no guide to increase the system partition size in Nexus 7 (2013). The system partition is only around 880MB making it impossible to flash new ROMs and large package of GApps. This guide...
forum.xda-developers.com
Using the info in the above thread, I was able to use parted to recreate my /recovery and /userdata partitions. I'm still not home and dry yet as my Nexus is still not happy about installing any ROMs. But at least I've got a basis to work from here!
xxxmadraxxx said:
Phew! --well, as is so often the case, after spending a day in frustration and getting nowhere and then posting a thread on XDA, I may have belatedly stumbled on a [at least partial] solution:
[Guide] Repartition Nexus7(2013) to increase system partition - Extra Space for Rom
Hi, this is my first time posting here. I noticed there is no guide to increase the system partition size in Nexus 7 (2013). The system partition is only around 880MB making it impossible to flash new ROMs and large package of GApps. This guide...
forum.xda-developers.com
Using the info in the above thread, I was able to use parted to recreate my /recovery and /userdata partitions. I'm still not home and dry yet as my Nexus is still not happy about installing any ROMs. But at least I've got a basis to work from here!
Click to expand...
Click to collapse
got the same prob
any solutiotn?
I did get it sorted in the end. Here are the notes I saved at the time. Excuse the swearing but these were made for my own future reference and not for public consumption:
-----------------------------------------------------
Too long and boring to go into details but, basically Lineage-****ing-OS completely arse-****ed my Nexus: no /data partition nor /recovery partition. Tried every trick in the book to try and fix it, but nothing that used fastboot or TWRP [booted from fastboot] did **** all. In the end, the answer was to install parted on the Nexus. [ Downloaded from: iwf1.com/iwf-repo/parted.rar ] and use that to rewrite the partitioning map]. All from this thread:
[Guide] Repartition Nexus7(2013) to increase system partition - Extra Space for Rom
Hi, this is my first time posting here. I noticed there is no guide to increase the system partition size in Nexus 7 (2013). The system partition is only around 880MB making it impossible to flash new ROMs and large package of GApps. This guide...
forum.xda-developers.com
````
adb push parted /
adb shell
~ # chmod +x parted
~ # /parted /dev/block/mmcblk0
(parted): unit b
(parted): p
````
This was the guy in the thread’s partition map. Mine was almost the same, except my Block 25 was unnamed [so had to rename it to ‘recovery’] and I didn’t have a ‘userdata’ block at all:
````
Number Start End Size File system Name Flags
1 67108864B 156745727B 89636864B fat16 radio
2 201326592B 204472319B 3145728B modemst1
3 204472320B 207618047B 3145728B modemst2
4 268435456B 283795455B 15360000B ext4 persist
5 335544320B 336343039B 798720B m9kefs1
6 336343040B 337141759B 798720B m9kefs2
7 402653184B 403451903B 798720B m9kefs3
8 403451904B 406597631B 3145728B fsg
9 469762048B 471298047B 1536000B sbl1
10 471298048B 472834047B 1536000B sbl2
11 472834048B 474931199B 2097152B sbl3
12 474931200B 480174079B 5242880B aboot
13 480174080B 480698367B 524288B rpm
14 536870912B 553648127B 16777216B boot
15 603979776B 604504063B 524288B tz
16 604504064B 604505087B 1024B pad
17 604505088B 606041087B 1536000B sbl2b
18 606041088B 608138239B 2097152B sbl3b
19 608138240B 613381119B 5242880B abootb
20 613381120B 613905407B 524288B rpmb
21 613905408B 614429695B 524288B tzb
22 671088640B 1551892479B 880803840B ext2 system
23 1551892480B 2139095039B 587202560B ext4 cache
24 2147483648B 2148532223B 1048576B misc
25 2214592512B 2225078271B 10485760B recovery
26 2281701376B 2281709567B 8192B DDR
27 2281709568B 2281717759B 8192B ssd
28 2281717760B 2281718783B 1024B m9kefsc
29 2348810240B 2348843007B 32768B metadata
30 2415919104B 31272713727B 28856794624B ext4 userdata
````
````
(parted) name 25 recovery
(parted): rm 30 —might have to unmount it in shell if it’s busy
(parted): mkpart primary 2415919104B 100% —I used 100% instead of a stated block as he had, as I got an error about going past the end of the available space
(parted) name 30 system
(parted) p
(parted) quit
````
—then in adb shell again:
````
~ # mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p30
~ # /parted /dev/block/mmcblk0 p
````
need to reboot [bootloader] to make fstab update partition table.
That at least gave me a recovery and data partitions. Though I’m still wrestling to restore any kind of OS on them.
Please kick me hard in the bollox if I ever even look at lineageOS again!
Click to expand...
Click to collapse
-----------------------------------------------------
I can't remember exactly what I did to install an OS afterwards. I didn't make any more notes, so I assuming it wasn't *too* traumatic. Just getting the partitions restored and available to install anything on is the biggest hurdle!
Hey... So Im trying to boot/flash a Custom recovery for my Xperia XZ2 however It doesnt have a recovery... The reason I suspect this is when I try to boot to recovery via the button combo or ADB... It cycles once and on the next cycle it returns to the main phone screen. I never see a recovery screen and trying to boot a recovery.img just returns this
{
"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"
}
How screwed am I?