Related
use to follow darky's tutorial for my i9000 do a system dump then write an odin flashable rom for backup,
but i have no clue what to dump on my i9100??
The most common partitions are:
/dev/block/mmcblk0p5 -> Kernel
/dev/block/mmcblk0p7 -> Cache
/dev/block/mmcblk0p8 -> Modem / Radio / Baseband (w/e you like to call it)
/dev/block/mmcblk0p9 -> System (factoryfs for Odin .tars)
/dev/block/mmcblk0p10 -> (user) data
i tried it, extracted all the files and created the tar but it fails as soon as i start it..
heres the commands i used :
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Click to expand...
Click to collapse
then
tar -H ustar -c factoryfs.rfs cache.rfs modem.bin zImage > rom.tar
Click to expand...
Click to collapse
and then md5 ... ?? what am i doing wrong?
Yeah, you can't just reflash raw dumps with Odin, unfortunately.
You can use them to restore via dd though.
But this thread might help for Odin flashing: (the re-packing part)
http://forum.xda-developers.com/showthread.php?t=1081239
read a bunch of threads from that link and so on,
i dont have a linux machine at work so i need to take this home and try but i honestly got my doubts, looks too complicated for a noob like me ha!
i need some easy tutorial to follow, i guess i just have to wait till someone actually writes it!
thank for the help though!
Could anyone please post the correct SGS3 modem partition as below?
I can find the SGS2, but so far not SGS3.
As my firmware is not yet available for download, I need/want to extract my "T" modem.bin from my existing ROM using ADB commands and repackage into a CWM .zip file.
ie.
adb shell
su
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Once done, I can start flashing some of the excellent ROMs currently about and in development, but keeping the preferred modem for my carrier's 850MHz band.
Thanks
Edit: Current firmware rooted
Product code: GT-I9300RWTTHL
PDA: I9300TDUALE6
Phone: I9300TDULE6
CSC: I9300TTHLALE2
Bump anyone.
SO far I've found in ADB with "mount":
/dev/block/mmcblk0p9 /system ext4
/dev/block/mmcblk0p12 /data ext4
/dev/block/mmcblk0p8 /cache ext4
/dev/block/mmcblk0p3 /efs ext4
/dev/block/vold/179:17 /mnt/extSdCard vfat
After a lot more searching............
/dev/block/mmcblk0p5 / boot.img
/dev/block/mmcblk0p6 / recovery.img
But still no Modem,........
Anyone with the know-how or the correct ADB commands to show partitions including the Modem?
[Solved] Finally......... after a system dump:
/dev/block/mmcblk0p7 (modem/radio)
Cheers
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 ?
This morning I was coding this script, but didn't feel like extending it further. it basically just dumps all known partitions to the chosen dir and then makes a (compressed) odin rom from it, if chosen.
if anyone wants to use this, feel free to do whatever you want with it. I will occasionally dump some items on this forum that I find share worthy. just to share some inside stuff that will never get released when I don't share it here
Code:
#!/system/bin/sh
# Complete backup for Galaxy S4 (i9505)
# Created by broodplank1337
# Developer Sample (free for all kinds of use)
# www.broodplank.net
MAKEODIN="n";
ODINUSECOMPRESS="n";
BACKUPNONODIN="n";
OUTPATH="/storage/sdcard1/backup/";
echo "Starting backup..."
echo "Overall process may take upto 30 minutes"
echo
echo "BACKUP MODEM"
echo
echo "1. NON-HLOS.bin"
busybox dd if=/dev/block/mmcblk0p1 of=${OUTPATH}NON-HLOS.bin
echo "2. modem.bin"
busybox dd if=/dev/block/mmcblk0p2 of=${OUTPATH}modem.bin
echo
echo "BACKUP BOOTLOADER"
echo
echo "1. sbl1.mbn"
busybox dd if=/dev/block/mmcblk0p3 of=${OUTPATH}sbl1.mbn
echo "2. sbl2.mbn"
busybox dd if=/dev/block/mmcblk0p4 of=${OUTPATH}sbl2.mbn
echo "3. sbl3.mbn"
busybox dd if=/dev/block/mmcblk0p5 of=${OUTPATH}sbl3.mbn
echo "4. aboot.mbn"
busybox dd if=/dev/block/mmcblk0p6 of=${OUTPATH}aboot.mbn
echo "5. rpm.mbn"
busybox dd if=/dev/block/mmcblk0p7 of=${OUTPATH}rpm.mbn
echo "6. tz.mbn"
busybox dd if=/dev/block/mmcblk0p8 of=${OUTPATH}tz.mbn
echo
echo "BACKUP PLATFORM"
echo
echo "1. system.img.ext4"
busybox dd if=/dev/block/mmcblk0p16 of=${OUTPATH}system.img.ext4
echo "2. recovery.img"
busybox dd if=/dev/block/mmcblk0p21 of=${OUTPATH}recovery.img
echo "3. boot.img"
busybox dd if=/dev/block/mmcblk0p20 of=${OUTPATH}boot.img
echo
echo "BACKUP CSC"
echo
echo "1. cache.img.ext4"
busybox dd if=/dev/block/mmcblk0p18 of=${OUTPATH}cache.img.ext4
if [[ $MAKEODIN != "n" ]]; then
echo
echo "Making odin package, this may take a while"
echo
cd ${OUTPATH}
GETDATE=`busybox date -I`;
if [[ $ODINUSECOMPRESS != "n" ]]; then
echo "Making compressed tar ball"
busybox tar -cz NON-HLOS.bin modem.bin sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn rpm.mbn tz.mbn system.img.ext4 recovery.img boot.img cache.img.ext4 > odin-${GETDATE}.tar.gz
echo "Writing MD5 sums..."
busybox md5sum -t odin-${GETDATE}.tar.gz >> odin-${GETDATE}.tar.gz
echo "Renaming..."
busybox mv odin-${GETDATE}.tar.gz odin-${GETDATE}.tar.md5.gz
else
echo "Making tar ball"
busybox tar -c NON-HLOS.bin modem.bin sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn rpm.mbn tz.mbn system.img.ext4 recovery.img boot.img cache.img.ext4 > odin-${GETDATE}.tar
echo "Writing MD5 sums..."
busybox md5sum -t odin-${GETDATE}.tar >> odin-${GETDATE}.tar
echo "Renaming..."
busybox mv odin-${GETDATE}.tar odin-${GETDATE}.tar.md5
fi;
echo
echo "Odin package has been created"
echo
fi;
if [[ ${BACKUPNONODIN} != "n" ]]; then
echo
echo "backup non odin (others).."
echo
busybox dd if=/dev/block/mmcblk0p9 of=${OUTPATH}PAD
busybox dd if=/dev/block/mmcblk0p10 of=${OUTPATH}efs.img.ext4
busybox dd if=/dev/block/mmcblk0p11 of=${OUTPATH}nvrebuild1.bin
busybox dd if=/dev/block/mmcblk0p12 of=${OUTPATH}nvrebuild2.bin
busybox dd if=/dev/block/mmcblk0p13 of=${OUTPATH}m9kefs1.bin
busybox dd if=/dev/block/mmcblk0p14 of=${OUTPATH}m9kefs2.bin
busybox dd if=/dev/block/mmcblk0p15 of=${OUTPATH}m9kefs3.bin
busybox dd if=/dev/block/mmcblk0p17 of=${OUTPATH}PERSIST
busybox dd if=/dev/block/mmcblk0p19 of=${OUTPATH}param.lfs
busybox dd if=/dev/block/mmcblk0p22 of=${OUTPATH}FOTA
busybox dd if=/dev/block/mmcblk0p23 of=${OUTPATH}BACKUP
busybox dd if=/dev/block/mmcblk0p24 of=${OUTPATH}FSG
busybox dd if=/dev/block/mmcblk0p25 of=${OUTPATH}SSD
busybox dd if=/dev/block/mmcblk0p26 of=${OUTPATH}persdata.img.ext4
busybox dd if=/dev/block/mmcblk0p27 of=${OUTPATH}hidden.img.ext4
busybox dd if=/dev/block/mmcblk0p29 of=${OUTPATH}userdata.img.ext4
busybox dd if=/dev/block/mmcblk0p28 of=${OUTPATH}carrier.img.ext4
fi;
echo
echo "BACKUP COMPLETED!"
echo
Thanks friend! :good:
regards!
I'm pretty sure this needs to run as root because some of those partitions are likely read protected.
CNexus said:
I'm pretty sure this needs to run as root because some of those partitions are likely read protected.
Click to expand...
Click to collapse
Anyone tried restoring an odin tar generated with this using the odin app? I thought the files had to be signed by samsung to be accepted by odin?
Also, do you set the tar.md5 file generated in the "PDA" field of Odin?
prisonnet said:
Anyone tried restoring an odin tar generated with this using the odin app? I thought the files had to be signed by samsung to be accepted by odin?
Also, do you set the tar.md5 file generated in the "PDA" field of Odin?
Click to expand...
Click to collapse
Nope, only zips to be flashed through (stock) recovery need to be signed by Samsung
found a typo:
line 38: if [[ ${BACKUPNONODIN} != "n" ]]; then
and on some roms may need to edit:
OUTPATH="/storage/extSdCard/backup/";
TRusselo said:
found a typo:
line 38: if [[ ${BACKUPNONODIN} != "n" ]]; then
and on some roms may need to edit:
OUTPATH="/storage/extSdCard/backup/";
Click to expand...
Click to collapse
That first one isn't a typo btw.
CNexus said:
Nope, only zips to be flashed through (stock) recovery need to be signed by Samsung
Click to expand...
Click to collapse
Trying to flash with Odin 3.07, MD5 verifies but getting this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.img.ext4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img.ext4
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
Click to expand...
Click to collapse
Any idea?
CNexus said:
That first one isn't a typo btw.
Click to expand...
Click to collapse
really? seems like it is, and my script editor was highlighting it too as an error. that bracket never ends {
prisonnet said:
Trying to flash with Odin 3.07, MD5 verifies but getting this error:
Any idea?
Click to expand...
Click to collapse
Hmm thats kinda strange, it should work just fine actually. can you list the files inside the .tar.md5 please?
TRusselo said:
really? seems like it is, and my script editor was highlighting it too as an error. that bracket never ends {
Click to expand...
Click to collapse
At first I though you were wrong but you're actually right, it should be either $VAR OR ${VAR}, despite that the script runs successfully.
I'm curious to know why we can only flash modems (modem.bin and non-hlos.bin) via odin
Why won't the following commands for example work in a shell called in a CWM.zip?
dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
dd if=/sdcard/modem.bin of=/dev/block/mmcblk0p2
What is causing the restriction for modems to only be able to be flashed through Odin and not CWM?
Has this also got something to do with the fact that you can only successfully flash a modem if entered download mode through a complete power-off, and not via the power menu?
hawkerpaul said:
I'm curious to know why we can only flash modems (modem.bin and non-hlos.bin) via odin
Why won't the following commands for example work in a shell called in a CWM.zip?
dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
dd if=/sdcard/modem.bin of=/dev/block/mmcblk0p2
What is causing the restriction for modems to only be able to be flashed through Odin and not CWM?
Has this also got something to do with the fact that you can only successfully flash a modem if entered download mode through a complete power-off, and not via the power menu?
Click to expand...
Click to collapse
The thing is no one ever tries to do this. I'm almost 100% sure that this is just possible.
Maybe you cannot directly flash those 2 files, but you can do this without any problems:
Backup modem partition and just flash it on an other device. same amount of blocks, so should be no problem.
dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
but it still forced you to use odin once atleast to flash it
(no confirmed results though)
I agree with you. I just don't see any reason why the device dump commands can't also work for modems. I've just taken it as one of those things that cannot be done via cwm.
I was worried in case I did dump to those partitions it might screw the device taking into consideration it just isn't the done thing to do.
I will write a shell script to be called through cwm to see if it can be done..... just hope it don't bugger my device up!
Edit:
I've just tried the following:
dd if=/dev/block/mmcblk0p2 of=/sdcard/modem.dd.bin
I then opened the downloaded modem.tar file that I have for my current modem (currently I'm on XXUFNBE), extracted modem.bin onto pc, then copied it to /sdcard/modem.bin
Unfortunately, these 2 files differ in a diff command, and if I do an ls -l, they differ quite drastically:
ls -l:
-rw-rw-r-- root sdcard_rw 52354048 2014-03-07 21:13 modem.bin
-rw-rw-r-- root sdcard_rw 54030336 2014-03-07 21:07 modem.dd.bin
Obviously its not even worth attempting to dd this modem.bin file back to /dev, as its not the same as original modem.dd.bin I created.
Either there is a problem with the way modem.bin gets extracted from the .tar file on PC through 7zip, (as 7zip does complain with "no correct record at the end of the archive" when I extract it) or I need to supply dd with different command line parameters.
You have to know that this is totally normal when using dd, the thing with dd is that it dumps the WHOLE partition, so also all zero's (no data) to a file. for example if you dd boot.img you will get a file that is EXACTLY 10mb, since that is the size of the partition. but when flashing it back to the partition it won't cause any problems afaik. I have done it a couple of times.
(To lookup how big the files will turn out, check: 'cat /proc/partitions')
Code:
[email protected]:/ # cat proc/partitions
major minor #blocks name
7 0 4190 loop0
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
254 0 4189 dm-0
sizes are expressed in KiloBytes
Here is my little experiment to prove it to you:
Code:
[email protected] ~ $ [B]adb shell[/B]
[email protected]:/ # [B]dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 2.283 secs (4592974 bytes/sec)
[email protected]:/ # [B]dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.470 secs (7133170 bytes/sec)
[email protected]:/ # [B]reboot[/B]
and my phone just booted as it normally does.
What you could do, but NEVER EVER should do is removing all zeros from the partition file with a hexeditor to get the actual size. but if you will flash back this image you probably screw up your partition as it's an invalid image for that partition.
So long story short, you can NEVER EVER flash modem.bin directly to the partition, but you can flash a partition dump you made earlier to the partition without causing damage (at least to your own device).
It's just a pity the modem does not come in .img format by default.
When using dd better be sure to know what you're doing :good:
broodplank1337 said:
You have to know that this is totally normal when using dd, the thing with dd is that it dumps the WHOLE partition, so also all zero's (no data) to a file. for example if you dd boot.img you will get a file that is EXACTLY 10mb, since that is the size of the partition. but when flashing it back to the partition it won't cause any problems afaik. I have done it a couple of times.
(To lookup how big the files will turn out, check: 'cat /proc/partitions')
Code:
[email protected]:/ # cat proc/partitions
major minor #blocks name
7 0 4190 loop0
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
254 0 4189 dm-0
sizes are expressed in KiloBytes
Here is my little experiment to prove it to you:
Code:
[email protected] ~ $ [B]adb shell[/B]
[email protected]:/ # [B]dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 2.283 secs (4592974 bytes/sec)
[email protected]:/ # [B]dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.470 secs (7133170 bytes/sec)
[email protected]:/ # [B]reboot[/B]
and my phone just booted as it normally does.
What you could do, but NEVER EVER should do is removing all zeros from the partition file with a hexeditor to get the actual size. but if you will flash back this image you probably screw up your partition as it's an invalid image for that partition.
So long story short, you can NEVER EVER flash modem.bin directly to the partition, but you can flash a partition dump you made earlier to the partition without causing damage (at least to your own device).
It's just a pity the modem does not come in .img format by default.
When using dd better be sure to know what you're doing :good:
Click to expand...
Click to collapse
Hey broodplank, your scripts are excellent btw. But I just wanted to let you know flashing modems through recovery does work and there's quite a few ways to do this.
1. assert extract dir "/tmp/modem.bin" then write raw image method
2. run program "/sbin/sh" "script.sh" method
3. run program "dd if=/..... method
4. Use the flash_image binary
You get the picture from the above I hope, 1-3 are updater-script related. I have a Verizon S4 Modem thread where I include zips that flash modems but also the modem.bin files can be extracted from the zips and used in odin.
I regularly hexedit the padded bootloaders to cut the trailing zeroes so the partition registers as signed (I recommend only experienced individuals do this though). When you say the partition would be invalid I take it you mean that unless the individual who is hexediting knows how to correctly do it that it will be invalid.
Surge1223 said:
Hey broodplank, your scripts are excellent btw. But I just wanted to let you know flashing modems through recovery does work and there's quite a few ways to do this.
1. assert extract dir "/tmp/modem.bin" then write raw image method
2. run program "/sbin/sh" "script.sh" method
3. run program "dd if=/..... method
4. Use the flash_image binary
You get the picture from the above I hope, 1-3 are updater-script related. I have a Verizon S4 Modem thread where I include zips that flash modems but also the modem.bin files can be extracted from the zips and used in odin.
I regularly hexedit the padded bootloaders to cut the trailing zeroes so the partition registers as signed (I recommend only experienced individuals do this though). When you say the partition would be invalid I take it you mean that unless the individual who is hexediting knows how to correctly do it that it will be invalid.
Click to expand...
Click to collapse
Thank you. Oh ok, I didn't know that
I actually know those methods, but with the second one what script do you mean, or just a partition flash script in general?
So I downloaded one of your zips and found this.
Code:
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p2"),
delete("/tmp/modem.bin"));
That's amazingly easy! Wow! Never knew this was so easy to do, I thought a special flashing binary would be needed.
Thanks a lot for this tip! It's great
And yes I mean do not ever use hexeditor if you don't know what you're doing :good:
I still can't get a modem flash to work in recovery. (I happen to be using Philz)
I use the Modem tar files in djembey's thread.
I open the modem.tar file, and 7zip says tar error: there is no correct record at the end of archive
It opens regardless, so I extract modem.bin
I then place the modem.bin in a typical cwm-flashable zip file, which includes updater-script as above post, ie:
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p2"),
delete("/tmp/modem.bin"));
However, the script hangs, and I have to long-press the power button in recovery to reboot.
Is the modem.bin incorrect from the original extraction via 7Zip perhaps? (Although the .tar file from which I extracted modem.bin flashes successfully in Odin by the way.)
Any ideas appreciated.
hawkerpaul said:
I still can't get a modem flash to work in recovery. (I happen to be using Philz)
I use the Modem tar files in djembey's thread.
I open the modem.tar file, and 7zip says tar error: there is no correct record at the end of archive
It opens regardless, so I extract modem.bin
I then place the modem.bin in a typical cwm-flashable zip file, which includes updater-script as above post, ie:
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p2"),
delete("/tmp/modem.bin"));
However, the script hangs, and I have to long-press the power button in recovery to reboot.
Is the modem.bin incorrect from the original extraction via 7Zip perhaps? (Although the .tar file from which I extracted modem.bin flashes successfully in Odin by the way.)
Any ideas appreciated.
Click to expand...
Click to collapse
Actually this is kind of a known issue. I believe some have found a work around with Philz. @Bait-Fish what was it that you guys do to flash modems with Philz?
Surge1223 said:
Actually this is kind of a known issue. I believe some have found a work around with Philz. @Bait-Fish what was it that you guys do to flash modems with Philz?
Click to expand...
Click to collapse
I would be extremely interested and appreciative to find this out
:good:
EDIT:
Just tried a flash through TWRP, and no joy, so this is not specific to Philz.
hawkerpaul said:
I would be extremely interested and appreciative to find this out
:good:
EDIT:
Just tried a flash through TWRP, and no joy, so this is not specific to Philz.
Click to expand...
Click to collapse
Im able to flash modems quite easily hmm... can you send me the modem zip package you are trying to flash so I can take a look at it?
P.S. This dev talk forum is finally starting to be useful again!
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.