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
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
otisranson said:
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Click to expand...
Click to collapse
otisranson said:
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
Click to expand...
Click to collapse
yup, this ones explainable. classic symptoms of a ns with its internal sd card dying/dead. it happens way too often unfortunately. luckily its a fairly easy and inexpensive repair, if youre not under warranty.
Any direction on how to fix it while not under warranty?
Or take it to tmobile?
otisranson said:
Any direction on how to fix it while not under warranty?
Click to expand...
Click to collapse
check out any local mobile device repair shops. you could probably do it yourself if you dont fear taking the phone apart, it should be to difficult of a repair. its just a matter of buying a replacement(ebay?), taking the phone apart, and replacing the sd.
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
I've been having similar issues..what is the exact part name for the SD?...I wanna search to buy one
Sent from my Nexus S 4G using XDA Premium App
I think its:
Samsung KB100D00WM-A453 memory package and S5PC110A01 1GHz Cortex A8 Hummingbird Processor.
I'm going to try to find another nexus s mother board as a whole, that's my only option.
otisranson said:
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
Click to expand...
Click to collapse
I think it's in step 10
i seen something a few weeks ago online on how to replace this...it was a video..i just cant remember where i seen it!
I ended up just purchasing a new phone on ebay.. If I find a nexus s with a cracked screen, I will swap out the mobo.
You can check whether there are blocks flagged as bad by FTL (Flash Translation Layer) in recovery. Check recovery.log file (it can be, the bad blocks will show up after formats).
"So here's the problem. Just got my One S the other day and I attempted to install trickDroid on it. I got it rooted and unlocked and tried installing. Something went wrong somewhere along there and it wont boot up, only past the first screen and its all black after, i do hear the start up sound after a while but it stays black screen. So i tried to revert it back to stock and during the process I though I had to erase/reset data, so i did that. Only then did i realize that everything was on internal memory and it did not have an external sd card. So I cant install anything without transfering the files from my PC. I tried different versions of clockwork by fastbooting it because i heard it connect to pc automatically. But i end up with an I drive I cant access(insert disk in to I) or on the phone its says something about "unable to open ums lunfile htc one s" I also tried the all in one tool and the latest version doesnt have stock recovery. So the main problem is I can't transfer files on to the phone to reinstall any ROMs and I cant revert back to stock. I am thankful for any help anyone can provide me." sorry for the double post
My stock, untouched, unrooted HTC One S has randomly got itself stuck in a boot loop. It goes through the 'quietly brilliant' screen, onto the 'htc one' screen and then it restarts. I am desperately trying to recover my files and photos from the memory before I try a Factory Reset, because while these.threads mention ways to recover deleted files, these.posts from the OP suggest that it doesn't work for files lost to a factory reset.
Things I have tried:
Selecting the 'Recovery' option from the bootloader shows a black screen with green arrows on it for about 10s, but then the green arrows change to a red triangle with a '!' in it and it eventually reboots into the same loop.
Connecting to the phone using ADB over USB fails as the device is unseen. I believe this is failing because the phone is locked, and/or does not have USB debugging enabled on it??
The Fastboot tool does seem to be able to see my device, but from what I can tell fastboot is more used for flashing ROMs, and I'm not really trying to do this.
So my questions are:
Does anyone know of a way to access the files/folders on my device in its current state?
Since the SD card on the One S is fake, is there a way for me to fix the section of memory that boots the device, whilst leaving the storage bit untouched?
Any advice is greatly appreciated as I've got a lot of personal photos and videos on the device. I didn't think to back them up because on previous phones they've always been safely accessible on a physical card =(
Thanks in advance,
Tom
Hi Tom,
I'm not familiar with stock recovery, as I unlocked and rooted my device almost immediately. So I'm not really sure, but here are some suggestions anyway:
Try and see if vol-up or -down gets you in a state where you can get adb when booted into stock recovery.
You can also try and fastboot boot directly into a custom recovery image, but that may not be possible with a locked bootloader.
If not, I'm afraid you're SOL, since unlocking wipes the storage.
-Jobo
I cant think of any way to recover from this situation except reflash ruu but then your sd card is wiped. Did you not activate dropbox?
What about vol down and power, rebooting into HBOOT? Then can't you dd if sdcard of?
Or fastboot pull /sdcard/ C:\Users\User\Desktop\sdcard
Sent from my locked, tampered ville
I'm in the same situation, it happened on Thursday night (the 8th), when did your's start? I'm struggling to find a solution for this as well. The closest I've got to anything is that on Linux Ubuntu, when I book the phone connected to my laptop one the second (out of three) boot screens it recognizes the device as an inaccessible HTC Phone, disappearing then once it reboots. Nothing is accessible.
Thanks all for your replies. I'll try to respond in order...
@Jobo - Sorry to be a noob, but how do I boot into stock recovery? The Recovery option from the HBOOT screen fails like I said above. Regarding fastboot, does it let you boot into an image that is stored on your PC? Is that how it works? Obviously I'm not going to be able to get an image onto the phone without most likely wiping everything. FYI, my HBOOT screen says ***LOCKED*** on it, but the phone was bought outright so it is not locked by a provider.
@gazknight - I saw Dropbox more as a solution for the One S's limited storage capacity. Since I didn't expect to go over the fixed limit, I didn't really think I'd need the service. Backing up for security's sake would obviously have been a good idea but then I've never had a phone break quite so suddenly as this so I didn't think to do that.
@usaff22 - I can get into HBOOT successfully, but in this state (or whilst in the FASTBOOT menu) my SD card is not mounted and not visible over USB. Does the DD command require a mounted drive? Also, is it a LINUX command? I'm running Windows on my laptop, but with the Android SDK installed. I tried FASTBOOT PULL, but that's not a recognised command when I try it; listing the commands available only shows options like 'flash', 'erase', 'format', 'boot' etc.
@nickrr1 - Mine went bad just a few days before yours I think. I see what you mean, I think; on Windows, when I leave the phone connected via USB for the duration of its boot loop, a mounted drive does appear for just a few seconds, but if I click it it says "Please insert a disk" and then it's gone within a few seconds.
tommy_g003 said:
Thanks all for your replies. I'll try to respond in order...
@Jobo - Sorry to be a noob, but how do I boot into stock recovery? The Recovery option from the HBOOT screen fails like I said above. Regarding fastboot, does it let you boot into an image that is stored on your PC? Is that how it works? Obviously I'm not going to be able to get an image onto the phone without most likely wiping everything. FYI, my HBOOT screen says ***LOCKED*** on it, but the phone was bought outright so it is not locked by a provider.
@usaff22 - I can get into HBOOT successfully, but in this state (or whilst in the FASTBOOT menu) my SD card is not mounted and not visible over USB. Does the DD command require a mounted drive? Also, is it a LINUX command? I'm running Windows on my laptop, but with the Android SDK installed. I tried FASTBOOT PULL, but that's not a recognised command when I try it; listing the commands available only shows options like 'flash', 'erase', 'format', 'boot' etc.
Click to expand...
Click to collapse
Locked means the bootloader being locked/unlocked, not the SIM's state.
dd if of should work after typing adb shell. Have you tried flashing a recovery in fastboot? I need the sdcard partition number though, for the dd to work.
It is fastboot flash recovery recovery.img (recovery should be named recovery.img and placed in the fastboot folder)
Edit: tried this?
http://forum.xda-developers.com/showthread.php?p=25557817#post25850720
tommy_g003 said:
@Jobo - Sorry to be a noob, but how do I boot into stock recovery? The Recovery option from the HBOOT screen fails like I said above. Regarding fastboot, does it let you boot into an image that is stored on your PC? Is that how it works? Obviously I'm not going to be able to get an image onto the phone without most likely wiping everything. FYI, my HBOOT screen says ***LOCKED*** on it, but the phone was bought outright so it is not locked by a provider.
Click to expand...
Click to collapse
As I said, I'm not familiar with stock recovery and I don't have it installed.
After you select recovery from hboot, and before it reboots again, does it respond to the volume buttons?
Yes, you can fastboot boot into a recovery image without copying the file to the device:
fastboot boot recovery-cwm-ville.img (substitute the actual file name of the recovery image. but im not sure whether this requires an unlocked bootloader.)
As usaff22 pointed out, **LOCKED** means bootloader locked, not provider SIM locked.
usaff22 said:
Have you tried flashing a recovery in fastboot? I need the sdcard partition number though, for the dd to work.
Click to expand...
Click to collapse
He can not flash recoveries since his bootloader is locked.
The sdcard partition is /dev/block/mmcblk0p36
EDIT: Here is another thought:
Have you tried booting into safe mode? (Power on the device, when on the boot splash hold vol-down and keep holding until you feel a long buzz or until you see 'safe mode' in the lower left corner of the screen.) If not, you can try to fastboot erase cache and even fastboot erase userdata. This should not erase your sdcard, just your apps and app data, but it might get your device back into bootable state, if the bootloop was caused by a user app or some corrupted user data.
usaff22 said:
Edit: tried this?
http://forum.xda-developers.com/showthread.php?p=25557817#post25850720
Click to expand...
Click to collapse
That will erase the sdcard. The whole point of this thread is to save the sdcard contents.
touch of jobo said:
That will erase the sdcard. The whole point of this thread is to save the sdcard contents.
Click to expand...
Click to collapse
My bad. Sorry.
I wonder if the following will work:
dd if=/dev/block/mmcblk0p36 of=C:\Users\UserAccount\Desktop\
Have you tried the wipe user data option in HBOOT? Not clear storage, if I remember correctly there is another option to wipe user data.
usaff22 said:
I wonder if the following will work:
dd if=/dev/block/mmcblk0p36 of=C:\Users\UserAccount\Desktop\
Click to expand...
Click to collapse
It will not. dd must be run on the device. What would work (on a linux host) is this:
(adb shell dd if=/dev/block/mmc0p36) > ~/rescued_sdcard.img
But still .. you would need to be able to get an adb shell first.
Thanks so much for your time and suggestions on this. I've tried a few things now, but to no avail so far...
ADB - Still no luck with this. I think this is expected because of the state my phone is in... I have read that it needs to be actually booted up, and with USB Debugging enabled for it to work.
Safe Mode - No joy. I can use a long press of Volume Down to get a long buzz, but then it still reboots a few seconds later.
Recovery Boot - Selecting Recovery from the HBOOT menu and then pressing/holding the Volume Up and Down buttons does not seem to have any effect. I'm not sure exactly when I should be pressing them, but I have tried a few different methods and it always ends up on the same red triangle screen.
Fastboot - This does seem to be connecting, but because the damn thing is locked I'm getting access errors when I try to do anything useful...
fastboot erase cache works, but then rebooting normally or with safe mode both fail as usual.
fastboot erase userdata fails with a "remote: not allowed" error.
fastboot boot ville_recovery_signed.img posts success at reading the image file but then it fails at the 'booting' stage with the same remote access error.
HBOOT wipe - My only two options relating to data at the top level menu are 'FACTORY RESET' and 'CLEAR STORAGE'. I have not tried selecting either of these, so I am not sure of any deeper options, but I did research these options and it does seem like they will likely wipe my SD data. I am wondering though if maybe the FACTORY RESET might save my data on the SD partition. This is the opposite of what an HTC support guy told me though.
Also I found a report of another poor guy having the same issue this week. Add 'www' to the following: peoplesrepublicofcork.com/forums/showthread.php?p=4528285 (soz, I can't post links yet)
>_< Why didn't I just back up my photos & videos!?!
UPDATE:
So after a bit of back-and-forth with HTC's tech support over the last few days, I got some instructions from them to use the Factory Reset...
HTC: "...I would like you to perform a factory reset of the phone. This will erase all data saved to the memory of the phone, but will not clear the phone storage..."
ME: "...Will the Factory Reset really spare the 'storage' as suggested, or is this wording aimed at phones with a physical SD card?..."
HTC: "On the HTC One S there are 2 different types of storage. The phone memory and the internal storage of the phone. A factory reset will erase all data from the memory of the phone, but leave the phone storage intact, it is easiest if you think of phone storage as an internal SD Card. There are 2 settings on the phone which reflect this, a factory reset and the option to clear storage. If you choose a factory reset of the phone your internal storage should remain intact and your photos will not be wiped from the device."
So I did the Reset, and the phone now boots, but I've lost all my photos and videos. They don't show up on the phone; they don't show up on a mounted drive; they don't even show up using typical 'undelete' software on the mounted drive. Thanks for the great advice, HTC!
Now my last option is to follow this thread, but this will involve me knowingly voiding my warranty on a piece of hardware which I already know is potentially unreliable.
So I think I'm just going to give up....
What a drama...
@tommy_g003
How did things work out? Did you manage to recover your data after the factory reset?
I have exactly the same bootloop problem you described and I'm beyond despair. Over the past couple of weeks I've used an app on my phone (PCM recorder) to record interviews for my master thesis. I've backed up several of them, but not all... I have gone above and beyond to get these interviews and there is no way I'll be able to redo them. I really truly cannot lose these recordings!
I think at this point I'd rather even sacrifice my phone by physically removing the storage from it and somehow recovering the data from it, but I have no clue whether this is even possible.
I read a thread (androidforums. com/htc-wildfire-s/560123-unrooted-wildfire-s-bootloop-help. html - remove spaces in url) that describes how to re-flash the stock ROM when not rooted. Presumably this can fix the bootloop, while not deleting the internal storage. Does anybody know if something like this exists and works for the One S as well?
jazzmijnhv said:
I read a thread (androidforums. com/htc-wildfire-s/560123-unrooted-wildfire-s-bootloop-help. html - remove spaces in url) that describes how to re-flash the stock ROM when not rooted. Presumably this can fix the bootloop, while not deleting the internal storage. Does anybody know if something like this exists and works for the One S as well?
Click to expand...
Click to collapse
Running a RUU will erase your sdcard. So will unlocking your bootloader. Don't do it.
You can try booting up in Safe Mode (power down, boot back up and as soon as you see your boot splash (quietly brilliant) hold vol-down until youre fully booted.
You can try erasing your data and cache partitions in fastboot, and then booting back up.
Both of these suggestions were already offered in this thread so you probably tried already, but just to make sure.
Finally, you can look at the unbricking tutorial in the development forum, and see if the same method can be used to extract partition #36. Personally I've never had to unbrick/downgrade, but maybe someone familiar with the process can weigh in. If this is possible, you can then mount it and extract the files from it. Since you're not unlocked and you can't unlock (without losing your data) you'll have to be able to get into download mode by powering up holding vol-up.
I haven't really got any further with this. My One S now works, but I'm avoiding using it for now until I've imaged & extracted its storage for a salvage op (see the link in my post above) and I'm too lazy to go about rooting etc. right now in order to do this.
I had the exact same issue as you, multiple times now.
First time I did a factory reset and everything was erased (pics, videos, downloaded apps, etc).
After that I'm just doing clear storage - which removes all the apps that were installed and all configuration, but my photos, videos, and all other documents remain intact.
Fix bootloop without losing data
After my phone shut down because of the % of the battery, it was low, phone got stucked on samsung logo after power up. I dont want to lose data on my phone, how can i recover data first and then factory reset it, or to access device without losing data, is it possible? If its not, ill do the factory reset....
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!