Hi.
I get a Nexus 7 2013. Problem is, it will not boot any rom.
Fastboot, TWRP, flash rom or factory image works fine, but i will bootloop every time with any rom.
Tried with CM14.1, CM13, AOSP, latest factory image and first factory image.
Someone has an idea? Can i log the boot somehow?
baggerbodo said:
Hi.
I get a Nexus 7 2013. Problem is, it will not boot any rom.
Fastboot, TWRP, flash rom or factory image works fine, but i will bootloop every time with any rom.
Tried wich CM14.1, CM13, AOSP, latest factory image and first factory image.
Someone has an idea? Can i log the boot somehow?
Click to expand...
Click to collapse
Hello, I think I know the problem but let's see some logs first. Start your OS and on the next bootloop turn it off and as quickly as possible turn it back on to TWRP recovery. The off/on must happen within max 2 seconds in order to preserve last_kmsg in RAM intact. Then while in TWRP attach an OTG USB drive with my get-logs.zip on it, 'install' it and post 'logs.tgz' which was created on the flashdrive.
If you don't have an OTG drive/adapter, have a look inside the zip and use ADB to get the logs manually.
That´s crazy. Now i havo no bootloops more but stuck on boot logo.
Anyway, here is my log after 15 minutes boot. (please remove .zip)
The kernel cannot communicate properly with LTE modem and constantly, repeatedly logs this sequence:
Code:
mdm_modem_ioctl: Powering on mdm id 0
mdm_do_soft_power_on: id 0: soft resetting mdm modem
It is either a software/data or hardware issue.
Apart from the 'radio' partition which you have reflashed many times, the modem also needs:
Code:
modemst1 mmcblk0p2 3MB
modemst2 mmcblk0p3 3MB
fsg mmcblk0p8 3MB
These partitions are never flashed from OS and I/we always back them up before any ROM changes on mobile phones.
I don't have the LTE N7 and can't help you if the partitions are corrupt or erased.
As for possible hardware issue I note on the pictures antenna sockets, so the modem seems to be next to SIM card reader on the daughterboard PCB. If so, then the fix is very simple. The wide silver flex cable which connects both PCBs is notoriously unreliable and needs to be re-seated on both connectors. I'd bet on it :fingers-crossed:
So you think i need a complete system dump?
Here are my partitiones.
Code:
179 0 30539776 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 28180463 mmcblk0p30
Code:
drwxr-xr-x 2 root root 640 Jan 1 00:02 .
drwxr-xr-x 4 root root 700 Jan 1 00:02 ..
lrwxrwxrwx 1 root root 21 Jan 1 00:02 DDR -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 1 00:02 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 00:02 abootb -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 1 00:02 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 00:02 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 1 00:02 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs3 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 1 00:02 m9kefsc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 1 00:02 metadata -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 1 00:02 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 1 00:02 modemst1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 00:02 modemst2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 00:02 pad -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 1 00:02 persist -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 00:02 radio -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 1 00:02 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 1 00:02 rpm -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 00:02 rpmb -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 1 00:02 sbl1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl2b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl3b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 1 00:02 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 1 00:02 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 00:02 tz -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 00:02 tzb -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 1 00:02 userdata -> /dev/block/mmcblk0p30
Now i get bootloops again, please have a look in my logs.
baggerbodo said:
So you think i need a complete system dump?
Now i get bootloops again, please have a look in my logs.
Click to expand...
Click to collapse
I think you need to check the cable first.
The new logs don't offer more insights but if you are successful in capturing logcat during bootloop it would be very interesting:
http://forum.xda-developers.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818
http://forum.xda-developers.com/showpost.php?p=47172724
Related
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 512000 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 9728000 mmcblk0p29
Code:
lrwxrwxrwx root root 1970-01-02 04:23 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:23 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:23 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:23 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:23 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:23 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 04:23 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:23 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:23 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:23 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 04:23 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:23 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:23 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:23 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:23 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:23 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:23 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:23 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:23 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 04:23 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:23 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:23 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:23 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:23 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:23 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:23 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 04:23 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:23 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:23 userdata -> /dev/block/mmcblk0p29
I am just trying to get a rough feel for the demand that exists for getting CM-12 on the T-Mobile variant of the Tab S 10.5.
I have one that I picked up, and I have not done much with it. I have been kicking around the idea of trying to get CM-12.0 up on it, but I dont want to soak a ton of time into if there is not a decent demand for it.
Anyway guys, let me know!
Sounds like a great idea, I don't have one yet, but would definitely consider picking one up if CM12 came out.
This is all I really want out of this tablet. Let me know if you're seriously thinking about doing it because I'll kick you a few bucks if its doable.
do it please!
I would also shoot you some money I get paid on Friday and would love to donate to getting my tablet rooted
Yes, yes please.
I have the T-Mobile variant and would really appreciate the effort. I, too, would be happy to kick a few bucks your way for the trouble.
It would be amazing to have an AOSP option for it without shutting out LTE.
Please. I am so ready for 12.
Before you try does the Tmobile variant have an unlockable bootloader if it does its going to be a brand new bring up none of the work for the t805 (Exynos Galaxy tab S 10.5 LTE) will work because the US LTE variants have Qualcomm chipsets you would have to base the work off of mondrianlte (Galaxy Tab Pro 8.0 LTE)
deadman96385 said:
Before you try does the Tmobile variant have an unlockable bootloader if it does its going to be a brand new bring up none of the work for the t805 (Exynos Galaxy tab S 10.5 LTE) will work because the US LTE variants have Qualcomm chipsets you would have to base the work off of mondrianlte (Galaxy Tab Pro 8.0 LTE)
Click to expand...
Click to collapse
T807T has unlocked bootloader (T-Mobile device). Specs are exactly the same as T805 exynos. The only thing that's different is that it won't connect to Lte and such since its an T-Mobile device from what I heard.
T807P= Sprint Tab S with Snapdragon. Unlocked bootloader too.
Hopefully this helps!
DUHAsianSKILLZ said:
T807T has unlocked bootloader (T-Mobile device). Specs are exactly the same as T805 exynos. The only thing that's different is that it won't connect to Lte and such since its an T-Mobile device from what I heard.
T807P= Sprint Tab S with Snapdragon. Unlocked bootloader too.
Hopefully this helps!
Click to expand...
Click to collapse
Sweet did not know i will take a peek at the kernel source for the tmobile and see whats needed to add support for it in my kernel
Edit: Took a quick peek its using the gpu that all the other tab S's use except the chagalllte and its not using the broadcom wifi cob for whatever reason
Edit 2: There you go kernel support right away (Was not hard at all it only needed a new defconfig, i did not find any other differences kernel source wise)
https://github.com/LiquidSmooth-Dev...mmit/26f98a28280b72c135c81a0304152f550ffe9603
Edit 3: Now all you need is some basic edits to the chagalllte tree to change it too chagalltmo
Edit 4: Basic Device Tree: https://github.com/deadman96385/android_device_samsung_chagalltmo
I would need someone who owns it too pull the system partition not in img form though to make somthing that will actually work
deadman96385 said:
Sweet did not know i will take a peek at the kernel source for the tmobile and see whats needed to add support for it in my kernel
Edit: Took a quick peek its using the gpu that all the other tab S's use except the chagalllte and its not using the broadcom wifi cob for whatever reason
Edit 2: There you go kernel support right away (Was not hard at all it only needed a new defconfig, i did not find any other differences kernel source wise)
https://github.com/LiquidSmooth-Dev...mmit/26f98a28280b72c135c81a0304152f550ffe9603
Edit 3: Now all you need is some basic edits to the chagalllte tree to change it too chagalltmo
Edit 4: Basic Device Tree: https://github.com/deadman96385/android_device_samsung_chagalltmo
I would need someone who owns it too pull the system partition not in img form though to make somthing that will actually work
Click to expand...
Click to collapse
Tell me what to do and I will. To give you an idea of my skill level - I have made kernel edits before from guides and can sometimes get away with smali changes. My device is rooted and I am not worried about warranty voids. TWRP recovery only as far as I know.
In fact, if you could get Liquidsmooth working too I would be thrilled to pieces. I love that rom! I will help you test both and report any bugs I find.
thats good news if you are going to work on an exynos based tablet. this way cm12 can support other exynos models too .. i have a 805y model.
You will need to do section 1 and 2 and pull the system partition like they do there and make sure to also right down the partition layout and sizes http://forum.xda-developers.com/showthread.php?t=2450045
deadman96385 said:
You will need to do section 1 and 2 and pull the system partition like they do there and make sure to also right down the partition layout and sizes http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Code:
s[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 10240 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 49152 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 3719168 mmcblk0p18
259 11 512000 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 10985472 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
[email protected]:/ $ ls -al /dev/block/platform/dw_mmc.0/by-name
ls -al /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2015-06-21 13:21 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-06-21 13:21 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-06-21 13:21 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-06-21 13:21 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-06-21 13:21 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-06-21 13:21 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-06-21 13:21 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-06-21 13:21 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-06-21 13:21 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-06-21 13:21 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-06-21 13:21 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-06-21 13:21 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-06-21 13:21 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-06-21 13:21 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-06-21 13:21 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-06-21 13:21 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-06-21 13:21 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-06-21 13:21 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs3 -> /dev/block/mmcblk0p6
I am currently uploading the .img dump and will edit this post when it is up. If you need in another format you'll have to let me know how to go about that.
mmolitor87 said:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 10240 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 49152 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 3719168 mmcblk0p18
259 11 512000 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 10985472 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
[email protected]:/ $ ls -al /dev/block/platform/dw_mmc.0/by-name
ls -al /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2015-06-21 13:21 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-06-21 13:21 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-06-21 13:21 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-06-21 13:21 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-06-21 13:21 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-06-21 13:21 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-06-21 13:21 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-06-21 13:21 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-06-21 13:21 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-06-21 13:21 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-06-21 13:21 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-06-21 13:21 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-06-21 13:21 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-06-21 13:21 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-06-21 13:21 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-06-21 13:21 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-06-21 13:21 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-06-21 13:21 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs3 -> /dev/block/mmcblk0p6
I am currently uploading the .img dump and will edit this post when it is up. If you need in another format you'll have to let me know how to go about that.
Click to expand...
Click to collapse
I have updated the tree with the partition sizes for your variant in theory it should build now i will be gone for 6 days so i will work on it again then.
deadman96385 said:
I have updated the tree with the partition sizes for your variant in theory it should build now i will be gone for 6 days so i will work on it again then.
Click to expand...
Click to collapse
https://mega.co.nz/#!ikEGFByQ!ye01JD1anD6xNItVJXdd69YN2uTFhkEkxrQdVmsaKeY
This is the .img file! Let me know if you need anything else for it. I'm excited to get flashing.
mmolitor87 said:
https://mega.co.nz/#!ikEGFByQ!ye01JD1anD6xNItVJXdd69YN2uTFhkEkxrQdVmsaKeY
This is the .img file! Let me know if you need anything else for it. I'm excited to get flashing.
Click to expand...
Click to collapse
Thanks that helped, sadly i have to go before my build finishes but if it does it will copy the build to the link below so give it a few hours after this post for it too appear if it doesn't i'll fix it when i get back had to do some hacky kernel work.
http://www.drdevs.com/devs/teamliquid/Test/
deadman96385 said:
Thanks that helped, sadly i have to go before my build finishes but if it does it will copy the build to the link below so give it a few hours after this post for it too appear if it doesn't i'll fix it when i get back had to do some hacky kernel work.
http://www.drdevs.com/devs/teamliquid/Test/
Click to expand...
Click to collapse
Glad it helped! I will keep an eye out for it. Nothing just yet. I can't wait...this would be the first AOSP rom for this variant as far as I'm aware!
mmolitor87 said:
Glad it helped! I will keep an eye out for it. Nothing just yet. I can't wait...this would be the first AOSP rom for this variant as far as I'm aware!
Click to expand...
Click to collapse
Another interested t807t user here. Would help with testing. Surprised to find that CM12 isn't already a thing on this device. We need more heroes to continue this quest
Nice to see CM12 coming to this device.
I am waiting patiently for this. I have a question. Can I install the other variant roms on this device as well? I am ok with no lte.
EDIT: oops problem solved using carliv image kitchen
I'm completely at a loss here trying to just make an image or mount the stock recovery partition on the F460 variant. Much thanks to anyone who looks at this...
I did the standard dd to img file and I can't open it, getting a bunch of errors (see below) when run through various disk tools. I tried to dd the exact block range which just produces the same result.
I tried mounting the recovery partition on the device but mount doesn't want to work with me.
Code:
1|[email protected]:/ # mount /dev/block/mmcblk0p21 /sdcard/recovery
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount -t ext4 /dev/block/mmcblk0p21 /sdcard/recovery
mount: Invalid argument
I booted into recovery from ADB just to see if it was even intact and it showed the stock recovery logo just fine.
Here's some (helpful??) details...
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 87536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 16 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 4 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 512 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2044 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 32768 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 1 mmcblk0p25
179 26 4 mmcblk0p26
179 27 3072 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 4 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 5104 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 8192 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 32768 mmcblk0p39
259 8 32768 mmcblk0p40
259 9 32768 mmcblk0p41
259 10 2523136 mmcblk0p42
259 11 868352 mmcblk0p43
259 12 16384 mmcblk0p44
259 13 26480640 mmcblk0p45
259 14 188399 mmcblk0p46
179 32 4096 mmcblk0rpmb
179 64 30703616 mmcblk1
179 65 30702592 mmcblk1p1
Code:
[email protected]:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-04 01:47 DDR -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 01:47 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 01:47 abootb -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-04 01:47 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 01:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-04 01:47 drm -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-04 01:47 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-04 01:47 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-04 01:47 factory -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-04 01:47 fota -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-04 01:47 fsc -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 01:47 fsg -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 01:47 grow -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-01-04 01:47 laf -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefsc -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 01:47 misc -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-04 01:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 01:47 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-04 01:47 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 01:47 pad1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-04 01:47 pad2 -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-04 01:47 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 01:47 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-04 01:47 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 01:47 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 01:47 rpmbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-04 01:47 rpmf -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-04 01:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 01:47 sbl1b -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 01:47 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 01:47 sdibak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-04 01:47 sdif -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 01:47 sec -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 01:47 sns -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-04 01:47 spare1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 01:47 spare2 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-04 01:47 spare3 -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-04 01:47 ssd -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-04 01:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-04 01:47 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 01:47 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 01:47 tzf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 01:47 userdata -> /dev/block/mmcblk0p45
Code:
[email protected]:~/Desktop$ parted recovery.img
WARNING: You are not superuser. Watch out for permissions.
GNU Parted 2.3
Using /home/shawn/Desktop/recovery.img
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Error: /home/shawn/Desktop/recovery.img: unrecognised disk label
[email protected]:~/Desktop$ fdisk -l recovery.img
Disk recovery.img: 16 MB, 16777216 bytes
255 heads, 63 sectors/track, 2 cylinders, total 32768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk recovery.img doesn't contain a valid partition table
[email protected]:~/Desktop$ e2fsck recovery.img
e2fsck 1.42.9 (4-Feb-2014)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open recovery.img
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
[email protected]:~/Desktop$ e2fsck -b 8192 recovery.img
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open recovery.img
Could this be a zero-length partition?
I am using a Linux machine and adb.
Nubia NX503a (25S)
Code:
[email protected]:~$ adb devices
List of devices attached
MSM8974 recovery
[email protected]:~$
Code:
~ # ls -la
drwxr-xr-x 22 root root 0 Jan 3 18:48 .
drwxr-xr-x 22 root root 0 Jan 3 18:48 ..
drwxr-xr-x 2 root root 0 Jan 3 18:46 boot
drwxr-xr-x 4 root root 4096 Jan 3 18:03 cache
drwxr-xr-x 5 root root 4096 Jan 3 20:15 data
drwxr-xr-x 2 root root 0 Jan 3 18:46 datadata
-rw-r--r-- 1 root root 5785 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 15160 Jan 3 18:46 dev
drwxr-xr-x 2 root root 0 Jan 3 18:46 emmc
drwxr-xr-x 2 root root 0 Jan 3 18:46 etc
drwxr-xr-x 2 root root 0 Jan 3 18:46 external_sd
-rwxr-x--- 1 root root 113592 Jan 1 00:00 init
-rwxr-x--- 1 root root 1417 Jan 1 00:00 init.rc
drwxr-xr-x 2 root root 0 Jan 3 18:46 internal_sd
drwxrwx--x 6 system system 4096 Jan 2 00:30 persist
dr-xr-xr-x 158 root root 0 Jan 1 00:00 proc
drwxr-xr-x 2 root root 0 Jan 3 18:46 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 30 2013 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 3 18:46 sd-ext
drwxrwxrwx 2 root root 8192 Jan 1 00:00 sdcard
dr-xr-xr-x 15 root root 0 Jan 3 18:46 sys
drwxr-xr-x 16 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 0 Jan 3 18:46 tmp
-rw-r--r-- 1 root root 272 Jan 1 00:00 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5897 Jan 1 00:00 ueventd.rc
~ #
It can be seen that the sdcard is 0% used:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 924.0M 48.0K 924.0M 0% /dev
/dev/block/platform/msm_sdcc.1/by-name/cache
492.6M 8.7M 483.9M 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/userdata
2.5G 424.5M 2.0G 17% /data
/dev/block/platform/msm_sdcc.1/by-name/grow
9.8G 8.0K 9.8G 0% /sdcard
/dev/block/platform/msm_sdcc.1/by-name/system
1.2G 485.0M 726.5M 40% /system
/dev/block/platform/msm_sdcc.1/by-name/persist
4.9M 4.1M 812.0K 84% /persist
~ #
The sdcard:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 32 mmcblk0p4
179 5 512 mmcblk0p5
179 6 500 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 500 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1536 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 1258290 mmcblk0p14
179 15 2621440 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 512000 mmcblk0p17
179 18 153600 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 1 mmcblk0p21
179 22 8 mmcblk0p22
179 23 10276838 mmcblk0p23
179 32 4096 mmcblk0rpmb
~ #
Is 179 23 10276838 mmcblk0p23, but I forget how I linked the sdcard to mmcblk0p23
Using:
adb push -p /home/makem/Downloads/update2.zip /dev/block/mmcblk0p23/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /data/media/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /sdcard/
Each fail by stopping anywhere between 5% and 47%. I have wiped the cache, data and delvik cache prior to pushing.
When I check the sdcard again with df I find it is still at 0%, except for the last push which stopped at 10% and showed 1% used sdcard.
EDIT: After the last push the file update2.zip showed in the sdcard when I went to install it. However, it stopped with a 'bad' error. Obviously an incomplete upload but why????
Tearing my hair out here lol.
TLDR: My phone keeps booting into recovery. I have full root and adb access. How do I tell it to boot elsewhere?
So, I had this phone in deep freeze for a while. It already had an old version of CM on it. I flashed a newer version and all was good for a while. Then at some point I had so many issues with it I decided to go back to stock.
I used these files to flash stock. After several connection issues I managed to get it working.
LGUP_8974_DLL_Ver_0_5_CODEFIRE.MSI
LGUP_LG_G3/LGUP_Install_Ver_1_14_3.msi
Europe D85530B_00_1217.kdz
Fast forward a few weeks, and I'm sick of stock and want to go back. So I rooted it. I don't remember the exact method, cos all I was interested in was bumped TWRP, which I got, then I upgraded to the latest version. At that point, I wiped system, data and all caches then installed LineageOS(lineage-14.1-20170124-nightly-d855-signed.zip). It reported various errors to do with partitions, but installed successfully anyway. I rebooted, and got the secure boot error.
So I went looking for a bumped bootloader, and found this thread with a boot partition, that claims to be bumped, so I flashed that. Didn't work either, and now the phone keeps booting into TWRP.
So I tried to go back to stock once more, with the previous method. It took far less time, and since then the phone has been booting into TWRP no matter what I do. So my question is how does the phone decide where to boot, and how do I change that? I have full adb access through TWRP with root.
To my knowledge, it defaults to boot the Recovery if the System partition is not bootable.
To clarify, does it continue to boot only to Recovery even after the 2nd time you kdz flashed it? You also said the 2nd kdz flash went faster? How much faster? Did you get any errors?
The second kdz flash took less than five minutes. The first one, that worked took enough time for two cups of coffee, a sandwich and then some. The first time, things like RECOVERY, SYSTEM, etc. appeared on the progress bar. I'm assuming that was it flashing those partitions.
The second time, none of that happened, it went straight from connecting, then some weird code, then straight to waiting for 120s, at which point the phone rebooted. I tried and had the same result on two different PCs.
And what exactly does 'bootable' entail? LineageOS installed successfully, I can mount the partition and on a cursory glance everything looks okay.
Additionally, I just took a dump of all the partitions on it. Some of the files have size zero, and I'm a bit worried. The folder listing looks like this:
Code:
total 15G
drwxr-xr-x 2 user user 4.0K Jan 29 17:13 .
drwxr-xr-x 3 user user 4.0K Jan 29 16:16 ..
-rw-r--r-- 1 user user 2.1M Jan 29 16:24 aboot
-rw-r--r-- 1 user user 2.0M Jan 29 17:02 abootf
-rw-r--r-- 1 user user 17M Jan 29 17:02 boot
-rw-r--r-- 1 user user 609M Jan 29 17:13 cache
-rw-r--r-- 1 user user 180M Jan 29 17:14 cust
-rw-r--r-- 1 user user 513K Jan 29 16:23 dbi
-rw-r--r-- 1 user user 513K Jan 29 16:24 dbibak
-rw-r--r-- 1 user user 512K Jan 29 16:23 DDR
-rw-r--r-- 1 user user 8.1M Jan 29 17:02 drm
-rwxr-xr-x 1 user user 2.9K Jan 29 16:22 dump-parts.sh
-rw-r--r-- 1 user user 512K Jan 29 17:02 eksst
-rw-r--r-- 1 user user 512K Jan 29 17:14 encrypt
-rw-r--r-- 1 user user 0 Jan 29 16:23 factory
-rw-r--r-- 1 user user 33M Jan 29 16:23 fota
-rw-r--r-- 1 user user 512K Jan 29 16:24 fsc
-rw-r--r-- 1 user user 3.0M Jan 29 17:02 fsg
-rw-r--r-- 1 user user 20M Jan 29 17:02 grow
-rw-r--r-- 1 user user 33M Jan 29 17:14 laf
-rw-r--r-- 1 user user 0 Jan 29 16:23 misc
-rw-r--r-- 1 user user 65M Jan 29 16:23 modem
-rw-r--r-- 1 user user 3.1M Jan 29 16:24 modemst1
-rw-r--r-- 1 user user 3.1M Jan 29 17:02 modemst2
-rw-r--r-- 1 user user 33M Jan 29 17:02 mpt
-rw-r--r-- 1 user user 4.0K Jan 29 17:14 pad
-rw-r--r-- 1 user user 0 Jan 29 16:23 pad1
-rw-r--r-- 1 user user 4.0K Jan 29 16:23 pad2
-rw-r--r-- 1 user user 33M Jan 29 16:24 persist
-rw-r--r-- 1 user user 8.0K Jan 29 17:02 rct
-rw-r--r-- 1 user user 17M Jan 29 17:03 recovery
-rw-r--r-- 1 user user 1.1M Jan 29 17:14 rpm
-rw-r--r-- 1 user user 0 Jan 29 16:23 rpmbak
-rw-r--r-- 1 user user 1.0M Jan 29 16:23 rpmf
-rw-r--r-- 1 user user 1.1M Jan 29 16:24 sbl1
-rw-r--r-- 1 user user 1.1M Jan 29 17:02 sbl1b
-rw-r--r-- 1 user user 512K Jan 29 17:03 sdif
-rw-r--r-- 1 user user 8.1M Jan 29 17:14 sns
-rw-r--r-- 1 user user 0 Jan 29 16:23 spare1
-rw-r--r-- 1 user user 5.0M Jan 29 16:24 spare2
-rw-r--r-- 1 user user 16M Jan 29 16:24 spare3
-rw-r--r-- 1 user user 512K Jan 29 17:02 ssd
-rw-r--r-- 1 user user 2.1G Jan 29 17:12 system
-rw-r--r-- 1 user user 1.1M Jan 29 17:14 tz
-rw-r--r-- 1 user user 0 Jan 29 16:23 tzbak
-rw-r--r-- 1 user user 1.0M Jan 29 16:24 tzf
-rw-r--r-- 1 user user 12G Jan 29 17:02 userdata
And the fdisk listing from a shell on the phone is:
Code:
fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 30777344 sectors, 2740M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 44 entries
First usable sector is 34, last usable sector is 30777310
Number Start (sector) End (sector) Size Code Name
1 32768 163839 64.0M 0700 modem
2 163840 165887 1024K 0700 sbl1
3 165888 166911 512K 0700 dbi
4 166912 167935 512K 0700 DDR
5 167936 172031 2048K 0700 aboot
6 172032 174079 1024K 0700 rpm
7 174080 176127 1024K 0700 tz
8 176128 176135 4096 0700 pad
9 176136 178183 1024K 0700 sbl1b
10 178184 179207 512K 0700 dbibak
11 179208 181255 1024K 0700 rpmbak
12 181256 183303 1024K 0700 tzbak
13 183304 185351 1024K 0700 rpmf
14 185352 187399 1024K 0700 tzf
15 187400 188423 512K 0700 sdif
16 188424 192519 2048K 0700 abootf
17 192520 196607 2044K 0700 spare1
18 196608 229375 16.0M 0700 boot
19 229376 294911 32.0M 0700 persist
20 294912 327679 16.0M 0700 recovery
21 327680 333823 3072K 0700 modemst1
22 333824 339967 3072K 0700 modemst2
23 339968 339975 4096 0700 pad1
24 339976 346119 3072K 0700 fsg
25 346120 347143 512K 0700 fsc
26 347144 348167 512K 0700 ssd
27 348168 348175 4096 0700 pad2
28 348176 349199 512K 0700 encrypt
29 349200 350223 512K 0700 eksst
30 350224 350239 8192 0700 rct
31 350240 360447 5104K 0700 spare2
32 360448 393215 16.0M 0700 misc
33 393216 458751 32.0M 0700 laf
34 458752 524287 32.0M 0700 fota
35 524288 557055 16.0M 0700 spare3
36 557056 573439 8192K 0700 drm
37 573440 589823 8192K 0700 sns
38 589824 655359 32.0M 0700 mpt
39 655360 720895 32.0M 0700 factory
40 720896 4947967 2064M 0700 system
41 4947968 6193151 608M 0700 cache
42 6193152 6717439 256M 0700 cust
43 6717440 30736383 11.4G 0700 userdata
44 30736384 30777310 19.9M 0700 grow
Also, if there's anywhere I can get info on android partitioning, please point me to it.
For instance, some ROMS have the ability to reboot into recovery. ADB also does this.
Do they write a file somewhere? Flip a bit or what?
Update: I followed this guide to try and install stock from TWRP. Still didn't work, still booting into TWRP every time I turn on the phone.
Does anyone know what makes the phone boot to which partition?
waspish_ly said:
Update: I followed this guide to try and install stock from TWRP. Still didn't work, still booting into TWRP every time I turn on the phone.
Click to expand...
Click to collapse
Sorry for the delay, but you gotta quote or mention a user with a @ in order for that user to know you responded. I'm horrible at following up without a notification from XDA.
The first thing I would assume from the info you supplied is that it sounds like the second KDZ flash failed or did not complete properly. I'm guessing that is due to corrupt partitions. To my knowledge (anyone correct me if I'm wrong), a KDZ flash just formats existing partitions and copies over the data. However, a TOT flash completely re-partitions the entire phone back to factory. (and, yes, they arn't really partitions in the traditional definition, but I won't get into that today).
If you are able to get your hands on a TOT for your model and the required .dll files, I would try flashing it with a TOT to truly start from scratch.
EDIT: Make sure to backup your EFS to your computer before flashing a TOT! I've seen a few reports of folks losing their EFS data after a TOT, but it shouldn't happen.
@AlwaysLucky
I've taken a backup of all the partitions on the phone, as they are in the bricked state. It was basically cat from partitions by-name.
I have access to fdisk on the phone through twrp, so I can repartition if I have to. Gonna try the tot method next. Does LGUP flash those as well, and do they repartition?
Also, is there any info on the proper partition table for the G3, d855 on MM or Nougat?
waspish_ly said:
Also, is there any info on the proper partition table for the G3, d855 on MM or Nougat?
Click to expand...
Click to collapse
I believe a successful TOT flash will accomplish what you are trying to do.
Here is a guide. Scroll down to the TOT method section. You will find helpful downloads here, but more specifically I think you will find a TOT for your model here.
@AlwaysLucky Thanks. The TOT flash finished successfully and I now have a working phone.
I'd like to know more about the specifics of android partitioning, but I'm kinda sick of that LG, so that'll have to wait.