Database Info

[Q] gt-i9003sl odd boot loop

Hi every body.
I have a gt-i9003sl that I'm trying to fix.
It was never flashed or root, and one day, it start to slowly screw, for finishing by boot looping.
Well, I know there is a lot of theads about boot loop on gt-i9003sl.
I read a lot of them, I tried a lot of things, and no solution find in xda-developers or else where, worked.
But today, the phone works, but not as I want.
I get from here http://forum.xda-developers.com/showthread.php?p=12310841#post12310841 the XKPQ rom.
I flash the phone with. (I used heimdall under Debian Sid)
I put a 4 go and 16 go microsd in the phone.
Make three partition before :
1 Partion fat16
1 fat32
an other fat16
turn on the phone, and after reboot the recovery menu, the phone works.
Nothing else done.
I tryed it many times, and it always works.
But the phone use only 297.94 mo for the first fat16 partition.
1.87 go for the second fat32 partition.
959.94 mo for the last fat16 partition.
Even if I make greater partition size, the recovery is lunched at boot, and every changes are canceled.
Moreover I dont have anymore access to the external memory from the phone.
When i try to mount sdcard or usb, the system seems to try something, but nothing happen.
And if I erase from android menu, memories (sd and usb), at boot, recovery menu is lunched again, and the phone is reset.
It erases the whole sdcard.
last but not the least, the camera doesn't work.
Android asks to "turn off usb storage before using camera".
How can I use the whole memory?
How can I get back the camera?
Thank you

work in progress
Hi
I found something that bring back the camera.
I fallow this post and it works :
http://forum.xda-developers.com/showpost.php?p=32969876&postcount=24
But I have always the same problem, the phone partioning itself the 16go sdcard :
1 fat32
1 Partion fat16
1 fat32
an other fat16
and make
/dev/block/mmcblk0p3
the main storage.
How can I change the /dev/block/mmcblk0p3 size and type (like ext4?).
How and why android make these changes?

initrd
Hi
I think I begin to understand.
Changes made by android, are hardcoded in the kernel.
It's like linux kernel...
At least, I understand this from here :
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
So I have to modify the 'initrd.img' like image.
Where is it?
And I have some questions :
Why when I remove the micro sdcard, I see this from adb :
Code:
# parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
Retry/Cancel?
and :
Code:
ls /dev/block
bml0!c bml4 loop2 ram10 ram4 stl11 stl7 tfsr13 tfsr9
bml1 bml5 loop3 ram11 ram5 stl12 stl8 tfsr2 zram0
bml10 bml6 loop4 ram12 ram6 stl13 stl9 tfsr3
bml11 bml7 loop5 ram13 ram7 stl2 tfsr0!c tfsr4
bml12 bml8 loop6 ram14 ram8 stl3 tfsr1 tfsr5
bml13 bml9 loop7 ram15 ram9 stl4 tfsr10 tfsr6
bml2 loop0 ram0 ram2 stl1 stl5 tfsr11 tfsr7
bml3 loop1 ram1 ram3 stl10 stl6 tfsr12 tfsr8
Code:
mount -a
mount: mounting /dev/block/mmcblk0p3 on /data failed: No such file or directory
mount: mounting /dev/block/mmcblk0p1 on /emmc failed: No such file or directory
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory
Where are :
/dev/block/mmcblk0p3
/dev/block/mmcblk0p2
/dev/block/mmcblk1p1
Is it very usefull to have swap partition in android?
Thanks

Flashing First ROM - System Reading as 15 MB !!

Hi everyone,
I have successfully unlocked bootloader and flashed CWM...
now, I have downloaded Xperience CN10 & Gapps Packages to my external sd card.
I have then performed a factory reset in recovery, and formatted System.
After this, I went to flash the ROM .zip from recovery, and it fails staying symlink fails.
When I run "adb shell busybox df -h" to get partition infomation, this is the output:
tmpfs 204.5M 48.0K 204.4M 0% /dev
/dev/block/mmcblk0p12 157.6M 4.3M 153.3M 3% /cache
/dev/block/mmcblk0p17 2.0G 384.0K 2.0G 0% /sdcard
/dev/block/mmcblk1p1 1.8G 1.1G 731.6M 61% /external_sd
/dev/block/mmcblk0p10 15.8M 15.8M 0 100% /system
So why is my system reading as 15.8MB ???

GT-P5100 in read only

Hello to all
I am fighting since 2 weeks with a GT-P5100 that seems to be in read only and in boot loop (it shows the CM9 boot animation and then reboot ...). This after a simple update of some apps that seems to have corrupted the sdcard inside ...
I have tried to clear the cache and the user data via the recovery mode, but nothing happen ... (boot in recovery, choose to wipe data/factory reset and wipe cache partition)
To make a long story short:
I am able to boot in recovery and enter as root via adb. Whatever change I do in the filesystem it seems to be done, but when I unmount/mount the fs or reboot I find the same initial situation !
So for example:
a) enter as root, mount /data, delete data content via rm -rf /data/* ... then if I do ls -la /data I see the device empty ... if I unount /data and then mount /data .. all the files are there !!!! :-O
b) enter as root and activate parted ... remove the data partition (for me n. 10) and quit. Run parted again and the partition is still there :-O
c) enter as root and touch a file in any filesystem ... when I ls after I can see the file ... as soon as I reboot, not such file is there
I have tried with ODIN and HEIMDAL (booting in download mode or fastboot mode) also to flash new system.img from stock roms and different recovery.img (currently I have CWM-based recovery v6.0.1.0)... no way. system.img flash does not work, while recovery.img flash say ok, but when I reboot in recovery mode still find always the same partition :-O
It seems somehow that the overall internal disk is in read only and - I do not understand why - when I do changes they are recorded locally, but when I reboot the fs really does not store anything.
BTW, this is my partition table
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 15.2GB 12.9GB ext4 DATAFS
11 15.2GB 15.8GB 537MB ext4 HIDDEN
Any idea ?

[Resolved] Huawei P8 Lite - Flashing shrinked the /data partition

Some info:
Code:
Phone: Huawei P8 Lite (ALE-L21) - 1 SIM
So, i've been rooting my device and got it working after probably 12 hours of downloading Firmwares that were corrupted and had slow download speed and flashing up to 12 updates.
I got it working, still not rooted but i can live with that. TWRP is enough.
The problem is, I've downloaded some apps, and some updates were applied from Google Play.
What I've encountered is that the memory is just 2G big!
That's so strange, because I've already had a bigger storage size before flashing.
I'll show you what's the problem:
As i've found out, mmcblk0 is the internal NAND memory.
So, we fetch the partition table which is stored in mmcblk0
Code:
/data # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 30785536 sectors, 2744M
Logical sector size: 512
Disk identifier (GUID): f9f21fff-a8d4-5f0e-9746-594869aec34e
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30785535
Number Start (sector) End (sector) Size Code Name
...
40 8118272 30785535 [U][COLOR="Red"]10.8G[/COLOR][/U] 0700 userdata
Ok, so now we have this information,
Partition is 10.8G big
The partition name in the /dev/block is mmcblk0p40 (as mmcblk0 is the main internal disk and "/data" partition is the 40th partition)
Ok, It's least 10G big, so, what's the problem?
We see the partition is 10.8G big. BUT...
If we use "df" we can see the real deal
Code:
/data # df -h
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p10
11.7M 7.3M 4.1M 64% /mnvm1:0
tmpfs 917.2M 16.0K 917.2M 0% /dev
tmpfs 917.2M 16.0K 917.2M 0% /tmp
/dev/block/mmcblk0p40
[U][COLOR="Red"]2.4G[/COLOR][/U] 2.4G 50.6M 98% /data
My mom's phone, that is the same phone as mine.
i(dot)imgur(dot)com(slash)dZcD1ME(dot)png
Mine instead
i(dot)imgur(dot)com(slash)Z9aybBu(dot)png
Anyone knows what's going on?
Do i need to wipe partition?
Do i need to resize fs?
Thanks beforehand

Solution:
If you have TWRP:
Wipe -> Advanced Wipe -> Select "Data" and press "Repair or Change File System" -> Resize -> Swipe to Resize
If you dont have TWRP:
Use resize2fs command

ZP980 unbrick/study of partition table

Hi to all, I hope to be posting in the right section...otherwise...punish me plz
It's a long story, so i hope that someone has time and want to put some effort to help me understand what i'm doing wrong.
By the way i work in IT field and have some knowledge about linux (let's say 5 on 10) but not so many on how android really works, but i'm confortable with custom recovery and roms, i'm still using an s4 mini (GT-I9195) with mine android 9 custom rom and i'm super happy with it.
Now that presentation are done , here is the matter.
I've found an old zp980 32GB (NOT the "plus one") that some years ago i've rooted it flashed with recovery and custom rom. all was working, but at some point i started playing with fdisk and parted and i messed up things.
Honestly i don't remember what exactly i was doing, but now the status of the phone is:
System not booting
I can enter into Recovery (custom TWRP by dezmen3 v2.4.4.0)
I can connect to adb into recovery
I cannot flash rom trough recovery due the actual system partition (589 MB)
I cannot flash the original rom trough SP flash tool due "SFT enable dram failed (4032)" error
The partitions actually are (what i can see from recovery):
System (589 MB)
Data (54MB)
Boot (6 MB)
Recovery (6MB)
Cache (4 MB)
uboot(0 MB)
nvram (5 MB)
Free space: 27412 MB
Actually, I've tried to reformat the memory using SP flah tool, but i got the same error "SFT enable dram failed (4032)", all drivers are ok, i can see COM port in deivce manager tried win 10 and even win 7.
SP tool ver. used v5 1720 more updated version tells me that the brick i'm tringo to flash in not supported anymore xD
Here a dump of fdisk -ul /dev/block/mmcblk0 from adb shell
Bash:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 1022 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26624 47103 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 47104 67583 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 93184 105471 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 134144 1465343 665600 83 Linux
/dev/block/mmcblk0p6 4869120 1022 2145049599+ 83 Linux
if i make a print from parted (pushed with adb) I get:
Error: Can't have a partition outside the disk!
Before i was also having an error saying that there was an extended partition into a logical one (don't ask me how I do it), but i removed it
So, now....what to to to rescue this device?
by the way honestly except for the instinct of "recover things that doesn't work" my main purpose is understand:
What I've messed on the partitions
Why sp flash tool can't reformat/flash the memory (i haven't tried to manually modify it again)

no brave person hat want to help me to brick it in a bad way?
EDIT NEW INFO
i've understtod that the problem was caused by
/dev/block/mmcblk0p1
and
/dev/block/mmcblk0p6
start and end were inverted , them were overflowing.
Now i used fdisk to remove part 1 (the extended), so i've lost also 5 and 6 (system and cache) and i have recreated them using 1 GB for each and using correct sector order.
now SD and try to flash a ....random compatible rom....see u later for info.
Cross your finger for me xD

flash failed it cant mount system and emmc.....
and now
~ # cat /etc/fstab
/cache ext4 rw
/data ext4 rw
/emmc vfat rw
/system ext4 rw
/sdcard vfat rw
/sd-ext auto rw

if someone has a zp980/c2 working can please post me the result of
cat /etc/fstab
from adb shell??
and a fdisk -ul?