Related
Righto. Before we go any further, jsut to say I am a relatively experienced rooter of Android handsets. Not tabs, granted, but handsets. Last night I rooted my TF and flashed Megatron and recommended kernel, no problem. I've had no problem taking nandroid backups or restoring as I've done that several times today, all with expected results.
Then I opened ROM Manager and allowed the app to update, I guess updating CWM too.
I then fiddled with SetCPU overclocking the CPU. This caused the tab to stutter a bit. Then freeze. Anyway, I hard rebooted and went into recovery to try and flash the backup I took about an hour ago. Now, CWM looks different (I guess this is where ROM Manager updated). I flashed the backup which seemed to go ok, but then when the TF rebooted I got an Android message saying that encryption hadn't worked properly, and that I would need to do a full (factory) reset. I hit ok and let it do it's think. The TF rebooted, but went direct into Recovery.
I tried wiping everything using Factory Reset, and wiping Dalvik, etc, but every time I tried I got a message saying "E: Can't mount /sdcard/" and then it reverted back to the main menu structure. Even when I choose "Install zip from sdcard" > "choose zip from sdcard" I just get a message up saying "E: Can't mount /sdcard/" and that's all she wrote. I think a) ROM Manager may have caused this and b) it's royally wrecked.
I did find teh following in a TF guide regarding cold booting:
-Quote-
11. Now do a Cold Boot (aka Hard Reset). This cleans system caches, but does not delete any user data.
Unplug the power cord and shut the unit off. Press and hold the VOL DOWN and then POWER button at the same time for at least 10-12 seconds until after the start-up screen appears and is joined by some small print at the top of the screen, then let them both go. If the TF booted the way it always does, you have not accomplished the task, try again until you have seen the 2 icons in the screen.
After a few seconds you should see a couple of icons in the middle of the screen called "Wipe Data" and "Android". The right "Android" will have a green highlight fading in and out. Wait a few more seconds until the term "Cold Booting Linux" appears in the list near the top of the screens and let it reboot. If you own a keyboard dock be sure you do this with the dock connected.
This process applies to all TF models, however, if your Prime or tf300 is locked up, there is a reset available using the hole just below the microSD slot, this is NOT the same as a hard reset.
12. Finally, restore your photos, docs etc & reinstall your apps from the backups, one group at a time & cold boot between each group that you restore. (Unless you are resetting because of system instability. In which case, read the next section, first.)
-Unquote-
I tried doing this but the TF froze at the point where the unit says "Cold-booting Linux". I left it for a good 30 minutes but no joy...
The other issue I have is that even when I attach my TF to my PC the PC doesn't recignise the unit. It knows I'm trying to attach something but it doesn't know what. Therefore I don't think I can flash anything like a new CWM version or kernel if the PC doesn't know where or what to flash to...?
I'd love to hear anyone's thoughts on this one...
Thanks in advance!
"Then I opened ROM Manager and allowed the app to update, I guess updating CWM too." - Never use ROM manager on the TF, it causes extensive problems. There is a warning thread about this in General.
You'll want to try running Roach2010's fix, either via my PERI tool (in my sig) or by manually typing the commands.
Lifesaver! One problem - when I plug my TF into my PC using the USB cable it doesn't recognise it. Won't this be a problem?
Sent from my GT-I9100 using xda app-developers app
(Also, I've replied a bit more to your post on Transformer Forum - Thanks mate!)
Alright you're going to want to download this while you read -- http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
In the link below a driver package is also included, you need to either...
Code:
Open the Start Menu, type 'cmd' and hit enter, then type:
pnputil -a C:\path\to\driver folder\NvidiaUsb.inf file
exit
Then plug in the TF in APX mode and windows will find drivers automatically
Or you right click computer and hit 'Manage' and then hit 'Device Manager', find the ? entry that says APX and right click and hit 'update driver', then navigate to the folder.
Download the unbrick .zip from here: http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
(Before each file are 2 letters, (US, WW, CN, TW...) pick the one that is your Region. I'm assuming you need WW, which stands for World Wide, but if you reside in Taiwan take TW, China take CN and America take US.
Also download Wheelie NvFlash from here: http://androidroot.mobi/2012/05/31/wheelie-for-windows-beta/
Extract it, and copy the Contents of the folder into the Unbrick .zip folder's contents main folder, Overwrite any files that conflict.
Then you should be able to run Reflash_Sbkv#.bat to unbrick your TF in APX mode that is connected, try Sbkv2 first, then if you get access denied try Sbkv1.
Hope you're sorted out!
[This is a repost of my post over at Android Central]
Hey Everybody,
My Nexus S 4G has been unusable for a few days now and I need some help diagnosing the problem and determining if it can even be fixed.
What happened: I was running jstntp's Android 4.1.1 rom (ver 2.0). I liked the performance of version 1.2 a little better so I went back to it. Being 1.2 didn't have wifi tethering enabled I figured I'd try a 3rd party wifi tethering app just to see if it'd work (I can't remember the name of it). After install my phone rebooted itself (looking like a crash) and went into an immediate boot loop. I quickly booted to recovery and tried simply reinstalling 1.2. That failed. So I tried restoring a nandroid backup. That failed too.
What i've tried to fix it: I have tried flashing (via fastboot) stock gingerbread, stock ics, google's official stock gingerbread, google's official stock ics, sprint's official ics via odin, and a half a dozen different 3rd party roms such as some bugless beast roms that I have used in the past. The stock images all appear to flash fine with no complaints from installers. Even odin installed and displayed it's "passed" message.
Where it gets weird: In all of my recovery efforts I noticed a strange occurance happening. Everytime I would load something to the "sdcard" (whether it be by mounting in cwm or pushing through adb) it would appear in cwm while it was booted there (yet fail to install anything) and would disapear as soon as I booted out of cwm. Also, if I deleted any files while mounted (or deleted from adb shell for that matter) they would reappear after rebooting. At this point I figured the root of all of my problems is that my "sdcard" partition has a problem and needs to be fixed.
How i've tried to fix the "sdcard" partition:
- Chose to format /sdcard in cwm recovery. It said it was successful but didn't do anything at all
- Chose to format /sdcard in twrp recovery. It said "E:tw_format_rmfr: unable to locate volume for device "/dev/block/mmcblk0p3" "
- Did fastboot erase media
- Locked the device and unlocked it again agreeing to wipe all data (nothing got deleted)
- Pushed busybox over adb and ran mkfs.vfat on /dev/block/mmcblk0p3. It didn't complain and said it was successful. (still nothing deleted)
At this point I'm really at a loss. I will do anything to get this to boot. I don't care what version of Android I wind up on, I don't care that I have to lose all of the stuff on my "sdcard" (it's all backed up anyway). Just having a working phone would be great.
Thanks in advance,
- Phil -
Mount USB on Windows and just format it. Or before that you could try running chkdsk {yourdrive} /F
The chkdsk is on windows.
I had already opened a post that no one has found a solution, I just have to give your phone to a service center HTC, my problem at this point is:
The data can not be erased, as the title, even with the formatting of the SD through the PC, so they are visible to anyone, and all my mail and all the other private data, photos, etc.. etc. .. This is something that disturbs me a lot, any of you know how to help me? If you need more information, just ask.
What have you tried?
I am going to suggest booting unto recovery and performing a data reset from there vice the settings menu.
If that doesn't work then give me some more details so I could help.
FYI, verify fastboot is not checked in your power settings.
dellenrules said:
What have you tried?
I am going to suggest booting unto recovery and performing a data reset from there vice the settings menu.
If that doesn't work then give me some more details so I could help.
FYI, verify fastboot is not checked in your power settings.
Click to expand...
Click to collapse
Format SD from PC, formatting OK - Switch phone to "Charge only" files and folders, all present.
Deleting files and folders with "Root EXplorer" - Restart Phone: all the files you are all still present.
Installation of utilities, programs or Apk file, even if the installation is successful, restart, everything goes back to the previous configuration without any alteration.
In short, it is as if the reboot, will mount the same image previous .
I tried to reinstall the Fastboot stock_boot.img and stock_recovery.img, the flash file is successful, but when it reboots no goes into recovery mode, we see only a moment, Recovery, and then go reboot.
I also tried to do the Fastboot boot recovery.img, it should be for a few seconds the white screen with HTC green then reboots with the old installation.
The phone often restarts when I try to camibare configuration, if I go "back to factory settings" but when you restart back as it was before, always the same image.
Forgive my bad english, thanks
So I have a problem with my Nexus 5. Yesterday I tried all kinds of different Lollipop roms and at the end of the day I sticked to Cataclysm. I liked it and my phone was all set up but I noticed there were a lot of unnecessary folders on my internal storage and a nested 0 folder (0 inside /0). I didn't like that so I thought about making a nandroid backup, storing it on my computer (together with my music etc.), wiping everything and restoring it by using TWRP and then eventually putting my music back.
So after I stored a backup on my computer, I started my device into recovery mode and chose the option 'advanced wipe'. Usually I would do a lot of research for everything I do but in this case I was a bit lazy to do that, I tried digging into the search results of Google concerning wiping but I gave up after some unsatisfying results. So I checked every box in the list, including data and system and went through with the wiping. So because my storage was completely wiped I didn't have a 'WRTP/BACKUPS' folder anymore. I made a backup from the stuff I had (which was only a few mb's) so I would have that folder again (otherwise I wouldn't be possible to locate my nandroid backup). I wanted to transfer my nandroid from my computer to my phone by connecting it through USB but for some reason the Nexus 5 didn't show up on my PC when it was booted in recovery (this sometimes happens for some reason)
I managed to do it by using 'adb push Cataclysm folder' in cmd. I went into recovery and restored my backup. My phone booted and I thought everything was as it should be. The wallpaper was black but that was logical because my internal storage was wiped, including my custom wallpaper. But then I noticed something strange, my status bar disappeared, sames goes for my navigation bar. I really have no idea what happened because I've restored nandroid backups before and everything went fine.
So then I put a clean version of Cataclysm on my phone and for some reason it asks me to insert a SIM-card into my device while it has one. I skipped that step and then it asked for my home Wi-Fi and I chose mine, then it checked the connection way longer than it would normally do. After I was done with all the steps my homepage entered my screen and guess what, my status bar and also my navigation bar were absent. It was like my cell phone was in immersive mode all the time. Then I tried flashing the KitKat factory image by going into recovery with my phone and opening 'flash-all.bat' on my PC but then it said '< waiting for devices >' while I enabled USB debugging... I opened cmd and typed 'adb decives' and mine showed up, so it was connected (although it now says 'unauthorized' when my phone is normally booted).
Then I flashed clean Cataclysm again and it again said I had to insert my SIM-card and it then again checked the connection with the Wi-Fi for a couple of minutes. When I was done with the installation I tried replacing the wallpaper with one from Lollipop but it didn't work although there was a preview available. There was again no status bar and navigation bar. I then opened chrome and went to this website and now I'm typing this on my Nexus 5 which has a permanent immersive mode now.
So I don't have much in my internal storage anymore, only a TWRP folder with backups, nothing more, not even a 0 folder if I'm not wrong. There's something wrong with my mobile connection and definitely something going on with my navigation bar and status bar. I hope anyone could help me with this because this is really frustrating becausr I tried to fix it for the last couple of hours, unfortunately without any result...
EDIT: I forgot to mention that when I was trying to figure out how to send the nandroid without being able to access my internal storage via my computer, I booted in recovery, went to 'advanced' and then to 'adb sideload' and tried that because I saw it somewhere on the internet. I somehow believe this contributed to the problem I have.
EDIT2: Now, when I try to power off my phone by holding the power button, it reboots the device instead, what's going on... And as I said, I have a black screen as wallpaper for some reason and I can't change this, but if I open my weather widget, the widget window shows up with my chosen wallpaper on the background, what kind of sorcery is this?
EDIT3: I wanted to download a terminal emulator from Google Play to do this but I couldn't get to 100% so I thought there was something wrong with the app on my device. I googled the apk and I wanted to download it from Zippyshare and when I clicked on the button 'download now', the phone showed the message 'no SD card', so I guess that's the culprit of all of this?
TL;DR My phone is acting really weird (no status or navigation bar, phone reboots instead of asking whether I want to have it shut down when I hold the power button, the wallpaper being strange, SIM-card isn't being recognised) after I wiped data and system and actually everything...
Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google
Niflheimer said:
Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google
Click to expand...
Click to collapse
Thank you for reading my huge explanation. After hours of searching and trying a lot of things with my device I figured out how to fix it. Do you remember I said that when I tried to flash the factory image with 'flash-all.bat' that it responded with '< waiting for devices >' ? Well, after reinstalling the drivers countless times and trying to find the culprit I realised I was trying to flash it with TWRP being open, and not the bootloader... So after I was aware of that I finally managed to put stock Lollipop on my phone, then I wiped everything and flashed Cataclysm. It felt pretty satisfying to have a working phone again, it's a pity I had to start from scratch but on the other side, I now how a phone without any rubbish.
Regarding adb push, if I would like to ever push a rom or a big file onto my phone in case I would ever have a similar annoyance, what do you recommend me to do it with?
And what is EFS exactly and what happens if I would ever wipe that? Thank in advance!
Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.
Niflheimer said:
Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.
Click to expand...
Click to collapse
I'll definitely make a nandroid, just in case. Thanks for the help and the clarification!
Try wiping your bum more thoroughly
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
temme how to recover the system folder. i have a system folder on my desktop. help me. my phone isnt turing on
If you can get into fastboot and recover you can restore your phone. You just need a complete ROM, and restore it with mfastboot method.
It doesn't matter if you wiped system, you can do that in TWRP, if you reboot it won't boot into the OS (obviously) but go into fastboot mode.
Download mfastboot, a ROM image, and go through the command lines. There is a FAQ on how to restore.
felmaster said:
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
Click to expand...
Click to collapse
Also TWRP/CWM has support for adb, u just need to install the drivers manually. Then you can push whatever you want.
Of course you can try restoring stock as suggested above.
How did u fixed it? :/
As a last resort there is always OTG (this thing has OTG support right?). Life was so much simpler when you could just put your sd card into a card reader and put your zip on there. A quick google search makes me think its got support, but who knows