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.
Related
Hi,
First off thanks for looking at this post; second the problem I'm having might be hardware related as I believe I'm having an ssd issue; anyway I've read about 300 posts relating to write failures. here's a little back story.....
Got a tablet from my mom(stuck on acer screen after ics ota)... anyway did the timmydean 3.2.1 root....it worked until I flashed the skrillax_cz bootloader.......after this however, anytime I booted to recovery, I had recovery boot (sos) failed.....any ideas on how to get back to "red" "boot verified failed" as I can recover from this point on.... and anytime I try to over write with manually crated partitions I get to formatting partition bct2... failed. I think the problem lies with the flash.cfg file as most are set for a 32gb tab when the tab is only a 16gb. If some one has a flash.cfg file for the 16gb wi-fi model or a way to manually partition the ssd through a lnx cmd prompt I can most likely recover.
Thanks,
Kw1k
btw: its stuck in apx mode now.
note: timmydeans and afterota and V8 all use a 32gb flash.cfg file(tried interchanging them as well as veiwing them as a .txt files there almost all exactly the same)
Flash.cfg is universal and doesn't depend on flash size. The user data partition (wchich is the last one) is created dynamically to stretch to the end of available emmc space.
I have 64GB version and have had this error too. It is very likely that you have a faulty emmc chip. I've fixed mine with help from Skrillax_CZ. You can find the solution we've worked out together here http://forum.xda-developers.com/showthread.php?t=1691729&page=3#postcount27456113.
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.
So after spending a whole afternoon flashing 4.3 onto the N7 via fastboot and finally getting root to work, I connect my N7 to the PC and get the shock of my life to see my internal storage has shrunk to 6GB...it currently says I only have 5GB free out of 6GB...is there any way to fix this ? My N7 is the 3G, 32GB model running 4.3 with stock kernel, twrp and rooted.
Solution : http://forum.xda-developers.com/showthread.php?t=2033692
Just edit the steps to adapt to our Nexus 7 PM me if you need help with that
Anyone ?
We've had that with the first custom roms. The only way to fix that, that I know know of, is to flash back to older stock rom, verify the storage is right, and try again.
I would download the 4.3 rom from another source and/or verify the MD5 package.
Just for laughs, perhaps you could try to reflash the kernel (which is what I think gives the reading).
That or you are the only person with a 6gb N7.
Well, I talked to two other people and they said this is bound to happen with flash happy morons like me who go straight for the IMGs...will try re-doing from step 1, or else I'll go back to 4.2.2...oh and 1 more piece of info...as I was done with flashing 4.3, my sd was formatted as well...
This has also happened to me on more then one occasion when flashing back to stock would show only 6/27.5GB available. Rebooting into recovery and reformatting fixes it.
Username invalid said:
This has also happened to me on more then one occasion when flashing back to stock would show only 6/27.5GB available. Rebooting into recovery and reformatting fixes it.
Click to expand...
Click to collapse
i got that once...formatted all in Philz recovery...DONE..no problem..
Hey guys!
I'm coming to you at the end of a loooong way after trying to upgrade to KitKat.
I started the upgrade to 4.4, on the go, and quite confident. What a mistake ...
The upgrade failed, and my device got bricked. Fortunately, I had the recovery partition. Unfortunately, I destroyed the recovery partition by mistake...
I finally succeed to fix the things, but I have no idea how exactly I did it (I just tried the things as they were coming, messing around with partitions and switching from tutorial to tutorial),
Anyway, I made it.
This was 2 months ago ... then time passed, and today I got a message "no space left on device". Hm, weird. I check and oh damn, my SD card only had 5GB on it ...!!
It looks like I've loaded the *GB version partition scheme at some point ... or just wrongly formatted the partitions ... or I don't know.
I've tried to check using fdisk, but it doesn't help me much.
I also tried some tools like "Partition table" but I still can't find the missing 10GB. it seems like they're just unpartitioned, but not even recognised as it ...
Did anyone ever had this issue? Any process to fix it? Or at least any way to rollback to the original partition scheme.
Many thanks!
Best,
Stop messing with all this crap.
Get the factory images.
Put the phone into fastboot mode and connect to the computer
Your computer needs to have a working fastboot set up. If not fix it.
Run the flash all script include in the factory images. It's the. Bat on Windows and. Sh on osx / Linux.
It fully wipes the phone. Everything gets wiped and flashes the stock images.
If you have anything on the internal storage you want to keep you can remove the - w line from that script and it won't wipe it.
When done you a stock phone with a unlocked bootloader. From there do what you want.. Either run stock. Flash a custom recovery and root or rom etc.
Or just use stock recovery and factory reset. It fix the storage size problem for me. You'll lose everything on your internal though, so make a backup of your pic/music/anything you think important in your phone.
**** it seems like the post subscription didn't work, I've just seen your replies.
Thanks guys, it seems like the right way to do it.
I'll try to do it tonight and let you know the progress.
Cheers!
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...