Database Info

Create Odin flashable rom on Tab 2

I'm working on customizing my rooted tab 2 and then exporting to an Odin flashable ROM (following instructions from (http://forums.androidcentral.com/dr...create-custom-odin-images-backup-restore.html)
The reason for this, rather than using CWM to more easily make a backup, is that I need to flash my customizations onto a BUNCH of tablets, and don't want to go through the process of unlocking the bootloader and installing CWM for each of them.
What I'm wondering is this:
Which partitions should I be copying to build an Odin flashable rom. The instructions I linked say that I need zImage, factoryfs.rfs and recovery.bin - which I'm hoping is the case.
I'm not sure which partitions correspond to the necessary files for creating the flashable ROM. Any ideas?
Here are my partitions by name:
1|[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-11-16 22:48 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-11-16 22:48 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-11-16 22:48 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-11-16 22:48 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-11-16 22:48 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-11-16 22:48 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-11-16 22:48 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-11-16 22:48 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-11-16 22:48 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-11-16 22:48 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-11-16 22:48 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-11-16 22:48 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-11-16 22:48 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-11-16 22:48 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-11-16 22:48 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-11-16 22:48 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-11-16 22:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-11-16 22:48 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-11-16 22:48 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-11-16 22:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-11-16 22:48 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-11-16 22:48 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-11-16 22:48 userdata -> /dev/block/mmcblk0p15
Thanks again for the great thread!

I'm not sure what you're following.
But in my limited experience all you will ever need is a system.img, boot.img and a cache.img to tell the recovery to wipe the data. And a recovery.img is optional. The zImage is the kernel and it is in the boot.img.
Also wrong section.

... and crossposting http://forum.xda-developers.com/showpost.php?p=48143832&postcount=177

Luigi2012SM64DS said:
I'm not sure what you're following.
But in my limited experience all you will ever need is a system.img, boot.img and a cache.img to tell the recovery to wipe the data. And a recovery.img is optional. The zImage is the kernel and it is in the boot.img.
Also wrong section.
Click to expand...
Click to collapse
Cool, thanks for the help. Which section would be better to post this in?
so I pull
boot (/dev/block/mmcblk0p7) to zImage
and
system (/dev/block/mmcblk0p14) to factoryfs.rfs
The instructions I linked to say that cache is optional if I don't want to pull personal data, so I might omit that.
If I don't pull the recovery.img, how does that impact the next tablet I install this on? Does it mean a factory wipe would reset it to its previous image, or is that unrelated.
Thanks again for the help - sorry for the cross-post, I'm pretty new to this entire thing.

Android-Andi said:
... and crossposting http://forum.xda-developers.com/showpost.php?p=48143832&postcount=177
Click to expand...
Click to collapse
Should I delete that one? I figured it was relevant to that thread / people who were interested in rooting that tab, but I guess not posting twice supersedes that. Thanks.

evrkusd said:
Cool, thanks for the help. Which section would be better to post this in?
so I pull
boot (/dev/block/mmcblk0p7) to zImage
and
system (/dev/block/mmcblk0p14) to factoryfs.rfs
The instructions I linked to say that cache is optional if I don't want to pull personal data, so I might omit that.
If I don't pull the recovery.img, how does that impact the next tablet I install this on? Does it mean a factory wipe would reset it to its previous image, or is that unrelated.
Thanks again for the help - sorry for the cross-post, I'm pretty new to this entire thing.
Click to expand...
Click to collapse
The thread has already moved from development to Q and A.
And no, i'm still not understanding. you should pull /system and make it into a system.img
And for the boot.img, I am not really sure how you can pull that from that tab. But I think you can just get a stock kernel boot.img from any ol' stock rom.

Luigi2012SM64DS said:
The thread has already moved from development to Q and A.
And no, i'm still not understanding. you should pull /system and make it into a system.img
And for the boot.img, I am not really sure how you can pull that from that tab. But I think you can just get a stock kernel boot.img from any ol' stock rom.
Click to expand...
Click to collapse
Hm ok. I guess other threads are pointing me to think that I need more than just a system.img.
See here:
http://forum.xda-developers.com/showthread.php?t=960946
or the original link I posted.
If all I need is system (/dev/block/mmcblk0p14) dumped to system.img, that would be easier, but I'm not sure that's all I need. If so, I guess I could pull system.img and tar it and try it out..
Thanks for the advice

evrkusd said:
Hm ok. I guess other threads are pointing me to think that I need more than just a system.img.
See here:
http://forum.xda-developers.com/showthread.php?t=960946
or the original link I posted.
If all I need is system (/dev/block/mmcblk0p14) dumped to system.img, that would be easier, but I'm not sure that's all I need. If so, I guess I could pull system.img and tar it and try it out..
Thanks for the advice
Click to expand...
Click to collapse
That guide is not for tab 2.
You only need a modem.bin if you have the P3100 the gsm tab and not the wifi only.
The zImage is the same as boot.img
The cache is only needed as, again, you need to make it so the data will be wiped to avoid bootloops if coming from custom roms.
And the system is the rom so you will obviously need that.

Luigi2012SM64DS said:
That guide is not for tab 2.
You only need a modem.bin if you have the P3100 the gsm tab and not the wifi only.
The zImage is the same as boot.img
The cache is only needed as, again, you need to make it so the data will be wiped to avoid bootloops if coming from custom roms.
And the system is the rom so you will obviously need that.
Click to expand...
Click to collapse
Ok, thanks. The tab 2 I'm using is the Verizon SCH-I705, btw, so should I include modem.img? It seems like I could just leave the existing modem partition on the device, since I don't want to make any changes there.
Here's my current setup
/boot send to boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img bs=4096
/system send to system.img
dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img bs=4096
/recovery send to recovery.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery.img bs=4096
/cache send to cache.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/cache.img bs=4096
Then I'll roll all 4 of them into a tar package with:
tar -H ustar -c system.img cache.img boot.img recovery.img > package.tar
md5sum -t package.tar >> package.tar
mv package.tar package.tar.md5
and flash via Odin
Does it sound like that will work?
Thanks again for the help

evrkusd said:
Ok, thanks. The tab 2 I'm using is the Verizon SCH-I705, btw, so should I include modem.img? It seems like I could just leave the existing modem partition on the device, since I don't want to make any changes there.
Here's my current setup
/boot send to boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img bs=4096
/system send to system.img
dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img bs=4096
/recovery send to recovery.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery.img bs=4096
/cache send to cache.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/cache.img bs=4096
Then I'll roll all 4 of them into a tar package with:
tar -H ustar -c system.img cache.img boot.img recovery.img > package.tar
md5sum -t package.tar >> package.tar
mv package.tar package.tar.md5
and flash via Odin
Does it sound like that will work?
Thanks again for the help
Click to expand...
Click to collapse
Oh the verizon tab.
Yes you should have the modem.
Don't take the cache from the /cache partition you should make a cache.img from scratch.

Luigi2012SM64DS said:
Oh the verizon tab.
Yes you should have the modem.
Don't take the cache from the /cache partition you should make a cache.img from scratch.
Click to expand...
Click to collapse
Ok, thanks. Am I right in thinking that if the tab already has a working modem (since verizon is working on it), do I need to flash modem.img if I haven't made any changes on the new version?
Also, not sure how to make a cache.img from scratch. I've searched for similar terms on xda and haven't come up with anything.
Thanks again.

[Q] GT-N8013 Bootlogo Bricked

Hi, I need your Help. I have problems with my n8013, sm-p600, note 10.1 2014 edition. I've tested many roms and decided to use the clean rom. All works perfect but I want to test the cyanogen mod too. That was my mistake. ^^ First, I use twrp 2.6.3.3 recovery, thats the only recovery working for me, flashed with odin 3.09. I couldn't flash any other recovery, whenever I test it, it goes to standard recovery. I tried a mass of tipps, data factory wipe, wipe cache partition, reroll to stock rom ... nothing works. Cyanogen wants twrp 2.7.0.0. or philz recovery but I couldn't flash it. Any tipps? Second, my Start Logo is bricked now, only white stripes to see, animation logo works, system run. But I'd like to change the startlogo to normal. Any help would be nice. THX and sorry about my bad english.

Seems like this:
durien said:
Hi, I need your Help. I have problems with my n8013, sm-p600, note 10.1 2014 edition. I've tested many roms and decided to use the clean rom. All works perfect but I want to test the cyanogen mod too. That was my mistake. ^^ First, I use twrp 2.6.3.3 recovery, thats the only recovery working for me, flashed with odin 3.09. I couldn't flash any other recovery, whenever I test it, it goes to standard recovery. I tried a mass of tipps, data factory wipe, wipe cache partition, reroll to stock rom ... nothing works. Cyanogen wants twrp 2.7.0.0. or philz recovery but I couldn't flash it. Any tipps? Second, my Start Logo is bricked now, only white stripes to see, animation logo works, system run. But I'd like to change the startlogo to normal. Any help would be nice. THX and sorry about my bad english.
Click to expand...
Click to collapse
It same as user describe here: http://forum.xda-developers.com/showthread.php?t=2104538&page=2 You can use my BOOT LOGO MODDER, link is in my signature
My MOD erase and then recovery block PARAM:
lrwxrwxrwx root root 2014-03-15 19:06 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-03-15 19:06 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-03-15 19:06 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-03-15 19:06 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-03-15 19:06 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-03-15 19:06 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-03-15 19:06 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-03-15 19:06 PARAM -> /dev/block/mmcblk0p4 <--- Here is hide Boot Logo picture
lrwxrwxrwx root root 2014-03-15 19:06 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-03-15 19:06 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-03-15 19:06 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-03-15 19:06 USERDATA -> /dev/block/mmcblk0p12
Wish you luck! :victory:

I've tried it ^^
Hi,
thanks for your reply. I've tried your mod before and YES I reboot into recovery first after flashing before I reboot the system. Bootlogo still bricked.
:crying:
tanker32 said:
It same as user describe here: http://forum.xda-developers.com/showthread.php?t=2104538&page=2 You can use my BOOT LOGO MODDER, link is in my signature
My MOD erase and then recovery block PARAM:
lrwxrwxrwx root root 2014-03-15 19:06 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-03-15 19:06 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-03-15 19:06 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-03-15 19:06 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-03-15 19:06 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-03-15 19:06 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-03-15 19:06 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-03-15 19:06 PARAM -> /dev/block/mmcblk0p4 <--- Here is hide Boot Logo picture
lrwxrwxrwx root root 2014-03-15 19:06 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-03-15 19:06 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-03-15 19:06 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-03-15 19:06 USERDATA -> /dev/block/mmcblk0p12
Wish you luck! :victory:
Click to expand...
Click to collapse

[Q] VERIZON Samsung Tab 2 10.1 sch-i915 Hardbrick help

I have an incident that I have accrued myself so no need for those comments. The history of the hardbrick i created. If any information regarding anything feel free.
First of all i rooted my device using towelroot. It works for alot of devices and runs as 3rd party apk installer. Created by the infamous Geohotz. Godbless. https://towelroot.com/ for those of you who do not know.
2nd i was looking and trying to swap my extSdCard with my internal /sdcard. I edited the vold.fstab and the vold.conf files thinking hey i can use the external as full internal to have the devive install apps on properly w/o manually moving and use the internal remaining sdcard memory as virtual Ram. I have not completed this process yet. Ill explain.
After mounting the internal as external and vice. I ended up being stuck in a boot loop. NOTE: i did not have custom recovery(was one of the oopsies) so was stuck with basic android recovery. Reset device did not fix. Was going to Odin flash the stock rom and/or CWM Recovery, but there is absolutely NO STOCK or LEAKED rom anywhere for the verizon model. I also pulled those 2 files off of my other tab 2 10.1 NON VERIZON *vold.fstab and vold.conf and places it into zip file and signed it using signapk.
which now i feel like an idiot finding this link "http://forum.xda-developers.com/galaxy-nexus/themes-apps/tutorial-making-flashable-zips-edify-t1611615"
NOTE: I used a different post somewhere that didnt explain to have the right binary so it gave me a signature mismatch error when trying to flash. Use above post to make sure you use propery binary.
Luckily i did some research and knowledge of what i actually did to fix it and plus my addiction to play around and learn things. I manually duplicated the vold.fstab/vold.conf files from my one device to the bricked one
Boot up device in Android recovery.
installed and loaded up ADB.exe from command line.
Code:
adb shell
su
echo *yourlinehere*> /system/etc/vold.fstab
echo *yourlinehere*>> /sytem/etc/vold.fstab
the first > rewrites the file from start black document and inputs the first line
the 2nd >> note the double >> appends to the next line.
i rebooted and VOILA FIXED!!! but wait....theres more ><
So knowing the troubles i had to fix my lil play around mistake. I wanted to get custom recovery partition installed. Used Rom Manager to install CWM Recovery. I picked the wrong rom for my device and flashed it. The one i used was for the international Tab 2 10.1 the gt-5100. It said it successfully flashed so i figured wth it couldnt hurt right? WRONG i clicked reboot to recovery to check it. and here is where I lie. HARD BRICK. No boot up at all. Plug in charger to outlet or PC i dont even get the charging device battery image. So now here we go more research fun!!!
I looked up some information on how to fix a hard bricked device. some posts say using a jig to bypass it and get into download mode. Ok this is a 30 pin connector not a 4 pin like most the android devices. I could do some research on this and probably rig a jig to convert and match the pin layouts but meh my problem still lies within not having stock firmware for this model. I also learn of Jtag methods. Oh all well and handy but buying the Riff Box and all this gets your device bootable, but hey guess what? it would allow me to boot into that download mode or android recovery. Which still bottom line fails as i dont have a stock rom to flash. OH the dilemna.
What ive come up with. I plugged in my device into my pc. Well what do you know i can actually get recognition. but this is where i am stuck at.
I figured out that the device is recognized and i needed drivers. I found this handy site
https://developer.qualcomm.com/forum/qdevnet-forums/general-discussion/9428 Which also explains that i messed up my boot partition.
I download and installed the QPST program and installed the drivers on win7. I had to reboot and use advanced options to disable the unsigned drivers check. OK sweet connection is up!
I tried using ADB shell but device isnt connected that way.
In the QPST program it shows my device on com10 in download mode. I tried to retrieve some data or partition information from the device but it says i cannot when device is in download mode. So no pulling files and fixing and reflashing them. Back to the same problem before NO STOCK ROM.
So here are the questions I have regarding my situation. The android device im playing with has the base partitions. As an example of this http://www.all-things-android.com/content/review-android-partition-layout
I do not have my partition layout for my device as its bricked. I dont even know if it needs to be repaired yet. If any of you with a verizon tab 2 10.1 sch-i915 has a rooted device and can get me this table or a pit file for this device it would be appreciated
2nd firmware vs firmware. As previously stated I do not have firmware for this verizon tab. HOWEVER i did find firmware for the Sprint version of this exact tablet. My question is, could these stock firmwares be exact duplicates with the exclusion of the boot up screen bs and the /misc partition containing the imei phone stats and carrier information?
3rd Flashing just certain partitions of this firmware. Is it possible if the above is feasible considering i know my /boot partition is messed up and my /recovery partition is messed up to only flash those 2 partitions with the one from sprint. The stock kernal should be the same in both devices for the /boot and the /recovery partition should hold the same android recovery should it not?
4th. If anyone has a rooted sch-i915 device would you be willing to make dump of the partitions using this guide http://forum.xda-developers.com/showthread.php?t=2450045. That would be appreciated.

Let Me Work On That
You Are Possibly In Luck. I Know Somone That Has That Tablet. Problem Is It Is My Mom's And Well She Rather Beat Me With It Then Let Me Touch It. I'll See What I Can Do And Will Post Back.. Wish Me Luck i Will Need It :fingers-crossed:

][NT3L][G3NC][ said:
You Are Possibly In Luck. I Know Somone That Has That Tablet. Problem Is It Is My Mom's And Well She Rather Beat Me With It Then Let Me Touch It. I'll See What I Can Do And Will Post Back.. Wish Me Luck i Will Need It :fingers-crossed:
Click to expand...
Click to collapse
Appreciated good luck.
If not possible and i get it fixed ill post how i did it and such. and also post up a JB 4.12 stock/updated leaked rom of this device which apparently seems to be missing in the world for some damn reason.

I Got A Question
Sorry I Been Busy, & Google Has Not Been Kind 2 Me. I Did Find The California Lottery Vulnerability Report Generated By Nessus. But If Someone Could Please Point Me In The Right Direction Or Just Break It Down For Me As Quickly And Light As You Could, Short, Straight Forward, The LIghtest Kliff Notes Ever Would Be Appreciated.
Verizion SCH-I915 [ 4.1.2 ]
I Only Had A Few Minutes With The Tablet But I Already Rooted It, Installed BusyBox, I Barely Started To Get Into The FIle System.... I'm Using Kali LInux
1. What Partitions/Blocks Do I Need To Obtain To Create An Odin Flashable Recovery Image
2. Is There A Droid Binary, Or Script I Can Use To Dump The Rom While Creating The Above For Odin?
Just Found Something I Downloaded At Some Point Called: ROMGEN Any Idea On That Binary??? And phantomphr33k Any Request.
Forgive Me I Work Nights, Two Kids, So I'm Up Days + On Call During The Day.
lrwxrwxrwx root root 1970-10-27 01:41 aboot -> /dev/block/mmcblk0p5 ???
lrwxrwxrwx root root 1970-10-27 01:41 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-10-27 01:41 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-10-27 01:41 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-10-27 01:41 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-10-27 01:41 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-10-27 01:41 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-10-27 01:41 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-10-27 01:41 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-10-27 01:41 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-10-27 01:41 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-10-27 01:41 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-10-27 01:41 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-10-27 01:41 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-10-27 01:41 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-10-27 01:41 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-10-27 01:41 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-10-27 01:41 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-10-27 01:41 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-10-27 01:41 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-10-27 01:41 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-10-27 01:41 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-10-27 01:41 userdata -> /dev/block/mmcblk0p15

Should Post The Rest Tomorrow
I Have Attached Some Text Files With The Output Of A Couple Commands To Get The block/partition layout.
I Have Dumped The system.img which is 1.6gb In SIze
Tomorrow I Should Have : Modem "firmware" , Boot , Recovery
QUESTIONS:
What Is aboot?
Which Is The Kernel?
What Is Modemst*?
And More Important, Which Ones Do I Need To Pull For A Complete ROM Dump?
lrwxrwxrwx 1 0 0 20 Nov 2 1970 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 0 0 21 Nov 2 1970 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 0 0 20 Nov 2 1970 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 0 0 21 Nov 2 1970 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 0 0 21 Nov 2 1970 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 0 0 21 Nov 2 1970 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 0 0 21 Nov 2 1970 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 0 0 21 Nov 2 1970 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 0 0 20 Nov 2 1970 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 0 0 21 Nov 2 1970 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 0 0 21 Nov 2 1970 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 0 0 20 Nov 2 1970 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 0 0 21 Nov 2 1970 param -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 0 0 21 Nov 2 1970 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 0 0 21 Nov 2 1970 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 0 0 20 Nov 2 1970 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 0 0 20 Nov 2 1970 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 0 0 20 Nov 2 1970 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 0 0 20 Nov 2 1970 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 0 0 21 Nov 2 1970 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 0 0 21 Nov 2 1970 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 0 0 20 Nov 2 1970 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 0 0 21 Nov 2 1970 userdata -> /dev/block/mmcblk0p15

Sorry its the Holidays so its understandable. Cant really twist your arm to rush it Im by far not an expert on this i do research myself. Ill do my best and if anyone else can shed light please do.
][NT3L][G3NC][ said:
QUESTIONS:
[*]What Is aboot?
[*]Which Is The Kernel?
[*]What Is Modemst*?
[*]And More Important, Which Ones Do I Need To Pull For A Complete ROM Dump?
Click to expand...
Click to collapse
1) Aboot partition is basically your "Odin Downloader" protocol. while booting pressing power + Vol Dwn will put your device in this mode.
2) The kernel/ramdisk is stored in the /boot partition
Note Primary Bootloader and SB* are secondary bootloaders 1,2,3 those are loaded up as well to set certain params + setup/initialize hardware as far as im understanding. and loads up the kernel/ramdisk.
3)Ill quote from another thread: http://forum.xda-developers.com/showthread.php?t=2582811
][NT3L][G3NC][ said:
- backup and restore important device partitions - EFS (Samsung), TA (Sony), MODEM (Exynos devices), MODEMST1 & MODEMST2 (Qualcomm devices),
- root is required
- easy to use
- many localizations
- see paths to important partitions of your device using Menu -> Device Partitions
Click to expand...
Click to collapse
As far as im understanding these partitions hold carrier information/imei and all other sorts of GRPS information in regards to connecting your devices radio to Service. Sorta like your network card drivers and Mac Address
I looked at another persons rom dump and I seen only these partitions in the archive. Sadly I dont remember where i found this but is from a guy who JTAGS devices. So im pretty sure its legit. Its from the Sprints version of this device.
/system.img.ext4(going to be the biggest dump)
/recovery.img
/cache.img.ext4
/boot.img
[QUOTE=']
1. What Partitions/Blocks Do I Need To Obtain To Create An Odin Flashable Recovery Image
2. Is There A Droid Binary, Or Script I Can Use To Dump The Rom While Creating The Above For Odin?
Just Found Something I Downloaded At Some Point Called: ROMGEN Any Idea On That Binary??? And phantomphr33k Any Request.
[/QUOTE]
So basicallly special request if you could is mainly dump those partitions above
This Romgen seemingly looks to dump what is needed for the rom. It also makes and update-script flashable Odin file. Never tried it myself. ive used cygwin/kitchen personally.
If you would do that would be sufficient as a stock rom. Granted if the rom is updated its not stock.....BUT at least it will be an updated stock vwz sch-i915 out there in public finally.
AND...extra special request is a pit file. Reason being is i need to attempt to flash by other means not via odin.(more personal use than general public) and i need the block information to flash partitions to the chip at the certain points. Im extracting the *.img/bin files and compiling *.mbn files and going to attempt to flash directly to the chip. As far as ive seen its worked on a few other devices and i might as well try considering this is a Qualcomm device and it is recognized in QPST. Maybe the security on the bootloader may not allow it but what could it hurt? its already hard bricked right? lol
http://forum.xda-developers.com/showthread.php?t=1916936
program here for windows. I never checked for any linux based tools cuz i use cygwin if i absolutely need linux.
Much appreciated ][NT3L][G3NC][ your making my day :laugh:

happy new years intelligence since it seems ur the only one to view this thread.

so did you ever get a good romdump? I have been trying all night to do it to mine but can not get it to work.

[FIXED][GUIDE][BOOTLOADER UNLOCKED][LG G4c] Bootloader is unlocked!

Hi guys!
You can donate to me here https://paypal.me/penvineeth and @cerg2010cerg2010 through paypal.
@cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Bootloader is unlocked in LG G4c!
-> Requirements:
(1) LG UP
(2) Device must be: LG G4c
Fixed: Brightness.
Make sure you have Lollipop firmware.
(1) Download this patched aboot file: https://drive.google.com/file/d/11xFfJipkSTZ1-DRRI1kebmotIm0zM89K/view?usp=drivesdk
(2) Connect your phone to the computer. In command prompt, type "adb shell".
(3) Transfer the aboot file into /sdcard/ folder.
(4) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_5120.bin of=/dev/block/mmcblk0p5" (without quotes).
(5) Restart your phone by typing "reboot".
You have unlocked your bootloader!
Refer Notes for more information.
-> Notes:
1) The aboot_5120.bin is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.

@pvineeth97 how do we flash twrp after the bootloader unlock?

ahmed546 said:
@pvineeth97 how do we flash twrp after the bootloader unlock?
Click to expand...
Click to collapse
Using flashfire app
Wysłane z mojego LG-H525n przy użyciu Tapatalka
---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------
Isn't that mmcblk0p7 partition ?
Wysłane z mojego LG-H525n przy użyciu Tapatalka

@pvineeth97 can you post this guide also in the g4c forum?

ahmed546 said:
@pvineeth97 can you post this guide also in the g4c forum?
Click to expand...
Click to collapse
There is no proper LG G4c forum. First tell mods to create that then I will post it there.
Anyways I posted: https://forum.xda-developers.com/android/development/guide-bootloader-unlocked-t3637155

pvineeth97 said:
There is no proper LG G4c forum. First tell mods to create that then I will post it there.
Anyways I posted: https://forum.xda-developers.com/android/development/guide-bootloader-unlocked-t3637155
Click to expand...
Click to collapse
You sure it's mmcblk0p5 partition not mmcblk0p7 ?

<Snip - Mod EDIT>
And about the patched aboot for LG G4. They asked me to patch their bootloader to try if it works. Patched aboot method doesn't support phones with Snapdragon 8xx. It only supports Snapdragon 410 SoC. Even after I told them they don't listen.

DonOleq said:
You sure it's mmcblk0p5 partition not mmcblk0p7 ?
Click to expand...
Click to collapse
Yep, check one of my very few earlier posts. We got the mapping done and it's the right partition.

Guys lets keep it civil. This is why we dont have any lg devs left everyone wants to raise cain and scream and hollar. No one wants to read this crap. This patch works on the 410s. Doesnt work on 8 series.
Dont hate because your devices are not included thats just how it is blame lg and qualcomm

<Snip - Mod EDIT>
Did you even test it? I don't think so. It's against XDA rules, I'll report this today let's see what mods will do. I wouldn't trust any of your work
Sent from my LG-H815 using Tapatalk

Minto107 said:
Did you even test it? I don't think so. It's against XDA rules, I'll report this today let's see what mods will do. I wouldn't trust any of your work
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Yes. I got it tested. I gave you the link for proof too. I don't care what you trust and what you don't!
Here is the link: https://forum.xda-developers.com/showpost.php?p=73030513&postcount=105
If you show this aggression towards LG rather than accusing me atleast you might even get bootloader unlock for G4.

<Snip - Mod EDIT>
@Minto107 it was tested. The user @Willstetictac even send @pvineeth97 a PM about his issue. He just had a problem with his brightness thats all. TWRP worked and the bootloader unlock worked. @pvineeth97 already gave proof that it worked, the mods will see that.

ahmed546 said:
@Minto107 it was tested. The user @Willstetictac even send @pvineeth97 a PM about his issue. He just had a problem with his brightness thats all. TWRP worked and the bootloader unlock worked. @pvineeth97 already gave proof that it worked, the mods will see that.
Click to expand...
Click to collapse
Lol ive had briteness issues in twrp before. On a lot of devices actually.
I always chalked it to twrp. Not being say faulty but naturally dim.
---------- Post added at 05:55 AM ---------- Previous post was at 05:42 AM ----------
Minto107 said:
Did you even test it? I don't think so. It's against XDA rules, I'll report this today let's see what mods will do. I wouldn't trust any of your work
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I would thank you also. Im outa thanks for the day. But this is the proper procedure. If it is found to be be a fluke they will end it. As stated it has been suposedly confirmed now if that 1 confirmation is also "in on it"
The mods will be able to tell. I just hate to see people fightin. Throughout the threads.
Im just trying to keep the peace. Wich i understand exactly where you are coming from.

Sorry I didn't check the link, stuff is working, sorry that I was rude. I just wanted to warn people that they should proceed with caution as you already tried to unlock G4 Dual sim and we all know how it ended. I don't own G4c so obviously I couldn't give it a try but as its tested and proofed to be working then it's all right of course
Once again sorry for being rude
Sent from my LG-H815 using Tapatalk

So i have it straight from the 1 confirmation. The backlight isnt working in o.s. so aboot needs to be reworked.
DO NOT ATTEMPT UNTIL FIXXED
Said problem isnt in twrp so yes twrp works but this has broight on a diffrent issue.
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
pvineeth97 said:
Yes. I got it tested. I gave you the link for proof too. I don't care what you trust and what you don't!
Here is the link: https://forum.xda-developers.com/showpost.php?p=73030513&postcount=105
If you show this aggression towards LG rather than accusing me atleast you might even get bootloader unlock for G4.
Click to expand...
Click to collapse
So it does seem as if this does bring out an issue that needs to be fixxed. Props on the modded aboot without a secure boot error. But backlight in os is kinda a big deal. U need to disclose this

TheMadScientist420 said:
So i have it straight from the 1 confirmation. The backlight isnt working in o.s. so aboot needs to be reworked.
DO NOT ATTEMPT UNTIL FIXXED
Said problem isnt in twrp so yes twrp works but this has broight on a diffrent issue.
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
So it does seem as if this does bring out an issue that needs to be fixxed. Props on the modded aboot without a secure boot error. But backlight in os is kinda a big deal. U need to disclose this
Click to expand...
Click to collapse
I just got to know yesterday night.

TheMadScientist420 said:
So i have it straight from the 1 confirmation. The backlight isnt working in o.s. so aboot needs to be reworked.
DO NOT ATTEMPT UNTIL FIXXED
Said problem isnt in twrp so yes twrp works but this has broight on a diffrent issue.
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
So it does seem as if this does bring out an issue that needs to be fixxed. Props on the modded aboot without a secure boot error. But backlight in os is kinda a big deal. U need to disclose this
Click to expand...
Click to collapse
I have updated the "main post". Sorry I forgot to update before. Thanks for reminding.
https://forum.xda-developers.com/g4/development/guide-bootloader-unlocked-t3637105/

Minto107 said:
Sorry I didn't check the link, stuff is working, sorry that I was rude. I just wanted to warn people that they should proceed with caution as you already tried to unlock G4 Dual sim and we all know how it ended. I don't own G4c so obviously I couldn't give it a try but as its tested and proofed to be working then it's all right of course
Once again sorry for being rude
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
No problem.

Hi all,
Just to remove the last few doubts, I've checked on my phone the partition layout.
The aboot is /dev/block/mmcblk0p5 .
It's for a French Open H525n.
C:\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
[email protected]:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1970-03-16 06:08 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-16 06:08 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-16 06:08 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-16 06:08 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-16 06:08 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-03-16 06:08 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-16 06:08 drm -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-03-16 06:08 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-16 06:08 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-16 06:08 factory -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-16 06:08 fota -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-16 06:08 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-16 06:08 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-16 06:08 grow -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-03-16 06:08 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-16 06:08 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-16 06:08 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-16 06:08 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-16 06:08 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-16 06:08 modem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-03-16 06:08 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-16 06:08 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-16 06:08 mpt -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-16 06:08 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-16 06:08 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-16 06:08 persist-lg -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-16 06:08 persistent -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-16 06:08 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-16 06:08 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-16 06:08 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-16 06:08 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-16 06:08 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-16 06:08 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-16 06:08 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-16 06:08 sns -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-16 06:08 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-16 06:08 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-03-16 06:08 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-16 06:08 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-16 06:08 userdata -> /dev/block/mmcblk0p39

Any news in fixing the bootloader?

K1 Not booting after flashing stock image

Yesterday I flashed BitO-KU kernel with dtb and blob file provided in this thread https://forum.xda-developers.com/sh.../tweaked-kernel-nvidia-shield-tablet-t3069776 on my Shield Tablet K1. Since then the problem started and my tab didn't boot.
How problem started?
Flashed BitO-KU kernel https://forum.xda-developers.com/sh.../tweaked-kernel-nvidia-shield-tablet-t3069776
Reboot (working fine)
Flashed dtb file "tegra124-tn8-p1761-1270-a04-e-battery.dtb" (provided in same thread)
Reboot (stuck on bootloader)
Flashed blob file (provided in same thread)
Reboot (stuck on bootloader)
After that I flashed factory images provided on Nvidia official site for K1 Tablet but still not booting. Although many times I have successfully flashed firmware images before, but only this time it's not booting. I think that the dtb and blob files I flashed previously with BitO-KU kernel were for Original Shield Tablet not for K1, that's why my tablet bricked.
What's working and what's not:
Bootloader is working and able to flash files using fastboot. But it's niether showing any error nor booting after flashing firmware images.
Recovery Not Working. Flashed various versions of TWRP from official website, none of them is working. Even tried directly booting to twrp recovery instead of flashing, still not working.
Any help is appreciated.
Sorry for my bad English!

Did you flash the stock system file and the stock blob? I think the instructions (recovery image) say to flash a few other things (recovery, userdata) but I was able to just flash the system and blob (flashing stock recovery might not hurt either).
Also, please don't apologize for your bad English. Your post is very well written, and I never would have guessed you are not a native English speaker.

redpoint73 said:
Did you flash the stock system file and the stock blob? I think the instructions (recovery image) say to flash a few other things (recovery, userdata) but I was able to just flash the system and blob (flashing stock recovery might not hurt either).
Also, please don't apologize for your bad English. Your post is very well written, and I never would have guessed you are not a native English speaker.
Click to expand...
Click to collapse
Hi @redpoint73, thanks for your response. Yes I did flash the stock system file, stock blob file and stock boot file. Still it wasn't booting.
And thanks for your compliment about my English.

Hello,
I was in a similar situation but finally managed to fix this boot issue on my K1.
What I have, Nvidia Shield Tablet K1
What I did wrong, flashed via fastboot a stock ROM image from Nvidia GameWorks - SHIELD Open Source Resources and Drivers
But not the correct one for Shield K1
I had the following steps for this recovery ROM (not for K1 tablet...):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
fastboot reboot
Flashing them failed on userdata (not enough space) and results in K1 to be stuck on boot and the Nvidia logo for ages.
(For a K1 tablet, you don't have a userdata and dtb flash image steps). I think what messed up my K1 is the dtb flashing step because formating, erasing and flashing recovery, boot, system and userdata partitions didn't have any effects on being stuck at boot.
What I did to get out of this mess and what you need:
Stock ROM K1: nv-recovery-image-shield-tablet-k1-factory0_0_0
fastboot + adb
twrp for K1 for revovery partitions
And know your K1 partitions
Via adb shell:
cd /etc
cat recovery.fstab
shieldtablet:/etc # cd /etc
shieldtablet:/etc # cat recovery.fstab
Result:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc wait,formatable
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=writeback,noauto_da_alloc wait,check,formatable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/RP3 /usercalib ext4 noatime,data=writeback wait,formatable
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host* auto vfat defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/tegra-ehci.0/usb* auto vfat defaults voldmanaged=usb:auto
/dev/block/platform/sdhci-tegra.2/by-num/p1 /sdcard vfat defaults recoveryonly
Via adb shell:
cd dev/block/platform/sdhci-tegra.3/by-name/
ls -al
Resust:
shieldtablet:/dev/block/platform/sdhci-tegra.3/by-name # ls -al
total 0
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxr-xr-x 2 root root 520 2019-11-19 08:27 .
drwxr-xr-x 4 root root 600 2019-11-19 08:27 ..
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 APP -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 CAC -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 CHG -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 DTB -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 EKS -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 FB -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FBP -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FCG -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 FCT -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 GPT -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 LBP -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 LNX -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 MDA -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 MSC -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 NCT -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP2 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP3 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 RP4 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 SOS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 TOS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 UDA -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2019-11-19 08:27 USP -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 2019-11-19 08:27 WB0 -> /dev/block/mmcblk0p5
MAP boot, system, blob (staging) partitions with corresponding memory block
Ex: boot -> LNX -> /dev/block/mmcblk0p12
Via adb shell and using the images from K1 ROM nv-recovery-image-shield-tablet-k1-factory0_0_0 (check if your tablet k1 has the same partitions)
dd if=boot.img of=/dev/block/mmcblk0p12
dd if=system.img of=/dev/block/mmcblk0p13
dd if=blob of=/dev/block/mmcblk0p16
By getting from another ROM: tegra124-tn8-p1761-1270-a04-e-battery.dtb (renamed tegra124.dtb)
dd if=tegra124.dtb of=/dev/block/mmcblk0p11
Still failing... and stuck at boot so I decided to restore nv-recovery-image-shield-tablet-k1-factory0_0_0 via fastboot a last time but cleaned everything first:
twrp wipe all system cache data
then
fastboot flash system
fastboot erase boot
fastboot flash boot
fastboot erase staging
fastboot flash staging blob
fastboot reboot
And my Shield Tablet K1 was working again!! And very happy to have my Nvidia Shield K1 back (with latest LineageOS 15.1 ROM and working like a charm)!
I did a lot of stock ROM erase / format / restore on these partitions before and they all failed before. But I thing here the main difference is around the DTB partition.
May be the dd if=tegra124.dtb of=/dev/block/mmcblk0p11 step did properly restore the dtb info and partition or actually "corrupt" it in a way that cause the K1 to properly boot back. I don't know.
Hope that can help someone in the same situation!