Related
I used RSD lite to flash to 4.1.2.6 and when it boots up the touch screen is way off and i can even go back or click the buttons on the bottom row. Anyone else have this happen? I reflashed twice already to see if it would fix it.
I've been toiling day and night for the last few days with the exact problem!!!
Tenfar is trying to help me via PM.
Because I partitioned internal SD this happened. I figure we need to do following command:
adb shell mkfs.vfat /dev/block/mmc0p18
And then
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18
But I'm getting random daemon errors now because my PC is a piece of ****!! Trying to fix that problem to run the first command. Second command goes through okay but I'm still having touch screen issues.
Waiting for him to PM back. I'm in Canada with an AT&T Atrix and although the seller can send me proof of purchase, to send it to Motorola would take super long and would cost lots in shipping.
If you find anything, please post it here. I'll do the same!
lol
lol yup thats what i did. I realized it wouldnt let me install from internal sd and i didnt have a external sd at the time so is figured let me format it.. whats the harm. Well the harm is the whole bottom row of buttons doesnt work and the bottom of the screen is a half inch off lol. Been driving me crazy, let me know if u get anywhere with tenfar
Getting stupid daemon errors I can't fix. Going to try on another machine and will let you know if there's any progress. Seems simple enough in concept but I'm no Linux genius.
I'll keep you posted.
Have u tried booting into the recovery and partitioning the internal sd another way?
fallchild said:
Have u tried booting into the recovery and partitioning the internal sd another way?
Click to expand...
Click to collapse
Yep. I've tried it all. Has to be manual now from what I gather... didn't get the chance to try on a new computer last night but will after work. I'll send you the commands if it works.
Dear lord, I hope it works!
Any Luck? I use my phone heavily for work and i had to use bluetooth all day with voice commands just to use the phone half way decently lol.
I had the same issue. I wasn't able to boot into my custom recovery and repartition. I ended up taking it back to AT&T and getting it exchanged. Can always pass it off as a bad device.
No luck. Same error. I tried mounting SD but I think I must be doing something wrong..
Still giving it another few tries. What a bummer. Gotta rip through the Atrix dump to see if I can find something else useful.
Can't unmount my SD card and successfully run the other command. Not sure what the heck I'm doing wrong. Now I'm uncertain what state my phone should be in when I run these commands.
I'm going to keep tinkering around but I'm waiting for the proof of purchase because I think I'll need to send it in. Damn. Wish I had someone in person that knew how to use shell commands properly. I'm not the greatest at this. Using an Xperia X10 in the meanwhile and dying to use my Atrix again. :'(
Hopefully someone will be kind enough to do a Nandroid backup of a fresh install and post it. I'm not sure but I think it could possibly help. It's worth a shot. Would pay someone $10 via Paypal if they could upload it to their Dropbox or something.
Hey OP, any luck?
If you have a new Atrix. Could you do a Nandroid backup and upload it to Dropbox by any chance???
I've exactly the same problem! (And when you are in some menu, you can't go back, so you have to reboot!!)
I did the same thing (Root, put recovery and so...)
I partitioned internal SD... And now, it's like touchscreen completly disturbed.
When you click on home - back or search, the screen select the bottom of the android interface!
I need to know if someone has a correct issue for that... I'm not at home, I will test the commands in adb from the second post later...
Also, I don't understand how a nandroid backup could resolve the problem... A backup will resize and fix the internal memory?
Thanks
well, i got the dreaded "can't mount /dev/block/mmcblk0p1" error, and decided to try some stuff i learned since i had some important photos/videos from a recent trip on there. turns out it worked, and figured i'd share with anyone (although it seems this error is fixed with the latest software). i recovered everything off my phone, totalling to approximate 1.7gig.
flash a adb recovery ROM with SU (can't remember if the SU is necessary, but there are pre-rooted roms out there, i just used one). also make sure all the drivers for the phone are installed on your computer
adb shell
su
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
with winhex, open drive. a directory browser will show your file structure, and right click-->recover/copy whichever files you want. i went a step further created an full image so i can send in the phone. now i have a complete backup i can go back too at any time in case i forgot something i needed.
i tried re-flashing this phone with jg8/jh2/jk3/jl2 with different PITS trying to bring it back and nothing. tried force mounting it and some other commands, but in the end, this worked.
somebody should give this a try.
great work
i could've really used this had it been a month ago, before i sent it in and lost everything
hey Ziostilon, when you had your phone fixed last month, did they mail you a new phone, or did you bring it in for repair? these Bell guys are breaking my balls and saying samsun can recover all my data, and i have to send it in for repair for a month
edit: it looks like this worked because the data on the partition is still intact, just the partition table is messed up. i wonder if a program like partition magic can repair the partition in it's current state? it might be something to look into for people without a warranty.
so my lovely G2 had a personality split.. sorta. as you can see from the attached image its done for. however, the bottom part (with the battery) still may work, even though its without the screen. when i plug it into my computer though, nothing happens. but nothing happened when i plugged it in when it was not broken either, its only when i set it to the USB storage device is when the PC recognized it.
i really would like to get a bunch of **** off this phone if possible. i had a lot of stuff on the SD card (including a bunch of apps that were installed/moved on the card), but all my texts and such are on the phone.
is there a way to get that stuff of the phone, through some debugging software maybe? also, the apps that are on the sd card, how would i put them on the whatever new phone i get? they're not with the .apk extension.
thanks guys for any help
Hey sell me it or something I want that front part so bad.
Sent from my Energized Amaze 4G
Or My Sexy Nexus 7
Yes girls know about XDA
you can thank a girl on here
how did u do that? take a look at the instruction how to change the display maybe you get forward with it
xbleem said:
how did u do that? take a look at the instruction how to change the display maybe you get forward with it
Click to expand...
Click to collapse
i was thinking of swapping the display, but don't want to risk buying one and then it not working anyway due to the damage elsewhere on the phone. i think i'll just buy another g2. love the ergonomics of it. got a galaxy s3 as a replacement and can't stand it. way too huge for me and the design is awful.
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
gee one said:
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
Click to expand...
Click to collapse
thank you. i will fiddle with that this weekend.
what is the jtag info you're referring to?
It's a protocol from communicating wiht the chips directly- it's usually used to unbrick android devices, but I don't recall too much info for the g2, other than someone posted a pict of some of the jtag ports.
If you have a recent cwm backup, that will probably be the easiest way to recover. As a matter of fact, I did that just now. I upgraded to jellybean, but in a moment of noobness, I wiped data before backing up the two files that have to be backed up manually (mileage.db and wpa_supplicant.conf). A little command line hacking and everything is right in the world.
gee one said:
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
Click to expand...
Click to collapse
If you have a friend with another G2, you could probably mimic button presses in order to do a nandroid backup (then extract the /data image).
Failing that, I'm sure someone on here could give you the exact button press count to do what you need to.
the thing is guys, i'm not very good with adb. i found a few videos online on how to do a screen portion swap along with the rails. and i'm going to bid on a G2 on ebay. i'll swap the screen and rails from the one i buy to my G2. see if that works, then probably just sell the unused portion of the other G2. i will hook up my G2 to adb though tomorrow. i have to install it when i get home. anyone know the link to the adb download?
what kind of OS do you have? It's much easier in linux, if you know linux.
There might be a link to a binary, but this will get you going with adb.
https://developer.android.com/sdk/index.html
You don't need to update everything - just the SDK platform tools.
So how bad is it? What type of data are you trying to save? Most of it will probably be on the SD card. Do you have a clockwork mod backup?
Disclaimer
Before even consider reading this, know that I cannot be held responsible if following these steps will: brick your device, make your girl friend break up with you, start third world war or do any other kind of damage.
Motivation
This tutorial is intended to help people who did not make a full backup of their device and applied the Alpha-FormatTouch-2.zip to their device and as a result lost the GlowLight feature. It took me a couple of days to figure out how to revert to factory settings, and thus, I hope that I can save others time.
Preliminary
You need
Nook Simple Touch Glowlight, semibricked
SD Card
SD card reader
Downloads
Download the following files:
factory.zip - downloads[dot]nanophysics[dot]dk/nstg/factory[dot]zip (if you have a copy of your own factory.zip -- found on the partition /factory/ -- use that instead)
[ClockworkMod - downloads[dot]nanophysics[dot]dk/nstg/sd_128mb_clockwork-rc2[dot]zip
Install Clockworkmod on SD card
On Mac OS X, plug in the SD card and find the device using
Code:
$ diskutil list
I will assume that your device is /dev/disk1. Unmount the disk
Code:
sudo diskutil unmountDisk /dev/disk1
and write the ClockworkMod to it
Code:
sudo dd if=128mb_clockwork-rc2.img of=/dev/disk1
Copy the factory.zip to the disk and eject it.
On Windows you can use Win32Imager.
Install factory image
Power off your Nook and insert the SD card. Then power it up. After a while the CWM menu will appear (if you get a white screen press right-down). Select "install zip from sdcard" using the right side navigation to go up and down and u to enter. If you enter the wrong menu you can go back on right up. Now select "choose zip from sdcard" and choose factory.zip. Finally, click the option saying "yes - install factory.zip"
After a few minutes the installation is complete and if everything went ok, you should now be back to the original factory software.
Reset user settings (optional)
If you want your Nook to be completely reset, you can optionally do a reset of your settings. Power off you Nook. Power it up again and hold left and right down simultaneously for around 30 s. Answer yes twice. After a while your Nook has been reset.
Backup
Finally, it is time to do what you should have done in the first place (and probably also the reason why you are following this tutorial): Make a full backup of your Nooks internal SD card. See blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch for more information.
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
shank21101985 said:
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
Click to expand...
Click to collapse
If your NSTG is rooted, this may remove rooting - at least I think, I did not try. However, you can always reroot.
Regarding backup, I would make a full image backup before starting. If you have a Windows box, follow the instruction on blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch and make a full backup of your system.
I have only done backup of individual partitions on Linux: Boot the device with noogie.img and plug it in. On Ubuntu,t 6-8 partitions should immediately appear.
jjinkou2 said:
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
Click to expand...
Click to collapse
There was missing a slash in the URL. It has been fixed.
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
roustabout said:
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
Click to expand...
Click to collapse
Remark that I recommend that people use their own factory.zip image. Nevertheless, all these data you mention are stored on the rom partition. To my awareness this partition is only overwritten if one applies rombackup.zip, but not by factory.zip. Thus, your B&N shop should be fully functional afterwards. I did apply someone elses factory.zip first, and I had no problems registering my device. However, if anyone would experience such an issue, please drop a line in this thread.
In any case, you should always do a full system image before following tutorials like this one, or for that matter, before apply someone elses partition images to your own device.
roustabout said:
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
Click to expand...
Click to collapse
Judging from your other post (http://forum.xda-developers.com/showthread.php?t=1836188&page=4), the partition you have made a copy of, is the boot partition? If glow was already working, it will still work after overwriting the boot image.
However, if it was not working already, it is very unlikely that installing a new boot image will resolve the issue described here, since it is a consequence having downgraded the OS.
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
roustabout said:
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
Click to expand...
Click to collapse
Ok. No this thread is not intended for people who have destroyed partition tables etc., but only for people who have downgraded their software by using NST recovering guides on their NSTG device. I found it relevant to explain how this is done, since many people complain that their NSTG works, except that glow light no longer works. If they look into the software version they find something below 1.1.5, like 1.1 which was my case. I could not find a guide which explained me what to do after screwing up the software, hence this guide.
Partition tables and "accidently formatting" is a completely other issue. In the end, here the main problem is that people do not make a backup as they assume that everything is going to be fine. I assumed that myself. However, at some point I will have a look at the rom partition, because I think it is quite limited amount of information you find their. It should be possible to restore your Nooks serial number -- it is written on the package of the Nook -- after applying another Nooks image. I just received my second Nook so I am going to try this at some point.
Thank you so much for sharing the solution.. finally my glowlight works now !!
shank21101985 said:
Thank you so much for sharing the solution.. finally my glowlight works now !!
Click to expand...
Click to collapse
Hic, I cannot download the image file, my backup file was deleted, anyone can upload that image for me?
Thanks so much:crying:
factory.zip
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
So did you actually replace the factory.zip with one for the NST or did you just run a restore from, say, NookManager? I'm not too sure about this, but I think it's kind of difficult to wipe the factory.zip. Anyway, since I'm not familiar with the NTG, and you seem to have done something that others have also done before, have a look at this old thread and see if it gets you anywhere:
http://forum.xda-developers.com/showthread.php?t=1936458
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
nmyshkin said:
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
Click to expand...
Click to collapse
Its dead I need a glowlight factory image
can someone please re-upload the glowlight factory image please.... Thank you in advance
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