I was running CM10 on a rooted TFT101. I was having some WiFI connectivity issues so I decided I would try out a new rom. I used Titamium Backup and backed up all my needed files to my Mico SD card. Once backed up, I rebooted into CWM v6.0.1.3. I went to do a factory reset prior to flashing the new rom. The tablet just froze. I rebooted the tablet back into CWM. I tried to again do a factory reset and again the tablet just froze. I tried to boot back into CM10 and I just sits and spins and never actually boots into the OS. I decided that I would just go ahead and just flash the new rom and do a factory reset after the fact. I placed the new rom on the micro sd card and booted back into CWM. I attempted to install zip from SD card and now I get e:can't mount /sdcard/. I have tried 3 different micro sd cards and nothing. I have formatted each to fat32 and not one of them is recognized. All 3 are recognized by windows.
Since I can't boot into the OS...and I can't load a new rom....I am dead in the water. Any help would be greatly appreciated.
Thank you in advance.
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Lethe6 said:
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Click to expand...
Click to collapse
Thank you Lethe6. I saw that option and wondered if that might help me. I will try it out today.
One quick question. If I flash back to stock I am guessing I will just need to reroot once I am able to boot it back up?
Thank you again for your assistance.
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Lethe6 said:
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Click to expand...
Click to collapse
Go figure. I went to fix the issue last night per your instructions and I was sitting at the Google login screen for the the new rom I loaded. What ever issue I was having corrected itself. That never happens. I guess I shouldn't complain =)
Thank you again for your assistance Lethe6!
Related
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Yeah stop using that old version. Of ClockworkMod recovery
Seriously use 3.0.2.4. Its in the clockwork thread in the dev section.
Sent from my Nexus S using XDA App
Would if I could, but I can't get anything on the SD card!
Trying to mount USB storage from CWM-- no drive shows up on Mac or PC for me to move stuff onto it.
Boot into fastboot by turning off phone, turn back on while holding volume rocker up. Leave it at the screen where you could select reboot, recovery etc. Download the above mentioned clockwork recovery image from the thread to your computer. Flash using fastboot command. No need to copy anything to SD card.
Sent from my Nexus S using XDA App
Having the exact same issue. Nothing appears in the nandroid folder now either after replacing the recovery image with 3.0.2.4 and I can't mount the USB storage or get anything onto the SD card. Phone won't boot. Unsure of the folder structure on this phone to try pushing a file with adb or fastboot.
Same issues here. I was able to flash CWM recovery 3.0.2.4, but when I go to "mounts and storage" and "mount USB storage", I the drive does not appear on both Mac and PC. I'd like to transfer the stock NS4G image onto the phone so I can install the zip from the sdcard...
When I try to use the command, "adb push", it can't find the SD card.
Same problem
I flashed it , and since then i cannot mount the device , i have a good image to push but the device is not opening up the storage for me to push the image.
I had the same problem. Got it all fixed up.
peabody42 said:
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Click to expand...
Click to collapse
I had the same problem this morning:
I posted a workaround that worked well for me in Post #35
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
If it works for you click 'Thanks'
Figured it out
Alright , this is what i did to fix the problem, i booted up the system with the bad image i had, connected to wifi and downloaded the Nexus S 4G deoxed image that is out there directly from the internet to the phone. Then i moved it from the download folder to the root using file manager.
I rebooted into recovery and was able to wipe and then flash the recovery image and reboot. Once i rebooted i regained control over the usb and memory card. hope it helps you guys.
How Do I Fix "REALLY" Bricked and DEAD Nexus S4g?
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
sexynexy said:
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
Click to expand...
Click to collapse
Hi,
What method did u use to root? What thread? Cuz it may need to newest version of the recovery.
anyways...
Try charging up a battery on newer phone and put in dead phone... but instead if turning on normally, boot into recovery.
If it worked then use a back up to flash it back to stock. Assuming u were able to back it up b4 root.
If not plug into computer. See if it turns on or can go into either recovery or boat loader mode and if so perhaps computer will recognize it.
Vs Nexus S4G using tapatalk2
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
So I power it back up after a few mins of charging.....the LG screen comes on.....then the Ultimate 1.0 Rom loading logo comes up..after that every 10-15 seconds it turns on the screen, shuts it off, turns it on, off, etc. It keeps turning on and off...even after I left it there for 5 mins.
I'm going to flash back my Froyo stock rooted rom that I made a back up. The Ultimate 1.0 isn't the only rom I've flashed in the past. CM7 as well..many of the builds.
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
That happened to me. I had to reset - battery pull alone wouldn't work. That phone is now on its way to T-Mobile, and its warranty replacement is going to be soon due to really bad screen bleed (affects my watching video and game play).
flexnix said:
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
Click to expand...
Click to collapse
What was "it says" - ROM Manager?
If so, it looks for a androids on the internal SD. If you had used the easy recovery install tool, you would have been able to select internal or external to use with Recovery - NOT ROM Manager.
Based on your choice, you should be able to access you nandroid in the place you chose in RECOVERY MODE.
Since you fully drained you battery, you might want to erase battery specs in recovery, turn it off, and fully charge with it turned off for 8 hours. It is not recommended that you fully drain the battery and that may be your problem.
Then you could try wiping cache, dalvek, and format /system - and reflash your ROM. Save flashing the nandroid for last.
flexnix said:
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
Click to expand...
Click to collapse
have you tried a different battery?
According to the experts at Popular Mechanics running your battery dry is very bad for it. It greatly reduces the life according to them. There was a post about it last week. There are physics involved that apply to all.
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
You need to NVflash your Recovery
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You boot the phone holding Volume Up & Power buttons until recovery screen appears.
Recovery, if you flashed it using the NVflash tool, will be accessible by booting your phone while holding Vol Up & Power. You will go into Recovery. If you have never done this or do not get recovery its because you did not flash the Recovery onto your phone.
Basically, if all you did was download ROM Manager and start flashing the G2x you are playing with fire. You need to flash the Recovery onto the phone using NVflash tool. ( Follow Step2 in the following link: http://forum.xda-developers.com/showthread.php?t=1060715 )
I would recommend anyone with the same problem or the same question to go thru the link above and you will find answers to most of your problems.
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
flexnix said:
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
Click to expand...
Click to collapse
Did you rename your nandroid backup?
If you did that would be the problem. if you want to rename it, don't leave any spaces.
Sent from my G2x
This is my first thread that i ever needed to start on anything on phones so please understand that i'm REALLY DESPERATE i have looked in a ton of places for this fix and i tried to use clockworkmod and ended up doing that correctly but when i tried to restore it it say i dont have any backups nor recovery files and i tried putting cynagenmod on my sd card but it couldnt find the file and then i tried to use NFFLASH and make it stock android again but nothing happened and ended up stuck on the blue logo screen again. please i dont know what to do
Which version of Cyanogenmod is it? Put it on the root of your SD card. Is it already on the internal storage? I believe when you click "install from .zip" or something of the equivalent there's an option to select "choose from internal storage".
You can boot back into clockwork mod by turning the phone off, holding down the power and volume down buttons until the lg logo with the BLUE background appears, then release.
I was trying to install cynagen mod 7.01 from Rom manager but it froze in the logo screen and so i took out the battery and put it back on and it still continued to do that. After that i used CWM but i didnt have any ROMS to restore it and before it didnt correctly make my backup so i just want to restore it like the way it used to but i dont know where to put it in my sd card
crazian425 said:
This is my first thread that i ever needed to start on anything on phones so please understand that i'm REALLY DESPERATE i have looked in a ton of places for this fix and i tried to use clockworkmod and ended up doing that correctly but when i tried to restore it it say i dont have any backups nor recovery files and i tried putting cynagenmod on my sd card but it couldnt find the file and then i tried to use NFFLASH and make it stock android again but nothing happened and ended up stuck on the blue logo screen again. please i dont know what to do
Click to expand...
Click to collapse
Your sentence is incredibly long. Gave up after the desperate grab for attention. You may have wiped your backups by mistake. It happens. I did it not once, but twice. Give us more info so we can help. ROM, kernel, etc. A list of apps you run on a daily basis would be helpful.
crazian425 said:
I was trying to install cynagen mod 7.01 from Rom manager but it froze in the logo screen and so i took out the battery and put it back on and it still continued to do that. After that i used CWM but i didnt have any ROMS to restore it and before it didnt correctly make my backup so i just want to restore it like the way it used to but i dont know where to put it in my sd card
Click to expand...
Click to collapse
Never use rom manager to install on this phone, you'll continue to run into this problem.
Can you access your phone storage when it's plugged into your computer? If you can, drop CM onto it at the root directory, put it back into your phone, boot into CWM and install the zip.
i think my rom was stock rom 2.3.4 before i tried flashing cynagenmod the apps arent very important to me and i only had this phone for a week because i got too excited about the dual core.
Follow the instructions HERE to the letter. You'll go back to stock and you'll have to root your phone again (if that's what you want to do) but it should get you up and running again.
In future, search, search, and search some more. I assure you, most problems people have had have been discussed and probably solved on these forums.
Welcome to XDA!
What is the name for this process of trying to restore my device from blue logo screen? If i know the name of the issue im trying to fix maybe i can start searching for the guides. I can't really access my internal or sd card when i plug in my usb and i don't really understand what the problem i ran into if its even fixable or not. The link you've sent me for the guide i'm trying right now but i can't just sit here and wait for an hour. Feedback is really appreciated
crazian425 said:
What is the name for this process of trying to restore my device from blue logo screen? If i know the name of the issue im trying to fix maybe i can start searching for the guides. I can't really access my internal or sd card when i plug in my usb and i don't really understand what the problem i ran into if its even fixable or not. The link you've sent me for the guide i'm trying right now but i can't just sit here and wait for an hour. Feedback is really appreciated
Click to expand...
Click to collapse
The whole process (if done correctly) should take but about 15 minutes give or take. What you'll be doing is Flashing Stock Recovery. Download the file provided in the link I gave, and then follow each instruction exactly as it says. Shouldn't be a need to Google any guides as this spell it out for you. Just have read and execute.
If you used NvFlash/One Click Recovery to flash Clockwork Mod to your device then you should already have the APX driver installed on your computer. In that case, half of the battle is already done.
But, if you installed your recovery using Rom Manager, then I would download the APX driver and go through the whole process in the guide I've linked from start to finish.
My phone took a dump on me yesterday and I've been scouring XDA over the last few hours for a solution and I see a lot of similar issues but nothing exactly like mine. Please bear with me...
I was using the latest MIUI version by evol4g and the only persistent issue was some lag, nothing with my SD card or the core android processes. I went to bed last night and my phone was charging then a bright light in my room woke me up at about 0400. I looked at my phone and noticed it had rebooted itself into recovery. I attempted a simple reboot and it got stuck on the black Google screen. I pulled the battery and booted it back into recovery and attempted to restore it but noticed that none of my nand backups were available. I figured, this sucks, but I'm tired so I'll just re-flash the ROM and deal with it later. I attempted to flash a .zip from the SD card and it told me that no SD card could be found. I got up and went to my laptop to copy a ROM from my desktop to the SD card and when I went to mount the USB drive it told me that there was "no file to write to" (or something similar). Basically, I have no SD card access and no way to mount the USB to attempt re-flashing of anything.
I've made multiple attempts over the last 6+ hours to re-flash CWM to the latest version (using both ADB and the fastboot version), I've tried to re-flash through ODIN and I've even gone as far as attempting to UNroot just so I can get this thing to function. Every time, though, it gets stuck while writing the system files then doesn't get any further. When I'm using ABD, I've got no SU access and while in fastboot, the system gets stuck writing .system files. As of right now, it's been attempting to write the system files for the UNroot process via the Nexus S Hacks .zip for over an hour. Any and all advice is welcomed and thanks for reading!
jordanjackthomas said:
My phone took a dump on me yesterday and I've been scouring XDA over the last few hours for a solution and I see a lot of similar issues but nothing exactly like mine. Please bear with me...
I was using the latest MIUI version by evol4g and the only persistent issue was some lag, nothing with my SD card or the core android processes. I went to bed last night and my phone was charging then a bright light in my room woke me up at about 0400. I looked at my phone and noticed it had rebooted itself into recovery. I attempted a simple reboot and it got stuck on the black Google screen. I pulled the battery and booted it back into recovery and attempted to restore it but noticed that none of my nand backups were available. I figured, this sucks, but I'm tired so I'll just re-flash the ROM and deal with it later. I attempted to flash a .zip from the SD card and it told me that no SD card could be found. I got up and went to my laptop to copy a ROM from my desktop to the SD card and when I went to mount the USB drive it told me that there was "no file to write to" (or something similar). Basically, I have no SD card access and no way to mount the USB to attempt re-flashing of anything.
I've made multiple attempts over the last 6+ hours to re-flash CWM to the latest version (using both ADB and the fastboot version), I've tried to re-flash through ODIN and I've even gone as far as attempting to UNroot just so I can get this thing to function. Every time, though, it gets stuck while writing the system files then doesn't get any further. When I'm using ABD, I've got no SU access and while in fastboot, the system gets stuck writing .system files. As of right now, it's been attempting to write the system files for the UNroot process via the Nexus S Hacks .zip for over an hour. Any and all advice is welcomed and thanks for reading!
Click to expand...
Click to collapse
I hate to be the one to tell you this.. sounds like you got bit by the nand flash failure that all of us nexus s owners fear. Warrenty repair is the only recourse in that case.
Sad to say but sounds like you got bit .
I've been searching for 3 days now, and everything I've found has not worked. I am using twrp, and have tried flashing three different roms. Everything in fastboot and twrp runs fine, but as soon as I get to the asus boot screen (I've seen it to be called the circle/ring of death) it freezes, then reboots. I've tried re flashing back to stock rom, upgrading firmware/ downgrading firmware, different twrp versions, stock recovery, hitting my head on the tablet. I don't know what else to do.
My tablet was version 4.2.1 I used the boot unlocker v_8. Tablet was rooted and working for one day, then over night this began.
If someone could please point me in the right direction, or is this just a case of my tablet being done for?
Fox5.56 said:
I've been searching for 3 days now, and everything I've found has not worked. I am using twrp, and have tried flashing three different roms. Everything in fastboot and twrp runs fine, but as soon as I get to the asus boot screen (I've seen it to be called the circle/ring of death) it freezes, then reboots. I've tried re flashing back to stock rom, upgrading firmware/ downgrading firmware, different twrp versions, stock recovery, hitting my head on the tablet. I don't know what else to do.
My tablet was version 4.2.1 I used the boot unlocker v_8. Tablet was rooted and working for one day, then over night this began.
If someone could please point me in the right direction, or is this just a case of my tablet being done for?
Click to expand...
Click to collapse
Do you have valuable data on the tab? If yes, I'd suggest you copy them off your internal storage to your external Sd card with TWRP, then erase everything per buster99's script (search for the name); flash stock rom via fastboot. You don't need to reset the tab by poking the hole since you apparently can get to fastboot without issue.
DO NOT touch the wipe data icon on the boot screen! Do everything with TWRP only. If you choose to do it via SD card, remove the card before rebooting to see what happens. It has occurred to me that leaving the card inside might cause problems. Good luck.
graphdarnell said:
Do you have valuable data on the tab? If yes, I'd suggest you copy them off your internal storage to your external Sd card with TWRP, then erase everything per buster99's script (search for the name); flash stock rom via fastboot. You don't need to reset the tab by poking the hole since you apparently can get to fastboot without issue.
DO NOT touch the wipe data icon on the boot screen! Do everything with TWRP only. If you choose to do it via SD card, remove the card before rebooting to see what happens. It has occurred to me that leaving the card inside might cause problems. Good luck.
Click to expand...
Click to collapse
I copied anything I wanted saved, but I did not do a legitimate backup of software files.
I have pressed the wipe data icon on the boot screen under the confusment of the many different posts. What step does that leave me at?
EDIT:
So crazy Buster99 fastboot flash did it. Sucks because I tried that before but I guess I may have missed one line of the reflashing script. Well thanks, after three days I've finally been put in the right direction.
Seems like that pesky /misc partition is causing problems. Glad you got it sorted out though.
Sent from my SGH-T889 using xda app-developers app