Database Info

Wifi Bug found!

Hi all,
I can easy remake the bug of wifi sleep!
my ip is auto : 192.168.1.23 and work perfect!
why?
tape in terminal emulator:
iproute:
192.168.1.0/24 << 23MAX
if i put a ip fixe 192.168.1.50 the wifi bug in sleep is here!!!
please make a ip fixe in 192.168.1.2/24 Maximum 23 please !!!!
Reboot after

Nice one

i tried it with ...1.23 and it's not working.

yes he work,
put your ip fixe in 192.168.1.23 etc, deactivate and reactivate your wifi
and reboot

Afraid it made no difference to me... (thought I'd try a static address for the hell of it)
With Dynamic IP (assigned via DHCP)
Code:
# ip route
192.168.5.0/24 dev eth0 src 192.168.5.126
default via 192.168.5.1 dev eth0
# #Screen Awake
# ping 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
64 bytes from 192.168.5.1: icmp_seq=1 ttl=64 time=14.5 ms
64 bytes from 192.168.5.1: icmp_seq=2 ttl=64 time=13.7 ms
64 bytes from 192.168.5.1: icmp_seq=3 ttl=64 time=11.9 ms
64 bytes from 192.168.5.1: icmp_seq=4 ttl=64 time=10.5 ms
64 bytes from 192.168.5.1: icmp_seq=5 ttl=64 time=9.33 ms
64 bytes from 192.168.5.1: icmp_seq=6 ttl=64 time=7.44 ms
^C
--- 192.168.5.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 7.446/11.276/14.587/2.462 ms
# #Screen Asleep
# ping 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
64 bytes from 192.168.5.1: icmp_seq=1 ttl=64 time=810 ms
64 bytes from 192.168.5.1: icmp_seq=2 ttl=64 time=732 ms
64 bytes from 192.168.5.1: icmp_seq=3 ttl=64 time=652 ms
64 bytes from 192.168.5.1: icmp_seq=4 ttl=64 time=881 ms
64 bytes from 192.168.5.1: icmp_seq=5 ttl=64 time=806 ms
64 bytes from 192.168.5.1: icmp_seq=6 ttl=64 time=731 ms
^C
--- 192.168.5.1 ping statistics ---
7 packets transmitted, 6 received, 14% packet loss, time 5998ms
rtt min/avg/max/mdev = 652.954/769.292/881.775/73.098 ms
With Static IP (low-range)
Code:
# ip route
192.168.5.0/24 dev eth0 src 192.168.5.7
default via 192.168.5.1 dev eth0
# #Screen Awake
# ping 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
64 bytes from 192.168.5.1: icmp_seq=1 ttl=64 time=1.92 ms
64 bytes from 192.168.5.1: icmp_seq=2 ttl=64 time=43.6 ms
64 bytes from 192.168.5.1: icmp_seq=3 ttl=64 time=14.5 ms
64 bytes from 192.168.5.1: icmp_seq=4 ttl=64 time=2.22 ms
64 bytes from 192.168.5.1: icmp_seq=5 ttl=64 time=10.8 ms
64 bytes from 192.168.5.1: icmp_seq=6 ttl=64 time=9.36 ms
^C
--- 192.168.5.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 1.923/13.753/43.640/14.108 ms
# #Screen Asleep
#
# ping 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
64 bytes from 192.168.5.1: icmp_seq=1 ttl=64 time=710 ms
64 bytes from 192.168.5.1: icmp_seq=2 ttl=64 time=937 ms
64 bytes from 192.168.5.1: icmp_seq=3 ttl=64 time=860 ms
64 bytes from 192.168.5.1: icmp_seq=4 ttl=64 time=781 ms
64 bytes from 192.168.5.1: icmp_seq=5 ttl=64 time=702 ms
^C
--- 192.168.5.1 ping statistics ---
6 packets transmitted, 5 received, 16% packet loss, time 5002ms
rtt min/avg/max/mdev = 702.759/798.571/937.408/89.778 ms
I've found this on Google Bugs... Explains what it could possibly be...
http://code.google.com/p/android/issues/detail?id=9781
Also, where you say 23 is MAX, it isn't...
IP Address ranges are defined like that....
It designates a network address in the CIDR notation (Classless Inter-Domain Routing) which is defined in >RFC 1519<. It provides a more flexible notation of network addresses for subnets. The Number after the slash (/) in your case 24 bescribes how many bits of an anddress a uses as network bits, since here the typical subdivision in classes (A=8,B=16,C=24 bits) is no longer the only way to subclass.
So with 192.168.1.0/24 you have still your typical C-class IPv4 network with addresses form 192.168.1.0 - 192.168.1.255.
But you could have the following as well: 192.168.1.0./22 this denotes IPv4 addresses starting at 192.168.1.0 and ending at 192.168.4.255 inclusive, with 192.168.4.255 being the broadcast address for the given network.

wifi policy set to never and i use ip fix with 192.168.1.23 but it's not working goes to sleep. wifi turned off and later turned on but it's not changing result.

I've found this on Google Bugs... Explains what it could possibly be...
http://code.google.com/p/android/issues/detail?id=9781
Also, where you say 23 is MAX, it isn't...
IP Address ranges are defined like that....
It designates a network address in the CIDR notation (Classless Inter-Domain Routing) which is defined in >RFC 1519<. It provides a more flexible notation of network addresses for subnets. The Number after the slash (/) in your case 24 bescribes how many bits of an anddress a uses as network bits, since here the typical subdivision in classes (A=8,B=16,C=24 bits) is no longer the only way to subclass.
So with 192.168.1.0/24 you have still your typical C-class IPv4 network with addresses form 192.168.1.0 - 192.168.1.255.
But you could have the following as well: 192.168.1.0./22 this denotes IPv4 addresses starting at 192.168.1.0 and ending at 192.168.4.255 inclusive, with 192.168.4.255 being the broadcast address for the given network.
Click to expand...
Click to collapse
LOL never been so confused in my life

me too, ...
When i put my ip in 192.168.1.1/23 no wifi sleep issue ... after 23 ... issue bug for me

meLIanTQ said:
me too, ...
When i put my ip in 192.168.1.1/23 no wifi sleep issue ... after 23 ... issue bug for me
Click to expand...
Click to collapse
Tried your proposal but no success. I even configured my router to only DHCP the IPs you mentioned.
I think Paul is right here and is it hard to understand what HTC is doing for this? I.e. reverse engineer their ROMs and see how they solve the problem.

[Q] how to update android emulator truststore?

Hi,
i want to setup network traffic sniffing of an application. So I started a proxy on my computer and started the app in the emulator.
It works fine with http but for https traffic it does not work as the cert provided by the proxy is obviously not trusted by the default android os.
So i tried to update the truststore(/system/etc/security/cacertsnew.bks) with my proxy cert.
I copied the file to my computer and added my cert, but i'm having difficulties with putting it back to android.
I remounted the /system in write mode (./adb shell mount -o remount,rw /dev/block/mtblock3 /system) but i get 0 bytes available space, and can't write anything to it.
xxxxx-mac:tools xxxxx$ ./adb shell df
/dev: 47048K total, 0K used, 47048K available (block size 4096)
/mnt/asec: 47048K total, 0K used, 47048K available (block size 4096)
/system: 77568K total, 77568K used, 0K available (block size 4096)
/data: 65536K total, 20304K used, 45232K available (block size 4096)
/cache: 65536K total, 1156K used, 64380K available (block size 4096)
/mnt/sdcard: 129024K total, 1K used, 129022K available (block size 512)
/mnt/secure/asec: 129024K total, 1K used, 129022K available (block size 512)
Do you know any trick to be able to write to /system?
Or is there any way to change the image file to include my modified cacerts.bks file?
Thanks

Come on guys, I know this is not such a tough question for you!

[Q] Apps disappeared

I am trying to bring them back (with the data). As a bonus I would like that it does not repeat. And maybe optimizing the configuration of the phone in the meanwhile.
I have a EVO 4G running GingerBread 2.3.5 running the Nitrous 1.4.7 ROM (See http://forum.xda-developers.com/showthread.php?t=1486126 for change log) based on + OTA 4.67.651.3.
A few days ago when I went to use the phone, it had an error when I try to ignore it, it started bringing up new ones. I rebooted and pretty much all applications were gone.
I connected the SD-Card to a linux box and run fsck. Apparently nothing was found. I also used recovery (ClockworkMod 5.0.2.2) to wipe the dalvik-cache and /cache partition. I looked at the log of formatting "/cache" it says that there are 3 blocks that were bad so they did not get formatted ("mtd: not erasing bad block at xxxxxxx").
After that the apps that according to App2SD are on the SD came back. That was odd because I though that I hada problem with the SD that was worn out but this seems to says that instead it was the internal memory to be worn out.
I started some investigation with adb shell. And I found that a:
cd /system/sd/app
ls -l
Show all the apps that are supposedly on the phone (the one that I am not able to see under "applications" and on the homescreens.
So I am not an expert on android and Linux devices and I am not sure what is going on.
Any help would be appreciated.
Best,
Camicia
Extra info:
I was trying to find out with physical device (internal memory or SD) is attached at the different folders. But I do not understand it all.
Ideally I would like to have SDExt on SD and the DalvikCache on SD too. Maybe App2SD and A2SD are interacting with each others... I am not sure.
You tell me:
sh-3.2# df
/dev: 207100K total, 64K used, 207036K available (block size 4096)
/mnt/asec: 207100K total, 0K used, 207100K available (block size 4096)
/mnt/obb: 207100K total, 0K used, 207100K available (block size 4096)
/app-cache: 8192K total, 0K used, 8192K available (block size 4096)
/system: 358400K total, 238948K used, 119452K available (block size 4096)
/data: 437888K total, 336452K used, 101436K available (block size 4096)
/cache: 163840K total, 1680K used, 162160K available (block size 4096)
/system/sd: 937096K total, 78058K used, 859038K available (block size 1024)
/mnt/sdcard: 6696848K total, 3303280K used, 3393568K available (block size 4096)
/mnt/secure/asec: 6696848K total, 3303280K used, 3393568K available (block size 4096)
/mnt/asec/com.waze-1: 20764K total, 18996K used, 1768K available (block size 4096)
/mnt/asec/com.roamingsquirrel.android.calculator-1: 3124K total, 1420K used, 1704K available (block size 4096)
/mnt/asec/com.google.android.diskusage-2: 2088K total, 164K used, 1924K available (block size 4096)
/mnt/asec/de.stohelit.audiobookplayer-1: 5200K total, 3500K used, 1700K available (block size 4096)
/mnt/asec/com.duduapps.craigslistfree-2: 2088K total, 644K used, 1444K available (block size 4096)
/mnt/asec/com.evernote-2: 10388K total, 8752K used, 1636K available (block size 4096)
/mnt/asec/com.instagram.android-1: 16612K total, 15264K used, 1348K available (block size 4096)
/mnt/asec/com.blio.androidreader-1: 25952K total, 24220K used, 1732K available (block size 4096)
/mnt/asec/gbis.gbandroid-1: 3124K total, 1596K used, 1528K available (block size 4096)
/mnt/asec/es.expectro.revelan-2: 2088K total, 700K used, 1388K available (block size 4096)
/mnt/asec/org.lds.ldssa-1: 7276K total, 5192K used, 2084K available (block size 4096)
/mnt/asec/com.ihunda.android.binauralbeat-1: 3124K total, 1704K used, 1420K available (block size 4096)
/mnt/asec/com.adobe.reader-2: 12464K total, 10476K used, 1988K available (block size 4096)
/mnt/asec/com.google.zxing.client.android-1: 2088K total, 612K used, 1476K available (block size 4096)
/mnt/asec/com.biggu.shopsavvy-1: 7276K total, 5600K used, 1676K available (block size 4096)
/mnt/asec/com.quora.android-1: 6236K total, 4404K used, 1832K available (block size 4096)
/mnt/asec/mobi.mgeek.TunnyBrowser-2: 5200K total, 3968K used, 1232K available (block size 4096)
/mnt/asec/org.mozilla.firefox-1: 21800K total, 19692K used, 2108K available (block size 4096)
/mnt/asec/com.a0soft.gphone.app2sd-2: 3124K total, 1136K used, 1988K available (block size 4096)
/mnt/asec/com.keramidas.TitaniumBackup-2: 7276K total, 5600K used, 1676K available (block size 4096)
/mnt/asec/com.fitnesskeeper.runkeeper.pro-1: 6236K total, 4836K used, 1400K available (block size 4096)
/mnt/asec/com.wsl.noom-1: 10388K total, 8760K used, 1628K available (block size 4096)
/mnt/asec/com.estrongs.android.pop-1: 4164K total, 2368K used, 1796K available (block size 4096)
sh-3.2# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 202.2M 64.0K 202.2M 0% /dev
tmpfs 202.2M 0 202.2M 0% /mnt/asec
tmpfs 202.2M 0 202.2M 0% /mnt/obb
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mtdblock4 350.0M 233.3M 116.7M 67% /system
/dev/block/mtdblock6 427.6M 328.6M 99.1M 77% /data
/dev/block/mtdblock5 160.0M 1.6M 158.4M 1% /cache
/dev/block/mmcblk0p2 915.1M 76.2M 790.1M 9% /system/sd
/dev/block/vold/179:1
6.4G 3.1G 3.2G 49% /mnt/sdcard
/dev/block/vold/179:1
6.4G 3.1G 3.2G 49% /mnt/secure/asec
/dev/block/dm-0 20.3M 18.6M 1.7M 91% /mnt/asec/com.waze-1
/dev/block/dm-1 3.1M 1.4M 1.7M 45% /mnt/asec/com.roamingsquirrel.android.calculator-1
/dev/block/dm-2 2.0M 164.0K 1.9M 8% /mnt/asec/com.google.android.diskusage-2
/dev/block/dm-3 5.1M 3.4M 1.7M 67% /mnt/asec/de.stohelit.audiobookplayer-1
/dev/block/dm-4 2.0M 644.0K 1.4M 31% /mnt/asec/com.duduapps.craigslistfree-2
/dev/block/dm-5 10.1M 8.5M 1.6M 84% /mnt/asec/com.evernote-2
/dev/block/dm-6 16.2M 14.9M 1.3M 92% /mnt/asec/com.instagram.android-1
/dev/block/dm-7 25.3M 23.7M 1.7M 93% /mnt/asec/com.blio.androidreader-1
/dev/block/dm-8 3.1M 1.6M 1.5M 51% /mnt/asec/gbis.gbandroid-1
/dev/block/dm-9 2.0M 700.0K 1.4M 34% /mnt/asec/es.expectro.revelan-2
/dev/block/dm-10 7.1M 5.1M 2.0M 71% /mnt/asec/org.lds.ldssa-1
/dev/block/dm-11 3.1M 1.7M 1.4M 55% /mnt/asec/com.ihunda.android.binauralbeat-1
/dev/block/dm-12 12.2M 10.2M 1.9M 84% /mnt/asec/com.adobe.reader-2
/dev/block/dm-13 2.0M 612.0K 1.4M 29% /mnt/asec/com.google.zxing.client.android-1
/dev/block/dm-14 7.1M 5.5M 1.6M 77% /mnt/asec/com.biggu.shopsavvy-1
/dev/block/dm-15 6.1M 4.3M 1.8M 71% /mnt/asec/com.quora.android-1
/dev/block/dm-16 8.1M 6.9M 1.2M 85% /mnt/asec/org.lds.ldstools-1
/dev/block/dm-17 5.1M 3.9M 1.2M 76% /mnt/asec/mobi.mgeek.TunnyBrowser-2
/dev/block/dm-18 21.3M 19.2M 2.1M 90% /mnt/asec/org.mozilla.firefox-1
/dev/block/dm-19 3.1M 1.1M 1.9M 36% /mnt/asec/com.a0soft.gphone.app2sd-2
/dev/block/dm-20 7.1M 5.5M 1.6M 77% /mnt/asec/com.keramidas.TitaniumBackup-2
/dev/block/dm-21 6.1M 4.7M 1.4M 78% /mnt/asec/com.fitnesskeeper.runkeeper.pro-1
/dev/block/dm-22 10.1M 8.6M 1.6M 84% /mnt/asec/com.wsl.noom-1
/dev/block/dm-23 4.1M 2.3M 1.8M 57% /mnt/asec/com.estrongs.android.pop-1

I fixed it with:
rm -rf /data/app
ln -s /system/sd/app /data/app
I noticed that /data/app was empty and when I saw http://code.google.com/p/android-roms/wiki/A2SD something clicked.
Still curious to understand what is the physical mapping of my device and how I could improve it to get more memory and stability.
Best,
Chris

Can't Move App, insufficient storage availble

Any big Apks my Z5 tries this error when using built in Apps to SD function..
I'm at a loss.. Card is 32gb with over 20gb available.. Smaller apps are OK, it just seems to be with the bigger applications..
Any ideas what could be causing this.. ??
That being said Sony Storage Checker can move them over without a hitch, sadly it moves anything movable and doesnt allow you to select the apps you wish to move and those you don't..

and the answer... Bad coding from Google it seems..
No wonder my S5 didn't have the issue as it was running Lollipop 5.01
Known to affect at least Android 5.02 and 5.1. Using the Settings / Apps / Move to SD card feature on devices with external sd cards fails with apps larger than a certain size. It throws an error message saying "Couldn't move app. Not enough storage space" no matter how much free space is available. When the framework sends the command to generate the container file on the SD card for the app, it also starts a timer. If the process takes too long, the timer expires. The other part of the bug confuses the framework and sends the wrong notification up (insufficient space).
There is a maximum package size that the App2SD feature can handle due to this bug. That size is a function of the card's write speed, since the timeout is constant. A faster card will permit larger apps to be moved.
Suggestion for a fix would be to calculate a more appropriate timeout value based on the actual write speed * size of data to move + padding, or throw a timeout dialog box asking to abort or continue.
Relevant logcat:
08-07 11:26:41.750 I/LaunchCheckinHandler( 848): Displayed com.android.settings/.SubSettings,wp,ca,352
08-07 11:26:41.750 I/ActivityManager( 848): Displayed com.android.settings/.SubSettings: +352ms
08-07 11:26:41.762 I/Keyboard.Facilitator( 1340): onFinishInput()
.
.
.
08-07 11:27:08.971 I/make_ext4fs( 247): SELinux: Loaded file_contexts from /file_contexts
08-07 11:27:08.971 I/make_ext4fs( 247): Creating filesystem with parameters:
08-07 11:27:08.971 I/make_ext4fs( 247): Size: 240648192
08-07 11:27:08.972 I/make_ext4fs( 247): Block size: 4096
08-07 11:27:08.972 I/make_ext4fs( 247): Blocks per group: 32768
08-07 11:27:08.972 I/make_ext4fs( 247): Inodes per group: 7344
08-07 11:27:08.972 I/make_ext4fs( 247): Inode size: 256
08-07 11:27:08.972 I/make_ext4fs( 247): Journal blocks: 0
08-07 11:27:08.972 I/make_ext4fs( 247): Label:
08-07 11:27:08.972 I/make_ext4fs( 247): Blocks: 58752
08-07 11:27:08.973 I/make_ext4fs( 247): Block groups: 2
08-07 11:27:08.973 I/make_ext4fs( 247): Reserved block group size: 15
08-07 11:27:08.973 I/make_ext4fs( 247): Created filesystem with 11/14688 inodes and 959/58752 blocks
08-07 11:27:09.079 I/Vold ( 247): Filesystem (ext4) formatted OK
08-07 11:27:09.089 E/VoldConnector( 848): NDC Command {98 asec create smdl1534643135.tmp 225 ext4 [scrubbed] 10010 1} took too long (24191ms)
08-07 11:27:09.094 D/DefContainer( 8275): Copying /data/app/com.ironhidegames.android.kingdomrushori​gins.humble-1/base.apk to /mnt/asec/smdl1534643135.tmp/base.apk
.
Click to expand...
Click to collapse
Ah well I needed to buy a faster Micro Sd Card anyway..
Class 10 not enough it seems..

jonoathome said:
and the answer... Bad coding from Google it seems..
No wonder my S5 didn't have the issue as it was running Lollipop 5.01
Ah well I needed to buy a faster Micro Sd Card anyway..
Class 10 not enough it seems..
Click to expand...
Click to collapse
It was a security feature they added, which is a pain in the backside (you don't have write permissions from that file system location to the SD Card)
There is class 10 and then there is class 10 (class 10 is the highest) all it means is guaranteed to be no less than 10MB/s

[DEAD] Crius Mea Q7A+ - Qualcomm MSM8625 SoC ARMv7-A arch DEAD

ⴰⵣⵓⵍ,
When i say dead, it's typically dead.
The tablet is a Crius Mea Q7A+, uses the Qualcomm MSM8625 SoC based on the ARMv7-A arch that combines 2 ARM Cortex-A5.
While this tablet was just bricked for a long while, and i couldn't and didn't have time and firmware to reflash it, since it's one of those useless chinese low end tablets.
Having such a desirable SoC for a programmer i thought i can test on it my first steps bootloaders and Embedded OS while developing them for this sole purpose.
ⵣ Space to avoid readers jumping lines ⵣ
The tablet after i flashed it with a lower firmware of an equivalent or almost another SoC, was booting in fastboot mode only thinking that i could get more info's with that about partitions.
I didn't, so what i did was erasing the modem partition, and that left the tablet open as a generic storage drive, i saved almost every information i could have about this SoC, the partition that were available, Qualcomm's boot sequence, UART serial connection of the SoC, and read for week several pages to gather information useful to make a bootloader.
ⵣ Space to avoid readers jumping lines ⵣ
At the end i failed, i thought i could repartition the Flash memory of the SoC to prepare it for future uploading of my bootloader, there was a partition that is miss aligned, which was maybe the 3gb internal storage, so what i did is delete the partition and recreate it erasing the secondary ones, it was working normally as expected.
But then tomorrow i decided to plug the tablet again, but it doesn't get detected, this happened before, i cant really explain how the Primary core is trying to establish connection with the PC, but it's a bad mofo. Still it was detected all the time if i remember well.
But today the tablet was dead, i can even feel the SoC is not responding at all.
Not even detected when plugged to PC.
The battery does charges, cause i tested with a diode since i dont have a multimeter, which burned even with a resistor after the current was too high, but then with a DC brushless motor.
Mainly the charging circuit is separated from other components and connected directly to DC, that's why it's charging.
I opened the tablet, and took off the battery cables thinking i might be able to get the core to QDload mode which pressing some combinations...
And yeah i tried every combination i can think off, i even tried pressing my mouse in the PC and pressing the Vol UP in the tablet... am so funny.
I hope anyone can tell me a way to communicate with the SoC in this state, or any other solution thanks peace.
Finally i forgot the partition i saved as a text before i repartitioned the last ones only :
Code:
Disk /dev/sdd: 3.7 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 1 40 40 20K 4d QNX4.x
/dev/sdd2 41 540 500 250K 45 unknown
/dev/sdd3 541 102940 102400 50M c W95 FAT32 (LBA)
/dev/sdd4 102941 7634943 7532003 3.6G 5 Extended
/dev/sdd5 131072 135167 4096 2M 46 unknown
/dev/sdd6 135168 141311 6144 3M 58 unknown
/dev/sdd7 141312 147455 6144 3M 4a unknown
/dev/sdd8 147456 153599 6144 3M 4b unknown
/dev/sdd9 153600 157695 4096 2M 5d unknown
/dev/sdd10 157696 165887 8192 4M 90 unknown
/dev/sdd11 165888 167935 2048 1M 63 GNU HURD or SysV
/dev/sdd12 167936 169471 1536 768K 47 unknown
/dev/sdd13 169472 196623 27152 13.3M 60 unknown
/dev/sdd14 196624 217103 20480 10M 91 unknown
/dev/sdd15 217104 413711 196608 96M 83 Linux
/dev/sdd16 413712 440863 27152 13.3M 48 unknown
/dev/sdd17 440864 1362463 921600 450M 83 Linux
/dev/sdd18 1362464 1567263 204800 100M 83 Linux
/dev/sdd19 1567264 1567303 40 20K 4c unknown
/dev/sdd20 1567304 4536903 2969600 1.4G c W95 FAT32 (LBA)
/dev/sdd21 4536904 7510599 2973696 1.4G 83 Linux
/dev/sdd22 7510600 7634942 124343 60.7M 83 Linux
As you can the sdd4 partition was overlapping other partitions sectors so i had to erase it, the rest got erased in the way, but the main boot and from 1 to 3 are intact.
Something else, the MSM7627a is a close SoC to this one, except for the one i have got 2 Cores instead of one, and supports LPDDR and have a more developed GPU, here's a note i wrote :
Code:
MSM7627 seems close enough to the MSM8625, except that it uses a single core ARMv7-A CORTEX A5.
Which is the primary core that we need to boot up, then add the next core to the equation for the kernel.
Some differences about the MSM7627a and the MSM8625 :
MSM7627a | MSM8625
CPU Clock Speed 1,000MHz 1,200MHz
CPU Cores 1 2
GPU Qualcomm Adreno 200 Qualcomm Adreno 203
RAM Interface LPDDR2 SDRAM LPDDR, LPDDR2 SDRAM
As we can see here, they are almost identical, except for the cores which wont make a wall since we're making a bootloader, the GPU... and the RAM interface
Am on Debian Stretch and i dont have any ways of visualization but i accept any link on any platform. Thanks everyone peace again
I also want to add, that i can feel a bit of heat over the tablet it's certainly not from the battery, i dont really know if its coming from the SoC, but if it is am really glad he's doing some cycles.

And i thought i had a chance in this forum lol. looks like am on ma own.