Related
I need a litle help.
1st. AT&T tab flashed for voice (followed roto threads)
for few weeks worked nicely. (din't do any other flashing)
Then I did get some force closes and after reboot I don't have my mmc0. (which means I can get into recovery mode and ADB, doesn't boot android. (samsung logo keeps flashing from time to time)
Error in kernel:
mmc0: error -110 whilst initialising mmc card
and then complains to not seeing mmcblk0
I see my options as FLASH back to stock AT&T and return to Samsung.
does samsung complain about flashing? does it void The warranty?(do I need to flash it back?)
I have backup's of the flash BUT maybe there are other ways to help?
for the flash back I will post more questions as the tab is missing AT&T logo at boot time and I am worried about flashing boot) (someone could point me to stock firmware with boot which was tested).
Any ideas about samsung return policy? (paid full price which means no at&t help I guess)
adb still works but no root.
Thank you for your help.
Could it be corrupt internal storage
Sent from my HTC Wildfire using XDA App
I can't see device in /dev/block/mmcblk0 and mmcblk0p1, currently I am waiting till it dicharges it's battery. (hoping for cold start)
update:
Tab is able format and use external mmc as internal. (which means I have workable tab without 16G of internal storage)
now I am going to flash back from my backups to stock and return.
I will post updates, as I intend to flash boot and spl. (and I am worried I will have BRICK.)
monoko said:
update:
Tab is able format and use external mmc as internal. (which means I have workable tab without 16G of internal storage)
now I am going to flash back from my backups to stock and return.
I will post updates, as I intend to flash boot and spl. (and I am worried I will have BRICK.)
Click to expand...
Click to collapse
Don't do it! Try Roto-JME that reformats the internal sdcard.
any progress here?
how can you format internal SD if it cannot even be mounted? I have the same mmc0: error -110 whilst initialising MMC card issue.
tekky
Yes. After long time waiting I managed to send it to samsung for rma It took 2 weeks. And returned in working order. No problems with rma. Abou mmc0: kernel complained about hardware and then mmc0 was the next device, means external sd card was my new mmc0
I tried to flash it back to original state and managed to brick it. But rma was no problem. I told them that there is no power. My guess is that it was propably hardware error on side of internal sd.
Hi, My Galaxy Tab 10.1 is so far in its Sleep of Death that only the APX connection works (believe me, battery draining, holding Power button, getting into recovery, etc: it doesnt work).
Through NVflash, i can get its partition table and read all partitions 2-17 to .img files, but i can't recreate the entire filesystem because i don't have the right nvflash configfile (mostly named flash.cfg) and i presume i need a fresh bootloader file because i think the bootloader is hosed.
Can anyone help find me these files? Thanks
I had the same thing happen to my Tab.
I eventually sent it back to a Samsung service centre and they fixed it for me.
I was a bit worried because I had flashed an ICS ROM on it but they fixed it FoC and returned it to me. The whole process was really fast taking under a week.
pwhooftman said:
Hi, My Galaxy Tab 10.1 is so far in its Sleep of Death that only the APX connection works (believe me, battery draining, holding Power button, getting into recovery, etc: it doesnt work).
Through NVflash, i can get its partition table and read all partitions 2-17 to .img files, but i can't recreate the entire filesystem because i don't have the right nvflash configfile (mostly named flash.cfg) and i presume i need a fresh bootloader file because i think the bootloader is hosed.
Can anyone help find me these files? Thanks
Click to expand...
Click to collapse
Pershoot has them posted..
Http://droidbasement.com/db-blog
I/O recovery fast boot/nvflash in the middle of the page..
Hope this helps..
Sent from my SPH-D710 using xda premium
z31k said:
Pershoot has them posted..
Http://droidbasement.com/db-blog
I/O recovery fast boot/nvflash in the middle of the page..
Hope this helps..
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Hi, thanks for your help. Unfortunately i already flashed the stock recovery to partition 8, but i need at least the BCT & EPT partition contents, plus a cfg file which tells Nvflash how to recreate the partiitons from scratch. Off it goes to the repair centre, i hope it will return soon.
VERY similar problem
pwhooftman said:
Hi, thanks for your help. Unfortunately i already flashed the stock recovery to partition 8, but i need at least the BCT & EPT partition contents, plus a cfg file which tells Nvflash how to recreate the partiitons from scratch. Off it goes to the repair centre, i hope it will return soon.
Click to expand...
Click to collapse
Have you gotten anywhere with this? I'm in almost the exact same position with my I/O P7510
ayresd54 said:
Have you gotten anywhere with this? I'm in almost the exact same position with my I/O P7510
Click to expand...
Click to collapse
This is all original stuff from I/O tab https://www.dropbox.com/sh/ny5d3iu4mttfhgn/qOQ1IIRnzJ/tab1_3.0.1 hope you can cherry pick what you need from there (It's uploading now as I send this, give it a while to all be there)
If i have locked boot loader how to do this commands
stinky73 said:
This is all original stuff from I/O tab https://www.dropbox.com/sh/ny5d3iu4mttfhgn/qOQ1IIRnzJ/tab1_3.0.1 hope you can cherry pick what you need from there (It's uploading now as I send this, give it a while to all be there)
Click to expand...
Click to collapse
thank you,I downloaded your link files but is it for gt-p7510 32G
I have the same problem metioned above because i repartitioned internal storage with adb shell
but my tab has locked bootloader (0x4 error ) "so can't apply the above commands" and right now the only thing that i can see is apx mode with black screen
draining battery method not worked for me... i took it to center that provide jtag service but he said cant rewrite files "access denied"
so, after two weeks searching and trying my tab still dead. I live in Syria and we have somehow civil ware or revolution and most of people run out the country so i don't know where or how to fix it :crying: :crying:
I had a similar issue with my 4g 7500, just googled the crap out of it and repartitioned and fixed it. Took at least 10 flashes to fix
Sent from my GT-P7500 using xda app-developers app
If you have the eMMC brick bug with a locked bootloader the only way to fix this is to have it repaired by an official Samnsung service center (someone with access to the bootloader). None of the methods that were posted in the long threads will work nor have been reported to work if your bootloader is locked. In many cases it looks like the Samsung repair centers opted to replace hardware rather than flash the bootloader as many people reported their devices coming back with different chip IDs.
There was another soft brick issue before the eMMC brick bug appeared. With this issue it was possible to used the methods described in various threads to fix it (such as the battery drain method) regardless of whether the bootloader is locked or not. These methods do not fix the eMMC brickbug.
This is a long shot.
I also have the regular retail 16GB GT-P7510UW which sleeps the deep sleep of death. So far I tried everything on here, even replaced the battery with a brand new one. But still I can only access it in APX mode.
My Tab is not locked, so I don't get the 0x04 error with nvflash. But it looks like something is messed up pretty bad, in any case, the files from the I/O version do not work.
Does anyone have all the nvflash files and tables for the 16GB version? What parts would I have to rebuild to at least get access to Odin?
I would love to see that old thing live again, so help would be very much appreciated. Thank you very much!
With the C:\nvflash>nvflash --bl bootloader.bin --go command I get 13 lines of system information and then this:
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
It's the same error with part8.img.
Hi guys, I apologize for the very specific question, but I really need help and will try to be as informative as possible.
A few days ago, my tablet froze, and unlike the other times it's frozen, didn't restart automatically. When I rebooted it, it hung on the "ACER" boot screen. After hard resetting, and factory resetting after nothing else worked, I did some research, and found that I may have a burnt out NAND drive. ****.
Whenever I try to run NVFlash to read or write, I get the 0x8 error, "Fatal read/write error", which seems to back up the idea that the internal storage is shot. (And yes, I have the right SBK and everything, --sync works fine.) --- (Also, I spent two days learning an easy way to retrieve the CPUID from APX mode if anyone needs help with that.)
Blackthund3rs A500 APX Flash tool hangs on the "Uploading" part of the process. I tried both Thor's recovery and TWRP's recovery with the same results.
According to this topic it is possible to run the system from a micro sd card, though it will be slower than internal storage unless you have a class 8 or class 10 micro sd card. So I was wondering if there's any way to install a system, including rom, recovery, and bootloader, to a sd card to run on the A500? And if so, if it's ever been done before.
I really need this to work because I don't have the money for another tablet, and I don't want to spend the money for a whole new motherboard. If you can help me out, I'll buy you a drink.
Thanks,
-Tibyon
Tibyon said:
Hi guys, I apologize for the very specific question, but I really need help and will try to be as informative as possible.
A few days ago, my tablet froze, and unlike the other times it's frozen, didn't restart automatically. When I rebooted it, it hung on the "ACER" boot screen. After hard resetting, and factory resetting after nothing else worked, I did some research, and found that I may have a burnt out NAND drive. ****.
Whenever I try to run NVFlash to read or write, I get the 0x8 error, "Fatal read/write error", which seems to back up the idea that the internal storage is shot. (And yes, I have the right SBK and everything, --sync works fine.) --- (Also, I spent two days learning an easy way to retrieve the CPUID from APX mode if anyone needs help with that.)
Blackthund3rs A500 APX Flash tool hangs on the "Uploading" part of the process. I tried both Thor's recovery and TWRP's recovery with the same results.
According to this topic it is possible to run the system from a micro sd card, though it will be slower than internal storage unless you have a class 8 or class 10 micro sd card. So I was wondering if there's any way to install a system, including rom, recovery, and bootloader, to a sd card to run on the A500? And if so, if it's ever been done before.
I really need this to work because I don't have the money for another tablet, and I don't want to spend the money for a whole new motherboard. If you can help me out, I'll buy you a drink.
Thanks,
-Tibyon
Click to expand...
Click to collapse
why is it always locking up, little history of the tab and what has been done to it.
shaun298 said:
why is it always locking up, little history of the tab and what has been done to it.
Click to expand...
Click to collapse
It was running OTA ICS. It was rooted. Acer's ICS update was never stable,
I would really like some input here guys.
Maybe just a bad sector in memory card. I read somewhere (old guy can't remember where) some one had the same problem. They did a scan an repaired (locked out that sector) then the tablet worked because it did not use that area of memory. This is how hard drive disks fix memory errors.
Google search of repair memory card might get you tools.
Sorry can't be more help.
Hey guys,
Yesterday my phone froze completely while I was using it, so I pulled the battery without any second thoughts. However, when I attempted to start the phone up again, the Galaxy S4 screen showed up and disappeared, but the phone did not boot any further. Recovery mode also doesn't work anymore, everytime I try to enter it I get into Download Mode instead (but without the "Odin Mode" text in the upper left corner). Thinking that the kernel/rootfs might have gotten corrupted somehow, I tried to reflash using Odin, which failed with "There is no PIT partition". Repartitioning the phone with the "adonis.pit" file floating around on the internet does not work either, with Odin reporting either FAIL or getting stuck on "Set Partition", depending on the version used. In order to be sure that this is not a driver problem, I tried both using Odin to reflash my S3 (which worked) and Heimdall on Ubuntu with the S4 (which didn't). I am starting to think that my phone will have to be repurposed as a paperweight, as I won't be able to get it fixed under warranty with the Download Mode screen showing "System Status: Custom". If anyone could share any insight as to why something like this could have happened and whether it's possible to fix it, I'd be extremely grateful. It does sound suspiciously like the SDS on the S3, but I couldn't find anyone else with the same problem on the S4. Worst case scenario, might have to bite the bullet and get a new phone.
--fbrozovic
Does anyone have any idea what could have caused this? If the NAND/eMMC is shot I might be able to get a replacement eMMC chip, write the bootloader/system to it externally and then replace it on the mainboard (I do have access to the necessary BGA reworking equipment, so that should not be a problem). A problem I foresee with this is that I do not have a backup of the EFS partition, however I could try extracting it from an image of the current flash (since the bootloader is working, I assume that a part/most of the data is still there but the partition table has gotten corrupted somehow). Before going down this (rather drastic) route, is there anything else I can try to do?
--fbrozovic
fbrozovic said:
Does anyone have any idea what could have caused this? If the NAND/eMMC is shot I might be able to get a replacement eMMC chip, write the bootloader/system to it externally and then replace it on the mainboard (I do have access to the necessary BGA reworking equipment, so that should not be a problem). A problem I foresee with this is that I do not have a backup of the EFS partition, however I could try extracting it from an image of the current flash (since the bootloader is working, I assume that a part/most of the data is still there but the partition table has gotten corrupted somehow). Before going down this (rather drastic) route, is there anything else I can try to do?
--fbrozovic
Click to expand...
Click to collapse
Here :http://forum.xda-developers.com/showthread.php?t=2403292
i hope this will help.
im4eversmart said:
Here :http://forum.xda-developers.com/showthread.php?t=2403292
i hope this will help.
Click to expand...
Click to collapse
Thanks for the answer, however I cannot get into recovery mode at all (the phone just goes into download mode) and it seems I cannot flash anything with Odin/Heimdall with or without the PIT file. This seems strange, because Heimdall fails with "Failed to send data". From this error message I would gather that there is something wrong with the USB interface. I think that is unlikely though, so I wondered whether someone has experienced this kind of behavior already.
--fbrozovic
For the last two weeks, I've tried pretty much everything I can think of to get my TPT booted again. Symptoms of its current illness include:
Lots of error messages when booting into CWM recovery ("E:Can't mount /sdcard" for example)
If I attempt to boot normally, I get stuck on the Lenovo logo screen.
Randomly I'll boot into CWM recovery and get its logo on the screen, and a line of text, but no menus.
Other times I'll attempt to boot into CWM recovery, and just get a blank screen
So last night I used nvflash to put a new CWM recovery into partition 6: after which I was able to boot into CWM with no errors. (Yay) However, when I tried to reinstall CynogenMod (whose zip file was sitting on my external sd card), it hung during the installation. I rebooted anyway; this time it got as far as the CyanogenMod spinning logo and hung there. I went to bed, and seven hours later it was still spinning away.
Then I rebooted into CWM (without errors) and managed to install CM ROM this time also with no errors. However, again I can't boot. I get as far as the Lenovo logo, and if I boot into CWM recovery I have all the mount errors again.
Along the way I've erased the cache; done a factory reset, etc.
So: nvflash, new CWM recovery (but still errors), reinstalled CM ROM, but can't boot into it.
Any suggestions? Has this machine packed it in - is its hardware faulty in some way? Or is there something I could try which I haven't already?
Thanks folks - I think I've reached the limits of my fixing ability, and would be very gratefiul of some advice.
Thanks again,
Al
In CWM check to see if your /System folder is mounted with read-write privileges or only with read-only. If the former, then your bootloader may have locked itself. Also, what is your device model? If you have a have a US device then it cannot be unlocked as it has been encrypted by Lenovo...
Sent from my ThinkPad Tablet using Tapatalk
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
amca1960 said:
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
Click to expand...
Click to collapse
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
eKeith said:
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
Click to expand...
Click to collapse
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
amca1960 said:
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
Click to expand...
Click to collapse
No offense intended but you are somewhat peculiar as you are familiar with NVFlash, can determine which partitions to flash with the correct images but you don't have a record of, or can't find your device's model number? Check on your SD Card port flap (or your invoice). Then check out this page for details.
However if you decide to replace the motherboard then search eBay for "thinkpad tablet motherboard" and choose either of the 1838 or 1839 options. Any will fit and work but you probably won't get your (non-US) choice of replacement motherboard so will probably just have to get what's available.
See here for some basic dis-assembly instructions. Then just take you time and the rest will be obvious. Good luck!
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
amca1960 said:
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
Click to expand...
Click to collapse
No problem at all.
"I'm in the same boat": I replaced my motherboard with another US version about 6 weeks ago, rooted, installed CWM recovery and steady so far... "with fingers crossed"...
Let us know how it goes...