Database Info

[Fix] EMMC brick bug issue on P6200/P6210 16gb? Give this a go!!!

For those who have been living under a rock, problematic leaked builds of ICS were released for several different Samsung devices a few months ago. Users of those Devices for instance soon discovered that their devices were being ffected by what came to be known as the MMC_CAP_ERASE bug. Shortly after this*occurred, XDA Senior Member hg42 came up with a way to revive downed devices.
Now thanks to some more ingeniuty on his part, hg42 has also developed a companion application known as Partition Scanner to assist in this process.*The application features:
emmc_scan_all_partitions_once.zip
emmc_scan_all_partitions_infinitely.zip
these allow fast scanning of all blocks of all emmc partitions in 1MiB steps.
The main purpose is to access each emmc block to find any bricked block in the partitions after repartitioning.
The “infinitely” variant runs checks infinitely, which may help to find emmc brick effects which only occur sporadically (if such effect really exists). Run this as long as you want. Reboot to finish.
If this freezes the last partition shown may have a bricked block inside.
emmc_find_brick_start.zip
emmc_find_brick_end.zip
these scan the whole emmc device.
emmc_find_brick_start starts scanning from the beginning of the device upward.
emmc_find_brick_end searches the end of the device and then scans downward.
If this runs up to the end or down to zero (showing a message with “completed –> OK”), no bricked block was found.
If it freezes, the block shown last with “…” at end of line is the first bricked block in that direction.
The line before with “-> ok” is the first usable block before/after the brick.
The application has received excellent reviews, so if you’re one of those people currently facing an EMMC issue, or you had the issue previously and gave up on your device, head on over to the companion thread and give this a go.
Click to expand...
Click to collapse
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app

Bad2hold said:
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
@Bad2hold - have you tried this yourself as I am desperate for help in unbricking my device that Samsung refuse to repair as it is the P-6200L (non-UK model).
I can't use ADB as my pc won't recognise the Tab, have tried flashing the .pit file and firmware but no joy, can't use the partition scanner as I can't get it to scan the internal memory (it scans the external SD card instead).
I can install CWM recovery and also get to stock recovery but the Tab will not go past the white Galaxy Tab logo.
Any help is highly appreciated

There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..

chrisrotolo said:
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
Click to expand...
Click to collapse
Thanks for the advice mate.
Am going to flash it with the honeycomb firmware it came with from Sammobile and try a few factory resets to see if that works.
If not have found a place in the UK that will JTAG it for £38 if all else fails...:good:
UPDATE: Honeycomb doesn't let me access recovery so no way to wipe from there. Recovery is available on an ICS rom but am reluctant wipe in stock recovery as that's how I go in this mess to begin with :crying:

I currently cant help, as iam travelling without a pc... but this guy who developed this scanner, has pit files available for our device. So there is a good chance to get help from him. And iam sure, with some hours off every week, where u get bored, u can actually fix it by yourself as u already figured out that much... i would love to help, its a challange you know? maybe iam gonna buy a laptop... =p
Update: just curious, is it scanning without a external sd inserted? Because internal and sd are swapped in cwm recovery since 3 versions too...
Sent from my GT-P6200 using xda app-developers app

@Bad2hold - Thanks for the reply, have tried flashing the .pit file but no joy.
Can't get the scanner to scan internal card as it's loaded on my external sd and can't push it to the internal which then means I can't remove the external sd.
Have tried flashing various honeycomb and ICS firmwares with a combination of .pit files, the process flashed fine without errors but still no boot past the white Samsung writing
Sent from my GT-I9300 using xda premium

Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...

unclefab said:
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
Click to expand...
Click to collapse
I think we cannot remove the brickbug on stock ICS...that pit file just for solving hardbrick issue...
Sent from my GT-P6200 using xda premium

U can actually remove the brick bug issue, this is, what this post is about.
Basically, you just have to find the bad blocks in your sd partition.
After you found them, all is left, is to repartition your sd around the bricked blocks, which you have to delete from your partition.
He mentions several methods to use adb and other tools, helping to do this.
And i really recommend reading a bit through his first post, found the same problem after a minute:
I also had the following problem:
I couldn't format my internal sdcard with the cm9 recovery. I think it's too big for the mkfs.vfat tool of current cm9. So I installed another recovery, formatted the internal sd (I thought).
This erased all my current backups and downloads, because in reality it was my external sd. Fortunately I had a backup of the external sdcard from before rescuing my phone.
So, you may want to create a backup of your external sdcard first.
Then double check which is your internal sdcard (the UMS partition) and which is your external sdcard.
Or you could remove the external sd completely. But think about when to remove it, because you might need it for some files (e.g. to use the emmc partition scanner).
Click to expand...
Click to collapse
Of course, if u r not familiar with linux, u probably wont fix it in an hour.
But you can learn a lot within an hour. First of all, figure out how to connect your device to adb. (Which is still possible, if you didnt smash your tab against the wall or so...) After that, it should be lot easier to follow his instructions.(not just because u have adb working, but because you know what he is actually talking about.)
And he is really willing to help, so figure out as much as possible after connected to adb and just ask in his post if you get stuck.
Dont forget: if its not a issue by malfunctioning/broken hardware, then you actually can fix everything with your pc, you just need to know how.. so dont give up!!!
here his post again: http://forum.xda-developers.com/showthread.php?t=1667886
And @kersey: what pit file did u flash? The pits he provides are to repartition your SD AFTER you located the bricked blocks. But you cant know, if you cant get his scanner running..? You have to format data partition in recovery after flashing one of those, because of missing file system.
Note: Never flash a stock ICS after you fixed it. It will brick your device again. But u r safe with cm9 and others.
Sent from my GT-P6200 using xda app-developers app

Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too :good:

Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app

Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd

Happy Boy
Hi all
While trying to root and install custom rom I bricked my friends phone. I have been going crazy trying everything I could to get this brick back to life.
ITS ALIVE AGAIN!!!!!!!!
Thank you kersey for your post on how you got your Tab back.
This is what I did.
I installed the 5 files on the SD card.
120824-151927-emmc_find_brick_end
120824-151927-emmc_find_brick_start
120824-151927-emmc_scan_all_partitions_infinitely
120824-151927-emmc_scan_all_partitions_once
120824-220105-emmc_scan_write
I put the phone into recovery mode and ran 120824-151927-emmc_find_brick_start.
The program started scanning the memory and first froze on 2188.
I got back into recovery and ran 120824-151927-emmc_find_brick_end
once again the program started counting down and froze about 3189.
For this phone the correct pit files were in " pits-N7000_16GB "
I unzipped pits-N7000_16GB and looked for the nearest pit file , which was
N7000_16GB_Q1_20110914--patched--brick-between-1174-and-3321-MB--DATAFS-moved-by-2048-MiB.pit
I then put the phone back into download mode and using Odin flashed the patched pit file above.
Disconnecting the phone from computer I went back into recovery and ran120824-151927-emmc_scan_all_partitions_once
For the first time I was able to do a full scan without the program freezing.
Next step was installing Abyss Kernel 4.2. I then did the regular data wipe/cache wipe/dalvik wipe.
And finally I installed Rocketrom 11.
The phone rebooted and then came back to life.
I checked the internal memory and it was down to 9gb, but who cares as long as its ALIVE AGAIN !!!!
hg42 you sir are an absolute legend. Donation coming your way.
This method definitely works . Just be patient. I hope This helps others aswell

EDIT:
Is there any not so hard way to install the original rom with the pit i need? cm10 works, but i dont like it so much.
p6201dbtlpc_p6201xxlpc_p6201xxlp3_home.tar i would like to use
but i only know to flash this in odin, becouse it is no zip, i have no clue how to flash it in cwm
thanks for an answer!
-----------------
Your post should be on first post added =)
And in http://forum.xda-developers.com/showthread.php?t=1807002 !
Thanks for it!
kersey said:
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Click to expand...
Click to collapse

ICS update and emmc bug
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance

doaft said:
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
Click to expand...
Click to collapse
If you chose to do a factory restore via stock recovery, which is what you have due to not being rooted and not having CWM installed there is a very big chance you may brick your device. I speak from experience!!!
If you are that worried I would flash back to honeycomb rather than risking having an expensive paperweight
Sent from my GT-I9300 using xda premium

A little of my own experience with superbrick
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it

P6200
Hello man... I saw your post ''Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too'' ... I have the same problem with my P6200. Please give me that scanner to fix it or tell me how to put my tablet back On... Thanks

Androguide.fr said:
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
Click to expand...
Click to collapse
hey dude it's my first post in xda
i've succeded to unbrick my device but my internal memory is shrink a lot into 700+ mb but i don't understand how to use the script so
can u explain step by step ?

one can help me ??
hai everybody.... i'm from indonesia.., my friend just give me samsung galaxy tab 7 plus... ( GT-P6200 ) without any boxes, last day i try to get ICS update from kies , but the application won't update my firmware , so i try the alternative direction.
i try another application - Odin3-v1.85 and download the firmware..., but the fact is after few second running it self , the prosess can't continues get fail after
Note : i;m using : P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_HOME.tar.md5 firmware
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017> NAND Write Start!!
<ID:0/017> factoryfs.img
<ID:0/017> hidden.img
<ID:0/017> recovery.img
<ID:0/017> Sbl.bin
<ID:0/017>
<ID:0/017> Complete(Write) operation failed. >>> FAIL...
anyone can help me .... please

[Q] Corrupt GPT, SBF and Fastboot have no effect

Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!

Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!

No one?

Hello,
have you fixed it ?

Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.

ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer

jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?

ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+

Malata Zpad T2

After searching for ages, I stumbled upon a solution for my tablet. Although all GTab ROMS work in the Zpad, I haven't been able to use the full 1GB RAM present in my Zpad.
So Finally today I stumbled upon a solution posted in slatedroid by Micky.
Instead of flashing the Viewsonic ROM to start with, we need to flash this ROM instead.
After you download the ROM from the link above, search for the TeamDRH CWM 5.5.0.4 and download. Extract the RAR file and replace the recovery.img in the folder with the TeamDRH CWM, cuz the one in the ROM is too old and doesn't support the latest ROMs.
[Note: If you want a larger system partition, follow this.
Open the file flash.cfg and find this no. 209715200 and replace it with this no.419430400
Now when you flash this ROM, you will get a system partition of 400MB.
If you use this method, you don't need to delete any system files after install from the ROM.]
Reboot the tab to CWM and wipe data/factory reset and wipe dalvik cache. Twice.
Shutdown and reboot to APX mode and connect to PC
NV Flash the ROM, let it boot and then shutdown.
Now to flash Jelly Bean.
Download Smoother Bean by nobe1976
Then boot the tablet to CWM
Again wipe data/factory reset and wipe dalvik cache. Twice just to be sure.
Flash the Smoother Bean zip file
Do not wipe data/factory reset or wipe dalvik cache this time.
Just reboot
Let it boot and run for a few minutes.
[Optional: Now install an app from play store to delete system apps and also a keyboard, Swipe or as such.
Open the system app remover and uninstall Gmail and AOSP Keyboard.
A few more apps can also be uninstalled, such as wallpapers, DSP Manager, Music FX, but not all.
Before deleting the AOKP Keyboard, you can copy it from the system folder if you want the stock keyboard. LatinIME.apk file.
(This does not apply if you modify the flash.cfg for larger system partition)
We need to uninstall these apps cuz after flashing with the above ROM, the system partition is only 209MB, so after flashing JB, we get around 5-6 MB free in the system partition. After uninstalling the apps, we get around 34 MB free.]
Hats off to nobe1976. He is able to develop a JB ROM that can be installed in a 200 MB system partition.
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
[After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Its a small request from us Zpad users.
(Note: From the help of all the users, I have been able to increase the system partitiom to 400MB)]
If anyone could help, I will be gratefull, we all will be very gratefull.
This is really pushing the limit.
Edit: Now you can use 1GB RAM present in your tablet and all the space available in the flash memory.
Note: This method can be used in all variants of the Zpad which has 1GB RAM and 16GB ROM.
Note: This tablet is sold by different names all over the world. The one I use is HCL AP10-A1

kank_fraud said:
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
Click to expand...
Click to collapse
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]su -c dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]

After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Click to expand...
Click to collapse
Though @rajeevvp is the best person on xda to give you solution that is more logical on this, I will tell you quick and dirty way to do this, which I have adopted.
1> download stock zpad rom if you don't have it already "ftp://112.5.164.225/tablePC/T2_nvflash_mp_3g(WCDMA)_20110824.rar"
2> unzip it, delete recovery.img from unzipped directory, copy part9.img from DRH nvflash which is used for prep 350M system partition to this directory, rename it to recovery.img
3> edit "android_fastboot_full_i_malata.cfg” change "size" of partition id 11 (which is a system partition)
Make sure you do not give any arbitrary size here; calculate it with the formula @rajeevvp posted here "http://forum.xda-developers.com/showpost.php?p=22138304&postcount=14"
4>now nvfalsh your tablet in apx mode with download.bat, now format /data /system /cache and flash whichever rom you want on top.
memory/partition config is supplied to kernel through CMDLINE parameter, so even if you nvflash tab with above procedure, its not necessary that default memory/partition sizes are maintained created by above prcoess, Team DRH boot.img has a blank CMDLINE. That is the reason
Above process will work on most of the ROM, which is using TeamDRH boot.img.
(more technical explaination stright from one of the posts of @rajeevvp "When the bootloader runs, it reads PT (partition 3) and constructs a command line telling the kernel what the partition layout is on the onboard NAND flash. Normally, the bootloader will pass this command line to the kernel as part of the boot-up process. However, if the bootloader sees that the boot.img already contains a default command line then that will take precedence")

I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.

I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
Click to expand...
Click to collapse
glad to hear that it worked, BTW you will have to change /system size to minimum 350MB if you plan to use TeamDRH rom in future (hopefully with camera working)

I'll have a try later.Thanks So much.

Thank You all for the help.
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
It shows 419 MB in Titanium Backup
I am happy with it.
Its way better then before.
Thanks evryone
Problem solved

If anyone has formated or resized the internal memory resently, please try the maximum possible size for the system partition.
I tried 512MB but it didn't work. Maybe 490MB might work.
According to my knowledge, Android should support atleast upto 999MB for any partition.
Is it cuz of our tab or is it cuz of the architecture.
And if anyone knows, is it possible to create a larger internal partition.
As in 8GB or if possible the whole internal memory.
CWM doesn't allow more than 4GB internal space.

kank_fraud said:
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
Click to expand...
Click to collapse
Well this was expected result, /system partion resides on NAND flash chip (with is only 512MB) and not on SDcard.
Read this "http://raywaldo.com/2011/07/format-the-gtab/" and this "http://forum.xda-developers.com/showpost.php?p=15558724&postcount=12"
Also you need to bare in mind that other partitions also use 512MB nand flash as per explanation in above threads.
so if you take a close look at falsh.cfg file in nvflash directory you will understand that size allocation is sequential ("allocation_policy=sequential") and system partition (11) which is last to allocate the space, so you need to calculate it accordingly if you want to utilize all remaining space from NAND flash chip.

Well I cant open the page "http://raywaldo.com/2011/07/format-the-gtab/".
So according to this info I have hit the limit. I am already using 489MB of the 512MB flash. And as always, cuz of our storage manufactures, we get only 490MB in a 512MB chip.
What I wonder is why Malata and Viewsonic did not utilise the full NAND space available in the first place.
Is it used for something else.
I mean even the 350MB prep for Viewsonic GTab uses 350MB instead of 400MB.
It is so easy to to utilise and partition the NAND, then why not use the full available space.
What is the empty space used for!???
Or is it just a waste!!!

hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG

fanguru said:
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
Click to expand...
Click to collapse
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem

rajeevvp said:
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo > /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
Click to expand...
Click to collapse
Well I am very sorry for such a late reply. :angel:
I missed your post as I was out of station.
After I came back there were already solutions posted by a couple of users. :victory:
Well today while updating my original post, I noticed ur first reply. :silly:
Well thank you for your reply.
And thanks to all the ppl who provided for the solutions to our ZPad.
I guess the problems are solved for now.
:highfive: :highfive: :highfive: :good:

kank_fraud said:
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
Click to expand...
Click to collapse
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG

kank_fraud said:
I guess the problems are solved for now.
Click to expand...
Click to collapse
I'd still like the output of those commands--for my own edification.

fanguru said:
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
Click to expand...
Click to collapse
Well for Me it worked the first time itself.
Why don't u try giv it a few more couple of times. :laugh:
BTW, are you using the Malata Zpad or Viewsonic Gtab
If you are using Gtab, try TeamDRH method but modify the size of the partition.
If u are using Zpad, try again.
Clear cache and reset before installing.
Try previous older ROMs and gradually update to newer ones.
Reset and wipe before each update.
As I didn't get any problems, so I can't say whats wrong with your installation.
And very sorry for the late reply.
I have exams.
But my tablet is very stable after this.
Everything is running smooth, even HD games.
Goodluck :fingers-crossed::fingers-crossed::fingers-crossed:

rajeevvp said:
I'd still like the output of those commands--for my own edification.
Click to expand...
Click to collapse
I tried it in terminal emulator, but it says 'Operation not permitted'

kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
same here.

kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
Fixed commands. Try them again.

I seem to have everything running and it seems really fast, the only problem I have is that the home button (hardware and soft) does not work!
I've tried installing a different home app, tried home switcher and I get asked when the tablet boots as to which home app to use, but still the buttons don't work (back and recent apps work).
Any ideas???

[Q] Problems with flashing ROMs.

Hey everyone, this is my first thread. I'm really desperate. Here's the thing: yesterday my GF bought a phone (Galaxy SL i9003), previous owner flashed it with custom ROM and boke something, I wasn't sure what till now (in internal memory space it showed UNAVALIBLE), I decided to flash stock ROM to make it work.
I've spent ~10 hours straight but couldn't reach any result.
//I don't use any links or attach photos, because I can't, I insert spaces in them//
1. When I flash it, using ODIN, I use 5-file stock rom (XKPQ), it's ok (odin shows PASS), then the phone reboots and I get this in recovery:
dropbox. com/s/1hnim2sn1dphr6c/IMG_20130617_165950.jpg
As I've come to understand, there is a problem with internal memory, so I googled a little more and found this: androidforums. com/incredible-all-things-root/456898-my-phone-dead-single-tear .html
2. Then I tried to do as described on that forum, installed droid SDK, pushed those 6 files (after applying cf root, so i can access othere options in recovery), applied chmod to them, but I can't seem to do the last point:
Code:
parted /dev/block/mmcblk0 mkfs ext2
This exact command does nothing, only (for some reason) reboots the recovery. And, as you can see on my screenshot, the partition that doesn't work is mmcblk0p3, but when i try to do parted /dev/block/mmcblk0p3 mkfs ext2, it says 'could not stat device - no such file or directory'.
What should I do? Is there a way to fix my problems or is it dead and service center is the only option?
P.S. I'm not experienced with samsungs, so maybe I figured the problm wrong, help me, please!

devcor said:
Hey everyone, this is my first thread. I'm really desperate. Here's the thing: yesterday my GF bought a phone (Galaxy SL i9003), previous owner flashed it with custom ROM and boke something, I wasn't sure what till now (in internal memory space it showed UNAVALIBLE), I decided to flash stock ROM to make it work.
I've spent ~10 hours straight but couldn't reach any result.
//I don't use any links or attach photos, because I can't, I insert spaces in them//
1. When I flash it, using ODIN, I use 5-file stock rom (XKPQ), it's ok (odin shows PASS), then the phone reboots and I get this in recovery:
dropbox. com/s/1hnim2sn1dphr6c/IMG_20130617_165950.jpg
As I've come to understand, there is a problem with internal memory, so I googled a little more and found this: androidforums. com/incredible-all-things-root/456898-my-phone-dead-single-tear .html
2. Then I tried to do as described on that forum, installed droid SDK, pushed those 6 files (after applying cf root, so i can access othere options in recovery), applied chmod to them, but I can't seem to do the last point:
Code:
parted /dev/block/mmcblk0 mkfs ext2
This exact command does nothing, only (for some reason) reboots the recovery. And, as you can see on my screenshot, the partition that doesn't work is mmcblk0p3, but when i try to do parted /dev/block/mmcblk0p3 mkfs ext2, it says 'could not stat device - no such file or directory'.
What should I do? Is there a way to fix my problems or is it dead and service center is the only option?
P.S. I'm not experienced with samsungs, so maybe I figured the problm wrong, help me, please!
Click to expand...
Click to collapse
Idk what the problem is.. but try flashing it AGAIN, but this time select Re-partition.

nbrian2012 said:
Idk what the problem is.. but try flashing it AGAIN, but this time select Re-partition.
Click to expand...
Click to collapse
I did. With, without it. I reflashed different roms hundreds of times.

you should parted mmcblk0 not mmcblk0p3.
and i assumed u have micro sdcard inserted.
Sent from my Galaxy Nexus

chongns said:
you should parted mmcblk0 not mmcblk0p3.
and i assumed u have micro sdcard inserted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yeah, I tried, but it only reloads recovery for some reason.

Any ideas?

[GUIDE] Internal Memory Data / Deleted Files Recovery

This is the same tutorial written by Wartickler at this link. Thanks for his efforts, his work is appreciated.
Here we bring minor changes to the tutorial for those of you who are facing problems accomplishing the procedures.
The Problem
Internal Memory doesn't mount as a drive like external memory does. External memory would allow you to use data recovery tools that scan for deleted files and return them to a usable state. These tools work because most operating systems don't go through and set all of those 1's and 0's to just 0's when you delete a file. Usually the operating system will just delete the reference pointer in the index that says that a file exists with such-and-such name and it's located at this position on the hard disk / memory location. There are destructive delete tools out there that will overwrite the spot of a deleted file multiple times to discourage recovery in just this manner. The issue is that data recovery tools need an actual mounted drive in order to dig deep and unearth those funny pictures of cats you so tragically deleted by accident. These newest batches of phones don't have external SDcards which are super easy to mount as drives. Internal memory mounts as MTP/PTP which is not treated as a mounted drive and cannot be scanned by these data recovery tools. But still there is a hope.....
The Process
My phone is the Samsung Galaxy s4 (GT-I9500) though I imagine this should work for ANY phone with Internal Memory. We will be using a Windows 7 machine to:
back up the entire internal memory partition to your computer as a single, massive .RAW file,
convert the .RAW file output to a VHD,
mount the VHD as a disk in Disk Manager,
scan the attached VHD volume for files that have been deleted and recover them,
The Requirements
A rooted Android phone, (try to root with a non-destructive method as this appears to protect those who must root from wiping the device data a second time),
BusyBox installed on your device,
Cygwin installed to [c:\cygwin] with pv and util-linux from the repo (at the package selection screen search for pv then util-linux and click on Default to change it to Install). Make sure to open Cygwin once to make sure that the /bin folder is created. Also, I made a folder at [c:\cygwin\samsung] to put the exported .RAW file,
Netcat (download the ZIP file and extract nc.exe to [c:\cygwin\bin]),
ADB - You can use minimal adb and fastboot which is 2MB only. Attached, find the link at the bottom of this post. (make sure adb.exe is in your path. Path is in System Properties -> Advances -> Environment Variables -> System variables -> Path and add to the end: ";C:\Program Files\Android\sdk\platform-tools" or where ever you placed your adb.exe),
USB Debugging enabled on your device,
VHD tool from the mighty M$. Put the VhdTool.exe file in [c:\cygwin\samsung],
Piriform Recuva or your favorite data recovery tool, (it appears Recuva only finds the more common file types like images, videos, etc. Those were the file types in which I was interested. If you are after more exotic file types perhaps you might share the software you used.)
A calm sense of peace and serenity that you will get your files back... :fingers-crossed:
The Work
*****Based on the number of people having trouble with this step it is now my recommendation that you choose to recover your entire memory block instead of just the data partition. In my phone's case that is mmcblk0. Please discover if yours is different.
[*]*****For identifying which block/partition you want to recover, install DiskInfo from Playstore. Open the app and click on Data (USERDATA) to see the partition name for yours. For our purpose here we are seeking to recover the userdata partition: /dev/block/mmcblk0p21
Turn on your phone
Connect the phone in ADB mode
Unlock the screen.
Open a Cygwin terminal and enter (This assumes your BusyBox installation is at [/system/bin/busybox]. It may be at [/system/xbin/busybox]):
*Remember to enter codes line-by-line. After you enter su, you have to grant permission on your mobile phone at the same time
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p21
Open another Cygwin terminal and enter:
Code:
adb forward tcp:5555 tcp:5555
cd /samsung
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p21.raw
[*]Depending on the size of partition it may take a while to backup.
We need to convert the .RAW file to a virtual hard drive. VhdTool.exe basically just puts a VHD footer on the end of the .RAW file. Open a Windows command prompt, go to [c:\cygwin\samsung], and type:
Code:
VhdTool.exe /convert mmcblk0p21.raw
Now we need to mount the VHD in Windows. Select the Start button-->right-click Computer-->select Manage.
Select Storage-->Disk Management.
In the menu select Action-->Attach VHD.
For Location enter [c:\cygwin\samsung\mmcblk0p21.raw] and select the OK button.
Right-click on the name (e.g. "Disk 1") to the left of the Unallocated space and select Initialize Disk.
Select the GPT (GUID Partition Table) radio button and select the OK button.
Right-click on the Unallocated space and select New Simple Volume...
In the Wizard select Next>, leave the default for the volume size, select Next>, select a drive letter (e.g. K), select Next>, MAKE SURE to select the 'Do not format this volume' radio button, select Next>, select Finish.
A box will pop up asking you to format the drive. You DO NOT want to format the drive at this time.
Right-click on the RAW space and select Format... MAKE SURE to change the File system to FAT32. Set the Allocation unit size dropdown to 'Default.' MAKE SURE that the Perform a quick format checkbox is CHECKED. You do not want to overwrite the entire new drive with all zeroes (0's) and destroy your data. Quick Format means that it will only attempt to destroy the index for the drive by establishing a new index. Without this box checked the Windows operating system will write zeroes (0's) across the entire volume, potentially destroying your data. Select the OK button.
A box will pop up saying that Formatting this volume will erase all data on it. That would be doubly true if you actually didn't check the 'Perform a quick format' checkbox. Double check that you actually did check the box and select the OK button. (Don't worry. This essentially leaves the volume in the exact same state that your phone's internal memory is living in right now: there is data on the drive...you just can't see it. It's coming back, I promise!)
Open the Piriform Recuva application. In the wizard select the 'Next >' button. Select the 'Other' radio button and select Next >. Select the 'In a specific location' radio button and enter: k:\ (assuming K is the drive letter you chose...) Select the Next > button. Select the Enable Deep Scan checkbox. This is the magical setting that finds files that have been deleted...but not really deleted. Select the Start button.
The application may take about an hour to do the 'Deep Scan.' It's time for more laps around the house! Once the application has returned its results you can choose which files to recover using the checkboxes. Select the 'Recover...' button and choose the location to which you wish to output your files.
?
Profit! :victory:
Good Luck :good:

help
M S T F said:
This is the same tutorial written by Wartickler at this link. Thanks for his efforts, his work is appreciated.
Here we bring minor changes to the tutorial for those of you who are facing problems accomplishing the procedures.
Good Luck :good:
Click to expand...
Click to collapse
You should add that the x86 version of Cygwin is needed, not the x64.

Do you also know that as of Android 4.3 this method doesn't work anymore?

yes
Lennyz1988 said:
Do you also know that as of Android 4.3 this method doesn't work anymore?
Click to expand...
Click to collapse
it works with 4.4.x and 5.1.1, it probably also works with 4.3. it's just an adb command after all.

Filoppi said:
it works with 4.4.x and 5.1.1, it probably also works with 4.3. it's just an adb command after all.
Click to expand...
Click to collapse
No its not that. As of Android 4.3 Google enabled Trim on our decives. That means when you delete a file its really gone. Not even a professional company can get it back.
I have tried the above methode and I could not get any data back. Thats when I started reading about Google enabling Trim and found out its impossible to get it back.
Did you try it on Android 4.3+?

try
Lennyz1988 said:
Do you also know that as of Android 4.3 this method doesn't work anymore?
Click to expand...
Click to collapse
Lennyz1988 said:
No its not that. As of Android 4.3 Google enabled Trim on our devices. That means when you delete a file its really gone. Not even a professional company can get it back.
I have tried the above method and I could not get any data back. Thats when I started reading about Google enabling Trim and found out its impossible to get it back.
Did you try it on Android 4.3+?
Click to expand...
Click to collapse
I have tried on my previous Samsung galaxy s3 (i9300) and my one plus one, both 64gb, i got at least 20% of the pictures back (.png, .jpg, ...), possibly even 50% since i had no idea how many i had on the device, some zip, most of .pdf and .doc and some other random stuff.
In both cases i did not manually delete the files from the phone, instead, i screwed up the partitions by deleting some system file, so after restarting, the SDcard/used data partition was empty.
i noticed though that even if my phone only had 500mb of free space available, the .raw partitions i extracted with this method were mostly empty, they only had about 10% of the data, so i guess some happened when android restarted, maybe yeah, some kind of trimming.
i think its worth trying anyway. just remember to not open any program or copy any file in the memory, as it would lower the chances to get anything back.

Filoppi said:
I have tried on my previous Samsung galaxy s3 (i9300) and my one plus one, both 64gb, i got at least 20% of the pictures back (.png, .jpg, ...), possibly even 50% since i had no idea how many i had on the device, some zip, most of .pdf and .doc and some other random stuff.
In both cases i did not manually delete the files from the phone, instead, i screwed up the partitions by deleting some system file, so after restarting, the SDcard/used data partition was empty.
i noticed though that even if my phone only had 500mb of free space available, the .raw partitions i extracted with this method were mostly empty, they only had about 10% of the data, so i guess some happened when android restarted, maybe yeah, some kind of trimming.
i think its worth trying anyway. just remember to not open any program or copy any file in the memory, as it would lower the chances to get anything back.
Click to expand...
Click to collapse
Yes but that's something different I think. Then you never deleted the files, they were there but not accessible.
If you look for example in the last 10 pages of the main thread, then no one is able to recover anything. Because it's simple not possible anymore. That's just how Trim works.

Lennyz1988 said:
Yes but that's something different I think. Then you never deleted the files, they were there but not accessible.
If you look for example in the last 10 pages of the main thread, then no one is able to recover anything. Because it's simple not possible anymore. That's just how Trim works.
Click to expand...
Click to collapse
I'm sorry for your loss.

Filoppi said:
I'm sorry for your loss.
Click to expand...
Click to collapse
What kind of response is that?

gonna try.

for those of u who want to know the blocks and partitions to recover the user data..
ls -l /dev/block/platform/*/by-name
after the adb shell will list them

127.0.0.1 5555 | pv -i 0.5 > mmcblk0p16.raw 0 B 0:00:02 [ 0 B/s]
i stuck at step 7 which is
0 B/s transfer rate

GoGopowerRanger said:
i stuck at step 7 which is
0 B/s transfer rate
Click to expand...
Click to collapse
That su is the most important part of command, if you miss it adb will not be able to transfer any data

M S T F said:
That su is the most important part of command, if you miss it adb will not be able to transfer any data
Click to expand...
Click to collapse
You should be honest with people. You should put in the op that it will only work on Android versions below 4.3. People are just getting false hope and wasting their time.
This method does NOT work anymore.

Lennyz1988 said:
You should be honest with people. You should put in the op that it will only work on Android versions below 4.3. People are just getting false hope and wasting their time.
This method does NOT work anymore.
Click to expand...
Click to collapse
This is not my method nor I have, my self said that 100% you will get what you have deleted. I have only brought minor changes to the tutorial for the sake of successful transfer of data to the pc.
Now if you feel responsible for the feeling of people, definitely I will appreciate if you find another way.

M S T F said:
This is not my method nor I have, my self said that 100% you will get what you have deleted. I have only brought minor changes to the tutorial for the sake of successful transfer of data to the pc.
Now if you feel responsible for the feeling of people, definitely I will appreciate if you find another way.
Click to expand...
Click to collapse
That's the thing. You just copy paste a tutorial that does not work. Why would you do that? I can imagine that you did not know that it would not work anymore. But now you do know. What do you hope to achieve? Raising your thanks meter? You give people false hope and you waste their time.
And about me finding another way....There is not even a professional company that can do it. It's impossible at the moment.

Lennyz1988 said:
That's the thing. You just copy paste a tutorial that does not work. Why would you do that? I can imagine that you did not know that it would not work anymore. But now you do know. What do you hope to achieve? Raising your thanks meter? You give people false hope and you waste their time.
And about me finding another way....There is not even a professional company that can do it. It's impossible at the moment.
Click to expand...
Click to collapse
I don't need thanks... why I should do.... it doesnt give me anything... I have got my own forum with its nice members.... if someone is in need of thanks, thats is you which is trying to show himself as a defender of others feeling, time, blah blah.......
I have recovered my file on a 4.4.2 android after a system crash which I had to reset the phone. if someone is in desperate need of something s/he will try anything and as far as I know trying this one doesn't harm anyone.
for you I have a recommendation, go and drink something cold and calm down!!!

Errr...

Awesome....the raw extraction worked on my S6 running Android 5.0.2. This time I tried it on a Mac and used Homebrew to install PV. Is there a way to get the entire image, even with the unused space?

Great
Thank you!
Worked on my sm-g900f
If you get nc/pv command not found , try this:
When you open cygwin terminal, start with this line: export PATH="/cygdrive/c/cygwin/bin";$PATH
The terminal should now know the location of them.
Same if you get that "adb: command not found" just type: export PATH=/cygdrive/c/XXXXX";$PATH
Just replace that XXXXX= to your location of adb.exe.
Hope it helps someone out of this ****