Hi,
I want to extract logo.bin from /dev folder in the android OS. I have come across posts that say that logo.bin is present in boot.img and can be extracted from it. I used dsixda to unpack boot.img but did not get logo.bin inside the dev folder. the dev folder is empty. I did it for two phone models but both were unsuccessful. Can someone help me on how to get logo.bin?
Regards,
Parag
There are hundreds of developers working with logo.bin file day in day out. Can no one take out a few minutes to share how it is extracted from the device? Plz help
Sent from my iBall Andi4.5q using xda app-developers app
Logo.bin will be in stock firmware.
U can extract it from there
Sent from my Lava Iris458Q using xda app-developers app
ajparag said:
There are hundreds of developers working with logo.bin file day in day out. Can no one take out a few minutes to share how it is extracted from the device? Plz help
Sent from my iBall Andi4.5q using xda app-developers app
Click to expand...
Click to collapse
1. Root device
2.
Code:
adb shell
dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1
3. Copy logo.bin from sdcard to your PC
The blocksize (bs) can be bigger or smaller depends of device size.
lolet said:
1. Root device
2.
Code:
adb shell
dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1
3. Copy logo.bin from sdcard to your PC
The blocksize (bs) can be bigger or smaller depends of device size.
Click to expand...
Click to collapse
@lolet Thanks a ton! I will give it a try and share my experience soon.
How to edit logo.bin
BUT How to edit logo.bin ?
how can i convert logo.bin 2 in example BMP
or any other way to edit it
i use LogoBuilder_v1.4 and Image_Search_Editor_Eng
but android breaked down :
lolet said:
1. Root device
2.
Code:
adb shell
dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1
3. Copy logo.bin from sdcard to your PC
The blocksize (bs) can be bigger or smaller depends of device size.
Click to expand...
Click to collapse
Sir i have a rooted mt6589 device(FLY ALPS F45Q) and successfully changed second boot image and bootanimation. but the real headache is logo.bin file. I can't find it on phone.
I have backed up my stock rom via SP FLASH TOOLS and now
I have:- files.md5, boot.img, nandroid.md5, recovery.img and system.ext4.tar.
Can I extract logo.bin file from any of the above files....
Plzz help.
[email protected] said:
Sir i have a rooted mt6589 device(FLY ALPS F45Q) and successfully changed second boot image and bootanimation. but the real headache is logo.bin file. I can't find it on phone.
I have backed up my stock rom via SP FLASH TOOLS and now
I have:- files.md5, boot.img, nandroid.md5, recovery.img and system.ext4.tar.
Can I extract logo.bin file from any of the above files....
Plzz help.
Click to expand...
Click to collapse
Do everything as I wrote and you'll get logo.bin
ned000111 said:
BUT How to edit logo.bin ?
how can i convert logo.bin 2 in example BMP
or any other way to edit it
i use LogoBuilder_v1.4 and Image_Search_Editor_Eng
but android breaked down :
Click to expand...
Click to collapse
Use tools from https://github.com/bgcngm/mtk-tools
lolet said:
1. Root device
2.
Code:
adb shell
dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1
3. Copy logo.bin from sdcard to your PC
The blocksize (bs) can be bigger or smaller depends of device size.
Click to expand...
Click to collapse
I have an unlocked and rooted Moto X running Kit Kat 4.4 and want to pull the logo.bin file but these commands return an error that no such file or directory exist.
Any ideas?
NightThyme said:
I have an unlocked and rooted Moto X running Kit Kat 4.4 and want to pull the logo.bin file but these commands return an error that no such file or directory exist.
Any ideas?
Click to expand...
Click to collapse
This is instruction for MTK, but your Moto X has a Qualcomm CPU. Anyway for QC device procedure is more complicated, IIRC you need to edit some partition on /dev/block
lolet said:
1. Root device
2.
Code:
adb shell
dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1
3. Copy logo.bin from sdcard to your PC
The blocksize (bs) can be bigger or smaller depends of device size.
Click to expand...
Click to collapse
where to input this code?
lolet said:
1. Root device
2.
Code:
adb shell
dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1
3. Copy logo.bin from sdcard to your PC
The blocksize (bs) can be bigger or smaller depends of device size.
Click to expand...
Click to collapse
How to know bs of my phone's logo.bin xolo q700s
You can get it from /proc/dumchar_info. e.g
Code:
[email protected]:/ # cat /proc/dumchar_info
cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
logo [B]0x0000000000300000 [/B] 0x0000000003400000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000003700000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x0000000004180000 2 /dev/block/mmcblk0p5
cache 0x0000000007e00000 0x000000002cb80000 2 /dev/block/mmcblk0p6
usrdata 0x0000000060000000 0x0000000034980000 2 /dev/block/mmcblk0p7
fat 0x0000000052da0000 0x0000000094980000 2 /dev/block/mmcblk0p8
bmtpool 0x0000000000000000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Then convert the value from size column to decimal.
/dev/logo: cannot open for read: Permission denied
What should I do?
it say no such file
lolet said:
This is instruction for MTK, but your Moto X has a Qualcomm CPU. Anyway for QC device procedure is more complicated, IIRC you need to edit some partition on /dev/block
Click to expand...
Click to collapse
Hello.... how complicated is it on a Y560 huawei with android 5.1.1 ???
Maybe this will solve all problem
I SAW SOME POST IN WHICH PEOPLE ARE ASKING WHERE TO PUT ADB SHELL COMMAND, PEOPLE CAN'T UNDERSTAND THE DIFFERENCE BETWEEN STOCK FIRMWARE & A SP FLASH TOOL BACKUP:crying:
TO THOSE PEOPLE I WILL SAY - " PLEASE STAY AWAY FROM YOUR INNOCENT PHONE,PLEASE". I AGREE I WAS A NOOB BUT I DIDN'T EVER ASKED THESE TYPE OF FOOLISH SUPER DUMB QUESTION.THIS IS A FORUM , DO READ FORUM RULE & DO A DEEP SEARCH BEFORE POSTING NONSENSE POSTS.
SOMEBODY REPORTED AN ERROR WHILE PULLING LOGO.BIN THROUGH ADB,ERROR WAS "PERMISSION DENIED" THIS MEANS YOUR BOOTLOADER IS NOT UNLOCKED.YOU NEED TO UNLOCK YOUR BOOTLOADER FIRST IN ORDER TO USE ADB & FASTBOOT WITH ROOT LEVEL COMMANDS.
FINALLY WHERE IS LOGO.BIN ?
EVERY PHONE HAS IT'S OWN PARTITION NO.(mmcblk0xxx) IT DEPENDS ON YOUR PHONE.YOU HAVE TO GET IT UNLESS SOMEONE TELL YOU WHAT IS YOUR LOGO PARTITION SERIAL NO FOR THAT PARTICULAR DEVICE.
TO KNOW THE PARTITION NAME & NO OF YOUR DEVICE ,A QUICK COMPREHENSIVE GUIDE IS HERE
DETAILED INFO
HIT THANKS IF THIS HELPED YOU
GEEKOFIA said:
I SAW SOME POST IN WHICH PEOPLE ARE ASKING WHERE TO PUT ADB SHELL COMMAND, PEOPLE CAN'T UNDERSTAND THE DIFFERENCE BETWEEN STOCK FIRMWARE & A SP FLASH TOOL BACKUP:crying:
TO THOSE PEOPLE I WILL SAY - " PLEASE STAY AWAY FROM YOUR INNOCENT PHONE,PLEASE". I AGREE I WAS A NOOB BUT I DIDN'T EVER ASKED THESE TYPE OF FOOLISH SUPER DUMB QUESTION.THIS IS A FORUM , DO READ FORUM RULE & DO A DEEP SEARCH BEFORE POSTING NONSENSE POSTS.
SOMEBODY REPORTED AN ERROR WHILE PULLING LOGO.BIN THROUGH ADB,ERROR WAS "PERMISSION DENIED" THIS MEANS YOUR BOOTLOADER IS NOT UNLOCKED.YOU NEED TO UNLOCK YOUR BOOTLOADER FIRST IN ORDER TO USE ADB & FASTBOOT WITH ROOT LEVEL COMMANDS.
Click to expand...
Click to collapse
Is your CAPS LOCK key broken?
Because we can read very well without capital letters.
Or are you shouting? If yes, maybe you need some anger management classes...
masster64 said:
Is your CAPS LOCK key broken?
Because we can read very well without capital letters.
Or are you shouting? If yes, maybe you need some anger management classes...
Click to expand...
Click to collapse
I don't waste energy by shouting to kids.:laugh:
By the way i am feeling very very sorry for those poor people
By the way what's point to quote my post ? are you asking a valuable question or just trying to increase your post count ?
Related
Hello guys,
I'm looking into the Xperia P and I would like to make a backup of the recovery partition.
For now I know that this is the partition in /dev/block/mmcblk0, but I'm not able to create a backup of it with cat or dd. The created file just grows up to 4GB and then the process dies.
The tool /sbin/fota-ua says some interesting things like
Code:
Info [153] EMMC using: /dev/block/mmcblk0 (size 15267840 kB)
Info [135] partition id: 0
Info [136] partition name: FOTAKernel
Info [137] partition start: 86016
Info [138] partition length: 32768
I'm pretty sure the partition size isn't 15267840 kB but rather only bytes :laugh:
My goal is to have a recovery.img file that I can mount with Ubuntu. Things like
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0 skip=86015 count=32768
returned rubbish. It would be great if anyone could help me, I really want to know what files are in this partition. I don't want to edit them and flash them back on the phone or something.
Thanks in advance
Brandon
Edit: Crap I forgot the [P] in the title, sorry.
Got it, still thanks.
since i can't put a thread in development i put it here what is this command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 /dev/block/mmcblk0p4 no such file or directory i don't even no what or where mmcblk0p4 is at help
mininessie said:
since i can't put a thread in development i put it here what is this command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 /dev/block/mmcblk0p4 no such file or directory i don't even no what or where mmcblk0p4 is at help
Click to expand...
Click to collapse
Are you successfully temp-rooted (and related, are you on the latest OTA? 2.17.605.2)
This procedure is really dangerous so I have to warn that you can brick your phone. It directly modifies partition tables so if something goes wrong you may have a bricked phone. Do it at your own risk and I'm not responsible for any damage it may cause.
By following the procedure, you acknowledge and accept that the author is not liable for any loss, material or otherwise howsoever caused.
OK, you've been warned Now to the fun part.
This procedure does work but, please, follow it only if you are an advanced user or a developer.
It also has some unnecessary steps but I include them since they can help you to learn something.
Later, I might write an "update.zip" for cwm which automatically does all the work
This works only on top of the existing N4 8G conversion.
So if you're stock etc then you'll need to do N4 8G conversion first, that is to flash the tot listed in N4 conversion topic in LGNPST.
This is a link to the N4 conversion thread: http://forum.xda-developers.com/showthread.php?t=2099784
You also need cwm recovery installed. I did it in sk8's cwm touch recovery. So I suggest using it: http://forum.xda-developers.com/showthread.php?t=2010984
Also, you need an external sd card with at least 100MB(after doing all rom backups) of free space and I recommend to do a filesystem check of the sd card in windows/*nix/osx.
And another requirement is to have working adb and fastboot drivers for Nexus 4.
Before starting the procedure look through all the steps and please stop if you don't understand something. No rocket science here but it's just a dangerous thing to do.
- Download the following 3 files and copy them to your _external_ sd card root directory
Links:
Modified busybox dd : http://d-h.st/cFA
16G Primary GPT(includes MBR): http://d-h.st/yUQ
16G Secondary GPT: http://d-h.st/0dH
- if you care about the content of your internal sd card then back it up somewhere. After doing this conversion all your data and /sdcard will be purged.
- boot into cwm recovery.
- if you care about your current ROM/data do a backup to _external_ sd.
- connect the phone via USB to your pc and on your pc run 'adb shell'. Once in shell:
Code:
# cp /external_sd/dd /
# chmod 755 /dd
- Backup your existing partition tables. Make sure you put / in front of dd to use my modified dd
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/pgpt8G.img bs=512 count=34
# /dd if=/dev/block/mmcblk0 of=/external_sd/sgpt8G.img bs=512 skip=30777311
- By default cwm mounts userdata and cache partitions. You need to unmount them
Code:
# umount /data
# umount /cache
- Make sure no partition from /dev/block/mmcblk0 is mounted. df should return only this with no extra rows:
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 911.7M 48.0K 911.6M 0% /dev
/dev/block/mmcblk1p1 59.4G 4.8G 54.6G 8% /external_sd
- Move content of DDR and grow partitions to their new locations. I doubt this step is required, but did it for safety. Seeking to the end of the mmc may take couple of minutes, don't freak out:
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/DDR bs=512 skip=15267840 count=2015
# /dd if=/external_sd/DDR of=/dev/block/mmcblk0 bs=512 seek=30775296 conv=notrunc
- Install new partition tables. Seeking to the end of the mmc may take couple of minutes:
Code:
# /dd if=/external_sd/sgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
- At this point you have new partition tables installed. Verify this by running parted. You should see this:
Code:
# parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1040MB 881MB ext4 system
22 1040MB 1627MB 587MB ext4 cache
23 1627MB 15.8GB 14.1GB ext4 userdata
24 15.8GB 15.8GB 524kB DDR
25 15.8GB 15.8GB 507kB grow
(parted) quit
quit
Notice that userdata partition is 14.1GB in size
In case parted reports an error I suggest to return back to the old 8G partition tables, see below.
- Reboot the phone into bootloader: run reboot command and hold 'Up' button to enter bootloader menu
Code:
# reboot
- on your pc command line run:
Code:
fastboot erase userdata
fastboot -w
- In phone bootloader enter 'Recovery Mode' to load cwm
- In cwm restore your previous N4 rom from external sd or flash a new N4 rom
PS
In case parted reported an error, put the old 8G partition tables back. This should not happen but never say never:
Code:
# /dd if=/external_sd/sgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
reserved
Awww Look at the "community" sharing!!!
really easy process thank you!
This is the final straw for me, I'm gonna try the conversion tonight. Thanks a ton!
Damn, so was this the final problem with the conversion? Does this mean all the bugs have been worked out? If so, this is awfully tempting... haha
blenkows said:
Damn, so was this the final problem with the conversion? Does this mean all the bugs have been worked out? If so, this is awfully tempting... haha
Click to expand...
Click to collapse
For the most part, I think a few people still have issues with NFC, but I think that's just about ironed out too. Goodbye Quickmemo and Q-slide, I'll actually miss you!
Awesome work but I'll wait tell you make a update zip since I don't trust my computer have USB problems
Sent from my LG-E970 using xda premium
Right now I have the little voices in my head. The good guy is saying "NO DUDE! WAIT FOR AOSP! ITS JUST AROUND THE CORNER!". The other dude is saying "OMG JUST DO IT YOU WUSS!"
Mannnnnnn. Now I'm confused as to what I wanna do. Stock JB or convert? Great job. Looks good!
Sent from my LG Optimus G
Neroga said:
Mannnnnnn. Now I'm confused as to what I wanna do. Stock JB or convert? Great job. Looks good!
Sent from my LG Optimus G
Click to expand...
Click to collapse
More like Nexus 4 with SD card and LTE 4.2.2 or LGOG with 4.1.2?
xxgmon3yxx said:
More like Nexus 4 with SD card and LTE 4.2.2 or LGOG with 4.1.2?
Click to expand...
Click to collapse
You know, plus the millions of other possibilities that come along with a nexus.
C2fifield said:
You know, plus the millions of other possibilities that come along with a nexus.
Click to expand...
Click to collapse
No doubt... this phone will be supported for years to come! I'm never getting rid of it.
C2fifield said:
For the most part, I think a few people still have issues with NFC, but I think that's just about ironed out too. Goodbye Quickmemo and Q-slide, I'll actually miss you!
Click to expand...
Click to collapse
If NFC does not work for you, try to flash zip from the 'Notes' section of http://forum.xda-developers.com/showthread.php?p=37518694
Now can people accept the conversion lol so we can move on with our phones?
Sent from my LG-E970 using xda premium
blenkows said:
Right now I have the little voices in my head. The good guy is saying "NO DUDE! WAIT FOR AOSP! ITS JUST AROUND THE CORNER!". The other dude is saying "OMG JUST DO IT YOU WUSS!"
Click to expand...
Click to collapse
Haha, I feel you! I don't even trust myself with the conversion, though :/
But if a flash zip comes out, all hell might break loose!
Sent from my LG-E970 using xda app-developers app
TangoXray said:
Haha, I feel you! I don't even trust myself with the conversion, though :/
But if a flash zip comes out, all hell might break loose!
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Just did it, it's all running smoothly, thanks again!
Seems to have worked here as well. Just restored my nandroid and its booting as we speak. And....... success. 12+ gigs of usable storage. Thanks a ton!!!!
thanks i just did it and works perfect
As I restore my backup, I have to wonder, why do we erase userdata and fastboot -w when a restore from backup works without a problem? Does the backup not look at the partition tables where booting straight up would and freeze up something?
Or is everything wiped from modifying the table and the fastboot part is just to make sure the partitions are empty?
I'm porting myllo.setya (and BigMajster)'s script.
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
Requirement:
G2 Mini D620
Recovery (not the original)
30MB on external SD card
A rom zip or a nandroid
Install:
Boot in recovery
Install the script
Install a rom or restore stock
Mode:
Maximal- system partition have only 730mb so you can install only custom rom like CynogenMod
Optimal- system partition have 1,5gb so you can also install stock LG rom, but you still have more data.
Stock- this is orginal partition table
Download here
|
v
GOOD LUCK :silly:
I used modific SH for D620r and it delete: system, cache, data, internal and RECOVERY (TWRP) , restored system not working for me. -> bootloop (Now Im with not working system and no recovery , Its NOT becouse sh is bad (its working), but its because I didnt flash recovery, and system not working - no idea why ) Yeah its my problem ( I dont take care , Its my stupidity) but I want to tell u how to do it better than me
Hmmm some realy function way how to flash kdz ?? or something to get my phone woking ??
Thanks a lot.
For others who want to use it on D620r do it this :
1) check u have some ROM and TWRP ( recovery) on yours SD card (backup not working for me, I used optimal settings)
2) go to recovery ,flash PTT
3) phone will be reboot and go to recovery (last chance !!) (DO NOT remove batteri !)
4) flash clear ROM (+ gapps) and RECOVERY (TWRP) !!
5) reboot and it will be working (I thing )
WoytazZer CZ said:
I used modific SH for D620r and it delete: system, cache, data, internal and RECOVERY (TWRP) , restored system not working for me. -> bootloop (Now Im with not working system and no recovery , Its NOT becouse sh is bad (its working), but its because I didnt flash recovery, and system not working - no idea why ) Yeah its my problem ( I dont take care , Its my stupidity) but I want to tell u how to do it better than me
Hmmm some realy function way how to flash kdz ?? or something to get my phone woking ??
Thanks a lot.
For others who want to use it on D620r do it this :
1) check u have some ROM and TWRP ( recovery) on yours SD card (backup not working for me, I used optimal settings)
2) go to recovery ,flash PTT
3) phone will be reboot and go to recovery (last chance !!) (DO NOT remove batteri !)
4) flash clear ROM (+ gapps) and RECOVERY (TWRP) !!
5) reboot and it will be working (I thing )
Click to expand...
Click to collapse
Do you have fastboot init message on top along with the LG logo ? If yes, connect to usb and try:
Code:
fastboot devices
If it shows your device, you are fine. Now download TWRP recovery from http://forum.xda-developers.com/g2-mini/development/recovery-twrp-2-8-3-0-recovery-lg-d620-t2990196 and boot it via fastboot:
Code:
fastboot boot <recovery image file>
This will boot into recovery with MTP support ( you will see you device on pc ), then upload ROM to SDcard and install it right away from recovery. Don't forget to install recovery later ( I hope you have unlocked bootloader )
I've just gone through similar issue, I have flashed partition table for D618 a got stuck on fastboot ... this thread ( and zip ) saved me !
"Zdravim taky z jednoho mista blizko Prahy"
kkoouu said:
Do you have fastboot init message on top along with the LG logo ? If yes, connect to usb and try:
Code:
fastboot devices
If it shows your device, you are fine. Now download TWRP recovery from http://forum.xda-developers.com/g2-mini/development/recovery-twrp-2-8-3-0-recovery-lg-d620-t2990196 and boot it via fastboot:
Code:
fastboot boot <recovery image file>
This will boot into recovery with MTP support ( you will see you device on pc ), then upload ROM to SDcard and install it right away from recovery. Don't forget to install recovery later ( I hope you have unlocked bootloader )
I've just gone through similar issue, I have flashed partition table for D618 a got stuck on fastboot ... this thread ( and zip ) saved me !
"Zdravim taky z jednoho mista blizko Prahy"
Click to expand...
Click to collapse
Thanks , but I can not go to fastboot mode (I don t know how , yeah its bad , but I used it only once, I google for it but nothing ) +vol + power and connect usb or how I can go to fastboot mode ? (I dont have fastboot init message on top along with the LG logo) I see extended kernel adn after that cpa bootanimation - > goes to bootloop. dowload mode works.
But I want ot try flash TWRP like u wrote here.
http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6
Try to get adb access in different modes ( even during system boot you can already have adb access ), try it with "adb shell" from pc and then try to zero the LAF as suggested in the post above, after reboot you should have a fastboot access
re
kkoouu said:
http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6
Try to get adb access in different modes ( even during system boot you can already have adb access ), try it with "adb shell" from pc and then try to zero the LAF as suggested in the post above, after reboot you should have a fastboot access
Click to expand...
Click to collapse
hmm, what keys do u use for fastboot ??
after this http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6 can I go to dowload mode ? or not? (its look its last think whats working and I want to take it works), and next questin , where do i write this ?
"( Broken dtb.img in kernel / recovery or by zero-ing out laf partition (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf)"
By doing so, the phone can't enter Download mode.
hmmm probablyin adb shell on pc , is it true ?? or Im stil on bad way ?
WoytazZer CZ said:
hmm, what keys do u use for fastboot ??
after this http://forum.xda-developers.com/showpost.php?p=57895748&postcount=6 can I go to dowload mode ? or not? (its look its last think whats working and I want to take it works), and next questin , where do i write this ?
"( Broken dtb.img in kernel / recovery or by zero-ing out laf partition (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf)"
By doing so, the phone can't enter Download mode.
hmmm probablyin adb shell on pc , is it true ?? or Im stil on bad way ?
Click to expand...
Click to collapse
You cannot enter fastboot via keys.
If you can enter adb shell ( yes on pc ), enter:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
After reboot you should be in fastboot mode and continue as written in my first post.
kkoouu said:
You cannot enter fastboot via keys.
If you can enter adb shell ( yes on pc ), enter:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
After reboot you should be in fastboot mode and continue as written in my first post.
Click to expand...
Click to collapse
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Its not name of internal or external order
Im in C./adb>
I wrote : adb shell
its show: started successfully
error: device offline
WoytazZer CZ said:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Its not name of internal or external order
Im in C./adb>
I wrote : adb shell
its show: started successfully
error: device offline
Click to expand...
Click to collapse
Sorry but these are basics ... try to google it - f.e. http://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands
kkoouu said:
Sorry but these are basics ... try to google it - f.e. http://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands
Click to expand...
Click to collapse
but with other phone Sony Ericsson live with walkman its work show me its code.
i dont know what im doing wrong , I will try it again after pc finish reboot.
WoytazZer CZ said:
I used modific SH for D620r and it delete: system, cache, data, internal and RECOVERY (TWRP) , restored system not working for me. -> bootloop (Now Im with not working system and no recovery , Its NOT becouse sh is bad (its working), but its because I didnt flash recovery, and system not working - no idea why ) Yeah its my problem ( I dont take care , Its my stupidity) but I want to tell u how to do it better than me
Hmmm some realy function way how to flash kdz ?? or something to get my phone woking ??
Thanks a lot.
For others who want to use it on D620r do it this :
1) check u have some ROM and TWRP ( recovery) on yours SD card (backup not working for me, I used optimal settings)
2) go to recovery ,flash PTT
3) phone will be reboot and go to recovery (last chance !!) (DO NOT remove batteri !)
4) flash clear ROM (+ gapps) and RECOVERY (TWRP) !!
5) reboot and it will be working (I thing )
Click to expand...
Click to collapse
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
sergioslk said:
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
Click to expand...
Click to collapse
yeah I m planing do that , but now im trying flash recovery via adb
http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664#post61015063
but i dont have luck to conect phone to pc
---------- Post added at 03:44 PM ---------- Previous post was at 03:27 PM ----------
sergioslk said:
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
Click to expand...
Click to collapse
yeah , Im trying cs_emergency and cse flash
and Im stil stop on 4% and said reconect phone - again again .....
sergioslk said:
If you can go to download mode try to flash kdz with "CS Emergency" this will repartition your phone to original
Click to expand...
Click to collapse
hmm no lucky with kdz ,I can not MTP drivers get working , is it theproblem ??
WoytazZer CZ said:
hmm no lucky with kdz ,I can not MTP drivers get working , is it theproblem ??
Click to expand...
Click to collapse
http://forum.xda-developers.com/g2-mini/general/complete-guide-vademecum-lg-g2-mini-t2900073
i used this guide to unbrick.
I downloaded lg flash tool then entered my IMEI on the lg website to download stock rom.
connect my phone with usb on pc while on download mode and then do cse flash with the flash tool.
it opens stock lg softaware updater and then it goes smoothly after showing "cant access the lg server"or smthing.
IIRC i used cdma and diag.
did u already fixed this?, maybe i can help u, because i've tried this and i lost all data on internal storage, even download mode, and it says no OS installed
PTT_D620 I do not advise to use is not built for LG G2 mini. It contains errors.
Manual is easy using parted:
Backup complet /system, /data, /cache. Backup type file *.tar in recovery mode.
in pc adb shell in recovery mode
# 1,5GiB /system 1610613247B
# 100MiB /cache 104858111B
# 5,22Gib /userdata 5601378303B
parted -s /dev/block/mmcblk0 rm 32
parted -s /dev/block/mmcblk0 rm 33
parted -s /dev/block/mmcblk0 rm 34
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
Click to expand...
Click to collapse
Restore /system, /data, /cache
I was trying to do this but couldn't, i get stuck on fastboot mode and my pc doesn't recognize it. I tried the partition tool from D618, same! So for the last post i can't exactly understand what to do from adb shell! Just do my backups and then start giving the commands:
Code:
parted -s /dev/block/mmcblk0 rm 32
parted -s /dev/block/mmcblk0 rm 33
parted -s /dev/block/mmcblk0 rm 34
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted -s /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
or there is something more to do??
????
Run phone recovery mode
Plug usb cable pc and phone
run cmd.exe -> adb shell
*show partitions
parted /dev/block/mmcblk0 p
*delete partitions 32 - system, 33 - cache, 34 - data
parted /dev/block/mmcblk0 rm 32
parted /dev/block/mmcblk0 rm 33
parted /dev/block/mmcblk0 rm 34
* create new resize partitions
parted /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
* format partitions
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
thank you :good: and one more!
this part:
Code:
parted /dev/block/mmcblk0 unit b mkpart primary ext4 478150656 2088763903 name 32 system
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2088763904 2193622015 name 33 cache
parted /dev/block/mmcblk0 unit b mkpart primary ext4 2193622016 7795000319 name 34 userdata
The sizes are on Byte (?) , because i want minimal partition.. (730MB System, 100MB cache, 6GB userdata) so i can change them...
Yes, unit byte. More info parted unit and parted syntax
Beware MB not MiB!
/ cache 100MiB = 104858111B = 104MB
Uploaded the recovery from the system dump posted here to TWRP builder and Yshalsager built this recovery for it, need testers for it View attachment TWRP-3.2.1-ali-20180612.img.zip
I'll gladly test it. I've been testing a version of my own but had issues with mounting the external sdcard.
EDIT - Quick test and it shows internal storage separate from external (mine showed the same internal for both) however it does not mount the external sd card.
Added a couple of logs. Sorry, it's been a while since I have had a devices I could unlock/etc... Please let me know if you want more.
likemiketoo said:
Uploaded the recovery from the system dump posted here to TWRP builder and Yshalsager built this recovery for it, need testers for it View attachment 4526176
Click to expand...
Click to collapse
TWRP has been using a boot Twrp.img and an TWRP Installer which installs TWRP to the system, if you dont use installer, you must Fastboot TWRP every time...
---------- Post added at 04:43 PM ---------- Previous post was at 04:04 PM ----------
likemiketoo said:
Uploaded the recovery from the system dump posted here to TWRP builder and Yshalsager built this recovery for it, need testers for it View attachment 4526176
Click to expand...
Click to collapse
do you just do a fastboot flash recovery with this or what? instructions are a little vague
Dadud said:
do you just do a fastboot flash recovery with this or what? instructions are a little vague
Click to expand...
Click to collapse
If it were me, I'd use the following:
Code:
fastboot boot twrp.img
That way you can test it without breaking your stock recovery. If it does end up working you can use it to backup your stock boot.img and recovery.img.
kwiksi1ver said:
If it were me, I'd use the following:
Code:
fastboot boot twrp.img
That way you can test it without breaking your stock recovery. If it does end up working you can use it to backup your stock boot.img and recovery.img.
Click to expand...
Click to collapse
i tried flashing it but it gave me an error saying it wasnt signed correctly, ill get back on with that command and grab the stock boot.img and recovery.img (if it works) and throw them up on google drive for anyone who might need them.
Update: not letting me backup, i have secure boot enabled, though and its not asking me for decryption password when i boot twrp like my nexus 6p did.
Dadud said:
Update: not letting me backup, i have secure boot enabled, though and its not asking me for decryption password when i boot twrp like my nexus 6p did.
Click to expand...
Click to collapse
When you've booted into TWRP does ADB work when you're connected to your PC?
kwiksi1ver said:
When you've booted into TWRP does ADB work when you're connected to your PC?
Click to expand...
Click to collapse
yeah, i can run adb shell no problem
Dadud said:
yeah, i can run adb shell no problem
Click to expand...
Click to collapse
from adb shell run
Code:
cd /dev/block/platform/soc/
ls
the ls command will list a partition or two try to cd to them and look for a structure like this:
/dev/block/platform/soc/c0c4000.sdhci/by-name/
the c0c4000.shci will not match, it will be specific to your device model, but once you find that folder you can try to copy the boot and recovery partitions using commands like this:
Code:
dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/boot of=/external_sd/boot.img
dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/recovery of=/external_sd/recovery.img
or if you don't have an external SD card try this
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
Again the folder name after the /soc/ in the path will be different for your device so replace that and you can save your stock boot and recovery images. From there we can use those to build a proper TWRP and get root by disabling dm-verity on the boot.img.
kwiksi1ver said:
from adb shell run
Code:
cd /dev/block/platform/soc/
ls
the ls command will list a partition or two try to cd to them and look for a structure like this:
/dev/block/platform/soc/c0c4000.sdhci/by-name/
the c0c4000.shci will not match, it will be specific to your device model, but once you find that folder you can try to copy the boot and recovery partitions using commands like this:
Code:
dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/boot of=/external_sd/boot.img
dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/recovery of=/external_sd/recovery.img
or if you don't have an external SD card try this
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
Again the folder name after the /soc/ in the path will be different for your device so replace that and you can save your stock boot and recovery images. From there we can use those to build a proper TWRP and get root by disabling dm-verity on the boot.img.
Click to expand...
Click to collapse
not seeing a c0c4000.shci or similarly named folder, just a lot of mmcblk folders, a by-name and a by-num folder. i see something called boot and recovery in by-name but when i try to adb pull it returns adb: not found
Dadud said:
not seeing a c0c4000.shci or similarly named folder, just a lot of mmcblk folders, a by-name and a by-num folder. i see something called boot and recovery in by-name but when i try to adb pull it returns adb: not found
Click to expand...
Click to collapse
Sorry, I should have been more clear, you can't be in adb shell when you run the adb pull command.
So you'd find the full path of the "by-name" folder and you'd copy the whole path name. Then exit out of adb shell by typing "exit" and you should be back to the command prompt/terminal on your computer.
Then you run the command: (but replace the path of your boot and recovery files with the file structure on your device)
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
Dadud said:
not seeing a c0c4000.shci or similarly named folder, just a lot of mmcblk folders, a by-name and a by-num folder. i see something called boot and recovery in by-name but when i try to adb pull it returns adb: not found
Click to expand...
Click to collapse
Opening command prompt/powershell (windows) or terminal ( linux) and type:
Code:
adb pull /dev/block/platform/soc/by-name/boot boot.img
adb pull /dev/block/platform/soc/by-name/recovery recovery.img
This works fine for me using my twrp and the twrp from the op. This does not work for you?
I have used this to boot into phh-treble and the lineage-phh-treble roms (with the stock kernel) and have gone back to stock (pulled the system.img before this). I have not been successful with Magisk myself.
EDIT- After typing this I just saw kwiksi1ver's reply...
Not that I've needed to but I had more lines in my fstab so I could mount more partitions like vendor (I believe Magisk wanted to mount it?) Included for whatever purposes. external sdcard not working right and I haven't tested out edits since I first tried it.
*** DISCLAIMER *** It's been a long time since I have messed with this stuff so excuse the messy stuff and my lack of knowledge of mounting flags. Also uh..... I'm not responsible for your choices.....
dejello said:
Opening command prompt/powershell (windows) or terminal ( linux) and type:
Code:
adb pull /dev/block/platform/soc/by-name/boot boot.img
adb pull /dev/block/platform/soc/by-name/recovery recovery.img
This works fine for me using my twrp and the twrp from the op. This does not work for you?
I have used this to boot into phh-treble and the lineage-phh-treble roms (with the stock kernel) and have gone back to stock (pulled the system.img before this). I have not been successful with Magisk myself.
EDIT- After typing this I just saw kwiksi1ver's reply...
Not that I've needed to but I had more lines in my fstab so I could mount more partitions like vendor (I believe Magisk wanted to mount it?) Included for whatever purposes. external sdcard not working right and I haven't tested out edits since I first tried it.
*** DISCLAIMER *** It's been a long time since I have messed with this stuff so excuse the messy stuff and my lack of knowledge of mounting flags. Also uh..... I'm not responsible for your choices.....
Click to expand...
Click to collapse
By chance could you also post the stock recovery.img and boot.img as well?
kwiksi1ver said:
By chance could you also post the boot.img as well?
Click to expand...
Click to collapse
I can. It boots but the sdcard is at least shown better on the op link. I took the one posted for the g6 play and swapped a few things with the stock recovery and came up with this. ***Again, I'm not responsible for how you use this and can't say anything is safe (though I have used it plenty). You WILL lose your data any time you want to mess with anything rom related.*** To get it to read the data partition you have to format it (that includes internal storage).
dejello said:
I can. It boots but the sdcard is at least shown better on the op link. I took the one posted for the g6 play and swapped a few things with the stock recovery and came up with this. ***Again, I'm not responsible for how you use this and can't say anything is safe (though I have used it plenty). You WILL lose your data any time you want to mess with anything rom related.*** To get it to read the data partition you have to format it (that includes internal storage).
Click to expand...
Click to collapse
I don't have a G6 myself, I was just trying to kickstart the development on it.
I have a G6 play, I was the one who made the TWRP image for the G6 Play.
dejello said:
Opening command prompt/powershell (windows) or terminal ( linux) and type:
Code:
adb pull /dev/block/platform/soc/by-name/boot boot.img
adb pull /dev/block/platform/soc/by-name/recovery recovery.img
This works fine for me using my twrp and the twrp from the op. This does not work for you?
Click to expand...
Click to collapse
no, it doesnt seem to be working, this is a log my my powershell prompt.
PS C:\Users\dadud\Downloads\TWRP-3.2.1-ali-20180612.img> adb shell
~ # [6n cd /dev/block/platform/soc/
/dev/block/platform/soc # [6nls
by-name mmcblk0p16 mmcblk0p25 mmcblk0p34 mmcblk0p43 mmcblk0p52
by-num mmcblk0p17 mmcblk0p26 mmcblk0p35 mmcblk0p44 mmcblk0p53
mmcblk0 mmcblk0p18 mmcblk0p27 mmcblk0p36 mmcblk0p45 mmcblk0p6
mmcblk0p1 mmcblk0p19 mmcblk0p28 mmcblk0p37 mmcblk0p46 mmcblk0p7
mmcblk0p10 mmcblk0p2 mmcblk0p29 mmcblk0p38 mmcblk0p47 mmcblk0p8
mmcblk0p11 mmcblk0p20 mmcblk0p3 mmcblk0p39 mmcblk0p48 mmcblk0p9
mmcblk0p12 mmcblk0p21 mmcblk0p30 mmcblk0p4 mmcblk0p49 mmcblk0rpmb
mmcblk0p13 mmcblk0p22 mmcblk0p31 mmcblk0p40 mmcblk0p5
mmcblk0p14 mmcblk0p23 mmcblk0p32 mmcblk0p41 mmcblk0p50
mmcblk0p15 mmcblk0p24 mmcblk0p33 mmcblk0p42 mmcblk0p51
/dev/block/platform/soc # [6ncd by-name
/dev/block/platform/soc/by-name # [6nls
DDR cmnlib64 fsg mmi_misc prov syscfg
aboot cmnlib64bak hw modem provbak system
abootbak cmnlibbak keymaster modemst1 recovery tz
apdp devcfg keymasterbak modemst2 rpm tzbak
boot devcfgbak kpan mota rpmbak userdata
cache dpo logo msadp sbl1 utags
carrier dsp logs oem sbl1bak utagsBackup
cid frp metadata padA sp vendor
cmnlib fsc misc persist ssd
/dev/block/platform/soc/by-name # [6nexit
PS C:\Users\dadud\Downloads\TWRP-3.2.1-ali-20180612.img> adb pull /dev/block/platform/soc/by-name/boot stockboot.img
remote object '/dev/block/platform/soc/by-name/boot' not a file or directory
PS C:\Users\dadud\Downloads\TWRP-3.2.1-ali-20180612.img>
(ive got adb/fastboot enabled system wide so itll work out of whatever folder i have open)
Dadud said:
no, it doesnt seem to be working, this is a log my my powershell prompt.
PS C:\Users\dadud\Downloads\TWRP-3.2.1-ali-20180612.img> adb shell
~ # [6n cd /dev/block/platform/soc/
/dev/block/platform/soc # [6nls
by-name mmcblk0p16 mmcblk0p25 mmcblk0p34 mmcblk0p43 mmcblk0p52
by-num mmcblk0p17 mmcblk0p26 mmcblk0p35 mmcblk0p44 mmcblk0p53
mmcblk0 mmcblk0p18 mmcblk0p27 mmcblk0p36 mmcblk0p45 mmcblk0p6
mmcblk0p1 mmcblk0p19 mmcblk0p28 mmcblk0p37 mmcblk0p46 mmcblk0p7
mmcblk0p10 mmcblk0p2 mmcblk0p29 mmcblk0p38 mmcblk0p47 mmcblk0p8
mmcblk0p11 mmcblk0p20 mmcblk0p3 mmcblk0p39 mmcblk0p48 mmcblk0p9
mmcblk0p12 mmcblk0p21 mmcblk0p30 mmcblk0p4 mmcblk0p49 mmcblk0rpmb
mmcblk0p13 mmcblk0p22 mmcblk0p31 mmcblk0p40 mmcblk0p5
mmcblk0p14 mmcblk0p23 mmcblk0p32 mmcblk0p41 mmcblk0p50
mmcblk0p15 mmcblk0p24 mmcblk0p33 mmcblk0p42 mmcblk0p51
/dev/block/platform/soc # [6ncd by-name
/dev/block/platform/soc/by-name # [6nls
DDR cmnlib64 fsg mmi_misc prov syscfg
aboot cmnlib64bak hw modem provbak system
abootbak cmnlibbak keymaster modemst1 recovery tz
apdp devcfg keymasterbak modemst2 rpm tzbak
boot devcfgbak kpan mota rpmbak userdata
cache dpo logo msadp sbl1 utags
carrier dsp logs oem sbl1bak utagsBackup
cid frp metadata padA sp vendor
cmnlib fsc misc persist ssd
/dev/block/platform/soc/by-name # [6nexit
PS C:\Users\dadud\Downloads\TWRP-3.2.1-ali-20180612.img> adb pull /dev/block/platform/soc/by-name/boot stockboot.img
remote object '/dev/block/platform/soc/by-name/boot' not a file or directory
PS C:\Users\dadud\Downloads\TWRP-3.2.1-ali-20180612.img>
(ive got adb/fastboot enabled system wide so itll work out of whatever folder i have open)
Click to expand...
Click to collapse
Okay try this from powershell, it should work.
Code:
adb shell
dd if=/dev/block/platform/soc/by-name/boot of=/tmp/stockboot.img
dd if=/dev/block/platform/soc/by-name/recovery of=/tmp/stockrecovery.img
exit
adb pull /tmp/stockboot.img
adb pull /tmp/stockrecovery.img
kwiksi1ver said:
Okay try this from powershell, it should work.
Code:
adb shell
dd if=/dev/block/platform/soc/by-name/boot of=/tmp/stockboot.img
dd if=/dev/block/platform/soc/by-name/recovery of=/tmp/stockrecovery.img
exit
adb pull /tmp/stockboot.img
adb pull /tmp/stockrecovery.img
Click to expand...
Click to collapse
ended up downloading the new (r40) of ADB instead of the old (r32) and using command line, and had success.. ill edit this post with the google drive links to my boot.img and recovery.img as soon as it uploads (stuck on 512k upload and both are about 22 megs, should be done in 10-15 minutes.)
Edit: Links
https://drive.google.com/open?id=1VWK24zyIl2sGz4H99YrG1G0KdTUmBsG3 <- Boot.img
https://drive.google.com/open?id=1xXEj7vdiikBY5ygZANNeMWwvI1S3DO4H <- Recovery.img
---------- Post added at 01:03 PM ---------- Previous post was at 12:32 PM ----------
Dadud said:
ended up downloading the new (r40) of ADB instead of the old (r32) and using command line, and had success.. ill edit this post with the google drive links to my boot.img and recovery.img as soon as it uploads (stuck on 512k upload and both are about 22 megs, should be done in 10-15 minutes.)
Edit: Links
https://drive.google.com/open?id=1VWK24zyIl2sGz4H99YrG1G0KdTUmBsG3 <- Boot.img
https://drive.google.com/open?id=1xXEj7vdiikBY5ygZANNeMWwvI1S3DO4H <- Recovery.img
Click to expand...
Click to collapse
Say i wanted to flash the pixel experience project treble rom, all i'd have to do is flash the system.img from their download through twrp/fastboot and boot? i've already backed up my original system.img.
edit: attempted, failed. just reboots into bootloader every time i try to start it. reflashing stock system.img
edit: that also failed, along with my twrp backup.
edit 3: unbricked with the firmware found on this forum.
So.... I have tried installing again and ended in bootloops. I just tried installing AOSP phh-treble via fastboot (system.img doesn't need to be signed) and it is booting with the stock unmodified kernel.
Photos.. Also seen this boot logo randomly.. Thought that was interesting..
I am working to see if I can figure out the external sdcard in twrp (as this thread should be about twrp). Figured a booting image might help in that, dunno.