Related
** UPDATED WITH .BCT saving, include USB as well as NVFLASH just copy in
** 1 dir, run the batch and keep those you may need them one day
** Read the batch file for more info
It is clear for me is that it is not a perfect solution to use nvflash with images that you do not know the source.
The tegra S.O.C. use the information from a file stored in partition#2 to configure some low level setting like flash memory chip speed, total memory installed, video memory installed, flash type etc. As an example, if for some reason a batch of tablet is built with more memory then the .bct files will need to be changed accordingly
It is already confirmed that there's at least 2 different type of hardware. (2 different images by bekit do not use the same .bct configuration)
When flashing after a full wipe after using the create command, nvflash read the .bct configuration files and store it in the partition #2 on the tablet, bct files are created by the manufacturer using a tool from nvdia called buildbct. They are not writen during regular nvflash (where the partition are not re-created)
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched).
This batch files will work under windows and will not modify your tablet in anyway
please make sure you use the nvflash tools that is 151K there's an older and smaller one in some package, it will output binary inside the partition.txt instead of plain text. The version 2 include everything you need to backup the device under windows
Thanks to the various poster of thread about nvflash for the correct command THEY did the hard work not me !
To Restore individual partition the command is
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
this will not work for partition below 4
P.S.
I am not trying to start a debate on the validity of the current recovery (thumb-up to the guy who offered those!) They are valid for MOST device however
if you do have a different device this will alleviate any issue that may happen with nvflash restore.
see 2 post below for full restore info
Hi,
I know that the partitiontable shows a partition named "BCT", but is there also something else, perhaps flashed into the SOC itself that is referred to as "the BCT"?
The reason for the question is that nvflash has a setbct and a getbct command, separate from the read and download commands, which work with the partitions.
Jim
Reserved
(will be completed a bit later)
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
10roller said:
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
Click to expand...
Click to collapse
My guess is yes, the platform of the ac100 laptop by toshiba is tegra based and they do it!
P00r said:
The set bct command probably write the 4080 byte to the partition named bct in the cfg, I have yet to test flashing a dummy FF filled partition with the command to confirm the flash.bct get writen there
So in fact when you restore with the nvflash restore images from bekit I think you are actually writing it twice... (it is in the image and you telling the nvflash to create it) but I have not confirmed this yet
Once the bct info is there, the SOC read his configuration there, as well as the ODM info, I have not found a way to use --getbct that reads back the BCT from mass storage yet...
I am not sure either why there's so many section being flashed it should work with only a few of those (I plan to test this) since nvflash is simply puting those one after the other. It make sense only sense for a dual booting unit
Click to expand...
Click to collapse
Hi,
I was able to get --getbct to output a 2048 byte file awhile ago. I think I had posted about it, but, sorry, I don't remember which thread. The only thing I vaguely remember was that I had to use some unobvious combination of parameters. Also, I think that it only worked right after pushing the bootloader.bin. If I find my post, I'll provide a link.
Jim
Thanks OP, I like the idea of being able to back up the partitions directly from my tablet so I know I'm restoring the proper thing should I ever have to resort to that.
Just starting to get into modding this thing after it showed up from Woot yesterday, been planning on buying one for quite some time to compliment my Epic 4g and when the woot sale dropped I had to jump on it. So far all I have done is flash clockwork, and make a nandroid backup with that. Also doing this backup method now.
So have you actually done a successful restore using this method?
so is it possible to back up your original hardware configuration and restore it when you got problems???
Yes and NO, I have error reading partition #11 (system) on my tablet (bad block)
if I use it as is for restore, it doesn't restore and boot, however replacing this partition with clockwork system.img backup give me back a full working tablet.
I can also reboot into recovery and restore from there.
Letters and numbers oh my
I ran the backup on my new replacement GTab yesterday. I had a size mismatch on partition 5, everything else backed up properly. Also, my partition 7 is BLO and partition 6 is MSC. Thanks for the script and capability.
Mike
P00r said:
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched). I will post later on how to flash back those if someone request it...
Click to expand...
Click to collapse
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
iamchocho said:
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
Click to expand...
Click to collapse
You can flash back the partition using
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
If needed you can use the nvflash format kit prior to restoring however it would be better to use your own .bct with that option
Getting stuck at partition 7.
xkwwwx said:
Getting stuck at partition 7.
Click to expand...
Click to collapse
What is the error you are getting ?
stock recovery image
Thank you very much for the sharing this.
Now I have 10 img files (part-2 to part-11)... wich one is the stock recovery image? I did this before installing clockwork mod...
Thanks!
I think this is fantastic. Gives us a chance to backup our gtab before deciding to try a new rom. I tried this today in the hopes to backup and then install the flashback HC rom. But unfortuntaly it stopped on image 7, as xkwwwx has also mentioned. The message seemed to be a issue with the size expected of the image as to what was received. Ill try and copy the message.
"nvflash.exe" -r --read 7 part-7.img
nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
At that point it stops, and i have to control c to exit the batch file. Id love to be able to backup with this pls, so i can try another rom, and know i can use this to return to this rom if i dont like the new one, any chance this can be resolved pls ?
Was also wondering if some form of GUI maybe of benifit, i know alot of people feel wary of NVFlash, perhaps with a GUI people would feel more comfortable using it. Maybe a simple screen with a backup and restore set of buttons ?
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Icedvoco said:
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Click to expand...
Click to collapse
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
P00r said:
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
Click to expand...
Click to collapse
Bad blocks may be common, but bad blocks in the exact same spot probably not. I get the exact same thing:
"nvflash.exe" -r --read 7 part-7.img
Nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
Any other thoughts on this?
Maybe someone here knows,
So with NVflashing, I've found only one file that has the alternative BCT (it's a tnt1.0 rom on BL1.1) and no other NVflash file sets work without causing a APX bootloop.
This is the NVflash file set that works for me http://db.tt/FvSeAZj
Ive read it was made when someone was trying to configure for the hardware variations.
Now is it possible to take my backup and insert just the files needed into another NVflash file set?
----------- FIXED ----------
Hey guys,
I'm encountering a terrible problem with my P6810 tab. Here is the story :
At first, I just did format /system/ (and /data/, cache and dalvik) in CWM before flashing a new Rom.
After reboot, the tab just got stuck on the "Galaxy Tab 7.7" logo. no bootloop, just stuck on static logo.
At this stage i could go to download mode and recovery, which I did.
I tried to reflash the rom, no success so then i tried to flash stock ICS firmware through Odin 1.85 : Stuck on flashing Factoryfs.img for several hours, so i had no choice but to reboot the tab. (i had no kies-related software running, neither my antivirus)
There, the tab got stuck on the "Firmware upgrade encountered an issue. please select recovery in Kies" screen, no way to go to either recovery or download mode (not even worth saying Kies didn't recognize the tab).
I've been struggling a few hours with that brick and finally managed to get acces to download and recovery modes again by flashing CWM with Odin alongside a PIT file with "repartition" ticked in Odin.
So there I could access recovery, I flashed CM9, everything went smooth. The tab rebooted and got passed the Galaxy tab 7.7 logo and went to the cm9 bootscreen but got stuck there (big desillusion right there).
So now in recovery, i can mount every partition but those two : /data/ and /sdcard/
I figured out by reading similar threads that the solution to my issue might be e2fsck through adb. I'm a complete noob to adb.
I can acces the adb shell but here are what the commands i've been reading about return me : (mmcblk0p9 is /data/ partition on P6810)
# e2fsck -fDC0 /dev/block/mmcblk0p9 :
e2fsck : Superblock invalid, trying backup blocks...
The superblock could not be read or does not describe as a correct ext2 filesystem.
If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else),
then the superblock is corrupt and you might try running e2fsck with an alternate superblock : e2fsck -b 8193 <device>
also had this once with this command :
bad magic number in superblock while trying to open /dev/block/mmcblk0p9
# e2fsck -b 8193 /dev/block/mmcblk0p9 :
Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p9
Could this be a zero-length partition ?
# e2fsck -c /dev/block/mmcblk0p9 :
same as above
can you guide me with e2fsck or give me a link to a specific tutorial related to android e2fsck?
is there not a way in adb to like replace the corrupt partitions with freshly created ones ? or any other workaround ?
Any help will be appreciated a lot, i'm willing to donate to whoever provides me with a solution to get my tab running again.
Thanks for reading.
check this thread, very informative, helped me before
http://forum.xda-developers.com/showthread.php?t=1625675&highlight=bootscreen
Thanks a lot, already checked that one though.
Everything that worked for the guys in that thread doesn't work for me, or I'm too ignorant to find out the right e2fsck command...
Still no one able to provide some help please ?
It's weird that so many people are having the same issue on 7.7 these days, could it be related to the EU ban of this tab ?^^
Anyway, last day before i send it to Samsung
check this thread here it may help you solve your issue. All problems are coming from a brick bug in the ICS Kernel thats trigerred by wiping.
Thanks a lot, trying this right now
Can someone please post a (parted) print of a safe and working Galaxy Tab 7.7 (either of the two models) ?
I need the exact size of the /data partition
ISSUE FIXED Thanks to Zorbakun's last post. A million thanks dude.
However, the actual internal storage of my tab is now 50mb :silly: anyway i'll find a way to fix that too.
the actual internal storage of my tab is now 50mb
Hello Androguide.fr.
Did you manage to find a way to fix your shrink of internal storage? If so, would you mind to share the method. Thanks
Regards
Budi
cakrabayu said:
Hello Androguide.fr.
Did you manage to find a way to fix your shrink of internal storage? If so, would you mind to share the method. Thanks
Regards
Budi
Click to expand...
Click to collapse
Well yeah, didn't recover the 16gb but you can try to earn yourself some extra gigs by doing this once you created a fresh /data partiton :
this is an example for p6810, replace resize 9 with resize 10 if on a p6800
Code:
adb shell
parted /dev/block/mmcblk0
print
resize 9
It will ask you for start/end values, keep the same start value otherwise it will give you an error. A good idea is to resize the partition like + 500mb at a time, to avoid i/o errors you might get when creating/resizing large file systems.
Hope it helps, good luck.
I am about to have to do this myself, and i'm not a developer. i have accessed and navigated around my device through adb, but this level of complexity *almost* over my head. i just want to make sure i'm not going to permanently mess this up. also, someone in another thread tried flashing ICS with an older version of ODIN and now his tab won't even power on. which i'm trying to avoid... so after reading around these forums for a few days (it happened saturday morning--and i KNEW to avoid flashing from stock ICS recovery--i think i wiped /data-cache-dalvik with CWM 5.0.1) i'm pretty sure that failure to mount /data seems to be the super brick bug everybody's talking about. i bought the p6800 as an import in the US so i am without warranty... if anyone can help with a step by step guide for the masses or something... i'm intelligent, and quite computer literate/net saavy, but i'm not a mentat ("dune" reference)...
like, i'm having trouble figuring out how to install adb on windows. and how do i use parted when it's linux software? i've repartitioned HD's before, and i'm familiar with some command-line basics, but....
--going to bed now...my head hurts--
aletheus said:
I am about to have to do this myself, and i'm not a developer. i have accessed and navigated around my device through adb, but this level of complexity *almost* over my head. i just want to make sure i'm not going to permanently mess this up. also, someone in another thread tried flashing ICS with an older version of ODIN and now his tab won't even power on. which i'm trying to avoid... so after reading around these forums for a few days (it happened saturday morning--and i KNEW to avoid flashing from stock ICS recovery--i think i wiped /data-cache-dalvik with CWM 5.0.1) i'm pretty sure that failure to mount /data seems to be the super brick bug everybody's talking about. i bought the p6800 as an import in the US so i am without warranty... if anyone can help with a step by step guide for the masses or something... i'm intelligent, and quite computer literate/net saavy, but i'm not a mentat ("dune" reference)...
like, i'm having trouble figuring out how to install adb on windows. and how do i use parted when it's linux software? i've repartitioned HD's before, and i'm familiar with some command-line basics, but....
--going to bed now...my head hurts--
Click to expand...
Click to collapse
Try the .PIT file for the P6800 located here. You will lose all data, and part of your internal SD space. Looks like the brick happens consistently at the same point of the memory chip, so the same .PIT works for most people. If that doesn't help, you will need parted.
How can you use parted? It's a Linux program that runs in your tablet. You will adb shell to it, then you will have a Linux shell. Everything you put down there will run in your tablet, as if you were typing on it (think ssh, or remote desktop). I can't help you much more, because (knocks on wood) my tablet is still very much alive, and I don't use ADB that much.
Now, I don't know how it works in your country, but here in Brazil the Samsung service accepts warranties issued anywhere. It may be worth a shot.
aletheus said:
I am about to have to do this myself, and i'm not a developer. i have accessed and navigated around my device through adb, but this level of complexity *almost* over my head. i just want to make sure i'm not going to permanently mess this up. also, someone in another thread tried flashing ICS with an older version of ODIN and now his tab won't even power on. which i'm trying to avoid... so after reading around these forums for a few days (it happened saturday morning--and i KNEW to avoid flashing from stock ICS recovery--i think i wiped /data-cache-dalvik with CWM 5.0.1) i'm pretty sure that failure to mount /data seems to be the super brick bug everybody's talking about. i bought the p6800 as an import in the US so i am without warranty... if anyone can help with a step by step guide for the masses or something... i'm intelligent, and quite computer literate/net saavy, but i'm not a mentat ("dune" reference)...
like, i'm having trouble figuring out how to install adb on windows. and how do i use parted when it's linux software? i've repartitioned HD's before, and i'm familiar with some command-line basics, but....
--going to bed now...my head hurts--
Click to expand...
Click to collapse
I am working on writing a specific 7.7 guide to teach people the parted/e2fsck technique I use to revive my bricked p6810 everytime I want to flash a new rom or test my builds.
First, as pointed out, try to Odin the PIT file for your particular model (eg : P6800 16gb).
You got to know that the parted technique is a pain in the ass, that you'll have to do it quite often if you like flashing roms, and that your tab will have a much smaller internal storage.
I think the guide will be ready in a couple days but you can pm be if you need help before that, no problem.
Good luck with this superbrick curse
thanks guys for your help, i'm going to try to figure this out this afternoon. i'm in the US, so they don't even offer warranties on imports. i was told by a samsung rep in the US that they don't grant warranties to imported models. i will first try the modified PIT file, then i will try the more complex method. @Androguide.fr i will PM you if i have trouble with the more complicated method later. thanks!!!!
aletheus said:
thanks guys for your help, i'm going to try to figure this out this afternoon. i'm in the US, so they don't even offer warranties on imports. i was told by a samsung rep in the US that they don't grant warranties to imported models. i will first try the modified PIT file, then i will try the more complex method. @Androguide.fr i will PM you if i have trouble with the more complicated method later. thanks!!!!
Click to expand...
Click to collapse
I just finished writing the guide, it's here : forum.xda-developers.com/showthread.php?t=1862294
Hi all,
Has anyone followed Rayman's excellent article the-inner-workings-of-secure-boot-key-and-nvflash and fully recovered a N7 from APX only mode?
I have this situation which I think resulted from the battery dying during the 4.4.2 update - Doh I know, but thought I had enough juice to complete the update.
Rayman says the required files will be made available but I cannot find them anywhere
Since every motherboard has a unique key, there is no generic blob. To be able to recover your N7, you will need a backup of it, but it's impossible to make if your device is dead.
Try to send it to Asus/Google.
Erovia said:
Since every motherboard has a unique key, there is no generic blob. To be able to recover your N7, you will need a backup of it, but it's impossible to make if your device is dead.
Try to send it to Asus/Google.
Click to expand...
Click to collapse
Did you read the article? Sounds like you can use the sbk which is a hash of the cpuid...
Nope, but why don't you ask around in the flatline topic?
Erovia said:
Nope, but why don't you ask around in the flatline topic?
Click to expand...
Click to collapse
too much of a noob to post on the forum, but thanks for the pointer.
FYI Raymans article. It does sound possible to bring it back, but there was no follow up with the required files;
What is Secure Boot Key and how does it work?
I've been getting lots of questions about this, so here is some simple background:
The secure boot key is an AES128 encryption key that can used to encrypt various data on the flash memory. It's a generic nvidia tegra2 thing, that the manufacturer can optionally use to make their device more "secure".
When the SBK is set, it's stored in a one-time-programmable "fuse". This also means that now that the key is out, they can't change it on already released devices, only new devices.
When the tegra2 starts up, the AES key is available to the hardware AES engine only. E.g. not even the bootloader can read it back! However, the bootloader can *use* the key to encrypt whatever data it wants through the hardware AES engine. And here is the explanation why the blob flashing method actually works! The bootloader checks for the blob in the staging partition and encrypts and flashes it as needed.
Once the bootloader is done, it clear the key from the AES engine which makes it impossible to encrypt or decrypt things from within the OS.
So what happens when it boots into APX/Nvflash mode?
The basic APX mode is stored in the BootROM and hence can never be changed. It appears to accept only a very limited range of commands, and each command needs to be encrypted using the SBK to be accepted. If it receives a command that's not properly encrypted, it disconnects the USB and appears to be off. This is the dreaded "0x4" error that people have been getting when attempting to get nvflash working.
It should be noted, that even with the SBK inputted into nvflash, most regular nvflash commands won't be available. I'm still not entirely sure why (and I can't rule out it will change).
What *is* available, is the nvflash --create command. What this command does is repartition and format all partitions, set bct and odmdata and send over all needed partitions to the device (and encrypt them as needed). This means a full recovery is possible, but regular ability to flash e.g. just boot.img or read partitions off of the device is not possible at this point.
So what do we need for nvflash?
In order to get a working (e.g. --create) nvflash, we need a few bits of information as well as some files:
◦Secure Boot Key
◦BCT file (boot device setup, ram configuration and a bit more)
◦ODM data (board-specific bit-field specifying various board settings. *Needs* to be correct
◦flash.cfg (e.g. list of settings and names/identifiers of partitions.
On top of these files, we also need all the partitions, e.g. bootloader.bin, boot.img, recovery.img and system.img. Luckily, these partition files are available in official ASUS updates and can be extracted from the blob file using my blob tools
The first four peices aren't readily available, but through lots of effort and a good deal of luck, we have managed to recreate the needed files. Secure Boot Key has already been released (note that this was by far the hardest!) and the rest will most likely follow over the weekend. Keep in mind that we want to keep this legal, so don't expect us to release any ready-made packs for unbricking! We will however make the recreated files available. Since these are recreated and not actual ASUS files, there should be no problems with them.
I hope this helps give a better understanding of how and what secure boot key is and what it gives us.
Well, I have been going through many tab owner problems on this forum who have tried everything on the book to get their tab back running. this experimental process is only for those people who have no option left than to throw away their tab as a dead glorious paperweight or play with it as a Frisbee. hopefully it can recover or at least it can open a new way for getting out of a brick or perhaps be a good learning experience, just for the sake of it. what else would you want to do? if your device is un-repairable? at least this can take a backup for the complete device in a different way though.
So what really is this about?
Well, Samsung tab 2 emmc is pretty much notoriously getting scarier, either it is happening because of flashing a wrong kernel or doing wrong with your tab, or in some cases where people had no clue. A sudden attack and the tab was dead. you may be lucky to get a replacement and get the tab running up again. but not all could be solved and resolved.
but what if we provide the tab a second emmc(your external card emulated and working as an exact image of the internal emmc with all the system files with their partition on it?) sounds good eh? there are 2 sides of this coin. one, our device is not made that way and it's definitely not going to work at all, second, it can work after a little hardware modification provided you have the right files and right tools and a insanely expert brain. Now the chances of this working is like that of flipped coin landing on it's edges. very tricky.
But how we can achieve this then?
Well, there are users on the internet that have some sort of success in this, while it wasn't guaranteed for their device, that this process can work for all and there is definitely nothing like this sort ever found for our device. which is on omap chipset, it's the debrick method. you can't tell unless you are from the development department of Samsung. So, I would say even if it's 0.0000000001 percent of having a chance to work for us. I would like to keep it.
Debrick.img? what does it do? how to get it?
Well, this file is generally taken out from a stock rom from location /dev/block/mmcblk0 which is where pit stores the data for all the partition and from there we can extract all the important parts, including the boot-loader, recovery, cache, hidden, sbl1, sbl2, factoryfs param, modem, EFS, DataEFS to a .img file. (as far as my definition goes for better understanding). please feel free to go through all the post that you can find about the debrick, or if you have more knowledge please share.
I was just going through these posts.
The whole process for sg s3 http://forum.xda-developers.com/showthread.php?t=2660566
http://forum.xda-developers.com/showthread.php?t=1818321 a guide that explains about taking backup of the entire memory block with all partitions or single partition. it's quite old but informative.
fixing a bootloader
http://forum.xda-developers.com/showthread.php?t=2345860
there are different parts to it, first is getting the bootloader written on a external sd card. but we still don't know if our device will be able to treat the external sd card as an internal emmc. it is yet to be found out.
my theory is suppose if we can get out the whole partition along with system written on a external card, can we make the device treat it as a internal emmc? will it then be possible to revive a dead internal emmc tab? there are chances it might. still no practical though and no guarantees for sure.
but it makes you feel better, I managed to get out those partition on a .img file which could be written on a external card as well. basically an image of your emmc. this might be a good backup too for those who would like to be safe in case a emmc bug hits them too.
Now, To get this data we need volunteers to take these files from their working rooted stock rom and upload these files for every model of samsung tab, if they wish to contribute to our community, you are welcome. or at least keep it safe on their disks. although, this process will require atmost care as we are dealing with bootloaders here, and one wrong bootloder and it
won't work, as much as my knowledge goes, there are two- the ics and jb for our tab 2. still there are many other variants and I really have no clue, how to work this out all by myself. so, I would like other great minds share their wisdom upon this and please before sharing files, mention everything you can, right from your
1. Device model number
2. 8gb or 16gb
3. Bootloader(ics or jb)
4. Stock rom, custom rom,
5. firmware
6. Baseband
7. Country and to your name.
Now before pulling out this file, I have a doubt, as I have got few imgs option. there is 128mb, 200mb, 256mb, 512mb and also I have got one img of around 2.17gb as well which is the complete backup I could take out from my device.
I am not sure which one to choose that's going to work. people have mostly used 128mb file to get access to the download mode, I guess in that 128mb, there is enough files needed to boot your device into download mode and recover from hard bricks, but there is no evidence as for now in our device section as to which is suffient for us. So for first try, we take 128mb, and keep doubt aside for one process.
but suppose it's our emmc bug and we want to use the external as a image of the damaged internal, in that case I suppose we need to take out the whole info! is it really possible with the 2.17gb of my device complete data? ah, I would really like to know about the answer myself, in case it hits my device, I would be prepared myself
anyways to try this you must have a sd card reader and use a external card of 16gb or 8gb depending upon your device variant (card class 10 required, on others it has high chance of not working at all)
Now the process to extract the file
The script that you need to enter into terminal emulator(download one from playstore) this will backup a 128mb file on your sdcard.
Code:
#su
#busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
128MB is arbitrary. on some devices 70MB was sufficient, on our device? maybe or maybe not. please test or help me answer this correctly, if I'm wrong. but untill then, use 128mb, if we fail, we will look for other options.
other dd commands
Code:
1. dd if=/dev/block/mmcblk0 of=/sdcard/backup.img
backup whole partitons thus will be large size and takes more time.
Code:
2. dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=70
70mb data from mmcblk0 will be copied to sd card
Code:
3 dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=512
512mb data from mmcblk0 will be copied to sd card
Code:
4. dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=4096
large size more than 4GB and more time consuming
Procedure
1. Connect the external sd card to the card reader move all the files to your pc and format it.
2. find the correct debrick.img image from post 2.
3. Download and extract this software win iso burner
4. Open the software win32diskimager.exe and browse the debrick.img
5. Successfully Write the debrick.img onto it.
6. Put the sdcard in your device
7. Pray, or do the cha cha, praise the droid lord.
8. switch it on or press power button + volume down/up, whatever you can.
9. if you can then get into download mode, you can try to flash stock firmware or dance your way around.
10. report us back what happened.
1. Download Debrick dump imgs. (128mb)
Samsung tab 2 10.1 P5100 16gb
jellybean boot-loader.
was on custom 5.1 rom and twrp recovery from UAE firmware.
Samsung Tab 2 P3100 16gb
shared by @jak978 on post 6 Hit thanks for him.
more will come, when people will share.
for other guides and ways
interesting, unfortunately my broken emmc have replaced with eemc from note 2, tho mine is p3100
jak978 said:
interesting, unfortunately my broken emmc have replaced with eemc from note 2, tho mine is p3100
Click to expand...
Click to collapse
So, you're one of those lucky ones. Getting a replacement is still the best way. So, do you think my theory here could work? Anyways it would be an interesting answer to find out. But people would need to share files here first for any samsung tab 2 model. I hope it becomes helpful rather than just interesting.
billysam said:
So, you're one of those lucky ones. Getting a replacement is still the best way. So, do you think my theory here could work? Anyways it would be an interesting answer to find out. But people would need to share files here first for any samsung tab 2 model. I hope it becomes helpful rather than just interesting.
Click to expand...
Click to collapse
here you go tab2 P3100 16GB
Anybody having any luck with this procedure??
Rag888 said:
Anybody having any luck with this procedure??
Click to expand...
Click to collapse
Well I still haven't faced the emmc bug, so can't really test on my device yet. nobody else who faced this issue had tried this and posted or shared any of the findings here.
Updating the emmc firmware via. ISP gives back life to >80% of affected devices.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get "read only", so you can't perform any write actions (also you can't format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
Click to expand...
Click to collapse
On a faulty EMMC firmware it happens a lot faster if the emmc reaches a wrong value.
Sadly Patching the emmc fw isn't possible running the device, at least there's no known kernel on chip power-on Method...
Those from europe can contact @html6405 , he is able to update the emmc firmware and he can also replace the emmc if needed.
Note:
Sharing a whole copy if mmcblk0 isn't good, because it will include efs partition which is sensible data.
~ All my work, news etc. on http://andi34.github.io ~
Found something interesting printing the pit using heimdall:
https://paste.omnirom.org/view/4173cc20
Someone knows what the GANG partition is for?
I wonder if it is the emmc firmware because emmc.bin is stored there...
I am waiting to get the fixed emmc firmware, i might be able to tell you once i have it.
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
Note:
Sharing a whole copy if mmcblk0 isn't good, because it will include efs partition which is sensible data.
Click to expand...
Click to collapse
Yes, better to keep them private. Users do not share, just keep a backup with yourself.
thanks for your thorough research.
Android-Andi said:
Found something interesting printing the pit using heimdall:
https://paste.omnirom.org/view/4173cc20
Someone knows what the GANG partition is for?
I wonder if it is the emmc firmware because emmc.bin is stored there...
Click to expand...
Click to collapse
I did notice the GANG partition since you mentioned it(strange I never realized this before as I have looked at the pit file many times earlier as well.) located at 0x64C.
it does look like the emmc firmware partition. what else it should have?
jak978 said:
interesting, unfortunately my broken emmc have replaced with eemc from note 2, tho mine is p3100
Click to expand...
Click to collapse
hi jak978,
i plan to replace my p3100 emmc with p5100 emmc, can i just flash p3100 firmware using odin after change the emmc?
some more, can u re upload the debrick dump for p3100, it says "file not found" in your link.
regards,
alms
here you go tab2 P3100 16GB UNABLE TO GOT FILE PLEASE SHARE THE FILE PLEASE
---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------
billysam said:
1. Download debrick dump imgs. (128mb)
samsung tab 2 10.1 p5100 16gb
jellybean boot-loader.
Was on custom 5.1 rom and twrp recovery from uae firmware.
samsung tab 2 p3100 16gb
shared by @jak978 on post 6 hit thanks for him.
More will come, when people will share.
Click to expand...
Click to collapse
please re share p3100 file i need it my tab was not work or trell me any way to get emmc chip from online or else process
my tab only in condition on restart restart.....
No recovery and firmware ll able to write on p3100
please help your reply too much helpful for me please give file p3100 so i can use your method
asiffrluv said:
here you go tab2 P3100 16GB UNABLE TO GOT FILE PLEASE SHARE THE FILE PLEASE
---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------
please re share p3100 file i need it my tab was not work or trell me any way to get emmc chip from online or else process
my tab only in condition on restart restart.....
No recovery and firmware ll able to write on p3100
please help your reply too much helpful for me please give file p3100 so i can use your method
Click to expand...
Click to collapse
Look at this on eBay http://www.ebay.com/itm/192025936615
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Hi,
I just tried this method. The tab boot on the sdcard, i have the charging logo displayed, and then screen turns black. The driver change from omap4430 to Android, and keep this driver until i unplug the usb cable.
On linux, the tab device is recognized as Android. Same on windows (loaded in virtualbox from linux).
adb device display an unauthorized device.
So from this step, it is still impossible to flash the tab.
Anyway thanks for sharing this; even if its painfull to lose a tab, it is nice to learn how all this work.
if other people have more information to share, i would appreciate any new info on this subject
billysam said:
1. Download Debrick dump imgs. (128mb)
Samsung tab 2 10.1 P5100 16gb
jellybean boot-loader.
was on custom 5.1 rom and twrp recovery from UAE firmware.
Samsung Tab 2 P3100 16gb
shared by @jak978 on post 6 Hit thanks for him.
more will come, when people will share.
Click to expand...
Click to collapse
Links are dead can you update them?
@Android-Andi @billysam @jak978
Sorry for pinging do you still have the p3100 debrick img?
No, never had it.
Ugh dev host dosent work in 2020
Still waiting for the link
I done ****ed up.
I was attempting to wipe modemst1 and modemst2 because I had flashed a good five different radio firmware packages, and I was rather concerned that there was some conflicting... stuff happening. I thought I had taken successful backups, just in case. However, it turns out these backups failed to write properly, and instead created blank files.
Lo and behold, when my IMEI decided it didn't want to IMEI anymore (it currently reports as 0), I had no recourse. However, all is not lost! I can edit a restored modemst1/2 and write these into position... I think. However, I need help - I don't have another Axon 7 to fetch from. So, if someone here would be so kind as to provide some, that would be extraordinarily good of them.
If you're wondering, this is the command to make a copy:
Bash:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/storage/0000-0000/modemst1backup
dd if=/dev/block/bootdevice/by-name/modemst2 of=/storage/0000-0000/modemst2backup
These commands should place the files modemst1backup and modemst2backup on your SD card. If you have no SD card at hand, replace 0000-0000 with self/primary to save on to your phone's internal storage.
It's probably a requirement for your handset to also be a European A2017G - a US or CN model might not be compatible, but I honestly don't know whether or not that is a load of horse-****e. Thankyou in advance!
That sucks man, I have no idea what to say so I'll just leave this here:
F
I fixed it! Turns out it's actually not that hard to write an IMEI to a Snapdragon device. I'll make a guid post on this in a moment.
Edit: guide up: https://forum.xda-developers.com/t/guide-imei-fix-for-zero-value-imei-strings.4402835/
Edit 2: Turns out I didn't fix it. Looks like I still have some issues. I could still use a copy of modemst1 and modemst1, if anyone could be so kind.