Related
Hi,
A long time ago, I kind of bricked my Nexus S GT-I9020T while flashing a non-official ICS rom. I was still able to turn the phone on but it was stuck on the Google boot logo. I really think I've tried everything to fix it but now it's even worse!
When I power on the phone, it automatically goes to fastboot mode. Here is what it says:
Code:
[B][COLOR="Red"]FASTBOOT MODE - NO BOOT OR RECOVERY IMG[/COLOR]
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXJK1
BOOTLOADER BUILD - Nov 4 2010
BASEBAND VERSION - I9020XXKF1
SERIAL NUMBER - 3933385EEB1F00EC
LOCK STATE - LOCKED[/B]
Of course, I already tried to re-unlock the boot loader with
Code:
fastboot oem unlock
but it doesn't work! The disclaimer pops up on the Nexus S screen, I choose "YES, I'm sure I wanna unlock the bootloader blablabla" then it's stuck on this screen and it does nothing for hours.
When I choose recovery, it boots the ClockworkMod Recovery v5.0.2.0. But each time I'm trying to do something including the internal storage in the process (e.g. mount /sdcard or restore) it says something like "E:Can't mount /sdcard" or "E:Unable to write to ums lunfile (No such file or directory)"...
I really don't know what to do since my phone is no longer under warranty.
gilgha said:
Hi,
A long time ago, I kind of bricked my Nexus S GT-I9020T while flashing a non-official ICS rom. I was still able to turn the phone on but it was stuck on the Google boot logo. I really think I've tried everything to fix it but now it's even worse!
When I power on the phone, it automatically goes to fastboot mode. Here is what it says:
Code:
[B][COLOR="Red"]FASTBOOT MODE - NO BOOT OR RECOVERY IMG[/COLOR]
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXJK1
BOOTLOADER BUILD - Nov 4 2010
BASEBAND VERSION - I9020XXKF1
SERIAL NUMBER - 3933385EEB1F00EC
LOCK STATE - LOCKED[/B]
Of course, I already tried to re-unlock the boot loader with
Code:
fastboot oem unlock
but it doesn't work! The disclaimer pops up on the Nexus S screen, I choose "YES, I'm sure I wanna unlock the bootloader blablabla" then it's stuck on this screen and it does nothing for hours.
When I choose recovery, it boots the ClockworkMod Recovery v5.0.2.0. But each time I'm trying to do something including the internal storage in the process (e.g. mount /sdcard or restore) it says something like "E:Can't mount /sdcard" or "E:Unable to write to ums lunfile (No such file or directory)"...
I really don't know what to do since my phone is no longer under warranty.
Click to expand...
Click to collapse
it sounds like you have to get the internal sd card replaced, it has gone bad. it should be a minimal charge for repair. most places that repair mobile devices would be able to do it for you.
Thanks for you answer.
I already opened the phone to see if the internal flash memory was easy to replace but it seems to be sticked on the motherboard. Where can I buy the components to replace it myself ?
gilgha said:
Thanks for you answer.
I already opened the phone to see if the internal flash memory was easy to replace but it seems to be sticked on the motherboard. Where can I buy the components to replace it myself ?
Click to expand...
Click to collapse
Unless you are used to soldering SMD components (in which cases I imagine you would know where to find these...) then I would take this to a professional. You can easily mess up your phone for good for something that really isn't all that difficult to someone used to doing these types of repair...
gilgha said:
Hi,
A long time ago, I kind of bricked my Nexus S GT-I9020T while flashing a non-official ICS rom. I was still able to turn the phone on but it was stuck on the Google boot logo. I really think I've tried everything to fix it but now it's even worse!
When I power on the phone, it automatically goes to fastboot mode. Here is what it says:
Code:
[B][COLOR="Red"]FASTBOOT MODE - NO BOOT OR RECOVERY IMG[/COLOR]
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXJK1
BOOTLOADER BUILD - Nov 4 2010
BASEBAND VERSION - I9020XXKF1
SERIAL NUMBER - 3933385EEB1F00EC
LOCK STATE - LOCKED[/B]
Of course, I already tried to re-unlock the boot loader with
Code:
fastboot oem unlock
but it doesn't work! The disclaimer pops up on the Nexus S screen, I choose "YES, I'm sure I wanna unlock the bootloader blablabla" then it's stuck on this screen and it does nothing for hours.
When I choose recovery, it boots the ClockworkMod Recovery v5.0.2.0. But each time I'm trying to do something including the internal storage in the process (e.g. mount /sdcard or restore) it says something like "E:Can't mount /sdcard" or "E:Unable to write to ums lunfile (No such file or directory)"...
I really don't know what to do since my phone is no longer under warranty.
Click to expand...
Click to collapse
The fastboot process freezes when the internal sd card becomes corrupt & is no longer usable! It needs to be repaired by a local reputable phone engineer!
Flash the latest software version for your Nexus S via Odin to fix everything.
Thank you for your answers.
I'll try to find a professional that would be able to replace the flash memory.
Do you know the exact reference of the flash memory that's in the Nexus S GT-I9020?
i have the same problem
gilgha said:
Thank you for your answers.
I'll try to find a professional that would be able to replace the flash memory.
Do you know the exact reference of the flash memory that's in the Nexus S GT-I9020?
Click to expand...
Click to collapse
i have the samme problem and i dont use my mobile from 2 month ago how can i fix it?
anyone can help me?
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
otisranson said:
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Click to expand...
Click to collapse
otisranson said:
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
Click to expand...
Click to collapse
yup, this ones explainable. classic symptoms of a ns with its internal sd card dying/dead. it happens way too often unfortunately. luckily its a fairly easy and inexpensive repair, if youre not under warranty.
Any direction on how to fix it while not under warranty?
Or take it to tmobile?
otisranson said:
Any direction on how to fix it while not under warranty?
Click to expand...
Click to collapse
check out any local mobile device repair shops. you could probably do it yourself if you dont fear taking the phone apart, it should be to difficult of a repair. its just a matter of buying a replacement(ebay?), taking the phone apart, and replacing the sd.
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
I've been having similar issues..what is the exact part name for the SD?...I wanna search to buy one
Sent from my Nexus S 4G using XDA Premium App
I think its:
Samsung KB100D00WM-A453 memory package and S5PC110A01 1GHz Cortex A8 Hummingbird Processor.
I'm going to try to find another nexus s mother board as a whole, that's my only option.
otisranson said:
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
Click to expand...
Click to collapse
I think it's in step 10
i seen something a few weeks ago online on how to replace this...it was a video..i just cant remember where i seen it!
I ended up just purchasing a new phone on ebay.. If I find a nexus s with a cracked screen, I will swap out the mobo.
You can check whether there are blocks flagged as bad by FTL (Flash Translation Layer) in recovery. Check recovery.log file (it can be, the bad blocks will show up after formats).
I'm still somewhat new to all this but after buying my tf700 last December I've been trying out a few things, unlocked/rooted and I have been happily using TWRP and various versions of Cromi X for months without any problem. Suddenly one day it didn't want to boot the ROM anymore and I have no idea the cuase (didn't just flash some kernel or drop the tablet, etc). I have TWRP 2.5.0.0 and CROMI-X 5.0.2.
I've dug through the forums and there doesn't seem to be anyone I can find who's having exactly the same problems. There was no special data I particuarlly needed on the tablet and I have backups on saved elsewhere so I am totally happy to wipe everything and start from scratch. I just want my tablet back. I'm just looking for the easist way to fix this (and I hope there is a way!) so any help is greatly appreciated.
Info is as follows:
Cromi x won't load stuck on ASUS logo. Same goes for cold booting
When I boot into recovery it says "Key driver not found.. Booting OS" at the top left
[when I enter TWRP it asks for password and says it can't mount E as below
when i "cancel" the password request i am taken to the usual home screen but installing from internal storage shows no files and a size of "0"
strangely I can get into the Micro SD card and load CROMI X from there which all goes through normally but at the finish when I'm going to reboot it says "No OS Installed!" and after restarting i'm back to same problem
I'm not getting the Fastboot USB logo I think I'm supposed to get in recovery when it is plugged it into my PC and ADB sideload in TWRP also not working (not so experienced with these though)
When I try to wipe data in TWRP I get "Failed" the message about being unable to mount E below
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
strangestribu said:
E: Unable to mount '/system'
E: Unable to mount '/cache'
Click to expand...
Click to collapse
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.
can't seem to connect through PC
_that said:
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.
Click to expand...
Click to collapse
Thanks very much for this. The problem I am having is I can't past the "error: device not found" message I get in the CMD on my (windows 7) PC. (yes I am opening the command line window on my android ADB folder). In fact the tablet doesn't appear in the Device Manager either. I'll admit I'm not so experienced working on the tablet through the PC (though I'm guessing I'm about to learn a lot), but I think the fact I get "Failed" when trying to ADB sideload in TWRP and nothing in the Device Manager is a big part of my problem though I'm stumped how to fix it.
Any ideas?
strangestribu said:
In fact the tablet doesn't appear in the Device Manager either.
Click to expand...
Click to collapse
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.
Try these drivers:
PC doesn't recognize tablet is plugged in
sbdags said:
Try these drivers:
Click to expand...
Click to collapse
_that said:
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.
Click to expand...
Click to collapse
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device. Because of this I'm not sure how to get the drivers loaded. Also have loaded Android SDK Build-Tools and Google USB Driver through the Android SDK Manager. That doesn't seem to solve it either.
Not surprisingly when I run fastboot from a cmd line window and look for adb devices the list is blank.
Not sure what else to do. Would be willing to create a second Ubuntu boot on my machine if using linux would help me get this fixed. Just at a loss about what to do.
Any further insights are welcome!!!
strangestribu said:
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device.
Click to expand...
Click to collapse
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.
Am I bricked?
_that said:
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.
Click to expand...
Click to collapse
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.
Sounds like it is bricked if you can't get into the bootloader.
What was the exact command you used to 'push' TWRP and which file did you use?
strangestribu said:
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.
Click to expand...
Click to collapse
If you cannot get into the bootloader and APX mode is your only access .... without nvFlash - sorry, it's a brick :crying:
The blobs for nvFlash are device specific, so somebody elses would not help you.
Your only option is to sell it for parts or have the main board replaced.
I don't have experience with that (thank God), but there are tear-down videos and instructions on iFixit.com. Maybe that'll help you decide if it would be something you can do yourself.
Otherwise sending it to Asus and have them fix it would be your only option. It is expensive....
My condolences....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
TF300T help
I've worked on this now for about 12 hours. I cannot figure it out. I run into the same roadblocks. I know this is an old thread, hopefully by now there's a solution for this kind of issue.
Can this be fixed in Odin or platform tools or something?
I've got TF300T where I believe I bungled the process by format/wiping from bootloader menu instead of TWRP. It's technically not bricked at all. But it's screwed up in the following ways (I was trying to get it to be a Clean Rom tablet, and there were so many sets of instructions, had them all open, and was trying to be careful about this, I've rooted and ROMed so many times and this is the first time I haven't been able to solve the issue in a reasonable amount of time)
-TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
-cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
-in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
I issued your commands:
DMESG.TXT (output too long to post here, exceeds xda allowable) &
MMC.TXT
brw------- 1 root root 179, 0 Jul 12 00:32 /dev/block/mmcblk0
brw------- 1 root root 179, 1 Jul 12 00:32 /dev/block/mmcblk0p1
Without a working fastboot connection you are one or two steps away from a hard brick. Proceed with caution!
chickenmusket said:
Can this be fixed in Odin or platform tools or something?
Click to expand...
Click to collapse
Odin is for Samsung devices only, the platform tools give you adb and fastboot, see below
TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
Click to expand...
Click to collapse
Usually the reason if TWRP is asking for a password is a corrupted data partition. The recovery cannot read /data, so it assumes that it's encrypted and it asks for the password. Surprising is that you can boot into Android if your data partition is corrupted!!
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
Click to expand...
Click to collapse
That's what stumps me... Most of the time, if you use the "Wipe Data" option in the bootloader or do a factory reset from within the stock rom with TWRP installed, you end up in a forced reboot to recovery loop - no boot to rom, no boot into the bootloader. So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom??
cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
Click to expand...
Click to collapse
That's totally normal because the factory reset command calls the recovery to perform a wipe of data. Since you don't have the stock recovery it calls TWRP - but TWRP cannot resolve the command. Read this for background, but you probably don't need bootit.ko since you can boot into the bootloader anyway.. http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
Click to expand...
Click to collapse
This is the part that worries me. Without a fastboot connection you could be dead in the water pretty quickly. And that's the problem you should tackle first.
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem. Read this to get fastboot working:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
And again - if that goes wrong and you don't have fastboot working, you could end up with a paperweight. Be careful!
Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7
chickenmusket said:
Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
Click to expand...
Click to collapse
Stick around enough long enough, read a ton and you will be
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
Click to expand...
Click to collapse
It probably was. Although with a different effect than usual...
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7
Click to expand...
Click to collapse
Yes. That would be the safest way to go, but you need fastboot for it. I thought you don't get the device ID returned when issuing 'fastboot devices' while in the bootloader??
As long as you can boot into the BL you don't need bootit.ko so follow that guide from the "fastboot devices" input
Correct, I do not have a fastboot ID.
chickenmusket said:
Correct, I do not have a fastboot ID.
Click to expand...
Click to collapse
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
The issue was resolved with the help of Joshua Lynch. He saw my post and PMed me. For those that are losing hope like I was, if you're coming back to this old tablet, all is not lost. I will post how this resolved as soon as I have time. Thanks for the answers. Bounty has been claimed.
the issue was a driver. the computer would only have one driver installed at a time and installing fastboot driver again fixed the not seen issue. I had installed another driver (as part of this process, and it eliminated the presence of fastboot driver), and was racking my brains because I didn't think to reinstall the original fastboot driver.
I had help from Joshua Lynch a couple months back on this. It turns out that the reason the tablet wasn't seen was indeed a driver issue. What had confused it with me is that I did physically install both drivers fastboot & adb. However, my system only allowed one to be active at a time. So when I was trying to, if I'm remembering this correctly, fastboot into the tablet to console, it wasn't seen because adb was the active driver. All that needed to be done was remove adb & put in fastboot.
Just to let you all know, I did a full one & zero wipe of the tablet & installed Zombi-Pop rom with Joshua's help. The tablet was still slower than hell. Slower than any device I've ever used. I'm talking 5 to 15 second delay time from when touching something & getting a response. I found that disabling everything google (except play store & play services) helped a great deal.
But the tablet has never returned to its former speed prior to the asus update. Tinfoil hat: I have this feeling that they sent out an update that permanently screwed up the hardware on purpose.
berndblb said:
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
Click to expand...
Click to collapse
Question: do you know if the original stock software that the tablet came with (before the update) can be installed? Is there a full set of instruction on this (and the stock rom)? I've got a ton of files (some roms, some files from asus website) downloaded for this tablet. I've taken a break from this thing, returning to it now... Ready to take another crack at it.
If someone wants to make some money and help me out with this, I'll pay them a total of 50 if all goes well. First 20 for their service to get the thing back on stock, original out of box software and updates disabled, another 30 when I've seen after a few days, that indeed it was done right and fast like it originally was.
Reason for this is that I already gave someone 50 for their help with this and the outcome wasn't acceptable. I've invested a ton of time in this and the $$ put in so far exceeds the value of the tablet.
I was using my XT925 normally. Then it hanged for some time and I restarted it. Suddenly it wouldn't get past the circling cm boot. I tried to wipe cache to see if it solved the situation. Entered recovery mode, wiped cache, tried to restart again, now it won't even turn on.
Except when I use power + vol -, it goes to the bootloader unlocked screen and stops there.
Is there something I can do about it?
somehow got into recovery mode. Tried to wipe cache and this appeared:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)
Update 2:
Using rsdlite I got this error:
failed flashing process 1/19 flash sbl1 "sb1_signed" -> Phone returned FAIL
remove "get var"line from xml,then flash away
Thanks for the answer, but early today I went to a Motorola oficial store to see what they could do about it. They told me it was a hardware problem with the memory. I guess downgrading won't fix, if they're right.
It's really sad to have your phone not working anymore 1 month past the warranty limit. :/
There are ways... I ll check with you tomorrow man. It may still work
Wireless...
xusa said:
Thanks for the answer, but early today I went to a Motorola oficial store to see what they could do about it. They told me it was a hardware problem with the memory. I guess downgrading won't fix, if they're right.
It's really sad to have your phone not working anymore 1 month past the warranty limit. :/
Click to expand...
Click to collapse
Happy ? year
Ur phone working?
Wireless...
hbenz2008 said:
Happy ? year
Ur phone working?
Wireless...
Click to expand...
Click to collapse
Nah. I've decided to get a 2nd gen Moto G. I've expired all known troubleshoots and wasn't capable of solving this issue :/
weird man, what android were you running, you had cm ,right?
I would still try and flash gpt and tz if you still have it.
Anyway peace out man
So i was using my phone 5 days ago like normal and sudendly it decided to reboot itself, after that it got stuck on the 4 balls android logo and doesnt boot into the system anymore.
what iv tried so far:
-Full Wipe
-Download and flash a full factory image, then full wipe
-Download and flash TWRP with SlimRom + Gapps then full wipe
Nothing works, it always get stuck in bootlogo, it just sits there dancing like its booting normally but it never does, im runing out of options here, what can i do guys?
Note: i have access to bootloader, all button works, also have access to recovery without any issues.
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
Let me download a kitkat image and see what happens, ill report back as soon as i do it
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
mediavieja said:
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
Click to expand...
Click to collapse
Aight so i flahshed twrp and slimrom again but im once again stuck on bootloop what do u suggest?
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
audit13 said:
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
Click to expand...
Click to collapse
Nope, tried stock MM (latest stock) and didnt work
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
audit13 said:
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
Click to expand...
Click to collapse
Must be then, cause i tried LP and didnt worked
I think it has something to do with differences in partition layouts between kk and LP/mm.
audit13 said:
I think it has something to do with differences in partition layouts between kk and LP/mm.
Click to expand...
Click to collapse
Do u know if theres anyway to fix it?
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
audit13 said:
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
Click to expand...
Click to collapse
Awww well thanks anyway for all ur help men, i really apreciate it
You are very welcome. We are all here to help and learn from each other.
The cheapest solution may be to buy a used nexus with a busted screen but working motherboard and perform a bit of phone surgery. I've done this a few times over the years with great results.
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
HSF3232 said:
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
Click to expand...
Click to collapse
Well i followed the procedure to fix persist, i was getting Unable to mount "/persist" (Invalid argument) so bu running command e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist i was able to mount it, after that i rebooted the phone to bootloader and i was able to flash and run the latest software update so i have to say thank you very much sir im gonna try to put slimrom now on this bad boy and change the post title to fixed