Related
I am on 3.4.3-11 and the phone is pretty good, but sometimes when i starts google maps, the phone becomes unresponsive sometimes i can close it, but sometimes it reboots the phone. Does anyone has a solution for that? As i remember i dont had the problem on eclair?
Root your phone, delete/rename the maps.apk that is in system/app/ folder and download a new one from the market.
It is already rooted so i will try it. I experienced it with other versions of froyo. The maps is already updated, should i uninstall the updates before deleting the apk? I will write back but it usually takes a half day before producing the slowdown and freezing. Did you experienced the issue and deleting the apk and installing a new one from the market solved it?
vick33 said:
It is already rooted so i will try it. I experienced it with other versions of froyo. The maps is already updated, should i uninstall the updates before deleting the apk? I will write back but it usually takes a half day before producing the slowdown and freezing. Did you experienced the issue and deleting the apk and installing a new one from the market solved it?
Click to expand...
Click to collapse
In my case starting maps resulted in extremely slow performance, so I uninstalled the updates through market and renamed the apk with root explorer. After that I installed maps through market and now everything is working perfect. I have had the same maps problem on all the froyo versions.
It was the same for me. Somtimes i can close the maps, but sometimes i had to remove the battery or the phone rebooted itself. I will write back if the problem occures again, but either way thanks for your help!
What connection are you using? Slow connection can often freeze connection based applications, but not cause reboot though.
Deleting and reinstalling the maps application did not help. It was good for 8 hours, but after it the slowdowns appeared again. The CPU usage was not high at all, but the io wait was. This is what top prints out:
Code:
$ $top -n 1
User 12%, System 22%, IOW 65%, IRQ 0%
User 16 + Nice 23 + Sys 73 + Idle 0 + IOW 211 + IRQ 0 + SIRQ 0 = 323
PID CPU% S #THR VSS RSS PCY UID Name
10962 10% S 23 194340K 24660K bg app_58 com.google.android.gm
1388 4% S 70 336836K 61732K fg system system_server
671 4% S 1 0K 0K fg root mmcqd
10713 4% S 11 162220K 13992K bg app_24 com.motorola.blur.home.newsstatus
11049 3% R 1 856K 392K fg app_93 top
353 3% D 1 0K 0K fg root kswapd0
1119 2% S 1 0K 0K fg root kjournald
1608 1% S 29 190900K 13588K bg app_39 com.google.process.gapps
9937 0% S 14 174704K 19816K bg app_113 com.rechild.advancedtaskkiller
1453 0% S 1 1992K 320K fg wifi /system/bin/wpa_supplicant
1259 0% S 1 6068K 1824K fg root /system/bin/vpnclientpm
203 0% S 1 0K 0K fg root kblockd/0
219 0% S 1 0K 0K fg root cpcap_irq/0
279 0% S 1 0K 0K fg root ksuspend_usbd
284 0% S 1 0K 0K fg root khubd
311 0% S 1 0K 0K fg root kmmcd
318 0% S 1 0K 0K fg root bluetooth
352 0% S 1 0K 0K fg root khungtaskd
355 0% S 1 0K 0K fg root aio/0
356 0% S 1 0K 0K fg root ecryptfs-kthrea
358 0% S 1 0K 0K fg root crypto/0
457 0% S 1 0K 0K fg root kxtf9_wq
497 0% S 1 0K 0K fg root mtdblockd
521 0% S 1 0K 0K fg root klink_driver_wq
539 0% S 1 0K 0K fg root usb_mass_storag
547 0% S 1 0K 0K fg root qtouch_obp_ts_w
556 0% S 1 0K 0K fg root bu52014hfv_wq
562 0% S 1 0K 0K fg root als_wq
594 0% S 1 0K 0K fg root bridge_work-que
595 0% S 1 0K 0K fg root bridge_recovery
601 0% S 1 0K 0K fg root w1_bus_master1
610 0% S 1 0K 0K fg root kstriped
612 0% S 1 0K 0K fg root kondemand/0
632 0% S 1 0K 0K fg root als_wq
646 0% S 1 0K 0K fg root usbhid_resumer
649 0% S 1 0K 0K fg root binder
666 0% S 1 0K 0K fg root krfcommd
668 0% S 1 0K 0K fg root dsi
703 0% S 1 0K 0K fg root mmcqd
725 0% S 1 0K 0K fg root pvrflip/0
730 0% S 1 0K 0K fg root ksuspend_usb_ip
731 0% S 1 0K 0K fg root kipcd
1109 0% S 1 0K 0K fg root kjournald
1129 0% S 1 0K 0K fg root kjournald
1132 0% S 1 0K 0K fg root flush-179:32
1143 0% S 1 0K 0K fg root kjournald
1 0% S 1 300K 252K fg root /init
1161 0% S 1 0K 0K fg root gannet
1173 0% S 1 0K 0K fg root smodule
1180 0% S 1 832K 84K fg root /system/bin/smoduled
1222 0% S 4 3312K 152K fg shell /sbin/adbd
1223 0% S 1 1036K 80K fg root /system/bin/ecckeyd
1225 0% S 1 716K 68K fg system /system/bin/servicemanager
1226 0% S 3 3648K 132K fg root /system/bin/vold
1227 0% S 3 3644K 128K fg root /system/bin/netd
1228 0% S 1 576K 48K fg root /system/bin/debuggerd
1231 0% S 8 18508K 436K fg radio /system/bin/rild
1233 0% S 1 788K 84K fg root /system/bin/usbd
1234 0% S 1 716K 76K fg radio /system/usr/bin/nvm_daemon
1237 0% S 7 7172K 140K fg radio /system/bin/gkisystem
1238 0% S 3 3312K 132K fg radio /system/bin/rild_tcmd
1239 0% S 1 1248K 128K fg mot_accy /system/bin/battd
1242 0% S 1 114524K 8804K fg root zygote
1243 0% S 9 35280K 1776K fg media /system/bin/mediaserver
1244 0% S 1 1176K 84K fg bluetoot /system/bin/dbus-daemon
1245 0% S 1 776K 128K fg root /system/bin/installd
1247 0% S 1 1528K 72K fg keystore /system/bin/keystore
1248 0% S 1 736K 80K fg radio /system/xbin/ssmgrd
1250 0% S 2 14220K 416K fg mot_tcmd /system/bin/tcmd
1251 0% S 1 1256K 128K fg radio /system/usr/bin/panic_daemon
1252 0% S 1 196K 36K fg compass /system/bin/akmd2
1254 0% S 2 3304K 284K fg radio /system/usr/bin/brcm_guci_drv
1256 0% S 1 1088K 112K fg mot_tpap /system/bin/secclkd
1260 0% S 1 584K 60K fg nobody /system/bin/RescueStarter
1261 0% S 7 17296K 536K fg radio protocol_driver
1262 0% S 9 10308K 256K fg radio location
1263 0% S 4 4172K 104K fg radio opprofdaemon
1283 0% S 1 660K 72K fg bluetoot /system/bin/hciattach
1427 0% S 1 0K 0K fg root sdio_wq
1429 0% S 1 0K 0K fg root tiwlan_wq
1450 0% S 12 166968K 14436K fg app_14 com.motorola.blur.providers.contacts
1471 0% S 10 176212K 18296K fg app_13 com.android.inputmethod.latin
1476 0% S 26 191948K 15844K fg radio com.android.phone
1479 0% S 35 235820K 17688K fg app_14 com.motorola.blur.service.main
1480 0% S 21 172160K 15792K fg app_26 com.motorola.blur.service.blur
1487 0% S 12 220628K 25304K fg app_24 com.motorola.blur.home
1491 0% S 6 150316K 9060K fg system com.motorola.atcmd
1493 0% S 7 152692K 11392K fg app_20 com.motorola.batterymanager
1506 0% S 7 159528K 11216K fg app_30 com.nuance.android.vsuite.vsuiteapp
1534 0% S 6 150388K 9184K fg system com.motorola.inpocket
1535 0% S 7 160144K 15524K fg app_72 com.motorola.PerformanceManager
1537 0% S 8 152736K 9740K fg app_78 com.motorola.usb
1664 0% S 7 155140K 10944K fg app_73 android.tts
1815 0% S 1 0K 0K fg root loop0
1819 0% S 1 0K 0K fg root kdmflush
1831 0% S 1 0K 0K fg root kcryptd_io
1832 0% S 1 0K 0K fg root kcryptd
2052 0% S 1 0K 0K fg root loop1
2055 0% S 1 0K 0K fg root kdmflush
2056 0% S 1 0K 0K fg root kcryptd_io
2057 0% S 1 0K 0K fg root kcryptd
2125 0% S 1 0K 0K fg root loop2
2128 0% S 1 0K 0K fg root kdmflush
2129 0% S 1 0K 0K fg root kcryptd_io
2130 0% S 1 0K 0K fg root kcryptd
2151 0% S 1 0K 0K fg root loop3
2154 0% S 1 0K 0K fg root kdmflush
2155 0% S 1 0K 0K fg root kcryptd_io
2156 0% S 1 0K 0K fg root kcryptd
7904 0% S 6 150648K 9140K bg app_50 com.svox.pico
8443 0% S 1 760K 92K fg dhcp /system/bin/dhcpcd
8998 0% S 6 150540K 9136K bg app_34 com.android.defcontainer
9006 0% S 6 152416K 9356K bg app_115 com.menny.android.anysoftkeyboard
9412 0% S 9 173572K 16776K bg system com.android.settings
9703 0% S 6 156128K 9772K bg app_3 com.android.calendar
9732 0% S 8 153824K 10720K bg app_4 android.process.media
9758 0% S 6 150564K 9140K bg app_18 com.motorola.btlowbattery
9839 0% S 6 155300K 9528K bg app_14 com.motorola.blur.contacts.data
10136 0% S 6 150872K 9600K bg app_53 com.motorola.android.datamanager
10143 0% S 7 151952K 9416K bg system com.motorola.process.system
10158 0% S 6 150932K 9388K bg app_41 com.motorola.nabsync
10183 0% S 6 150544K 9112K bg app_92 com.motorola.globalunplug
10191 0% S 6 151700K 9588K bg app_17 com.motorola.android.syncml.service
10650 0% S 12 174768K 11448K bg app_140 com.google.android.apps.maps:NetworkLocationService
10665 0% S 7 153296K 9552K bg app_105 net.rgruet.android.g3watchdog
10673 0% S 6 153700K 9236K bg app_24 com.motorola.togglewidgets
10679 0% S 9 159908K 10400K bg app_24 com.motorola.blur.friendfeed
10689 0% S 8 165296K 9964K bg app_24 com.motorola.blur.contacts
10699 0% S 10 172128K 10496K bg app_24 com.motorola.blur.weather
10706 0% S 9 191972K 10780K bg app_24 com.motorola.blur.quickcontact
10720 0% S 6 158148K 9684K bg app_24 com.motorola.blur.home.other
10727 0% S 7 156504K 9632K bg app_24 com.motorola.blur.home.message
10734 0% S 6 160932K 10504K bg app_116 com.maxmpz.audioplayer
10743 0% S 9 156112K 13168K fg app_93 jackpal.androidterm
10758 0% S 7 152504K 9448K bg app_101 com.noshufou.android.su
11022 0% S 1 648K 156K fg app_93 /system/bin/sh
1160 0% S 1 0K 0K fg root gannet_queue/0
2 0% S 1 0K 0K fg root kthreadd
3 0% S 1 0K 0K fg root ksoftirqd/0
4 0% S 1 0K 0K fg root watchdog/0
5 0% S 1 0K 0K fg root events/0
6 0% S 1 0K 0K fg root khelper
9 0% S 1 0K 0K fg root async/mgr
12 0% S 1 0K 0K fg root suspend
199 0% S 1 0K 0K fg root sync_supers
201 0% S 1 0K 0K fg root bdi-default
207 0% S 1 0K 0K fg root omap_serial
215 0% S 1 0K 0K fg root omap2_mcspi
So the case is someting polling the IO so fast that even system processes starve. Then i tried to get what are the exact processes using so much io. under linux i can do that, and no wonder it works under android too:
echo 1 > /proc/sys/vm/block_dump ; cat /proc/kmsg ; echo 0 > /proc/sys/vm/block_dump
During normal opareation kjournald, and flush-179:32 are the only processes using io wrting logs to mmcblk1p25, but when the phone starts to lag a couple process starts to read mmcblk1p21(the sytem) like hell. This is just a short example:
Code:
<7>[46906.785827] er.ServerThread(1396): READ block 33756 on mmcblk1p21 (8 sectors)
<7>[46906.786437] er.ServerThread(1396): READ block 33804 on mmcblk1p21 (8 sectors)
<7>[46906.786773] er.ServerThread(1396): READ block 33820 on mmcblk1p21 (56 sectors)
<7>[46906.787445] pal.androidterm(10743): READ block 33540 on mmcblk1p21 (8 sectors)
<7>[46906.787994] pal.androidterm(10743): READ block 33588 on mmcblk1p21 (64 sectors)
<7>[46906.803344] pal.androidterm(10743): READ block 591296 on mmcblk1p21 (40 sectors)
<7>[46906.804077] pal.androidterm(10743): READ block 591344 on mmcblk1p21 (8 sectors)
<7>[46906.804626] pal.androidterm(10743): READ block 591360 on mmcblk1p21 (16 sectors)
<7>[46906.804962] pal.androidterm(10743): READ block 591416 on mmcblk1p21 (16 sectors)
<7>[46906.818817] Binder Thread #(1556): READ block 606582 on mmcblk1p21 (16 sectors)
<7>[46906.819244] Binder Thread #(1556): READ block 606614 on mmcblk1p21 (32 sectors)
<7>[46906.819824] Binder Thread #(1556): READ block 606686 on mmcblk1p21 (136 sectors)
<7>[46906.820404] Binder Thread #(1556): READ block 606822 on mmcblk1p21 (2 sectors)
<7>[46906.828674] ConnectivityThr(1416): READ block 215246 on mmcblk1p21 (32 sectors)
<7>[46906.829254] ConnectivityThr(1416): READ block 215286 on mmcblk1p21 (40 sectors)
<7>[46906.829803] ConnectivityThr(1416): READ block 215334 on mmcblk1p21 (64 sectors)
<7>[46906.830139] ConnectivityThr(1416): READ block 215406 on mmcblk1p21 (16 sectors)
<7>[46906.830657] ConnectivityThr(1416): READ block 215430 on mmcblk1p21 (8 sectors)
<7>[46906.831207] ConnectivityThr(1416): READ block 215478 on mmcblk1p21 (24 sectors)
<7>[46906.840393] Binder Thread #(1556): READ block 606826 on mmcblk1p21 (8 sectors)
<7>[46906.853302] WebViewCoreThre(9943): READ block 285914 on mmcblk1p21 (136 sectors)
<7>[46906.862487] WebViewCoreThre(9943): READ block 285698 on mmcblk1p21 (8 sectors)
<7>[46906.881317] Binder Thread #(1556): READ block 214730 on mmcblk1p21 (8 sectors)
<7>[46906.881927] Binder Thread #(1556): READ block 214746 on mmcblk1p21 (24 sectors)
<7>[46906.882446] Binder Thread #(1556): READ block 214866 on mmcblk1p21 (8 sectors)
<7>[46906.887115] ConnectivityThr(1416): READ block 582618 on mmcblk1p21 (216 sectors)
<7>[46906.887695] ConnectivityThr(1416): READ block 582836 on mmcblk1p21 (40 sectors)
<7>[46906.907348] ConnectivityThr(1416): READ block 16492 on mmcblk1p21 (24 sectors)
<7>[46906.907989] ConnectivityThr(1416): READ block 16518 on mmcblk1p21 (50 sectors)
<7>[46906.923339] ConnectivityThr(1416): READ block 314154 on mmcblk1p21 (32 sectors)
<7>[46906.923950] ConnectivityThr(1416): READ block 314210 on mmcblk1p21 (200 sectors)
<7>[46906.938934] ConnectivityThr(1416): READ block 557382 on mmcblk1p21 (12 sectors)
<7>[46906.943695] WebViewCoreThre(9943): READ block 286404 on mmcblk1p21 (160 sectors)
<7>[46906.954528] WebViewCoreThre(9943): READ block 284516 on mmcblk1p21 (8 sectors)
<7>[46906.955291] WebViewCoreThre(9943): READ block 284526 on mmcblk1p21 (192 sectors)
<7>[46906.971923] WebViewCoreThre(9943): READ block 288636 on mmcblk1p21 (2 sectors)
<7>[46906.977264] ConnectivityThr(1416): READ block 557374 on mmcblk1p21 (8 sectors)
<7>[46906.983459] wpa_supplicant(1453): READ block 22688 on mmcblk1p21 (24 sectors)
<7>[46906.984161] wpa_supplicant(1453): READ block 22714 on mmcblk1p21 (232 sectors)
<7>[46906.996124] Binder Thread #(1556): READ block 313806 on mmcblk1p21 (80 sectors)
<7>[46906.996704] Binder Thread #(1556): READ block 313894 on mmcblk1p21 (32 sectors)
<7>[46907.009613] Binder Thread #(1556): READ block 582884 on mmcblk1p21 (256 sectors)
<7>[46907.022583] Binder Thread #(1556): READ block 109822 on mmcblk1p21 (168 sectors)
<7>[46907.031280] Binder Thread #(1556): READ block 583880 on mmcblk1p21 (232 sectors)
<7>[46907.044342] Binder Thread #(1556): READ block 591336 on mmcblk1p21 (8 sectors)
<7>[46907.044799] Binder Thread #(1556): READ block 591352 on mmcblk1p21 (8 sectors)
<7>[46907.045318] Binder Thread #(1556): READ block 591376 on mmcblk1p21 (8 sectors)
<7>[46907.045654] Binder Thread #(1556): READ block 591432 on mmcblk1p21 (48 sectors)
<7>[46907.046234] Binder Thread #(1556): READ block 591488 on mmcblk1p21 (52 sectors)
<7>[46907.059722] Binder Thread #(1556): READ block 215502 on mmcblk1p21 (72 sectors)
<7>[46907.060150] Binder Thread #(1556): READ block 215576 on mmcblk1p21 (40 sectors)
<7>[46907.066314] Binder Thread #(1556): READ block 606430 on mmcblk1p21 (8 sectors)
<7>[46907.066925] Binder Thread #(1556): READ block 606494 on mmcblk1p21 (88 sectors)
<7>[46907.067260] Binder Thread #(1556): READ block 606646 on mmcblk1p21 (40 sectors)
<7>[46907.083068] pal.androidterm(10743): READ block 606422 on mmcblk1p21 (8 sectors)
<7>[46907.084655] WebViewCoreThre(9943): READ block 288894 on mmcblk1p21 (256 sectors)
<7>[46907.098815] WebViewCoreThre(9943): READ block 280340 on mmcblk1p21 (72 sectors)
<7>[46907.099639] WebViewCoreThre(9943): READ block 280414 on mmcblk1p21 (56 sectors)
<7>[46907.105194] WebViewCoreThre(9943): READ block 283472 on mmcblk1p21 (24 sectors)
<7>[46907.113708] WebViewCoreThre(9943): READ block 280566 on mmcblk1p21 (16 sectors)
<7>[46907.114410] WebViewCoreThre(9943): READ block 280814 on mmcblk1p21 (88 sectors)
<7>[46907.119415] WebViewCoreThre(9943): READ block 280470 on mmcblk1p21 (88 sectors)
<7>[46907.132141] WebViewCoreThre(9943): READ block 283048 on mmcblk1p21 (168 sectors)
<7>[46907.140594] WebViewCoreThre(9943): READ block 623044 on mmcblk1p21 (12 sectors)
<7>[46907.149017] WebViewCoreThre(9943): READ block 282172 on mmcblk1p21
after i restart the phone i cannot get the error for at least 8 hours. It has to be something with the data connections but i can get the problem on wifi and on 3g too... So i am clueless Anyone has any idea?
I have the same problem. Reinstall the app didn't help.
I am too dumb to find correct region... adresses...
But 2 ways...
1.
JTAG
Not solved yet...
2.
Via Command... + WinComm...
http://forum.xda-developers.com/showpost.php?p=12798324&postcount=3
Code:
[B]Memcpy[/B] address length
Example:
Memcpy 0x00000000 0x100
On U700 I can dump RAM on 0... but not on S8500...
Any suggestions?
Thanx.
Best Regards
Edit.:
Found in ELFs:
SDRAM_START_ADDR 0x20000000
SDRAM_END_ADDR 0x6CFFFFFF
See Screenshots. If Debug Level is Mid or High... but I don't understand, what my handset say to me...
On U700 in Debug Level Low possible to read something... on S8500 no success yet.
But maybe my fault.
Have you find the secret upload mode?
If you go to Fota in internals menu and Type something in there than bada crashes and you have got the upload mode (light bluascreen than only restart with key). but how to communicate with the device, i had not found any tool on the GSPN from samsung.
Try to memcpy RAM from 0x20000000 and 0x40000000 in S8500/8530.
Under the first one address you should find 128MB (0x8000000) of oneDRAM and under the second one 256MB (0x10000000) of SDRAM.
Rebellos said:
Try to memcpy RAM from 0x20000000 and 0x40000000 in S8500/8530.
Under the first one address you should find 128MB (0x8000000) of oneDRAM and under the second one 256MB (0x10000000) of SDRAM.
Click to expand...
Click to collapse
A small doubt:
http://dev.odroid.com/wiki/odroid-t/pds/FrontPage/s_blockdiagram.jpg
Does LPDDR1 corresponds to SDRAM?
jake792 said:
A small doubt:
http://dev.odroid.com/wiki/odroid-t/pds/FrontPage/s_blockdiagram.jpg
Does LPDDR1 corresponds to SDRAM?
Click to expand...
Click to collapse
SDRAM is kind of RAM, widely used in computers nowadays
http://en.wikipedia.org/wiki/Synchronous_dynamic_random_access_memory
LPDDR is subtype of SDRAM designed for mobile phones, that is Low-Power Ram.
I'm not sure if thats LPDDR1 or LPDDR2 in Waves.
Thanx.Also since total amount of ram is 384mb.. lesser availibility of free ram would be there.
Bump...
I have not managed problem to dump memory...
Maybe in RAM it is possible to catch some uncompressed data...
Thanx in advance.
Best Regards
Blub...
Problem 1 unsolved to read from handset via Command in bada:
Code:
[B]Memcpy[/B] address length
Memory Map...Partition Table etc. would be interesting for me in 2013...
Maybe start with Partition Table...
I need more space for apps_compressed.bin in bada 2 XXLA1...
Other ideas decrease for instance OSP partition... for test...
I have now access to edit direct in Binary Bootloader... aka boot_loader.mbn.
My skills to understand source or ELF files are very very EXTREME limited.
Maybe S8500 and S8530 have easy "partition Block" like partition.bin from S8600...
Thanx for reading.
Best Regards
Edit 1.
In ELF it is easier to find...
Code:
FLASH_MODEM_START_ADDR 0x00400000
FLASH_MODEM_END_ADDR 0x01100000
FLASH_CODE_START_ADDR 0x01100000
FLASH_CODE_END_ADDR (0x03100000+FLASH_FOTA_HOLE_RESERVED_SIZE)
FLASH_CODE_COMPRESS_START_OFFSET 0x800
Hmm.
Code:
01100000
I could check Little Endian... in boot_loader.mbn
XPKG5 need other addresses for RC1 and RC2
Also MBUKI...
I need this to identify addresses in Boot...
Best Regards
http://forum.xda-developers.com/showpost.php?p=20188325&postcount=369
Code:
// firmware qmd ver start addr max length
{ S8500v12 | BADA_APPS, 0x03050000, 0x01100000, 0x03500000 },
{ S8500v12 | BADA_RSRC1, 0x04070000, 0x04800000, 0x06F00000 },
{ S8500v12 | BADA_RSRCS, 0x04070000, 0x0B700000, 0x00F00000 },
{ S8530v12 | BADA_APPS, 0x03050000, 0x01300000, 0x03500000 },
{ S8530v12 | BADA_RSRC1, 0x04070000, 0x04A00000, 0x05000000 },
{ S8530v12 | BADA_RSRCS, 0x04070000, 0x09A00000, 0x00F00000 },
{ S8500v20 | BADA_APPS, 0x04020000, 0x01100000, 0x02000000 },
{ S8500v20 | BADA_RSRC1, 0x05020000, 0x05D00000, 0x05A00000 },
{ S8500v20 | BADA_RSRCS, 0x05020000, 0x03A00000, 0x02300000 },
{ S8530v20 | BADA_APPS, 0x04020000, 0x01300000, 0x02000000 },
{ S8530v20 | BADA_RSRC1, 0x05020000, 0x03600000, 0x04100000 },
{ S8530v20 | BADA_RSRCS, 0x05020000, 0x07700000, 0x01E00000 },
{ S8600 | BADA_APPS, 0x04020000, 0x08000000, 0x02000000 },
{ S8600 | BADA_RSRC1, 0x05020000, 0x0A200000, 0x03200000 },
{ S8600 | BADA_RSRCS, 0x05020000, 0x0D400000, 0x02800000 },
{ S7250D | BADA_APPS, 0x04020000, 0x00E00000, 0x01F00000 },
{ S7250D | BADA_RSRC1, 0x05020000, 0x02F00000, 0x01E00000 },
{ S7250D | BADA_RSRCS, 0x05020000, 0x04D00000, 0x01C00000 },
Perfect overview, very helpfull.
Big thanx b.kubica :good:
Best Regards
Memo to me...
Code:
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co..
Build On: Jun 8 2011 21:44:47
-----------------------------------------------------------
Re_partition: magic code(0x0)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->[B]nNumOfPartEntry = 7[/B]
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : *unknown id* (0x9)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : *unknown id* (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 7
===============================
ID : *unknown id* (0x1)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 8
NO_UNITS : 796
===============================
ID : *unknown id* (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 804
NO_UNITS : 716
===============================
ID : *unknown id* (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1520
NO_UNITS : 372
===============================
ID : *unknown id* (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1892
NO_UNITS : 56
===============================
ID : *unknown id* (0x18)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 1948
NO_UNITS : 56
===============================
It is possible to "identify" partitons on OneNAND via SBL from I9000 etc...
pi->nNumOfPartEntry = 7
bada Bootloader shows something like this:
Code:
[BM : ] FSR_BML_GetFullPartI() is completed
[BM : ] stPartI.nNumOfPartEntry : 7
[BM : ] 1th PartEntrt(nAttr:0x1002)(nID:0x0)
[BM : ] [1th] pPEntry->n1stVun : 1
[BM : ] [1th] [B]pPEntry->nNumOfUnits : 7[/B]
[BM : ] [1th] pPEntry->nLoadAddr : 0x0
+-------------------------------+
| Bootloader Shadowing FINISHED |
+-------------------------------+
Launch Image at 0x42480000
Catched via UART cable... + JTAG...
Will play little bit with
I9000_s1_odin_20100512.pit
and
I9000_s1_odin_20100803.pit
Tasks for 2014...
Learning more about Partitions...
Best Regards
Edit 1.
Short modified I9000_s1_odin_20100512.pit...
Code:
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EF[COLOR="Red"]1[/COLOR] (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SB[COLOR="Red"]1[/COLOR] (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL[COLOR="Red"]1[/COLOR] (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARA[COLOR="Red"]1[/COLOR] (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNE[COLOR="Red"]1[/COLOR] (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVER[COLOR="Red"]1[/COLOR] (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYF[COLOR="Red"]1[/COLOR] (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAF[COLOR="Red"]1[/COLOR] (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACH[COLOR="Red"]1[/COLOR] (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 140
===============================
ID : MODE[COLOR="Red"]1[/COLOR] (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1954
NO_UNITS : 50
===============================
RO I think should mean read only
RW = read/write
SLC and STL
NO_UNITS = Number of ... maybe... not sure
STL = Section Translation Layer (Google for BML FSR and BML STL by Samsung)
unit = 256kB or so
No idea what's SLC, "Single Level Cell" doesn't make much sense here
Probably answer is in there - https://github.com/supercurio/samsung_fsr
About SLC, etc, I wrote something about this here:
http://forum.xda-developers.com/showpost.php?p=33359041&postcount=6
I think the relevant info is in the links...
http://forum.xda-developers.com/showthread.php?t=816449
Found this usefull thread about PIT...
2014 I will play little bit Partition file PIT.
Ideas.
1.
Modifying PIT to 1 partition over the whole size... in my case 512 MB...
To write maxbe Fulldumps...
If this is nonsense during few Security limitations...
2.
Increasing first Partition to write 4 MB boot.bin... to solve this Security thingie...
http://forum.xda-developers.com/showthread.php?t=1250270
So maybe then bada Boot restoreable with SBL...
Summary...
Units seems Blocks... seems 256 KB size...
So I need instead 1 Unit... 16 for Partition 1...
Later more, I will try to "convert" this info from here now:
Code:
==== PARTITION INFORMATION ====
ID : *unknown id* (0x9)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
Taken from here:
http://forum.xda-developers.com/showpost.php?p=49033160&postcount=11
Best Regards
Edit 1.
So bada Partition table/info looks like this... S8500..
Little bit explained... later more
Code:
==========================
ID
ATTR
FIRST_UNIT 0
NO_UNITS 1
00000000-00040000
[B]256 KB[/B]
==========================
ID
ATTR
FIRST_UNIT 1
NO_UNITS 7
00040000-001C0000
1792 KB [B]2 MB[/B]
1835008 Byte
==========================
ID
ATTR
FIRST_UNIT 8
NO_UNITS 796
203776 KB [B]203 MB[/B]
208666624 Byte
==========================
ID
ATTR
FIRST_UNIT 804
NO_UNITS 716
183296 KB [B]183 MB[/B]
187695104 Byte
==========================
ID
ATTR
FIRST_UNIT 1520
NO_UNITS 372
95232 KB [B]95 MB[/B]
97517568 Byte
==========================
ID
ATTR
FIRST_UNIT 1892
NO_UNITS 56
14336 KB [B]14 MB[/B]
14680064 Byte
==========================
ID
ATTR
FIRST_UNIT 1948
NO_UNITS 56
14336 KB [B]14 MB[/B]
14680064 Byte
===========================
Code:
<6>Scanning device for bad blocks
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x92 addr8 0x0
<6>OneNAND eraseblock 146 is an initial bad block
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x5cc addr8 0x0
<6>OneNAND eraseblock 1484 is an initial bad block
<6>OneNAND eraseblock 2047 is an initial bad block
<5>Creating 11 MTD partitions on "(null)":
<5>0x00001f000000-0x00001f500000 : "nv_data"
<5>0x000000400000-0x000009800000 : "fw_block"
<5>0x000000400000-0x000000600000 : "dbl"
<5>0x000000600000-0x000001380000 : "amss"
<5>0x000001300000-0x000003600000 : "apps"
<5>0x000003600000-0x000007700000 : "rsrc1"
<5>0x000007700000-0x000009500000 : "csc"
<5>0x000009500000-0x000009800000 : "fota"
<5>0x000009800000-0x000018f00000 : "stl1"
<5>0x000018f00000-0x00001ec00000 : "stl2"
<5>0x00001ec00000-0x00001f000000 : "secdata"
S8530 UART Log... with latest Android from volk204...
Later I will compare S8500...
Best Regards
S8530 SD-Version ZenDroKat
/proc/mtd
Code:
dev: size erasesize name
mtd0: 00500000 00040000 "nv_data"
mtd1: 09400000 00040000 "fw_block"
mtd2: 00200000 00040000 "dbl"
mtd3: 00d80000 00040000 "amss"
mtd4: 02300000 00040000 "apps"
mtd5: 04100000 00040000 "rsrc1"
mtd6: 01e00000 00040000 "csc"
mtd7: 00300000 00040000 "fota"
mtd8: 0f700000 00040000 "stl1"
mtd9: 05d00000 00040000 "stl2"
mtd10: 00400000 00040000 "secdata"
/proc/partitions
Code:
major minor #blocks name
31 0 5120 mtdblock0
31 1 151552 mtdblock1
31 2 2048 mtdblock2
31 3 13824 mtdblock3
31 4 35840 mtdblock4
31 5 66560 mtdblock5
31 6 30720 mtdblock6
31 7 3072 mtdblock7
31 8 252928 mtdblock8
31 9 95232 mtdblock9
31 10 4096 mtdblock10
253 0 488284 zram0
179 0 1912832 mmcblk0
179 1 602112 mmcblk0p1
179 2 401408 mmcblk0p2
179 3 909311 mmcblk0p3
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 15632384 mmcblk1
179 25 11330560 mmcblk1p1
179 26 18432 mmcblk1p2
179 27 563200 mmcblk1p3
179 28 3719168 mmcblk1p4
http://download.tizen.org/releases/daily/1.0/sbs/
Oh, about PIT...
Check content of file:
lutil.tar.gz
Attached...
Best Regards
Edit 1.
Oh, maybe this helps me to unterstand more...
PIT/XML files
=============
You can convert a PIT file to XML format as follows:
./pit2xml pit/SLP_ALL_Ver04.pit SLP_ALL_Ver04.xml
and back again:
./xml2pit SLP_ALL_Ver04.xml SLP_ALL_Ver04.pit
The relevant data in the file should remain the same.
The XML for SLP_ALL_Ver04.pit looks like this:
Click to expand...
Click to collapse
Edit 2.
According to this example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<partition Name="ipl+recovery" FileName="ipl-recovery.bin" DeltaName="" BlockSize="256" BlockLength="2"/>
<partition Name="pit" FileName="pit" DeltaName="" ID="1" BlockSize="256" BlockLength="2"/>
<partition Name="csa" FileName="csa" DeltaName="" ID="2" BlockSize="256" BlockLength="32"/>
<partition Name="u-boot" FileName="u-boot-whdr.bin" DeltaName="" ID="3" BlockSize="256" BlockLength="4"/>
<partition Name="u-boot_bak" FileName="u-boot-whdr.bin" DeltaName="" ID="4" BlockSize="256" BlockLength="4"/>
<partition Name="params" FileName="params" DeltaName="" ID="5" BlockSize="256" BlockLength="4"/>
<partition Name="config" FileName="config" DeltaName="" ID="6" BlockSize="256" BlockLength="8"/>
<partition Name="kernel" FileName="uImage" DeltaName="" ID="7" BlockSize="256" BlockLength="28"/>
<partition Name="kernel_bak" FileName="uImage" DeltaName="" ID="8" BlockSize="256" BlockLength="28"/>
<partition Name="log" FileName="log" DeltaName="" ID="9" BlockSize="256" BlockLength="5"/>
<partition Name="modem" FileName="modem.img" DeltaName="" BinType="1" ID="10" BlockSize="256" BlockLength="64"/>
<partition Name="qboot" FileName="qboot" DeltaName="" ID="11" BlockSize="256" BlockLength="240"/>
<partition Name="UBI" FileName="ubi.img" DeltaName="" ID="12" Attribute="1" BlockSize="256" BlockLength="1627"/>
<partition Name="movinand" FileName="movinand.bin" DeltaName="" DevType="2" Attribute="1"/>
<partition Name="csc" FileName="rfs_part4.csc" DeltaName="" DevType="2" ID="4" Attribute="1"/>
</root>
I will try to "convert":
Code:
I9000_s1_odin_20100512.pit
I9000_s1_odin_20100803.pit
First by hand and my low brain...
Code:
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : [B]130[/B]
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1944
NO_UNITS : [B]60[/B]
===============================
Aha...
increased reserved space for AMSS... in:
I9000_s1_odin_20100512.pit
Need this for stupid tests... to start with patched SBL...
Best Regards
didn't they already understood and documented every possible part of pit file format?
didn't they already understood
Click to expand...
Click to collapse
Thanx for Link, never seen before...
No idea yet, how easy it is to use... for me.
At the moment for me it is easier to use my little brain + WinHex + example from Samsung Tizen team... in XML Format.
And I am on the older Stuff like I9000 PIT... OneNAND... not eMMC/moviNAND...
No Encryption...
Best Regards
Edit 1.
Short tested this:
http://jenkins.casual-dev.com/job/Analyze PIT File/build
Used this PIT from I9000...
I9000_s1_odin_20100512.pit
Code:
-----BEGIN PIT ANALYSIS-----
PIT Name: T A
PIT Parameter: àú
PIT Parameter: ØC
Entry Count: 13
File Type:
--- Entry #0 ---
ID: 0 Partition Name: IBL+PBL param: S param: e param: r param: v param: e param: r param: \ param: 9 param: 0 param: \ param: T param: o
Filename: boot.bin param: i param: n param: n param: ; param: C param: : param: \ param: P param: r param: o param: g
Block Size: 1 (512B)
Block range: 256 - 256 (hex 0x100 - 0x100)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:6684783 Size: 2097268 FOTA: param: a param: m param: param: F param: i param: l param: e param: s param: \ param: E param: S param: T param: s param: o param: f
The IBL+PBL param: S param: e param: r param: v param: e param: r param: \ param: 9 param: 0 param: \ param: T param: o partition, identified as partition number 0, is 512B in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as boot.bin param: i param: n param: n param: ; param: C param: : param: \ param: P param: r param: o param: g.The partition carries a filesize of 2097268 and an offset of 6684783.
--- Entry #1 ---
ID: 1 Partition Name: PIT
Filename: param: ries.pit
Block Size: 1 (512B)
Block range: 256 - 256 (hex 0x100 - 0x100)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 1, is 512B in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as param: ries.pit.
--- Entry #2 ---
ID: 20 Partition Name: EFS
Filename: efs.rfs
Block Size: 40 (20.5kB)
Block range: 256 - 295 (hex 0x100 - 0x127)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The EFS partition, identified as partition number 20, is 20.5kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as efs.rfs.
--- Entry #3 ---
ID: 3 Partition Name: SBL
Filename: sbl.bin
Block Size: 5 (2.6kB)
Block range: 256 - 260 (hex 0x100 - 0x104)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The SBL partition, identified as partition number 3, is 2.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as sbl.bin.
--- Entry #4 ---
ID: 4 Partition Name: SBL2
Filename: sbl.bin
Block Size: 5 (2.6kB)
Block range: 256 - 260 (hex 0x100 - 0x104)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The SBL2 partition, identified as partition number 4, is 2.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as sbl.bin.
--- Entry #5 ---
ID: 21 Partition Name: PARAM
Filename: param.lfs
Block Size: 20 (10.2kB)
Block range: 256 - 275 (hex 0x100 - 0x113)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The PARAM partition, identified as partition number 21, is 10.2kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as param.lfs.
--- Entry #6 ---
ID: 6 Partition Name: KERNEL
Filename: zImage
Block Size: 30 (15.4kB)
Block range: 256 - 285 (hex 0x100 - 0x11d)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The KERNEL partition, identified as partition number 6, is 15.4kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as zImage.
--- Entry #7 ---
ID: 7 Partition Name: RECOVERY
Filename: zImage
Block Size: 30 (15.4kB)
Block range: 256 - 285 (hex 0x100 - 0x11d)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The RECOVERY partition, identified as partition number 7, is 15.4kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as zImage.
--- Entry #8 ---
ID: 22 Partition Name: FACTORYFS
Filename: factoryfs.rfs
Block Size: 1146 (586.8kB)
Block range: 256 - 1401 (hex 0x100 - 0x579)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The FACTORYFS partition, identified as partition number 22, is 586.8kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as factoryfs.rfs.
--- Entry #9 ---
ID: 23 Partition Name: DBDATAFS
Filename: dbdata.rfs
Block Size: 536 (274.4kB)
Block range: 256 - 791 (hex 0x100 - 0x317)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The DBDATAFS partition, identified as partition number 23, is 274.4kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as dbdata.rfs.
--- Entry #10 ---
ID: 24 Partition Name: CACHE
Filename: cache.rfs
Block Size: 140 (71.7kB)
Block range: 256 - 395 (hex 0x100 - 0x18b)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The CACHE partition, identified as partition number 24, is 71.7kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as cache.rfs.
--- Entry #11 ---
ID: 11 Partition Name: MODEM
Filename: modem.bin
Block Size: 50 (25.6kB)
Block range: 256 - 305 (hex 0x100 - 0x131)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The MODEM partition, identified as partition number 11, is 25.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as modem.bin.
--- Entry #12 ---
[B]ID: 11 Partition Name:
Filename:
Block Size: 0 (0B)
Block range: 0 - -1 (hex 0x0 - 0xffffffff)
FilesystemType: 0 PartType: 0 DevType: 1 BinType: 1
Offset:0 Size: 0 FOTA:
The partition, identified as partition number 11, is 0B in size and carries a raw format. This partition resides on the Raw section of the CP NAND.
[/B]
-----END PIT ANALYSIS-----
Helpfull to understand maybe last few Bytes of PIT...
Anyway... output not 100 % correct, because Blocksize is 256 KB, instead 512 Byte...
Its the difference between eMCC/moviNAND versus OneNAND...
Hello, can anybody with a rooted Gio point me out to the /dev/block files for /system , /data , /cache ?
For example for GSII is /dev/block/mmcblk0p24 25 26
At us i think it should be something with 12/13/14
I need the correct filenames from our Gio. Only names i don`t actually need the files
Thank u in advance
I have CyanogenMod 7.2 installed with ext4 partition on SD.
Here's what "mount" says on my phone (stripped the mounts for individual apps).
I decided to leave other non-/dev/block entries here, too, just in case
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl12 on /system type ext4 (ro,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl13 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/stl14 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /data/app type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /data/data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p2 on /cache/download type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
BML partition layout of the Samsung Galaxy Gio GT-S5660:
bml0: contents of the entire flash
bml1: mibib
bml2: qcsbl
bml3: oemsbl
bml4: amss
bml5: block level representation of /dev/stl5 (efs)
bml6: block level representation of /dev/stl6 (empty)
bml7: arm11boot
bml8: boot image
bml9: recovery image
bml10: unknown
bml11: empty (contains only 0xff bytes)
bml12: block level representation of /dev/stl12 (/system)
bml13: block level representation of /dev/stl13 (/data)
bml14: block level representation of /dev/stl14 (/cache)
STL partition layout of the Samsung Galaxy Gio GT-S5660:
stl5: /efs
stl6: empty partition (contains only 0xff bytes)
stl12: /system
stl13: /data
stl14: /cache
Partition layout used by ODIN (GIO_v1.0.ops):
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
Available partitions according to /proc/partitions:
major minor size device
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 192768 bml13
137 14 29696 bml14
138 12 214784 stl12
138 13 185600 stl13
138 14 25856 stl14
particle.blurringexistence.net/samsung-gt-s5660/partition-layout
Sent from my GT-S5660 using XDA Premium App
Thank u both ! I wanted to try to port DARKSIDE::SUPER::WIPE but it formats in Ext4 and i need in rfs because atm i only use stock rom
Note that my output is from CM which uses ext4, too. No rfs there, sorry
hsrars-d said:
BML partition layout of the Samsung Galaxy Gio GT-S5660:
bml0: contents of the entire flash
bml1: mibib
bml2: qcsbl
bml3: oemsbl
bml4: amss
bml5: block level representation of /dev/stl5 (efs)
bml6: block level representation of /dev/stl6 (empty)
bml7: arm11boot
bml8: boot image
bml9: recovery image
bml10: unknown
bml11: empty (contains only 0xff bytes)
bml12: block level representation of /dev/stl12 (/system)
bml13: block level representation of /dev/stl13 (/data)
bml14: block level representation of /dev/stl14 (/cache)
STL partition layout of the Samsung Galaxy Gio GT-S5660:
stl5: /efs
stl6: empty partition (contains only 0xff bytes)
stl12: /system
stl13: /data
stl14: /cache
Partition layout used by ODIN (GIO_v1.0.ops):
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
Available partitions according to /proc/partitions:
major minor size device
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 192768 bml13
137 14 29696 bml14
138 12 214784 stl12
138 13 185600 stl13
138 14 25856 stl14
particle.blurringexistence.net/samsung-gt-s5660/partition-layout
Sent from my GT-S5660 using XDA Premium App
Click to expand...
Click to collapse
Sorry to bring the thread back up from the ground but i need some info on how to rebuild/force format on block stl13.
Have tried multiple CWM flashes now and stock rom flashes via Odin but stilll no good
Hello!
I managed to flash the CM 12.1 rom but I noticed that the /system partition is barely large enough (585Mb). It is so small that
I can't install the gapps package I need.
I also note that my /userdata partition is 1200Mb.
I would like to decrease the size of the userdata partition and increase the size of the system partition.
I am able to do this fine through adb shell after booting into TWRP recovery - but
the changes don't stick.
In some cases (not sure if it's when I mess up the partition table) - the partition table is simply reset
upon reboot.
In other cases - the partition table is reset - but contains duplicate partitions (as shown below)
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2332 MB, 2332033024 bytes
1 heads, 16 sectors/track, 284672 cylinders, total 4554752 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4554750 2272311 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 137216 3072 4a Unknown
/dev/block/mmcblk0p14 137218 143361 3072 4b Unknown
/dev/block/mmcblk0p15 143363 145410 1024 74 Unknown
/dev/block/mmcblk0p16 145412 163326 8957+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1343486 571391+ 83 Linux
/dev/block/mmcblk0p26 1343488 3749886 1203199+ 83 Linux
/dev/block/mmcblk0p27 3749888 4046846 148479+ 83 Linux
/dev/block/mmcblk0p28 4046848 4358143 155648 83 Linux
/dev/block/mmcblk0p29 4358145 4364286 3071 33 Unknown
/dev/block/mmcblk0p30 4364288 4406782 21247+ 19 Unknown
/dev/block/mmcblk0p31 4406784 4407295 256 23 Unknown
/dev/block/mmcblk0p32 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p33 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p34 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p35 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p36 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p37 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p38 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p39 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p40 131073 137216 3072 4a Unknown
/dev/block/mmcblk0p41 137218 143361 3072 4b Unknown
/dev/block/mmcblk0p42 143363 145410 1024 74 Unknown
/dev/block/mmcblk0p43 145412 163326 8957+ 75 Unknown
/dev/block/mmcblk0p44 163328 163839 256 76 Unknown
/dev/block/mmcblk0p45 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p46 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p47 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p48 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p49 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p50 196096 196607 256 73 Unknown
/dev/block/mmcblk0p51 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p52 200704 1343486 571391+ 83 Linux
/dev/block/mmcblk0p53 1343488 3749886 1203199+ 83 Linux
/dev/block/mmcblk0p54 3749888 4046846 148479+ 83 Linux
/dev/block/mmcblk0p55 4046848 4358143 155648 83 Linux
/dev/block/mmcblk0p56 4358145 4364286 3071 33 Unknown
/dev/block/mmcblk0p57 4364288 4406782 21247+ 19 Unknown
/dev/block/mmcblk0p58 4406784 4407295 256 23 Unknown
/dev/block/mmcblk0p59 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p60 70131 95130 12500 50 Unknown
(Note how partition 32 and onwards are just copies of the earlier ones)
My question is, is there some part of the system that actually tries to repair/reset the partition table after I have changed it - or does TWRP simply not save the changes I do for some reason?
What part of my system might reset the partition table & why?
Thanks!
G710V
My Phone got bricked. Showing as Qualcom 9008.
I use LGUP of V30. Then I select G710T kdz and click start it gave me error at begining even not a Single Partition is flashed. 0x200 then i restart via buttons and then dead.
Talharshad said:
G710V
My Phone got bricked. Showing as Qualcom 9008.
I use LGUP of V30. Then I select G710T kdz and click start it gave me error at begining even not a Single Partition is flashed. 0x200 then i restart via buttons and then dead.
Click to expand...
Click to collapse
There's no way to fix the 9008 mode on these phones yet regardless of how it happened
Hey what variant is the g710v?
Was it factory unlocked?
Sent from my OnePlus 5 using the XDA Premium App
aaya888 said:
i can help you with your problem it's posible to repair LG G4 V10 G5 V20 V30 G6 online "online usbredirector customer module"
you can contact me on skype = Aaya888
https://www.facebook.com/18367302566...991780680/?t=5
Model Settings:
Interface : USB
Core : Qualcomm MSM8996 UFS
Loader : QLoader_v2_LG
Connecting...
Sending loader...OK.
Loader successfully initialized.
INFO: Device Total Logical Blocks: 0x75ec00
INFO: Device Block Size in Bytes: 0x1000
INFO: Device Total Physical Partitions: 0x0
INFO: Device Manufacturer ID: 0x1ad
INFO: Device Serial Number: 0x796e6978
INFO: {"storage_info": {"total_blocks":7728128, "block_size":4096, "page_size":4096, "num_physical":7, "manufacturer_id":429, "serial_num":2037279096, "fw_version":"003","mem_type":"UFS","prod_name":"H28U62301AMR"}}
UFS fInitialized: 0x1
UFS Current LUN Number: = 0xd0
UFS Total Active LU: 0x7
UFS wManufacturerID: 0x1ad
UFS Boot Partition Enabled: 0x1
UFS Raw Device Capacity: = 0x3b9e000
UFS Min Block Size: 0x8
UFS Erase Block Size: 0x2000
UFS Allocation Unit Size: 0x1
UFS RPMB ReadWrite Size: = 0x20
UFS Number of Allocation Uint for This LU: 0x0
UFS Logical Block Size: 0x0
UFS Provisioning Type: 0x0
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x8079
UFS dEnhanced1MaxNAllocU: 0x1dcf
UFS wEnhanced1CapAdjFac: 0x200
UFS dEnhanced2MaxNAllocU: = 0x1dcf
UFS wEnhanced2CapAdjFac: 0x200
UFS dEnhanced3MaxNAllocU: 0x1dcf
UFS wEnhanced3CapAdjFac: 0x200
UFS dEnhanced4MaxNAllocU: 0x0
UFS wEnhanced4CapAdjFac: 0x0
UFS LUN Enable Bitmask: 0x7f
UFS Logical Block Count: 0x0
UFS bConfigDescrLock: 0x0
UFS iManufacturerName String Index: 0x1
UFS iProductName String Index: 0x2
UFS iSerialNumber String Index: 0x3
UFS iOemID String Index: 0x4
UFS Inquiry Command Output: SKhynix H28U62301AMR D003
ACK
Device : SKhynix H28U62301AMR D003
Core : Qualcomm MSM8996 UFS
Page size : 4096 B
Block size : 4096 B
Block count : 7803904
Size : 29.77 GB (30484.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.6.0; FW: 1.23.
Physical partition number: 0
Block count : 7728128 (0x75EC00)
Size : 29.48 GB (30188.00 MB)
P00: GPT (00000000, 00000006) 24 KB
P01: laf (00000006, 00003000) 48 MB
P02: lafbak (00003006, 00003000) 48 MB
P03: mpt (00006006, 00002000) 32 MB
P04: drm (00008006, 00000A00) 10 MB
P05: sns (00008A06, 00000600) 6 MB
P06: misc (00009006, 00002000) 32 MB
P07: factory (0000B006, 00004200) 66 MB
P08: encrypt (0000F206, 00000080) 512 KB
P09: eksst (0000F286, 00000080) 512 KB
P10: rct (0000F306, 00000080) 512 KB
P11: ssd (0000F386, 00000080) 512 KB
P12: keystore (0000F406, 00000080) 512 KB
P13: carrier (0000F486, 00002800) 40 MB
P14: persist (00011C86, 00002000) 32 MB
P15: system (00013C86, 00169800) 5.648 GB
P16: cache (0017D486, 00081800) 2072 MB
P17: userdata (001FEC86, 0055F800) 21.49 GB
P18: grow (0075E486, 00000775) 7.457 MB
Physical partition number: 1
Block count : 8192 (0x2000)
Size : 32.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl (00000006, 00000300) 3072 KB
P02: xblbak (00000306, 00000300) 3072 KB
P03: fota (00000606, 00000400) 4 MB
P04: fsg (00000A06, 00000200) 2048 KB
P05: dip (00000C06, 00000100) 1024 KB
P06: devinfo (00000D06, 00000100) 1024 KB
P07: grow2 (00000E06, 00000001) 4 KB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl2 (00000006, 00000300) 3072 KB
P02: xbl2bak (00000306, 00000300) 3072 KB
P03: grow3 (00000606, 00000001) 4 KB
Physical partition number: 3
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ddr (00000006, 00000200) 2048 KB
P02: reserve (00000206, 00000008) 32 KB
P03: cdt (0000020E, 00000001) 4 KB
P04: grow4 (0000020F, 00000001) 4 KB
Physical partition number: 4
Block count : 59392 (0xE800)
Size : 232.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: boot (00000006, 00002800) 40 MB
P02: recovery (00002806, 00002880) 40.5 MB
P03: recoverybak (00005086, 00002880) 40.5 MB
P04: tz (00007906, 00000200) 2048 KB
P05: tzbak (00007B06, 00000200) 2048 KB
P06: aboot (00007D06, 00000200) 2048 KB
P07: abootbak (00007F06, 00000200) 2048 KB
P08: raw_resources (00008106, 00000400) 4 MB
P09: raw_resourcesbak (00008506, 00000400) 4 MB
P10: rpm (00008906, 00000080) 512 KB
P11: rpmbak (00008986, 00000080) 512 KB
P12: hyp (00008A06, 00000080) 512 KB
P13: hypbak (00008A86, 00000080) 512 KB
P14: pmic (00008B06, 00000080) 512 KB
P15: pmicbak (00008B86, 00000080) 512 KB
P16: devcfg (00008C06, 00000020) 128 KB
P17: devcfgbak (00008C26, 00000020) 128 KB
P18: modem (00008C46, 00005600) 86 MB
P19: sec (0000E246, 00000080) 512 KB
P20: keymaster (0000E2C6, 00000080) 512 KB
P21: keymasterbak (0000E346, 00000080) 512 KB
P22: cmnlib (0000E3C6, 00000080) 512 KB
P23: cmnlibbak (0000E446, 00000080) 512 KB
P24: cmnlib64 (0000E4C6, 00000080) 512 KB
P25: cmnlib64bak (0000E546, 00000080) 512 KB
P26: apdp (0000E5C6, 00000080) 512 KB
P27: msadp (0000E646, 00000080) 512 KB
P28: dpo (0000E6C6, 00000080) 512 KB
P29: grow5 (0000E746, 00000001) 4 KB
Physical partition number: 5
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: modemst1 (00000006, 00000200) 2048 KB
P02: modemst2 (00000206, 00000200) 2048 KB
P03: fsc (00000406, 00000080) 512 KB
P04: grow6 (00000486, 00000001) 4 KB
Physical partition number: 6
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: persistent (00000006, 00000200) 2048 KB
P02: grow7 (00000206, 00000001) 4 KB
Click to expand...
Click to collapse
That's for the Snapdragon 820.
Josh McGrath said:
That's for the Snapdragon 820.
Click to expand...
Click to collapse
INFO: Device Total Logical Blocks: 0xece800
INFO: Device Block Size in Bytes: 0x1000
INFO: Device Total Physical Partitions: 0x0
INFO: Device Manufacturer ID: 0x198
INFO: Device Serial Number: 0x48494241
INFO: {"storage_info": {"total_blocks":15525888, "block_size":4096, "page_size":4096, "num_physical":7, "manufacturer_id":408, "serial_num":1212760641, "fw_version":"100","mem_type":"UFS","prod_name":"THGAF4G9N4LBAIRB0100"}}
UFS fInitialized: 0x1
UFS Current LUN Number: = 0xd0
UFS Total Active LU: 0x7
UFS wManufacturerID: 0x198
UFS Boot Partition Enabled: 0x1
UFS Raw Device Capacity: = 0x7734000
UFS Min Block Size: 0x8
UFS Erase Block Size: 0x2000
UFS Allocation Unit Size: 0x1
UFS RPMB ReadWrite Size: = 0x40
UFS Number of Allocation Uint for This LU: 0x0
UFS Logical Block Size: 0x0
UFS Provisioning Type: 0x0
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x801f
UFS dEnhanced1MaxNAllocU: 0x3b9a
UFS wEnhanced1CapAdjFac: 0x200
UFS dEnhanced2MaxNAllocU: = 0x20
UFS wEnhanced2CapAdjFac: 0x200
UFS dEnhanced3MaxNAllocU: 0x0
UFS wEnhanced3CapAdjFac: 0x0
UFS dEnhanced4MaxNAllocU: 0x0
UFS wEnhanced4CapAdjFac: 0x0
UFS LUN Enable Bitmask: 0x7f
UFS Logical Block Count: 0x0
UFS bConfigDescrLock: 0x0
UFS iManufacturerName String Index: 0x1
UFS iProductName String Index: 0x2
UFS iSerialNumber String Index: 0x3
UFS iOemID String Index: 0x4
UFS Inquiry Command Output: TOSHIBA THGAF4G9N4LBAIRB0100
ACK
Device : TOSHIBA THGAF4G9N4LBAIRB0100
Core : Qualcomm MSM8998 UFS
Page size : 4096 B
Block size : 4096 B
Block count : 15613952
Size : 59.56 GB (60992.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.5.9; FW: 1.23.
Physical partition number: 0
Block count : 15525888 (0xECE800)
Size : 59.23 GB (60648.00 MB)
P00: GPT (00000000, 00000006) 24 KB
P01: laf (00000006, 00003000) 48 MB
P02: lafbak (00003006, 00003000) 48 MB
P03: mpt (00006006, 00002000) 32 MB
P04: drm (00008006, 00000A00) 10 MB
P05: sns (00008A06, 00000600) 6 MB
P06: misc (00009006, 00000100) 1024 KB
P07: ftm (00009106, 00002000) 32 MB
P08: factory (0000B106, 00004200) 66 MB
P09: encrypt (0000F306, 00000080) 512 KB
P10: eksst (0000F386, 00000080) 512 KB
P11: rct (0000F406, 00000080) 512 KB
P12: ssd (0000F486, 00000080) 512 KB
P13: keystore (0000F506, 00000080) 512 KB
P14: persist (0000F586, 00002000) 32 MB
P15: srtc (00011586, 00000800) 8 MB
P16: qni (00011D86, 00001800) 24 MB
P17: pstore (00013586, 00000200) 2048 KB
P18: system (00013786, 0019A200) 6.408 GB
P19: cache (001AD986, 00020000) 512 MB
P20: userdata (001CD986, 00D00E74) 52.01 GB
P21: grow (00ECE7FA, 00000001) 4 KB
Physical partition number: 1
Block count : 8192 (0x2000)
Size : 32.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl (00000006, 00000380) 3584 KB
P02: fota (00000386, 00000400) 4 MB
P03: fsg (00000786, 00000200) 2048 KB
P04: dip (00000986, 00000100) 1024 KB
P05: devinfo (00000A86, 00000100) 1024 KB
P06: grow2 (00000B86, 00000002) 8 KB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: xbl2 (00000006, 00000380) 3584 KB
P02: grow3 (00000386, 00000002) 8 KB
Physical partition number: 3
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: ddr (00000006, 00000200) 2048 KB
P02: cdt (00000206, 00000001) 4 KB
P03: grow4 (00000207, 00000002) 8 KB
Physical partition number: 4
Block count : 71680 (0x11800)
Size : 280.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: boot (00000006, 00002800) 40 MB
P02: recovery (00002806, 00002880) 40.5 MB
P03: recoverybak (00005086, 00002880) 40.5 MB
P04: tz (00007906, 00000200) 2048 KB
P05: tzbak (00007B06, 00000200) 2048 KB
P06: raw_resources (00007D06, 00000400) 4 MB
P07: raw_resourcesbak (00008106, 00000400) 4 MB
P08: rpm (00008506, 00000080) 512 KB
P09: rpmbak (00008586, 00000080) 512 KB
P10: hyp (00008606, 00000080) 512 KB
P11: hypbak (00008686, 00000080) 512 KB
P12: pmic (00008706, 00000080) 512 KB
P13: pmicbak (00008786, 00000080) 512 KB
P14: devcfg (00008806, 00000020) 128 KB
P15: devcfgbak (00008826, 00000020) 128 KB
P16: modem (00008846, 00006E00) 110 MB
P17: sec (0000F646, 00000080) 512 KB
P18: keymaster (0000F6C6, 00000080) 512 KB
P19: keymasterbak (0000F746, 00000080) 512 KB
P20: cmnlib (0000F7C6, 00000080) 512 KB
P21: cmnlibbak (0000F846, 00000080) 512 KB
P22: cmnlib64 (0000F8C6, 00000080) 512 KB
P23: cmnlib64bak (0000F946, 00000080) 512 KB
P24: apdp (0000F9C6, 00000080) 512 KB
P25: msadp (0000FA46, 00000080) 512 KB
P26: dpo (0000FAC6, 00000080) 512 KB
P27: abl (0000FB46, 00000100) 1024 KB
P28: ablbak (0000FC46, 00000100) 1024 KB
P29: limits (0000FD46, 00000001) 4 KB
P30: toolsfv (0000FD47, 00000100) 1024 KB
P31: logfs (0000FE47, 00000800) 8 MB
P32: storsec (00010647, 00000020) 128 KB
P33: storsecbak (00010667, 00000020) 128 KB
P34: grow5 (00010687, 00000002) 8 KB
Physical partition number: 5
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: modemst1 (00000006, 00000200) 2048 KB
P02: modemst2 (00000206, 00000200) 2048 KB
P03: fsc (00000406, 00000080) 512 KB
P04: grow6 (00000486, 00000002) 8 KB
Physical partition number: 6
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000006) 24 KB
P01: frp (00000006, 00000200) 2048 KB
P02: grow7 (00000206, 00000002) 8 KB
Yet again, that is the wrong model. That is not the G7. (!!!).
It's good you can do that particular chipset, but You're really taking a huge hit to your credibility here.
Hi,
Anyone had any luck? I also bricked my G710PM. I tried creating a Partition0.xml for QFIL from the PrimaryGPT_x.bin files extracted from G710EM10b_00_0521.dz but I can't test it because I can't find the correct Firehose file. I've attached the files, maybe it helps someone
DonDie said:
Hi,
Anyone had any luck? I also bricked my G710PM. I tried creating a Partition0.xml for QFIL from the PrimaryGPT_x.bin files extracted from G710EM10b_00_0521.dz but I can't test it because I can't find the correct Firehose file. I've attached the files, maybe it helps someone
Click to expand...
Click to collapse
You'd be very lucky to find d the Firehouse file. Last file that was leaked was for the G4!
There are companies like spammy above that do this but it'd be quicker to just get a warranty replacement from T-Mobile or LG.
F- LG I hope they get a million damaged units cause they won't release the files we need to fix them ourselves
I had the wrong person mentioned. Please ignore
Josh McGrath said:
Wtf is wrong with you? That's for the g6. Yet again you have proved you're ignorance and taken yet another serious blow to your credibility.
Maybe you missed it. The g7 has a different chipset than the 8996, 8998 chipset.
Mods can you please delete this thread? Its this guy and his spam, and incorrect spam at that.
Click to expand...
Click to collapse
Have you watched the movie? Unless it's fake around 13:05 there was a G7 folder with the SDM845 Firehose file.
@ aaya888
Would you mind sharing the file?
DonDie said:
Have you watched the movie? Unless it's fake around 13:05 there was a G7 folder with the SDM845 Firehose file.
@ aaya888
Would you mind sharing the file?
Click to expand...
Click to collapse
I did, and saw it was a g6 with v20 partition tables. And actually, I thought it was the same guy I was correcting over and over and it is not so I have corrected my earlier post. I think they other guy got banned ?
@aaya888
How is the state of H918 (TMO V20) firehose fixin now a days, still no go?
Josh McGrath said:
There's no way to fix the 9008 mode on these phones yet regardless of how it happened
Click to expand...
Click to collapse
contact me i can help you out
Tennolee said:
contact me i can help you out
Click to expand...
Click to collapse
It's not me that needs the help but I know a lot of people could use your help after a hard brick.
Tennolee said:
contact me i can help you out
Click to expand...
Click to collapse
Can you do it remotely and how much will it cost?
DonDie said:
Can you do it remotely and how much will it cost?
Click to expand...
Click to collapse
Hi all, I bricked my Tmobile variant and I have an Octoplus Pro box, however not the right loader. Octoplus only supports EWM version
KennynGGG said:
Hi all, I bricked my Tmobile variant and I have an Octoplus Pro box, however not the right loader. Octoplus only supports EWM version
Click to expand...
Click to collapse
The latest version of Octoplus LG has PM/AWM/EM support (v.2.8.9 but 2.9.2 is out as well):
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
Try selecting the version you wish to flash to, for example, G710AWM and write the .KDZ for that model. Hopefully that un-bricks it for you.
Dont hold me to this as my experience is more HTC/Samsung than LG, I am newer to LG so I dont necessarily know if it will re-write the partitions correctly to fix 9008 but thats where I would start. Trying to flash .KDZ through otcoplus to hopefully recover the device if I were in a bricked situation.
GROOVYJOSHCLARK said:
The latest version of Octoplus LG has PM/AWM/EM support (v.2.8.9 but 2.9.2 is out as well):
G710AWMH - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EM - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
G710EMW - added world’s first Write Firmware (“*.kdz”, “*.oct”), Reset FRP*, Read/Write QCN, Read/Write NVM, Factory Reset
Try selecting the version you wish to flash to, for example, G710AWM and write the .KDZ for that model. Hopefully that un-bricks it for you.
Dont hold me to this as my experience is more HTC/Samsung than LG, I am newer to LG so I dont necessarily know if it will re-write the partitions correctly to fix 9008 but thats where I would start. Trying to flash .KDZ through otcoplus to hopefully recover the device if I were in a bricked situation.
Click to expand...
Click to collapse
THanks, that's the reason I think JTAG pro can't send the loader to mine because it's G710TM which is not listed. I swear somehow that I had that same issue before but was able to fix just not now. Only if I can find the real Test Point to connect to ground. Their picture is very hard to see because it's not the whole motherboard picture just the section where the Test Points are.
Hi, I just changed the firmware on my G710 and LGUP informed Completed, but the phone never turned back on.
I just found out I am also on the Qualcomm 9008. Did you manage to fix your issue?
tks!
i need stock FirmWare for g570v stock rom, if anyone have?