Related
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
From bad to WORSE!
I discovered the dcom222 thread that describes my problem and details a solution. I followed it to the letter, changing the command and using my microSD as a secondary boot to reinstall the vanilla tnt ROM.
But then it just stuck on the tnt logo, faded in and out 3-4 times, and went dark! The device won't turn on or off (had a full charge when I pulled it from the wall socket a few moments ago)
Please tell me I haven't bricked this thing!
still no luck...
I was able to power the unit back up, but I've tried to recover and flash all three setup files I have (vanilla tnt, ota update tnt and tnt lite 2) but nothing works!
All of them create a loop of some sort, whether it's the viewsonic screen, gtablet screen loop, or the tnt logo screen blinking on and off, NOTHING boots to the desktop.
Going to bed before I drive my self insane. Hopefully someone in the know will reply by the time I check this at work.
thanks in advance
You have not bricked it, don't worry. This device is very hard to truly brick. If all else fails there is nvflash or the apx mode fallback. But I don't think you need that if you are still able to boot to clockwork recovery.
In clockwork go to advanced - mounts and try mounting and unmounting your partitions. I suspect your user partition may be screwed. This seems to happen fairly frequently especially the first time you flash a ROM. It happenend on my first flash and not again since. Clockwork lets you repartition though. Search the forum for partition fix, its not too big a deal.
If that fails try roebeet's thread on nvflash recovery for TNT lite. If that fails, search for APX mode.
As far as I know there are zero bricks from ROM flashing so far.
Sent from my SMB-A1002-3G using Tapatalk
Life in LA said:
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
Click to expand...
Click to collapse
Scroll down to post number #869 http://forum.xda-developers.com/showthread.php?t=842004&page=87
feeling better
Thanks for the assurances that I didn't wreck the device, and pointing me to some solutions. I have a few questions:
what is clockwork mod? If I am able to recovery boot from my micro SD card, do I already have it? (I downloaded a bunch of recovery images to start, per instructions)
If it's something I still need to download, is it a PC application? How am I supposed to change settings in it (manage partitions, etc) if I can't get the tablet to boot?
-- stuck at work and dying to get home to fix this thing...
Ok, more detailed instructions:
If you press and hold down Volume + when you are pressing the Power button to boot up, and keep holding the Volume + key until you see a message that says "Detect a Recovery Key Pressed", that should get you to a text menu from which you can navigate using the volume +/- keys and the Home soft button to flash ZIP files and do other things. That menu is ClockworkMod Recovery. Since you remember installing a recovery.img, it sounds like you probably (hopefully) have ClockworkMod Recovery on there.
If you get to ClockwordMod Recovery, you can go down to the Mounts and Storage option, then you will find the "Mount USB storage" option at the end of that list. That lets you plug in and mount your internal memory area as a standard USB drive to your Windows or Mac computer to copy over new ZIP files and the like to your G Tablet.
You can also check that partitions are all mounting and unmounting successfully in that menu. If you go instead into the Advanced menu, you will see Partition SD Card, which I believe is what you might need to do at this point.
If booting with the Volume + button held down doesn't get you anywhere and you see nothing about Recovery Key Detected and don't see any text menu, then you don't seem to have a working recovery. At that point you'll have to do what phfaty suggested, read the post he referenced, and follow the link therein to the tegratab forum post to get the NVidia Tegra SDK installed on your Windows desktop and use the NVFlash tool and APK mode (where you hold the Volume - key down while booting instead of the Volume + key) to reflash your tablet.
still not working...
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Life in LA said:
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Click to expand...
Click to collapse
1)Boot into clockwork.
2)Navigate to Advanced menu
3)Choose partition sdcard
4)Choose data partition desired size(1024=1GB)
5)Choose 0GB for the next selection(swap not used)
6)Do a factory reset from main menu
7)Reboot
8)If that doesn't work, then reinstall ROM, then reboot
UPDATE
partitioning the drive and wiping the user data did the trick. I'm up and running again. thanks to all who chimed in to help.
Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.
So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!
It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.
well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.
DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.
okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.
Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.
DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?
Thanks for that important tidbit, solarnz. I'm going to file it away for future use.
OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!
Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk
I just installed my first custom rom, which is indicated, from rooted Froyo (LG G2X). When I start the phone a get that process stopping message recurring and have to OK it for quite a while before it stabilizes.
I have almost completed the setup when this problem occurred. How can I fix it?
Thanks.
I just installed my first custom rom, which is indicated, from rooted Froyo (LG G2X). When I start the phone a get that process stopping message recurring and have to OK it for quite a while before it stabilizes. <br />
I have almost completed the setup when this problem occurred. How can I fix it?<br />
<br />
Thanks.
Click to expand...
Click to collapse
Try using the nullifier tool, and fix permissions after you install. It sounds like you got a bad flash.
Pin it to Win it.
I ran single wipe and it ran and has hung on the LG screen. I am unable to boot into recovery. The LG log and Label is displayed, despite pressing power, down volume.
I toggled the up and down arrows and the power button (after ~ 5 battery pulls) and S/W upgrade Please wait while upgrading is now displayed.
pmorrsn said:
I ran single wipe and it ran and has hung on the LG screen. I am unable to boot into recovery. The LG log and Label is displayed, despite pressing power, down volume.
I toggled the up and down arrows and the power button (after ~ 5 battery pulls) and S/W upgrade Please wait while upgrading is now displayed.
Click to expand...
Click to collapse
No biggie you must have messed a step up. You will have to nvflash your recovery again as the nullifier messes with it if you don't successfully install a new rom.
Also you could have a corrupt download so try redownloading the file.
Head over to the Hellion help page:
http://forum.xda-developers.com/showthread.php?p=22881829
And make sure you follow each step carefully to the "T".
Pin it to Win it.
no luck...I only have the LG screen no rebooting
no luck...I only have the LG screen no rebooting
I cannot boot up, power. down volume key.
pmorrsn said:
I cannot boot up, power. down volume key.
Click to expand...
Click to collapse
In order to nvflash your clockwork recovery you must do the following :
1. Take battery/USB cable out
2. Insert battery
3. Hold volume up and plug your USB into your PC
(You should hear your computer detect a device attatched)
4. Run nvflash
5. After cwm is flashed you will then be able to boot into recovery and flash a rom using the instructions in the Hellion help thread.
Edit:
This is where you get the one click recovery flasher which will make nvflashing cwm a breeze!
http://forum.xda-developers.com/showthread.php?p=13330067
Pin it to Win it.
Tried that, but is that a new nvidia AXP driver
Tried that, but is that a new nvidia AXP driver
I rooted my g2x with that process last fall. I tried that last night, and got it into Software updating screen, but it stayed there all night. So, what would be a next step, if stuck on that screen. I tried booting in several external SD card options, as I backed up my ROMs there, but maybe I should run the internal option?
It immediately finished with no obvious errors, saying hit return to get finish.
I rooted my g2x with that process last fall. I tried that last night, and got it into Software updating screen, but it stayed there all night. So, what would be a next step, if stuck on that screen. I tried booting in several external SD card options, as I backed up my ROMs there, but maybe I should run the internal option?<br />
It immediately finished with no obvious errors, saying hit return to get finish.
Click to expand...
Click to collapse
So I'm a little confused by your post... you followed the directions and it worked or no?
Pin it to Win it.
was stuck in Software Updating for hours
was stuck in Software Updating for hours
I then did a battery pull after ~5-6 hours and got no further. Off the computer, I can sometimes get the LG logo to appear, but sometimes, I get no response.
My phone is effectively bricked...but it did talk to my computer last night. So?
It isn't bricked if the computer recognizes it. Especially if it turns on.
Sent from my LG-P999 using xda premium
Keep the volume up key held the whole time during the nvflash process. if your comp recognizes the phone your still cooking with gasoline
Pin it to Win it.
OK, that means my phone is salvageable. I just need to have it respond to me or my computer.
Which of the one flash options will do the trick?
Since i saved my ROMS to the external SD, I chose the 5.0 version and I think a 4.0 version and they both hung me in the update mode...one for most of the night.
How long should I sit for the update, if that is a good think?
dont write your message here...
pmorrsn said:
OK, that means my phone is salvageable. I just need to have it respond to me or my computer. which of the one flash options will do the trick?
I tried two and they both hung me in the update mode...one for most of the night. How long should I sit for the update, if that is a good think?
Click to expand...
Click to collapse
this is easily fixable, but you will need to follow these directions very carefully and do not skip any step even if you have already done it. follow this guide here to re-flash CWM to your phone and it will also wipe your internalSD card and everything else. you will then flash a a rom from your externalSD card and you should be good to go.
PAY ATTENTION TO WHAT BUTTONS YOU NEED TO HOLD AT WHAT TIMES. i would recommend reading it a few times before doing it.
EDIT: please for the love of god do not ask questions or try to say something in the titles of your posts, most of us just skip over those without looking.
Thanks, this was one of my next steps..I need to get to my vista PC, but you'll hear back from me.
I'll try this first.
Thanks for the titles tip....I find the titles confusing...and have the need to use the space. I appreciate the feedback.
All fixed. I restored my old Froyo from my external SD following the cleaninstall process.
The only trick was that if I release the power key after the flash it does some default load. I have to first simply stop pressing the -Vol key and then I can up/down the Reboot/restore menu.
Glad you got it figured... sometimes our phones have the craziest quirks... makes me wanna laugh and cry when sh¡t like that happens to me... either way now your a pro on recovering your cwm and that's basically like wearing a helmet Hahahaha have fun
Pin it to Win it.
mt3g said:
It isn't bricked if the computer recognizes it. Especially if it turns on.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I didn't know it was possible to brick a g2x
Sent from my LG-P999 using XDA
Cause it isn't lol
Sent from my LG-P999 using xda premium
If you run into that problem again as stated in the OP, disable wifi calling. I was getting that error on all HFS versions.
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.
Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
PC connection
DieterW91 said:
Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
Click to expand...
Click to collapse
I've had success getting a connection to Windows just be using a different USB port, the ones at the back are best. Then at least you get fastboot access...But I also still have the problem with the sdcard, still working on that, trying to figure out a way to fix it from fastboot...
any progress yet rosanna? I was also able to make the connection with my pc, by using the usb ports on the back (thanks for that!). But I haven't been able to mount my sd card yet. I tried with another recovery but that didn't do the trick.
I got into the UI of my current ROM, and then my pc said I needed to format the SD before I could use it.
But I wasn't sure this is a good idea to do in windows.
Anyone know if it is save to format your internal sd card when prompted to do so in windows?
Have a look here
Sent from my ElementalXed One S
Try using a Linux live cd (try Ubuntu). You'll need a blank DVD to burn the iso to. Reboot your computer and see if it recognizes your device (no drivers needed). If it does try a more stable build this time.
benJX said:
Have a look here
Sent from my ElementalXed One S
Click to expand...
Click to collapse
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
DieterW91 said:
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
Click to expand...
Click to collapse
1 minute - downloadlink is on the way
Here you are: http://forum.xda-developers.com/attachment.php?attachmentid=2622663&d=1394422408
You can flash it with the toolkit selecting "Custom recovery".
When you're Storage is back alive and kickin' you can flash a custom revovery again.
My favourites are
TWRP 2.7.0.0 - http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.7.0.0-ville.img
and
PhilZ advanced CWM - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville
In my opinion TWRP is easiest to handle and PhilZ has some more features.
DieterW91 said:
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
Click to expand...
Click to collapse
Another direct link here, I personally flashed it manually trough fastboot, for me the easiest and fastest way to do it. Then proceed to the clear storage and flash your custom recovery (like @LS.xD I recommend TWRP but this is your choice )
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
DieterW91 said:
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
Click to expand...
Click to collapse
Feel free to hit the "thanks" button