As usual .
Code:
1|[email protected]:/ $ ls -al /dev/block/platform/12200000.dwmmc0/by-name
ls -al /dev/block/platform/12200000.dwmmc0/by-name
lrwxrwxrwx root root BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root m9kefs3 -> /dev/block/mmcblk0p6
[email protected]:/ $
Have fun!:good:
leoaudio13 said:
Have fun!:good:
Click to expand...
Click to collapse
Support for EFS backup added
Where i can download the SG-900H Efs backup tool, or is the same file as the SG-900F one?
system dump or at least build.prop.
PlayfulGod said:
system dump or at least build.prop.
Click to expand...
Click to collapse
we got a system dump! gonna add it to the thread in a sec!(the dump thread we made)
cant you just make a flash .zip about swap sd ? its easy way than editing lines etc
I need a
Code:
cat /proc/partitions
cat /proc/emmc
edit: LoL
success device
guyz what exactly is that? for transfer any app we want on sd?
and how to make it?
i am noob plz help me
hello can any one post good efs file for g900h in tar format please
thanks
Related
Partition mappings for the device, for developers only.
Also useful for ROM developers, as the mapping for the device is quite different from the international S3 (I9300)
As a reminder, do NOT touch the partitions in bold letters, if you do not know what you are doing. It will result in a brick and require JTAG service.
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3 is this where we make a backup for efs or /root/efs/ will do ?
prodigiez said:
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3 is this where we make a backup for efs or /root/efs/ will do ?
Click to expand...
Click to collapse
Correct, I have made a copy of it myself.
You can do so using the command to make a copy on your external SDCard:
Code:
su
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/efs.img
yea thx... an 20mb img...
hmmm... any idea what these "m9kefs*" partitions are for? (I'm unfamiliar with the i9300 international partitions).
nbates66 said:
hmmm... any idea what these "m9kefs*" partitions are for? (I'm unfamiliar with the i9300 international partitions).
Click to expand...
Click to collapse
No idea at the moment. why not dd it out as img and use a hex editor to take a look?
On a German T-Mobile i9305 is /preload on the HIDDEN Partition and it's filled with bloatware.
Read this: http://forum.xda-developers.com/showthread.php?t=2012491
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 896.6M 76.0K 896.5M 0% /dev
/dev/block/mmcblk0p12
1007.9M 17.3M 990.6M 2% /cache
/dev/block/mmcblk0p14
551.2M 175.7M 375.5M 32% /preload
/dev/block/mmcblk1p1 14.8G 13.3G 1.6G 89% /sdcard
/dev/block/mmcblk0p16
11.0G 7.7G 3.4G 69% /data
/dev/block/mmcblk0p13
1.5G 679.6M 832.3M 45% /system
/dev/block/mmcblk0p3 19.7M 4.2M 15.5M 21% /efs
Anyone knows if we can reformat the partition layout to use the unused 551.2 megabytes, maybe for /system or others?
Otherwise I can use /preload to store a version of TitaniumBackup that will be installed via the PreloadInstaller.apk after each flash. No need to download it from the play store. Any suggestions?
Thainks!!!!
Sent from my GT-I9305 using xda premium
nbates66 said:
hmmm... any idea what these "m9kefs*" partitions are for? (I'm unfamiliar with the i9300 international partitions).
Click to expand...
Click to collapse
kazuni said:
No idea at the moment. why not dd it out as img and use a hex editor to take a look?
Click to expand...
Click to collapse
Hi, I have already done an analysis into these partitions explained in the NV Backup and Restore sticky thread.
Don't dd the partitions to img files as they are not file system partitions and won't mount in this way.
These are binary data partitions relating to the Qualcomm efs structure which is most likely where the IMEI is stored.
So if you want to back these up you should dd the partitions to bin files.
Sent from my GT-I9305 using Tapatalk 2
Guys Efs partition backup is not enough read the sticky thread by Lyriquidperfection We also need to backup the other Efs just incase.. just read the sticky for information regarding efs/imei backup
We got an easy way to open the /preload partition in windows? would love to have access to this and set it as my davlik or what not.
sboot.bin partition
What is the correct partition for sboot.bin?
Thanks
Hi everyone,
Long time lurker but only got around to registering.
I believe I am getting a Samsung Galaxy Tab 2 10.1 Wifi (5110) next week for my birthday.
Does TriangleAway reset the counters correctly on Jellybean on this model?
I would be looking to root the device but ideally I would like to reset the counter for warranty purposes.
Thanks
Yes , I did on JB 4.1.1 TriangleAway ver2.37
there's 2 counters that samsung keeps track of. triangle away only resets 1. with the other they can tell you have installed a custom rom. I have seen threads of people stuck on update, just like mine did. that only happened with jelly bean 4.1.1 and above. not sure if others have been able to bypass it.
This is true, I also did TriangleAway, but I did not encounter any problems.
The latest secondary boot loader Sbl.bin check the recovery partition on every boot and mark the counter if found unofficial recovery.
P31xx and P51xx partition map:
Code:
$ su
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ <
lrwxrwxrwx root root 2013-01-20 08:04 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-20 08:04 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-20 08:04 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-20 08:04 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-20 08:04 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-20 08:04 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-20 08:04 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-20 08:04 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-20 08:04 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-20 08:04 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-20 08:04 SBL2 -> /dev/block/mmcblk0p3
Someone please extract the secondary boot loader from original 4.0.4 (have no recovery check) and share it here:
Code:
# dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2 bs=4096
# dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3 bs=4096
Απ: [Q] Triangle Away and Galaxy Tab 2 10.1 5110 Jellybean
Yes i did it too!
Στάλθηκε από το GT-P5110 μου χρησιμοποιώντας Tapatalk 2
Thanks
ketut.kumajaya said:
The latest secondary boot loader Sbl.bin check the recovery partition on every boot and mark the counter if found unofficial recovery.
P31xx and P51xx partition map:
Code:
$ su
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ <
lrwxrwxrwx root root 2013-01-20 08:04 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-20 08:04 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-20 08:04 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-20 08:04 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-20 08:04 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-20 08:04 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-20 08:04 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-20 08:04 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-20 08:04 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-20 08:04 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-20 08:04 SBL2 -> /dev/block/mmcblk0p3
Someone please extract the secondary boot loader from original 4.0.4 (have no recovery check) and share it here:
Code:
# dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2 bs=4096
# dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3 bs=4096
Click to expand...
Click to collapse
So if I root the Tab 2 using the stock recovery and CF-AutoRoot will it not change this recovery flag? It would seem logical as I am not changing the recovery.
will triangle away work for me
I have a p3100 with cm 10.2 and cwm recovery.
As said above there are 2 flash counters so will triangle away help me get back warranty.I plan to flash stock rom from sammobile once done with flash counter. So at the end will my status be completely stock???
If not what should i do to get my warranty back.
Thanks
This is indeed confusing
lg soruce code
http://www.lg.com/lgecs.downloadFil...TE3)_Android_JB_F260SV10J.zip&newOpensource=Y
root
https://dl.dropboxusercontent.com/u/3668343/f260s/motochopper.zip
https://dl.dropboxusercontent.com/u/3668343/f260s/optimus_jb_root-alldevices-3.zip
https://dl.dropboxusercontent.com/u/3668343/f260s/ToolBOX_2.2-BETA6.zip
root + 2nd init recovery
https://dl.dropboxusercontent.com/u/3668343/f260s/GomdoLightCWMrootTool_A.rar
2nd init recovery
https://dl.dropboxusercontent.com/u/3668343/f260s/CWM_JB.apk
10j kdz
https://docs.google.com/file/d/0B8gbVnsk92IuOFZJQmFnMVJUOE0/edit
10j tot
https://dl.dropboxusercontent.com/u/3668343/f260s/KDZTOOL/F260S10j_00.tot
lg mobile support tool
https://dl.dropboxusercontent.com/u/3668343/f260s/B2CAppSetup.7z
driver
https://dl.dropboxusercontent.com/u...leDriver_S4981MAN37AP22_ML_WHQL_Ver_3.8.1.zip
flash dll
https://dl.dropboxusercontent.com/u/3668343/f260s/F260S_flash_dll.zip
http://csmg.lgmobile.com:9002/csmg/b2c/client/sw_manual_list.jsp?model=LGF260S&suffix=ADEUSV
flash tool and patch
https://dl.dropboxusercontent.com/u/3668343/f260s/Setup_LGFlashTool_1.5.10.1120.zip
https://dl.dropboxusercontent.com/u/3668343/f260s/MegaLock.7z
system dump tool ,tar format
https://dl.dropboxusercontent.com/u/3668343/f260s/GomdoLightSystemDumpTool.rar
system dump 10j
https://docs.google.com/file/d/0B8gbVnsk92IuUXZnc014eTJSM3c/edit
FLASH INFO
http://forum.gsmhosting.com/vbb/f177/lg-flash-tool-free-no-need-b2b-user-pass-1628819/
http://androidforums.com/lg-optimus-f7-all-things-root/
US VER LG870 TOT AND CAB
https://docs.google.com/file/d/0B8gbVnsk92IuRll3S0x0aXFtTFE/edit?usp=sharing
http://csmgdl.lgmobile.com/swdata/WDLSW/LG870/ABMUBK/LG870ZV4_06/LG870ZV4_06.S4_06.P31103.cab
US VER LG870 system dump
http://www.oudhitsquad.com/android/?dir=LGE/Firmware/LG870
hidemenu
5457#*260#
3845#*260#
f260s 10m
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW299785432109876543213/F260S10m_00.kdz
============
http://forum.xda-developers.com/showthread.php?t=1566532&page=19
============
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 2013-08-30 20:55 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-08-30 20:55 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-08-30 20:55 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-08-30 20:55 drm -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-08-30 20:55 encrypt -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2013-08-30 20:55 fota -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-08-30 20:55 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-08-30 20:55 grow -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2013-08-30 20:55 lgipa -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2013-08-30 20:55 mdm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2013-08-30 20:55 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-08-30 20:55 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-08-30 20:55 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-08-30 20:55 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-08-30 20:55 mpt -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-08-30 20:55 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-08-30 20:55 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-08-30 20:55 rct -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2013-08-30 20:55 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-08-30 20:55 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-08-30 20:55 rpmbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2013-08-30 20:55 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-08-30 20:55 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-08-30 20:55 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-08-30 20:55 sns -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-08-30 20:55 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-08-30 20:55 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-08-30 20:55 tombstones -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-08-30 20:55 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-08-30 20:55 tzbak -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-08-30 20:55 userdata -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-08-30 20:55 ve -> /dev/block/mmcblk0p27
when does lg optimus lte3 have cyanogenMod rom?
please,I don't good at English :cyclops:
cuongdhytn said:
when does lg optimus lte3 have cyanogenMod rom?
please,I don't good at English :cyclops:
Click to expand...
Click to collapse
add +1 here
http://forum.cyanogenmod.com/topic/79047-request-cyanogenmod-10x-lg-f260s-f7-vs870-lg870/
god_md5 said:
add +1 here
http://forum.cyanogenmod.com/topic/79047-request-cyanogenmod-10x-lg-f260s-f7-vs870-lg870/
Click to expand...
Click to collapse
but still no rom :crying: g+
cuongdhytn said:
but still no rom :crying: g+
Click to expand...
Click to collapse
ms870 have cm rom...
http://unleashedprepaids.com/forum-1428.html
god_md5 said:
ms870 have cm rom...
http://unleashedprepaids.com/forum-1428.html
Click to expand...
Click to collapse
i asked members on my forum comment in your request,but need more.my device is korea version
what can i do ?
f260s F260S10L_00 kdz rom
csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW449965432109876543213/F260S10l_00.kdz
Is this the lg optimus F7 i just got from boost?
birddseedd said:
Is this the lg optimus F7 i just got from boost?
Click to expand...
Click to collapse
lg870?
here http://androidforums.com/lg-optimus-f7-all-things-root/
CWM recovery for F260s - LG Optimus LTE3.
Thanks @PlayfulGod for LG870 Ramdisk. THanks you very much.
- Fixed init.rc: always enabled adb from recovery
USE AT YOUR OWN RISK!!!
1.
Here is a zip that can be flashed with the 2nd-init recovery
https://drive.google.com/file/d/0B3J7gOQH7ViEX09BVHNENF9ldlU/edit?usp=sharing
OR
2.
Download, extract and run recovery.bat (with adb connect).
https://drive.google.com/file/d/0B3J7gOQH7ViENXdWVTY2TzQ4Z0U/edit?usp=sharing
More info (use google translate pls)
http://lgviet.com/forum/threads/test-recovery-vinh-vien-cho-lte3.6789/
Does anyone know where or if there are lgnpst dll files out there?
Sent from my SPH-L710 using XDA Premium 4 mobile app
im not so familiar in flashing rom
im sorry if im getting messy here
i got LG F260S from korea (gave as a gift)
im living here in the philippines
im looking for a custom rom for my LGF260S (hopefully with a process o how to do it)
merry xmas
thanks in advance
There are no Roms out
Sent from my SPH-L710 using XDA Premium 4 mobile app
you can find rom here
http://choimobile.vn/forums/lg-lte3-f260.84.html
made by Việt Nam user
thanks for the link
so hard to understand vietnamese (even if its translated by google)
i even registered in some vietnamese forum, hope i can get reply in english
crossing finger
f260s 10m out
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW299785432109876543213/F260S10m_00.kdz
cuongdhytn said:
you can find rom here
http://choimobile.vn/forums/lg-lte3-f260.84.html
made by Việt Nam user
Click to expand...
Click to collapse
thanks a lot for the link
now my F260s is rooted with sphinx rom installed ^:^
just wondering any software you can suggest that might get more interesting for F260S ?
regards ^:^
f260s cm10
goo.gl NaC9Nf
daebo01 said:
f260s cm10
goo.gl NaC9Nf
Click to expand...
Click to collapse
what for ? can you guide me?
s18(dot)postimg(dot)org/xq2hvqkp5/f260s_cm.jpg
I ported cm10 to f260s using f160l cm 10 rom.
It is very fast.
But it did not work much.
Working List)
WiFi
Vibration
Not Working List)
Sound
Mobile Network
Camera
Please help me fix it.
Download : 1drv(dot)ms/1fj5wHJ
www(dot)mediafire(dot)com/download/agcnwhwle1cc72d/cm-10-20140217-f260s.zip
Does anyone has by any chance the mount points table for the N915F?
Thank you.
Instruction
starbucks2010 said:
Does anyone has by any chance the mount points table for the N915F?
Thank you.
Click to expand...
Click to collapse
If you can instruct me - I'll do it.
I tried with (adb shell) cat /proc/partitions and cat /proc/mounts but I don't know which partition is which mmcblk.
I checked also in fstab file but the mount point information is missing from it.
PS. Finaly I found out. If anyone need it:
lrwxrwxrwx root root 2014-01-10 11:07 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-10 11:07 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-10 11:07 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-10 11:07 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-01-10 11:07 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-10 11:07 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-10 11:07 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-10 11:07 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-10 11:07 hidden -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-10 11:07 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-10 11:07 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-10 11:07 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-10 11:07 param -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-10 11:07 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-10 11:07 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-10 11:07 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-10 11:07 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-10 11:07 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-10 11:07 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-10 11:07 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-10 11:07 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-10 11:07 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-10 11:07 userdata -> /dev/block/mmcblk0p27
Good luck.
does anyone knows which mount point is for "data": mmcblk0p26 (hidden) or mmcblk0p27 (userdata)?
thank you
Here's some info from the N915T
Code:
lrwxrwxrwx 1 root root 20 Jan 3 2014 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 3 2014 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 3 2014 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 3 2014 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 Jan 3 2014 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 3 2014 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 3 2014 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 3 2014 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 3 2014 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 3 2014 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 3 2014 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 3 2014 param -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 3 2014 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 3 2014 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 3 2014 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Jan 3 2014 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 3 2014 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 3 2014 system -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 3 2014 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 3 2014 userdata -> /dev/block/mmcblk0p26
Hi, I want to (urgently) investigate the bootloader internals of recent Fire devices, so please provide me with a bootloader dump in Fire HD 10 (2017). Here's how to get it;
Get into an ADB command prompt/terminal.
Type the commands in this order;
Code:
adb shell
Code:
su
Code:
cd /dev/block/bootdevice/by-name
Code:
ls -all
Try to find the bootloader image, this is kind of hard. It's usually named as 'aboot'. If you fail to find that then please copy paste the result of the last command, I will try to guess what it is.
If you somehow notices the correct one, look at the text in front of it, in form of "/dev/block/****", and type;
Code:
dd if=/dev/block/**** of=/sdcard/Download/aboot.img
Of course replace the stars with your partition.
(aboot.img works universally I think because the dump name doesn't matter, if that doesn't work, replace aboot.img with [YOUR-ABOOT-ALTERNATIVE].img replacing with the bootloader image text you found above).
Upload the resulting .img file in a post in this thread quickly as possible!
Thank you!
I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15
luvboox said:
I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Uhhh, I'm not sure either. One of Amazon's obscure modifications. :crying::crying:
Supersonic27543 said:
Uhhh, I'm not sure either. One of Amazon's obscure modifications. :crying::crying:
Click to expand...
Click to collapse
Also, try "reserved" please? Thanks!
luvboox said:
I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Also, did you try /dev/block/bootdevice/by-name ? Thank you
Supersonic27543 said:
Also, did you try /dev/block/bootdevice/by-name ? Thank you
Click to expand...
Click to collapse
No /dev/block/bootdevice/ I'm afraid, just /dev/block/platform/ and /dev/block/vold (which is an empty folder).
@Supersonic27543 and others
Have you seen this : https://forum.xda-developers.com/showpost.php?p=74987132&postcount=3
The bootloader files you're looking for are in the update .bin (it's really a .zip; look in the "images" folder). The links to the update file are in the thread cited above (in post #2).
As discussed earlier in this thread, the preloader is locked down (read/write commands missing). Absent access to Amz's signature(s) for the DA, what are you looking to do with these files?
retyre said:
The bootloader files you're looking for are in the update .bin (it's really a .zip; look in the "images" folder). The links to the update file are in the thread cited above (in post #2).
As discussed earlier in this thread, the preloader is locked down (read/write commands missing). Absent access to Amz's signature(s) for the DA, what are you looking to do with these files?
Click to expand...
Click to collapse
I'm trying to see if any backdoor has been left by Amazon by looking at unusual differences.