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.
Related
NS4G
Will boot to fastboot and recovery
CWMR Touch 6.0.1.0
Situation:
My device started bootlooping after about a week of random restarts and freezes. I had just flashed BlackBean and now this, so I decided I was just going to flash a new ROM/Kernel combo. I remembered someone saying I should format /system to install the specific ROM, but I'm fairly sure I formatted /boot along with it, like an idiot. FYI - Fast Charge and a build.prop tweak to set permissions on boot was enabled when this happened. So then I try and flash a new ROM/Kernel combo to fix my bootloop and it wouldn't read the sdcard afterwards. Now it boots straight to fastboot everytime. Toolkit seems to be able to do some things via USB control like reboot the bootloader, but it does not detect an ADB device when I run the driver check or try to restore my CWM backup. I ran the stock+unroot option in Toolkit (was going to send it in thinking the sdcard thing was hardware at first) and it seemed to have went through the whole process correctly... Until the end when it did not reboot automatically like it should have. After doing this, I now get "STANDARD_SET_CONFIGURATION" on the phone when I insert the USB cord while in fastboot. It did not do this before, whether it is the new cord or the flash I do not know. My old cord WAS having problems with data though.
Problem:
I now have no USB debug or SDcard functionality. I assume because of missing files on /boot. I can mount nothing (except cache, but the PC doesn't recognize) without getting a "can't mount" error. This puts a serious dent in my novice ability to fix it. Anything in Toolkit that runs via ADB commands doesn't seem to work properly because it says the device is not in debug mode. PDAnet USB Drivers seemed to install without a hitch and device is recognized on my PC.
Errors:
When trying to mount ANYTHING except the cache while in CWM, I only get: "E:/ Can't mount /sdcard/".
If I try to mount USB storage I get: "E:/ Unable to write to ums lunfile (No such file or directory)Error mounting /sdcard!"
If I try to run any one click methods that use ADB I get: "Daemon not running* No ADB device detected. Make sure you have debugging enabled on your phone"
The log in CWM recovery always shows: "I: Set boot command "" failed to open /sys/class/android_usb/android0/state: No such file or directory" over and over (as many times as I tried to mount something while in recovery for that session)
Questions:
Do you think USB Fast Charge or having the build.prop tweaks enabled could have done something to USB debug? Is there a way to at least just fix the USB Debug problem? Am I correct in assuming that wiping the /system along with the /boot folder is what caused me to not be able to mount the /sdcard to flash another ROM? Is there a way to push the files I need onto the device to restore sdcard function and flash another zip?
Also, what fastboot do I need to be in to do the StockROM+Unroot method in the Toolkit? I have two. Only hold Vol Up/Power takes me to "FASTBOOT". Holding both Volumes+Power puts me into "FASTBOOT - NO BOOT OR RECOVERY IMG"
What is the difference?
I only ask because the Toolkit wants me to hold both volumes and up to get into bootloader mode, but they describe a big green "Start" with an android lying on it's back, mine does not look like that. It simply looks like regular fastboot, but says "FASTBOOT - NO BOOT OR RECOVERY IMG" instead.
It seems you messed with the ROM zip with some tool. Sorry could read your lengthy post completely.
I just want to know one thing clearly, what is the problem basically? where are you stuck?
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
DizturbedOne said:
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
Click to expand...
Click to collapse
Your storage memory is completely inaccessible?
Yes, no way to access it via CWM. ADB stuff does not work either. It seems Fastboot stuff DOES. I would like to find a boot.img and system.img to flash via Toolkit (I believe toolkit uses fastboot or odin for these) to see if that would work for me. Any ideas?
It seems like the easy nature of unlocking, rooting, and customizing this phone leads to less of these kind of discussions, I can usually find many files and discussions pertaining to this for HTC phones, but never for this phone.
My bootloader version is KE1, but my baseband version is LF2, makes no sense to me.
The KE1 bootloader was when I was on ICS, but the LF2 baseband was from Jellybean... wth?
Do you think the time I flashed "stock+unroot" on the toolkit that it only partially took? (I did try to back it up to ICS because the Jellybean download didn't work). It seemed as if it flashed everything via fastboot, but never restarted at the end and still won't boot when done.
same problem kinda
i am having the same problem as this with my nexus. mine started after i downloaded Jellybean.it worked fine for about 1 month. i had changed nothing but when i would change my battery or restart my phone it would get stuck at the google screen every now and then, then it started more often. i could normally pull the battery and restart it and it would work after a couple of times doing that. but now this last time i tried that the phone wouldnt go past google screen at all. i can access my clockwork mods recovery but when i try to install zip from sd i get the error cant load sd i have tried everything i know and cant get nothing to work. please help. i miss my nexus this prevail is too slow and small...
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
polobunny said:
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
Click to expand...
Click to collapse
@ polobunny - There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and manually reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such. I've tried it with PDAnet drivers and the Samsung drivers and have followed every driver install guide on the web... Any other suggestions on how to do this properly? I was even thinking of installing a Google SDK just to see if the drivers would work better...
@ Bamamac82 - Yes, that is pretty much the exact same problem, with the exception of the fact that you didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up. Not having a working USB cord at the time botched me, because I couldn't get my drivers reliably installed before anything happened, I was using AirDroid because my OEM cable wasn't working with data reliably.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
DizturbedOne said:
There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such.
And Bamamac82 has the exact same problem, with the exception of the fact that he didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
Click to expand...
Click to collapse
When you're in fastboot mode on your phone, on your windows PC point the unknown device or the device with an exclamation/question mark to the path where the .inf for the drivers are located. If it still doesn't detect it, you can always try and force it to install a certain device (adb debug bridge or something of the sort).
Once that is done as I said you won't have any problem fastboot'ing to your phone and doing the other steps. Windows drivers and especially the adb drivers can be finnicky.
Your SDcard problem has nothing to do with the fact your formatted boot partition though, those are not linked.
Edit: Oh and I know there is some people, namely with NS4Gs, that had issues with the drivers. I believe for some reason there's some missing IDs in the inf making it impossible to install automatically. Forcing it should work though.
Polobunny thank you so much for your help so far. My device has been softbricked for a week and I'm using a HTC Hero for now! It's atrocious. I'm going to try as you said when I get home tonight and will update if fastboot allows me to flash after that.
Any idea where I can get all the .img's I need? I can only find the complete .tgz for IMM76D (which is fine for now just want it back to working state) and don't know how to extract .img's from it. Can't even find the complete .tgz for JRO03R though, the link is always down. At this point, all I want is a factory img to start from so I can upgrade to JRO03R, root it, and then make a fresh NAND backup from there.
If I were you, I would download Odin, a factory image from Google (just search nexus s factory image), the SDK tools (Google it) and would "reset" the phone.
You will easily find a guide for Odin. Then you'll just have to follow it and your nexus should be fine (but it will be factory reseted and you will have lost all your data )
Sent from my Nexus S using xda premium
Sorry guys, have been putting late hours in at work and haven't had much time until this weekend.
@BenHeng, that's what I am about to look into tonight. I didn't want to learn an entirely new aspect to restore this, I have been limited on free time and am starting to think it will be less hassle than dealing with this.
Only caveat to that, is that I definitely would like to know what happened to cause the SDCARD problem, because that was the main problem that got to me here, would like to prevent that from happening again.
ADB
Make sure ADB debuging is checked under Developer options
localpagefirst said:
Make sure ADB debuging is checked under Developer options
Click to expand...
Click to collapse
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Hi, I don't understand why you want to use ODIN, fastboot commands still don't work after you installed correctly your driver?
Anyway you can find all (new and old) originals google image here:
http://www.randomphantasmagoria.com/firmware/nexus-s/
Listen mate, the best way would be to flash the factory image via fastboot in bootloader mode. Follow this simple step to step guide.
If you have any issues. post them there on the blog post itself :good:
DizturbedOne said:
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Click to expand...
Click to collapse
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
polobunny said:
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
Click to expand...
Click to collapse
I get nothing when I do that. It says "List of devices attached" and a blank line underneath. When I plug the USB in during fastboot I get "STANDARD_SET_CONFIGURATION" at the bottom, which I never get until I install the drivers.
It seems as if the computer must recognize the device in debug mode in some way to properly install the drivers.
Why is my sdcard partition unable to be written to? This never would have been a problem as I always keep a couple backup ROM's on the phone. Either way, it seems as if all of this is for nothing if the phone will not allow me to read/write to the memory in the device.
Ok, currently running
Unlocked bootloader using the TF300T 4.2 method.
Installed TWRP 2.5.0.0 (works great)
Running the lastest CROMi-X 5.1
Everything installed and was running ok, until I ran the encrypt android device. I started fine, then I left it for an hour and a half, came back to the device boot cycling (Was fully charged and plugged in). Since then I have tried reflashing the recovery via joelalmeidaptg’s installing TWRP recovery instructions.
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
fastboot reboot
No dice.
Tried formatting from the “Wipe” menu via TWRP, Always get a TON of E:errors
E:error: I/O error
E:error opening “/data/---a whole list of entries ----”
Installing a new ROM shows the same fault.
Currently I can still access adb, fastboot and all TWRP functions but E drive won’t allow me to mount. When booting into TWRP I get a password request from the encryption setup (still know the password, so no problems getting by that). The problem seems to be limited to the /data/ folder.
I’ve tried to get logs off the device, but I can’t seem to get the logs to go to the external SD card so I can pull em.
Not for this problem, but I've seen posts about deleting nearly every bit of content via fastboot in response to mostly bricked devices due to loading wrong recovery. Although you didn't do that, perhaps a similar approach would work for you!?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
funnel71 said:
Not for this problem, but I've seen posts about deleting nearly every bit of content via fastboot in response to mostly bricked devices due to loading wrong recovery. Although you didn't do that, perhaps a similar approach would work for you!?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I was thinking of using BrateloSlava's "[TOOLS] Command file install/check/repair" and just zero the whole /data partition (option 8) as that is where the errors show. I would like a second opinion before I try that.
Also the symptoms stink of an "Encryption Unsuccessful" error.
GRRRRREAT NEWS
Even though I couldn’t gain access to any folder in the /data folder, I went and ran BrateloSlava’s Tool anyways. Option 8 - FULL ZERO’n. It’s says it fails to mount the folders right off the start.
Go for a two hour walk or something this part takes forever
Odds are you’ll be like me and the device will still be trying to zero the device (which it never completed for me). Use the recovery's software to shut down the device (turn it off).
Turn back on the device, and reflash the recovery that you had before (If you don’t the recovery will have forgotten your encrypted password and you won’t be able to do much).
After you have flashed a new recovery, go back into recovery again. You’ll notice that there is no more encrypted password while logging in. Format your device, follow by a wipe for good measure and you have returned your device to working order. PHEW
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Can you access the recovery? If so, format cache partition and then perform a factory reset and try to boot. If it fails, download the factory images and flash it. Factory images are flashed in fastboot mode and doesn't require a working OS or USB Debugging.
Follow the links in my signature and read everything mentioned it those threads. I'm sure your phone will be up and running in no time!
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
Dumb question, but do you have access to your latest back up on your phone?
Boot into recovery and adb push a rom zip
Sent from my Nexus 5 using Tapatalk
zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
Try changing to TWRP recovery by using - fastboot flash recovery recoveryname.img
Format data, factory reset your devices in TWRP,
Then, install any rom using adb sideload in TWRP
Oh and if you're booting in any way possible, you're never screwed ?
Sent from my Nexus 5 using Tapatalk
zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
First of all you most certainly not screwed.
Now what you have done is oem unlock without google stock recovery.
For the process of wiping userdata to complete , after you type fastboot oem unlock and restart the phone will boot to recovery and execute the wipe.
Because you have cwm recovery the process is stuck and hence the bootloop.
You need to boot to bootloader and type : fastboot -w (press enter) ,it will erase userdata and cache, and restart to system.
You can also try "fastboot format data " and "fastboot format cache" .but if -w worked then no need for that.
If you still stuck in bootloop then you need to flash the stock factory img.
zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
No need to worry. Download the 4.4.3 factory images and follow the guide "How to flash factory image" which is linked in my signature.
Or, if you want to try out a custom rom, you can push the rom.zip and gapps.zip to your device using "adb push" or sideload it in recovery.
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.
zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
No, pick it yourself, see below the search for driver software
Sent from my Nexus 5 using XDA Free mobile app
vin4yak said:
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.
Click to expand...
Click to collapse
Doing that again. Maybe I missed a step last time but I tried that already a few times. Im trying again.
zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.
Ok so I uninstalled the drivers from the device manager, went to control panel did it there as well. I have the SDK on my desktop, I installed the google drivers. But I also had downloaded just the google driver manually from their website. Unrared it, plugged my phone in, it detected the phone, I manually updated drivers to the ones I got from the google page. It updated. I was in bootloader mode, and I get that the drivers installed successfully, then it also says Device could not start (error code 10). Anything I type into command prompt still says waiting for device.
Johmama said:
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.
Click to expand...
Click to collapse
Wow........switching usb ports worked..............Thanks so much! Ok so bootloader unlocked. Now Ill try factory reset, if nothing Ill flash original recovery and do it again. After I sideload the stock zip.
Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.
zeroshift11 said:
Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.
Click to expand...
Click to collapse
Clear cache and factory reset in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
Hi all
I've had my Tf700 for a long time now. I've had it unlocked and rooted and had CROMBi before trying OMNIRom and then finally moved to KatKiss7.1 last year. All was well until today when, having enabled screen rotation, the background went a strange looking pink colour and would flicker back and forth to black. Then the WiFi started to misbehave so I rebooted it. But instead of rebooting, it just went into a bootloop.
I used power + VolumeDown to access the recovery mode and tried to get to TWRP (2.8.7.4) via the RCK option but without any luck. At that stage, all it was doing was resuming the loop. I tried booting into Android but got the same result. I tried for TWRP a few times and it always failed.
My next move was the Wipe Data option. Turned out to be a bad one. I hadn't done anything with the device in so long that I forgot about the "don't use the Wipe Data" instruction and I didn't read up before doing anything else. The device rebooted itself and then appeared to be going into TWRP - I could see the logo coming up - but my hope was short-lived as the device then proceeded to go into a bootloop where it displays the TWRP splash screen, but then reboots.
About the only thing I seem to be able to do is access APX, but I didn't know about APX or NVFlash until today when I started trying to read everything to do with anything that might help.
I run Linux on my PCs and have installed ADB so that I can try to use fastboot or adb. Neither seem to work in that nothing shows up when issuing either "fastboot devices" or "adb devices". But on a more basic level, nothing shows up in lsusb. The mouse is listed, as is my card-reader, but the TF700 isn't. The thing is, I haven't connected the device to a PC in a long time and the last time, it was windows, so I can't say for sure that the PC is definitely seeing it or not.
And so to my questions:
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup?
(I've seen instructions for the TF201, but can't see anything for the TF700)
Any help would be really appreciated.
With thanks,
Scouser27
I don't like the sound of this. This "background went a strange looking pink colour and would flicker back and forth to black" business makes me suspect a hardware failure. Maybe something got fried on the board - don't know.
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
Click to expand...
Click to collapse
Yes, it should, something like this:
Code:
...
Bus 003 Device 009: ID 0bda:57af Realtek Semiconductor Corp.
Bus 003 Device 016: ID 0b05:4d01 ASUSTek Computer, Inc. Transformer Prime TF201 (debug mode)
Windows is not going to help you. If it doesn't connect in Linux it definitely won't in Windows....
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
Click to expand...
Click to collapse
Not unless you get a connection in either fastboot or adb
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup? (I've seen instructions for the TF201, but can't see anything for the TF700)
Click to expand...
Click to collapse
No, nvflash files are device specific
If you cannot get it to boot into fastboot or get an adb connection - however briefly - it is a brick.
Install Hardinfo in Linux - it is very similar to Windows Device Manager - and open the USB page. Then reboot into TWRP. If you are lucky you may get a few seconds before TWRP loops where the PC has an adb connection and sees the tablet. If that works, follow this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Still a tiny chance but better than nothing.
If bootit.ko kicks it into the bootloader and you get fastboot you can reflash the recovery, format data in fastboot and all that good stuff.
But my guess is: No dice
Try it anyway - good practice.
I still have a couple of TF700 lying around, one with a so so screen. If you want it, you can have it for the cost of shipping. You can either swap the screens or m-boards...
PM me if you want to go that route.
Good luck
Update
Thought I'd post something in case it's useful to anyone having similar trouble to what I described. This applies to my instance of TWRP booting in a loop and never exiting until the battery was flat.
Ensure your cable is working correctly.
If it's not, you won't see anything on your pc. (I use linux and nothing was showing up in lsusb or dmesg)
If this is the case, borrow a cable if you can or invest in one. I did - best 5 Euro ever.
Get the bootit.ko file that's mentioned in a few places such as here.
While you're getting that file, read the instructions there a few times and also have a look at the details over at this page (same one @berndblb links above)
Connect your tablet and boot it. As soon as you see the TWRP logo, it's time to try to run commands.
If you use linux, you can issue all commands at once like this:
Code:
sudo adb devices; sudo adb push bootit.ko / ; sudo adb shell insmod bootit.ko
Note the "/" after "push bootit.ko" - that's not a typo. If you leave it out, it won't work.
I don't know if sudo was strictly needed, but I wanted it to work and it didn't cause any trouble.
I haven't used Windows in a long time so I don't remember if you can do the same, but you could put the various adb commands into a batch file and run that. Don't forget to drop the sudo.
If it has worked, the tablet will reboot. You should now be able to get back to the bootloader.
Follow the fastboot erase instructions at this thread.
I found it useful to write the commands as
Code:
fastboot -i 0x0b05 erase boot
The last version of TWRP that I was using was KANG TWRP
I downloaded that, extracted the blob file and flashed it:
Code:
fastboot -i 0x0b05 flash recovery boot.blob
I used that because I wanted to install TimDuru's KatKiss 7, but you could presumably install whatever Recovery you wanted and proceed as normal.
And that's it. I flashed KatKiss7 and SU and all was well again:laugh:
Big thanks go to @berndblb for his help on this - If, like me, you didn't read his posts before, you really need to read them now. And maybe, just maybe, you'll be able to recover.
Thanks to all other contributors whose post's I've linked or whose work contributes to this solution - you've all just saved me having to buy a new tablet. Nice one!:victory:
If I'd prefer not to purchase a new phone, is there much risk a rootkit is installed? Or, is this certainly random device corruption that doesn't seem to be harming anything?
Is there anything I can do to fix the problem? (Yes, I could turn dm-verity off through adb, but that hides the error without fixing it.)
TL;DR
I have an Asus Zenfone V Verizon edition, which is the V520KL A006.
When I was using my phone a few days ago, it suddenly rebooted and since then shows:
Your device is corrupt. It can't be
trusted and may not work properly.
Visit this link on another device:
g.co/ABH
If power key is not pressed:
Your device will poweroff in 30 seconds
Click to expand...
Click to collapse
Fastboot shows:
TARGET PROJECT : V520KL
IMAGE VERSION : V5.6.0
BUILD VARIANT : USER
SECURE BOOT : enabled
DEVICE STATE : locked
Software status : Official
Click to expand...
Click to collapse
After a few days, I finally tried the power button, and it boots up just fine, and seems perfectly stable. I performed complete backups, and for what it's worth, I ran a bunch of droid virus/malware/rootkit scanners, and they found nothing. (Obviously, a good rootkit will hide itself.)
I eventually did a factory reset. This went well, but the red error message remains. So, I believe the corruption must be in a partition that a reset doesn't replace.
MORE DETAILS
I've never unlocked, rooted, or installed a custom ROM onto this phone. The only "beyond typical user" thing I'd previously done is to install adb sourced directly from Google, to be able to run Genymobile's scrcpy, which is an extremely fast open source program that allows me to remotely control my phone from my linux PC, via USB or wireless. I've been using this for many months without any issues.
This appears to mean dm-verity is detecting corruption, and is the "red" version of it which many have described as the death of their device. I believe this means the phone is able to verify the signature on the bootloader and it's able to verify the signature on the kernel, but that the kernel is finding an invalid block(s) on one of the many partitions being read right at turning on (detected because the hash for the block is not as expected.) When this happens, an I/O error is given indicating the block cannot be read.
I have been quite concerned if this might indicate a rootkit had been installed. I haven't done anything that I would suspect could let one in. After spending a lot of time learning about adb, fastboot, TWRP, and having the ultimate goal of discovering which partition has an unexpected hash, determining if this meant a rootkit or file corruption, and fixing the error, I've hit many brick walls.
For a day or two, I avoided seeing if the power button would allow it to boot, because if there was a rootkit, I didn't want it to run. I was disappointed to learn that through fastboot (specifically, I mean the fastboot PC program that connects to the droid when in fastboot mode), there is no way to do something like a full bitwise image of the internal storage, and analyze the situation in linux. Or, any type of backup whatsoever. I was frustrated to learn from another XDA thread about a lot of problems others have had rooting and/or installing TWRP on this device. I was frustrated to see there is no prebuilt version of TWRP for my device. (There is an image for the Asus ZenFone 5z 2018 ZS620KL which is very different than my Zenfone V520KL V.)
I realized with my particular device, I think, the only way I was going to take any next step required hitting the power button. (As I mentioned way above, that's when I found it appears to work fine, and I eventually did a factory reset.)
I attempted using the TWRP recovery.img posted by game #1 in that XDA thread about my device, but like he encountered, fastboot boot recovery.img doesn't work, and just reboots instead.
Without being able to extract the original recovery.img, I'm not sure that I'm willing to install his and see if it works for me. I was frustrated to find there appears to be no way to extract the original recovery.img without first having root access. All non-root methods I later found to do this didn't work. Notably, su can't run anymore through adb, and adb root can't run with a user build.
I've looked a bit at custom compiling TWRP myself, but haven't done that yet. In part, because if my version doesn't work through fastboot boot recovery.img, I'd have the same concern about overwriting the original one before getting some feedback here. Also in part, because I haven't looked enough to find how someone goes about making a BoardConfig.mk and the device tree from scratch.
Hey. I tried installing TRWP on my device, Asus Zenfone 5Z (ZS620KL) but I also got the same message. "This phone is corrupted and cannot be trusted." It also said it won't boot. Now I am stuck in Fastboot mode.
I tried installing a stock rom. Downloaded the firmware. i even downloaded python so I can extract the payload.bin file. Followed the steps but still to no avail.
Is there anyone who could help me?
If you could attach the files that I would be needing, that would be a great help.
Thanks.