Database Info

Samsung tab 2 7" p3100 : want pit files

Hello guys,
Can somebody provid3 me the pit files for samsung tab2 P3100???
Sent from my GT-P3100 using Tapatalk 2

You can get it from samfirmware.com
It comes bundled with the firmware files in a zip.
Cheers,
C.

I have downloaded the firmware from samfirmware only and in the bundle there is no pit file.
Sent from my GT-P3100 using Tapatalk 2

p3100 india firmware file
tapan15in said:
Hello guys,
Can somebody provid3 me the pit files for samsung tab2 P3100???
Sent from my GT-P3100 using Tapatalk 2
Click to expand...
Click to collapse
Hi,
I recently got my p3100.
can you give me the firmware flash file for India please.
Please i am in need of it.

Hey mainak
Just follow the guide here:
http://www.tsar3000.com/Joomla/inde...tab-2-7.0-firmware&catid=57:how-to&Itemid=104
Alternatively: Search for P3100 (login to downlaod)
http://www.sammobile.com/firmware/
I am not 100% sure - try at your own risk - but I read that this does infact work.
Also you can use odin to flash. Check out the procedure from the first link.
---------- Post added at 01:35 PM ---------- Previous post was at 01:26 PM ----------
tapan15in said:
Hello guys,
Can somebody provid3 me the pit files for samsung tab2 P3100???
Sent from my GT-P3100 using Tapatalk 2
Click to expand...
Click to collapse
Hope this helps:
http://www.mod2xtreme.com/showthread.php?11722-Download-OPS-amp-PIT-files
register to download the zip. It has a .pit file - I checked

Csn i flash the firmware without the pitfile ?
Sent from my GT-P3100 using Tapatalk 2

GT-P3100
plz give gt-p3100.pit
By-mistakenly i have put GT-P3113 (which is WiFi model),now i cant make phone calls.
i want the GT-P3100.pit (indian)

Actually no need .pit file for flashing, repartition not always safe.
P3110 or P3113 owner, please give me yours "ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/" and "cat /proc/partitions" output, over "adb shell" or Terminal Emulator:
Code:
su
ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
lrwxrwxrwx root root 2013-05-11 16:10 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-05-11 16:10 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-05-11 16:10 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-05-11 16:10 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-05-11 16:10 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-05-11 16:10 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-05-11 16:10 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-05-11 16:10 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-05-11 16:10 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-05-11 16:10 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-05-11 16:10 SBL2 -> /dev/block/mmcblk0p3

explain
ketut.kumajaya said:
Actually no need .pit file for flashing, repartition not always safe.
P3110 or P3113 owner, please give me yours "ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/" and "cat /proc/partitions" output, over "adb shell" or Terminal Emulator:
Code:
su
ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
lrwxrwxrwx root root 2013-05-11 16:10 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-05-11 16:10 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-05-11 16:10 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-05-11 16:10 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-05-11 16:10 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-05-11 16:10 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-05-11 16:10 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-05-11 16:10 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-05-11 16:10 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-05-11 16:10 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-05-11 16:10 SBL2 -> /dev/block/mmcblk0p3
Click to expand...
Click to collapse
Did not understand that
Can u clearly explain it plz

Controls stopped working?

I've had my Shield about two days now and suddenly the controls stopped working. I can only press Home, NVIDIA logo and back. I've tried a couple games but those controls don't work, nor do the controls work in the Android OS. Has anyone else experienced this? I'm backing up the game data to SD before I reset, but . I started today and I didn't root it or unlock the bootloader either. Sadness, as I love this thing.
*edit*
After reset, it looks like it's dead. I tried a game after resetting and nope, it doesn't work! How could that happen after two days?? Now I have to RMA and wait again for it. Sigh...

darkjedi said:
I've had my Shield about two days now and suddenly the controls stopped working. I can only press Home, NVIDIA logo and back. I've tried a couple games but those controls don't work, nor do the controls work in the Android OS. Has anyone else experienced this? I'm backing up the game data to SD before I reset, but . I started today and I didn't root it or unlock the bootloader either. Sadness, as I love this thing.
*edit*
After reset, it looks like it's dead. I tried a game after resetting and nope, it doesn't work! How could that happen after two days?? Now I have to RMA and wait again for it. Sigh...
Click to expand...
Click to collapse
By reset, do you mean you have switched it off by pressing the NVIDIA button for ~ 12 seconds, then switched it back on? If you did so, and it still does not work, you might have a faulty unit.
Can you enable USB debugging in the developer options, adb shell into your device, run "ls -l /sys/class/input/" and paste the output here? We'll see if the kernel can at least detect the joystick. If it does not, and you are running stock ROM, then it's likely a hardware issue.

Gnurou said:
By reset, do you mean you have switched it off by pressing the NVIDIA button for ~ 12 seconds, then switched it back on? If you did so, and it still does not work, you might have a faulty unit.
Can you enable USB debugging in the developer options, adb shell into your device, run "ls -l /sys/class/input/" and paste the output here? We'll see if the kernel can at least detect the joystick. If it does not, and you are running stock ROM, then it's likely a hardware issue.
Click to expand...
Click to collapse
Reset, meaning the "factory reset" in settings. I'll check adb tomorrow, but that's a good idea, thanks!

1|[email protected]:/ $ ls -al /sys/class/input
ls -al /sys/class/input
lrwxrwxrwx root root 2013-08-09 07:26 event0 -> ../../devices/p
latform/tegra11-spi.3/spi_master/spi3/spi3.2/input/input0/event0
lrwxrwxrwx root root 2013-08-09 07:26 event1 -> ../../devices/p
latform/tegra-snd-rt5640.0/sound/card1/input1/event1
lrwxrwxrwx root root 2013-08-09 07:19 event2 -> ../../devices/p
latform/gpio-keys.0/input/input2/event2
lrwxrwxrwx root root 2013-08-09 07:26 event3 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input3/event3
lrwxrwxrwx root root 2013-08-09 07:26 event4 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input4/event4
lrwxrwxrwx root root 2013-08-09 07:19 input0 -> ../../devices/p
latform/tegra11-spi.3/spi_master/spi3/spi3.2/input/input0
lrwxrwxrwx root root 2013-08-09 07:19 input1 -> ../../devices/p
latform/tegra-snd-rt5640.0/sound/card1/input1
lrwxrwxrwx root root 2013-08-09 07:19 input2 -> ../../devices/p
latform/gpio-keys.0/input/input2
lrwxrwxrwx root root 2013-08-09 07:19 input3 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input3
lrwxrwxrwx root root 2013-08-09 07:19 input4 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input4

Mmm I am not setting the joystick being listed here. it's supposed to be on the USB bus. Very likely, you got a faulty unit and need to ask NVIDIA for a replacement.

What's really weird, is that I flashed the recovery image (on NVIDIA's site) and it still didn't work. HOWEVER, NVIDIA called me to set up an RMA, then magically it started working. I now show this:
[email protected]:/ $ ls -al /sys/class/input
ls -al /sys/class/input
lrwxrwxrwx root root 2013-08-10 09:12 event0 -> ../../devices/p
latform/tegra11-spi.3/spi_master/spi3/spi3.2/input/input0/event0
lrwxrwxrwx root root 2013-08-10 09:12 event1 -> ../../devices/p
latform/tegra-ehci.2/usb1/1-1/1-1:1.0/input/input1/event1
lrwxrwxrwx root root 2013-08-10 09:10 event2 -> ../../devices/p
latform/tegra-snd-rt5640.0/sound/card1/input2/event2
lrwxrwxrwx root root 2013-08-10 09:12 event3 -> ../../devices/p
latform/gpio-keys.0/input/input3/event3
lrwxrwxrwx root root 2013-08-10 09:12 event4 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input4/event4
lrwxrwxrwx root root 2013-08-10 09:12 event5 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input5/event5
lrwxrwxrwx root root 2013-08-10 09:10 input0 -> ../../devices/p
latform/tegra11-spi.3/spi_master/spi3/spi3.2/input/input0
lrwxrwxrwx root root 2013-08-10 09:10 input1 -> ../../devices/p
latform/tegra-ehci.2/usb1/1-1/1-1:1.0/input/input1
lrwxrwxrwx root root 2013-08-10 09:10 input2 -> ../../devices/p
latform/tegra-snd-rt5640.0/sound/card1/input2
lrwxrwxrwx root root 2013-08-10 09:10 input3 -> ../../devices/p
latform/gpio-keys.0/input/input3
lrwxrwxrwx root root 2013-08-10 09:10 input4 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input4
lrwxrwxrwx root root 2013-08-10 09:10 input5 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input5
lrwxrwxrwx root root 2013-08-10 09:12 js0 -> ../../devices/plat
form/tegra-ehci.2/usb1/1-1/1-1:1.0/input/input1/js0
[email protected]:/ $
I didn't do anything different from the time I flashed the recovery to when it started working. I only had it powered off for 8 hours. And BAM came back to life. :\ Very, very strange indeed.

darkjedi said:
What's really weird, is that I flashed the recovery image (on NVIDIA's site) and it still didn't work. HOWEVER, NVIDIA called me to set up an RMA, then magically it started working.
I didn't do anything different from the time I flashed the recovery to when it started working. I only had it powered off for 8 hours. And BAM came back to life. :\ Very, very strange indeed.
Click to expand...
Click to collapse
Last night I was playing sg deadzone with my bluetooth headphones and my controls would stop working sometimes. I shut off bluetooth and everything was fine. Maybe it was just bad lag from their servers but I wasn't sure if it was the BT or not.

I've had mine stop working after the shield has been sleeping over night before. A reboot fixed them though and I never really gave it a second thought.

darkjedi said:
What's really weird, is that I flashed the recovery image (on NVIDIA's site) and it still didn't work. HOWEVER, NVIDIA called me to set up an RMA, then magically it started working. I now show this:
[email protected]:/ $ ls -al /sys/class/input
ls -al /sys/class/input
lrwxrwxrwx root root 2013-08-10 09:12 event0 -> ../../devices/p
latform/tegra11-spi.3/spi_master/spi3/spi3.2/input/input0/event0
lrwxrwxrwx root root 2013-08-10 09:12 event1 -> ../../devices/p
latform/tegra-ehci.2/usb1/1-1/1-1:1.0/input/input1/event1
lrwxrwxrwx root root 2013-08-10 09:10 event2 -> ../../devices/p
latform/tegra-snd-rt5640.0/sound/card1/input2/event2
lrwxrwxrwx root root 2013-08-10 09:12 event3 -> ../../devices/p
latform/gpio-keys.0/input/input3/event3
lrwxrwxrwx root root 2013-08-10 09:12 event4 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input4/event4
lrwxrwxrwx root root 2013-08-10 09:12 event5 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input5/event5
lrwxrwxrwx root root 2013-08-10 09:10 input0 -> ../../devices/p
latform/tegra11-spi.3/spi_master/spi3/spi3.2/input/input0
lrwxrwxrwx root root 2013-08-10 09:10 input1 -> ../../devices/p
latform/tegra-ehci.2/usb1/1-1/1-1:1.0/input/input1
lrwxrwxrwx root root 2013-08-10 09:10 input2 -> ../../devices/p
latform/tegra-snd-rt5640.0/sound/card1/input2
lrwxrwxrwx root root 2013-08-10 09:10 input3 -> ../../devices/p
latform/gpio-keys.0/input/input3
lrwxrwxrwx root root 2013-08-10 09:10 input4 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input4
lrwxrwxrwx root root 2013-08-10 09:10 input5 -> ../../devices/p
latform/tegra11-i2c.0/i2c-0/0-0068/input/input5
lrwxrwxrwx root root 2013-08-10 09:12 js0 -> ../../devices/plat
form/tegra-ehci.2/usb1/1-1/1-1:1.0/input/input1/js0
[email protected]:/ $
I didn't do anything different from the time I flashed the recovery to when it started working. I only had it powered off for 8 hours. And BAM came back to life. :\ Very, very strange indeed.
Click to expand...
Click to collapse
Yes, here the joystick appears as expected. Recovery should have nothing to do with joystick behavior, so I wouldn't say the two events are related. If you have flashed custom ROMs/kernels they might be the cause for this though. Joystick is driven by a microcontroller which requires the right firmware to be uploaded, if something tampered with the firmware then your joystick might indeed stop being detected.
I'm only speculating here though - a hardware problem is not to exclude, especially if you stayed with the stock ROM.

Sorry to dig up an old thread, but I thought it more appropriate than starting a new one. I've had this issue twice now myself (opening the shield and the controls do not work). Each time shutting down normally thorugh the android menu and starting back up do not work to bring the controls back, however if I hold the "nvidia button" down until the device shuts off, then turn it back on the controls come back just fine, like nothing ever happened.
I'm guessing this is some sort of software issue. Are there any logs I could take a look at to get more of an idea of what's going on? (ie if the microcontroller is being woken up properly, etc.)
I do also notice that every digital and analog input is broken with the exception of the touchscreen, the home button, the back button, and the "nvidia button". (so basically everything over the USB). I haven't really tried much more debugging yet, but I might try playing with a USB keyboard through the OTG port to see if that is affected as well.

[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.

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!

Verizon Pixel 2, assistance needed

Yes, there is a thread for unlocking the bootloader but that is for a previous version. If anyone with root is running the factory image for Android 9.0, we are in need of a bit image dump. If you can follow the link below and just provide the dump, I am more than happy to do the rest.
From what I have been noticing, there may be a hidden command that is preventing us from getting further in unlocking the bootloader. Any help to either prove or disprove this theory would be greatly appreciated. In the meantime, I am syncing with the aosp repo provided by Google.
Your help could greatly speed up the process ?
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands
Thank you

I've tried everything as far as decompiling system apks. Someone doing this would really really help out.

there is not one called aboot, here is a print out of what it shows. I did get the aboot1 and aboot2I uploaded them to my google drive.
walleye:/ $ su
walleye:/ # cd /dev/block/bootdevice/by-name
walleye:/dev/block/bootdevice/by-name # ls -all
total 0
drwxr-xr-x 2 root root 1540 1970-12-11 22:15:39.436666759 -0500 .
drwxr-xr-x 3 root root 1680 1970-12-11 22:15:39.436666759 -0500 ..
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.410000090 -0500 abl_a -> /dev/block/sda8
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.403333423 -0500 abl_b -> /dev/block/sda29
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.406666756 -0500 apdp_a -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.426666758 -0500 apdp_b -> /dev/block/sda35
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.423333425 -0500 board_info -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:38.666666683 -0500 boot_a -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.410000090 -0500 boot_b -> /dev/block/sda30
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.433333426 -0500 cdt -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.400000089 -0500 cmnlib64_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.423333425 -0500 cmnlib64_b -> /dev/block/sda34
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.420000091 -0500 cmnlib_a -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.416666757 -0500 cmnlib_b -> /dev/block/sda33
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.426666758 -0500 ddr -> /dev/block/sdd6
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.413333424 -0500 devcfg_a -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.403333423 -0500 devcfg_b -> /dev/block/sda37
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.436666759 -0500 devinfo -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.416666757 -0500 dip -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.430000092 -0500 dpo -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:38.670000016 -0500 dtbo_a -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.426666758 -0500 dtbo_b -> /dev/block/sda42
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.430000092 -0500 frp -> /dev/block/sdd4
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.430000092 -0500 fsc -> /dev/block/sdd17
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.433333426 -0500 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.413333424 -0500 hosd_a -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.420000091 -0500 hosd_b -> /dev/block/sda31
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.400000089 -0500 hyp_a -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.420000091 -0500 hyp_b -> /dev/block/sda26
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.423333425 -0500 keymaster_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.413333424 -0500 keymaster_b -> /dev/block/sda32
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.420000091 -0500 limits -> /dev/block/sdd11
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.410000090 -0500 lockbooter_a -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.420000091 -0500 lockbooter_b -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.433333426 -0500 logfs -> /dev/block/sdd13
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.420000091 -0500 metadata -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.420000091 -0500 mfg -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.426666758 -0500 misc -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.413333424 -0500 modem_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.423333425 -0500 modem_b -> /dev/block/sda28
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.413333424 -0500 modemst1 -> /dev/block/sdd15
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.416666757 -0500 modemst2 -> /dev/block/sdd16
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.416666757 -0500 msadp_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.426666758 -0500 msadp_b -> /dev/block/sda36
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.410000090 -0500 padding0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.426666758 -0500 padding1 -> /dev/block/sda44
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:38.673333350 -0500 persist -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.430000092 -0500 pg1fs -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.420000091 -0500 pg2fs -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.406666756 -0500 pmic_a -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.426666758 -0500 pmic_b -> /dev/block/sda27
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.416666757 -0500 ramdump -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.420000091 -0500 reserve3 -> /dev/block/sdd18
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.433333426 -0500 reserve4 -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.430000092 -0500 reserve5 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.420000091 -0500 rpm_a -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.413333424 -0500 rpm_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.413333424 -0500 sec -> /dev/block/sdd7
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.420000091 -0500 splash -> /dev/block/sdd10
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.416666757 -0500 ssd -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.430000092 -0500 sti -> /dev/block/sdd14
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.413333424 -0500 storsec_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.410000090 -0500 storsec_b -> /dev/block/sda38
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:38.670000016 -0500 system_a -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.430000092 -0500 system_b -> /dev/block/sda43
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.430000092 -0500 toolsfv -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.423333425 -0500 trusty_a -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.416666757 -0500 trusty_b -> /dev/block/sda40
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.420000091 -0500 tz_a -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.416666757 -0500 tz_b -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.403333423 -0500 userdata -> /dev/block/sda45
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:38.670000016 -0500 vbmeta_a -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.426666758 -0500 vbmeta_b -> /dev/block/sda39
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:38.670000016 -0500 vendor_a -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 1970-12-11 22:15:39.416666757 -0500 vendor_b -> /dev/block/sda41
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.430000092 -0500 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-12-11 22:15:39.416666757 -0500 xbl_b -> /dev/block/sdc1
<
the.puppet.master said:
Yes, there is a thread for unlocking the bootloader but that is for a previous version. If anyone with root is running the factory image for Android 9.0, we are in need of a bit image dump. If you can follow the link below and just provide the dump, I am more than happy to do the rest.
From what I have been noticing, there may be a hidden command that is preventing us from getting further in unlocking the bootloader. Any help to either prove or disprove this theory would be greatly appreciated. In the meantime, I am syncing with the aosp repo provided by Google.
Your help could greatly speed up the process
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands
Thank you
Click to expand...
Click to collapse

I'm using the pixel 2 and have factory Android 9 /P . Unrooted and waiting for a way to unlock. What is it you need. And they were saying in the other thread if you took the ota to latest Android 9 there is no way it can be done. There will be a way and I know this ,maybe just a matter of time.

mattie_49 said:
I'm using the pixel 2 and have factory Android 9 /P . Unrooted and waiting for a way to unlock. What is it you need. And they were saying in the other thread if you took the ota to latest Android 9 there is no way it can be done. There will be a way and I know this ,maybe just a matter of time.
Click to expand...
Click to collapse
Sorry boss what he's looking for you can't offer, as you're not rooted. "If anyone with root is running the factory image for Android 9.0"
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
@the.puppet.master did you get everything you needed? I'd be willing to update my Pix2 to 9.0 on stock to get what you need. I'm running an unlocked BL Pix2 on the July security patch. Since I mostly run stock, I'd be happy to assist... Just let me know...

b00ster23 said:
Sorry boss what he's looking for you can't offer, as you're not rooted. "If anyone with root is running the factory image for Android 9.0"
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
@the.puppet.master did you get everything you needed? I'd be willing to update my Pix2 to 9.0 on stock to get what you need. I'm running an unlocked BL Pix2 on the July security patch. Since I mostly run stock, I'd be happy to assist... Just let me know...
Click to expand...
Click to collapse
We will surely have an unlock method before long correct? Since it's actually based off Htc I wonder if sunshine might be a route to unlock bootloader ? Actually just looked sunshine released a free tool for pixel /pixel XL called depixel8. Hopefully they will update for pixel 2. Wonder if it would even be worth a try on the 2. I don't think it would hurt anything . I'm almost willing to give it a go.

mattie_49 said:
We will surely have an unlock method before long correct? Since it's actually based off Htc I wonder if sunshine might be a route to unlock bootloader ? Actually just looked sunshine released a free tool for pixel /pixel XL called depixel8. Hopefully they will update for pixel 2. Wonder if it would even be worth a try on the 2. I don't think it would hurt anything . I'm almost willing to give it a go.
Click to expand...
Click to collapse
That exploit was patched in Android 7.1. You can try it, but it simply won't do anything at all. It will eventually happen, but at a standstill right now. I decompiled everything I could to find any other OEM fastboot commands, dialer codes, etc... Found a few unrelated things that, although still cool, did not aid in my quest to unlock the bootloader any.

crixley said:
That exploit was patched in Android 7.1. You can try it, but it simply won't do anything at all. It will eventually happen, but at a standstill right now. I decompiled everything I could to find any other OEM fastboot commands, dialer codes, etc... Found a few unrelated things that, although still cool, did not aid in my quest to unlock the bootloader any.
Click to expand...
Click to collapse
I've always needed to work on my patience anyway. Device is still amazing stock. Getting close to 2 days off charger and nearing 8 hours on screen. No complaints. Thanks for your response.

b00ster23 said:
Sorry boss what he's looking for you can't offer, as you're not rooted. "If anyone with root is running the factory image for Android 9.0"
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
@the.puppet.master did you get everything you needed? I'd be willing to update my Pix2 to 9.0 on stock to get what you need. I'm running an unlocked BL Pix2 on the July security patch. Since I mostly run stock, I'd be happy to assist... Just let me know...
Click to expand...
Click to collapse
I haven't had time to do much of anything since posting this. I got hit with a heavy workload but I should be back on it the next few days. I'll post any findings I come across.
Thanks

the.puppet.master said:
I haven't had time to do much of anything since posting this. I got hit with a heavy workload but I should be back on it the next few days. I'll post any findings I come across.
Thanks
Click to expand...
Click to collapse
Pixel3 about to drop. Surely you guys will find the solution. Wish I knew more about it
So as to I could help.

Sorry to jump in the middle of the conversation. But if your looking for fastboot commands , there's plenty not mentioned anywhere. Using Linux I ran strings laf.img | grep OEM ,oem, etc. There's several lg commands. I even saw a command that , memory might be off, but it basically said skip check. May have printed it out. I'll post if so. Since there's no aboot.img as in previous Google phones I can only guess laf if the beholder now. It certainly hold a lot of info. Oddly I was able to extract it like a zip using 7z.
Sent from my Pixel 2 XL using Tapatalk

blueyes said:
Sorry to jump in the middle of the conversation. But if your looking for fastboot commands , there's plenty not mentioned anywhere. Using Linux I ran strings laf.img | grep OEM ,oem, etc. There's several lg commands. I even saw a command that , memory might be off, but it basically said skip check. May have printed it out. I'll post if so. Since there's no aboot.img as in previous Google phones I can only guess laf if the beholder now. It certainly hold a lot of info. Oddly I was able to extract it like a zip using 7z.
Click to expand...
Click to collapse
Your not interrupting anything . The op doesn't respond to anything. Oh well . It will be figured out. The matter is when

I'm surprised a year into this device none of the dozens of software masterminds haven't unlocked it. Every other Verizon phone seems to be getting unlocked, Samsung, LG. There's a couple sites saying that they can but using a drastic (might not get it back) system by essentially repartitioning it.
mattie_49 said:
Your not interrupting anything . The op doesn't respond to anything. Oh well . It will be figured out. The matter is when
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

blueyes said:
Sorry to jump in the middle of the conversation. But if your looking for fastboot commands , there's plenty not mentioned anywhere. Using Linux I ran strings laf.img | grep OEM ,oem, etc. There's several lg commands. I even saw a command that , memory might be off, but it basically said skip check. May have printed it out. I'll post if so. Since there's no aboot.img as in previous Google phones I can only guess laf if the beholder now. It certainly hold a lot of info. Oddly I was able to extract it like a zip using 7z.
Click to expand...
Click to collapse
You're on the xl and not regular pixel correct? I found a list of OEM fastboot commands for standard pixel, however a large portion did not work. I also researched and tried old HTC codes to see if perhaps they rehashed some. There was a fastboot command to get your unlock code, however entering it at htcdev does not work.

There's actually the same cmd to get pxl2s unlock code. Only useful after it's unlocked, same as the HTC. I have a OG xl, bought a Verizon 2xl thinking it'll be hacked as quickly as the OG. Just sold it on eBay, turned around and bought a Google version and didn't lose a dime.
crixley said:
You're on the xl and not regular pixel correct? I found a list of OEM fastboot commands for standard pixel, however a large portion did not work. I also researched and tried old HTC codes to see if perhaps they rehashed some. There was a fastboot command to get your unlock code, however entering it at htcdev does not work.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
https://drive.google.com/file/d/1mE2IgQ8_Gc4HdyeJjHQDuLTtEZxHkJWf/view?usp=drivesdk
Printed up some of the cmds
---------- Post added at 03:13 PM ---------- Previous post was at 02:52 PM ----------
I think these guys could do it , if you read their posts. True hackers, borderline criminals. Lol
https://sinister.ly/Thread-Google-Pixel-2-XL-IMEIs-Verizon-GS

blueyes said:
There's actually the same cmd to get pxl2s unlock code. Only useful after it's unlocked, same as the HTC. I have a OG xl, bought a Verizon 2xl thinking it'll be hacked as quickly as the OG. Just sold it on eBay, turned around and bought a Google version and didn't lose a dime.
Sent from my Pixel 2 XL using Tapatalk
https://drive.google.com/file/d/1mE2IgQ8_Gc4HdyeJjHQDuLTtEZxHkJWf/view?usp=drivesdk
Printed up some of the cmds
---------- Post added at 03:13 PM ---------- Previous post was at 02:52 PM ----------
I think these guys could do it , if you read their posts. True hackers, borderline criminals. Lol
https://sinister.ly/Thread-Google-Pixel-2-XL-IMEIs-Verizon-GS
Click to expand...
Click to collapse
**SCRATCH MY ORIGINAL RESPONSE, I TOOK A CLOSER LOOK WHILE I'M AT WORK**
I see what you mean, those are not commands however in the sense that we can enter them ourselves. We need to find a way to spoof the initial check that starts the provision, or use one of these ideas:
1.) fastboot oem get_identifier_token - this would be hard as it would require either breaking htcs method of creating unlock.bin files, or finding a way to sign them after tampering.
2.)fastboot oem readconfig/writeconfig. In order to use this we would need to figure out which bit is the "secure" bit. I believe writeconfig actually works on our device

crixley said:
Are you referring to "Bootloader OEM.txt"? That has nothing to do with the bootloader at all and is actually referencing wifi from what I can see. "OEM" does not necessarily refer to the bootloader, but qualcomm, etc.. as well.
Click to expand...
Click to collapse
Can't believe it's been like this since March. Maybe the sunshine people will find a new way

mattie_49 said:
Can't believe it's been like this since March. Maybe the sunshine people will find a new way
Click to expand...
Click to collapse
Feel free to help out. I've spent hours and hours on top of late nights at a busy engineering firm and two children. A lot of the exploits have been figured out by near luck. It takes a lot of time and effort, and unfortunately pixel devices are not as developer supported as nexus ones were.
The fact that we are even in this situation and that google even allows verizon to run the show is frustrating enough.

crixley said:
Feel free to help out. I've spent hours and hours on top of late nights at a busy engineering firm and two children. A lot of the exploits have been figured out by near luck. It takes a lot of time and effort, and unfortunately pixel devices are not as developer supported as nexus ones were.
The fact that we are even in this situation and that google even allows verizon to run the show is frustrating enough.
Click to expand...
Click to collapse
I wish I knew where to even begin helping. I know quite a bit but my knowledge is all about after the bootloader is already unlocked. Sorry didn't mean for it to sound pushy. Didn't mean it like that. I have a new baby as well. Life comes first for sure

mattie_49 said:
I wish I knew where to even begin helping. I know quite a bit but my knowledge is all about after the bootloader is already unlocked. Sorry didn't mean for it to sound pushy. Didn't mean it like that. I have a new baby as well. Life comes first for sure
Click to expand...
Click to collapse
I didn't mean to be rude either, you seem like a nice guy it is just that honestly it is the best way to get something done. I have been using android a long time and learned through practice and a ton of reading. Sometimes it is the only way you'll see any results.
I thought of something else as well as a possible solution:
Since our chips are qualcomm, we could try finding the firehose files for our device and use qloader/qpst to write directly to the partition, or even just as an easy method to provide folks on here to flash android version back to when lock_critical worked (some sort of a command line tool perhaps?)