Related
I started this thread as a constructive and positive place for those of us that have recently lost our G1's or ADP's. I am going to document all my settings, Radio version, Firmware, Build info, etc here and hopefully reverse engineer this issue until I have an answer. If anyone has any hardware engineering information on this device it would be greatly appreciated. I'm even willing to host a private forum from my site to work on this.
Thanks everyone for your continued hard work and Haykuro, you're still the man!
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Partioned Fat32/EXT2 1GB SDcard from t-mobile
Flashed RC29 via Bootloader .NBH file
Rooted with RC29
Updated to RC33
Flashed Hard SPL
Flashed JF v1.5 ADP Lucid MOD - did APPs2SD and Dalvik2SD
Flash 2.22.19.26I Radio
Flashed Grafitti Citrus Theme JFv1.50 Beta
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL.
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
ivanmmj said:
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
Click to expand...
Click to collapse
Goldcard as in a specialized SIM?
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
Goldcards as in a specialized SD card
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
MosquitoD4K said:
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Click to expand...
Click to collapse
This has happened to me many times when I didn't wipe (the PHONE ). Take the battery out, place back in and hold Home + Power to get into menu. Type alt + w to wipe, afterwards, alt + s to apply update.zip from sdcard, then Home+Back to restart. The first time loading, it can take up to ten minutes to get past the Android screen (mine took 7-10 minutes), so be patient.
Post back with any results.
ivanmmj said:
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
Click to expand...
Click to collapse
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you can bricking you phone. take patience and wait.
Good luck
ps:i change the final text for sir*mez
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
satru said:
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you and only you bricking you phone. take patience and wait.
Good luck
Click to expand...
Click to collapse
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone for my bricked phone, im just trying to find a solution. you are going to get this locked because of the bickering.
hey sir*mes was no my intentions blaming to anyone , i only want to say that all need to give more time to flash before take out the battery. only that.
i will do something for you , i will change the text, happy?
Good luck
sir*mez said:
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone im just trying to find a solution. you are going to get this locked because of the bickering.
Click to expand...
Click to collapse
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
I tried it and so far no luck...
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
ok but the phone wont go into bootloader. which is what im trying to get it to do. if i get it to bootloader i know i can fix it. even if it went to the recovery i could fix it. but I get nothing.
in order to create a goldcard for the dream it has to read the sdcard off fastboot which i cant get into.
d474rpr said:
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
Click to expand...
Click to collapse
Are you saying your screen doesn't turn on?
neoobs said:
Are you saying your screen doesn't turn on?
Click to expand...
Click to collapse
No, I'm saying it doesn't turn on.
d474rpr said:
No, I'm saying it doesn't turn on.
Click to expand...
Click to collapse
The same happens on Heralds when the imgfs is messed up. To fix it, we force it to go into the bootloader mode and it does turn on. I wonder if it's something similar.
I meantioned in the big main topic an idea though I dont think anyone saw it.
In the past for other phones I was able to make recoveries using the computer while it was in the boot loop.
Anyone with the brick, try to see what happens when you do this:
adb remount
After the "T-Mobile G1" screen shows up. See if it says mount sucessful. I would try though it does not stay on the screen too long for me, not only that it might work for me just because it continues fine so its inconclusive.
If you get lucky and it says remount successful, you could try this:
adb shell recovery
I am not sure of the commands to follow from there, but it might allow you to flash a different update.zip file from the command line. If you get lucky like that, look up the commands and see how that might go. There has to be a way to communicate to the hardware when that screen comes up. Its good that that screen comes up, because it means its not 'fried' so to speak, it just has a misconfigured loader which doesnt have the correct set of instructions (good point about the different types of boards, thats most likely the issue) for THAT board. I would go back to the one that worked previously.
My brain hurts...I'm so frustrated I feel like slamming the phone against the wall.
I've gone through 5 threads about bricked Inspire phones but it seems my case is a little different than those.
This was clearly a failed rooting. The phone is stuck on the white screen/boot logo.
It will let me go into HBOOT but none of the functions will work,i.e. recovery,bootlader,etc. It vibrates and keeps going back to the boot logo screen or the triangle icon appears. I've tried everything, the S-ON Tool did nothing because the phone is not recognized when connected to the PC. When I try "factory reset" on HBOOT,it acts like it's going to do it but after a few seconds it goes back to the logo screen. Attempted several rooting processes with Hack Kit but get "phone is offline" error or not connected. I've taken out the battery so many times it's ridiculous. At this point I feel helpless and hopeless.Surely I'm doing something wrong and I'm hoping one of the gurus here can point me in the right direction.
Thank you very much in advance to all those who answer this post.
Search the recent questions regarding problems while trying to root. I have said it over and over that the best thing is to go back to the hack kit thread and re read the op. Towards the bottom it says to hit up the irc for help. All the people that have gone to the irc have received the help they needed.
Edit...irc it seriously. Good luck! :-D
I got your 10 char right here
I think we should have a sticky in every forum explaining to people what a BRICKED phone is. Your phone is not bricked....and what cwhitney said also...........................yeah
KPOTT said:
My brain hurts...I'm so frustrated I feel like slamming the phone against the wall.
I've gone through 5 threads about bricked Inspire phones but it seems my case is a little different than those.
This was clearly a failed rooting. The phone is stuck on the white screen/boot logo.
It will let me go into HBOOT but none of the functions will work,i.e. recovery,bootlader,etc. It vibrates and keeps going back to the boot logo screen or the triangle icon appears. I've tried everything, the S-ON Tool did nothing because the phone is not recognized when connected to the PC. When I try "factory reset" on HBOOT,it acts like it's going to do it but after a few seconds it goes back to the logo screen. Attempted several rooting processes with Hack Kit but get "phone is offline" error or not connected. I've taken out the battery so many times it's ridiculous. At this point I feel helpless and hopeless.Surely I'm doing something wrong and I'm hoping one of the gurus here can point me in the right direction.
Thank you very much in advance to all those who answer this post.
Click to expand...
Click to collapse
It is so NOT bricked. Catch us in the IRC channel in my sig and we can get you sorted out, or, you can do it yourself.
If you "factory reset" all you did was wipe your dta settings - including USB debugging on.
Before you can do anything, you will need to install the factory RUU. You can do this from the FASTBOOT USB (note NOT HBOOT USB PLUG) and running the HTC/ATT RUU.
If you're still stuck i had the same issue. Had to reflash the pd98 image zip in hboot again to fix thru issue
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Problem solved. Attn1 and the guys on IRC took care of me.
Thank you very much for your help and patience.
Could you post your fix?I'm having the same problem
deandra said:
Could you post your fix?I'm having the same problem
Click to expand...
Click to collapse
Here is the fix: get on irc or read the forums to find your answer.
Mine was like that to, but because I was rooted I updated ota and it got the loop,I just took out the battery and the memory card out turn it on and was back to normal
Sent from my Inspire 4G using xda premium
glitterbug said:
Here is the fix: get on irc or read the forums to find your answer.
Click to expand...
Click to collapse
What a great idea!!I have done that but thanks for your help anyway
I had the same issue. I just took out my micro SD card, put it in my PC to load the ROM as a P98IMG.zip file on there, re-install the SD into my phone, the boot up in HBoot. It proceeded to find the zip file and continued to install the ROM to my phone. Afterwards it booted up as normal, but of course all of my information had been erased.
it's mya phone a brick!!!!
Ridn2Lo said:
I had the same issue. I just took out my micro SD card, put it in my PC to load the ROM as a P98IMG.zip file on there, re-install the SD into my phone, the boot up in HBoot. It proceeded to find the zip file and continued to install the ROM to my phone. Afterwards it booted up as normal, but of course all of my information had been erased.
Click to expand...
Click to collapse
At me the same problem. Prompt where to take please P98IMG.zip (for AT T). Give please the address for downloading. Also write the instruction as it to correct. At an input in мею HBOOT buttons (I select nothing I can) do not work for me. Help me please. Thanks.
i thought i bricked mine.....
all i did was drag p98 img on to sd card and loaded it and it fixed it...
spv4 said:
At me the same problem. Prompt where to take please P98IMG.zip (for AT T). Give please the address for downloading. Also write the instruction as it to correct. At an input in мею HBOOT buttons (I select nothing I can) do not work for me. Help me please. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1191959&highlight=Stock+Rom
Download from last link
(Here it is in a PD98IMG.zip : http://www.multiupload.com/P13PZJ2JBN)
Click to expand...
Click to collapse
If it's not already called PD98IMG.zip (which it should be), rename it to this. Put it on your SD card at the root directory (don't put it in any subfolders)
Boot to bootloader (Power off, hold Vol- and PWR until bootloader starts)
It should automatically find the PD98IMG.zip and tell you to press Vol+ to start the update.
When it's done, it will tell you to press PWR to reboot
This happened to me and I am hoping this will fix my phone, downloading now, getting a micro sd card reader tomorrow from best buy to put the new file on there to replace the old one. PLEASE WORK>....stay tuned
glitterbug said:
Here is the fix: get on irc or read the forums to find your answer.
Click to expand...
Click to collapse
That is great. A little bit of reading and a great amount of common sense never hurts a situation.
attn1 said:
It is so NOT bricked. Catch us in the IRC channel in my sig and we can get you sorted out, or, you can do it yourself.
If you "factory reset" all you did was wipe your dta settings - including USB debugging on.
Before you can do anything, you will need to install the factory RUU. You can do this from the FASTBOOT USB (note NOT HBOOT USB PLUG) and running the HTC/ATT RUU.
Click to expand...
Click to collapse
thank you so much this solved my problem!!
Never been rooted. My phone froze so I took out the battery and when I turned it back on, the phone was stuck on the boot logo. I've entered into the hboot menu by holding down the down volume key + power. I selected "Factory Reset " but it does nothing. I also tried selecting "Recovery Mode", which makes some green arrows appear, then the phone vibrates about 6 times in a row and goes blank.
Can I load a ROM or something to save the phone?
I also tried removing the SD card when booting, plugging the phone into the PC, etc. Nothing.
Running Gingerbread 2.3.4
I've never rooted or anything but I can follow directions if there's a way. Thanks a lot for reading.
Oh, and when I plug the phone into the computer, it appears to create a drive letter in My Computer, but when I click the drive, it doesn't open.
Should I just warranty out this phone or is there any hope? thanks.
confirm your sd card is good first.
flash your phone with the rom you like.
I think it will be ok after you flash it.
RussianSpring said:
Never been rooted. My phone froze so I took out the battery and when I turned it back on, the phone was stuck on the boot logo. I've entered into the hboot menu by holding down the down volume key + power. I selected "Factory Reset " but it does nothing. I also tried selecting "Recovery Mode", which makes some green arrows appear, then the phone vibrates about 6 times in a row and goes blank.
Can I load a ROM or something to save the phone?
I also tried removing the SD card when booting, plugging the phone into the PC, etc. Nothing.
Running Gingerbread 2.3.4
I've never rooted or anything but I can follow directions if there's a way. Thanks a lot for reading.
Click to expand...
Click to collapse
Goto the glacier forum. Download the factory img file found in the rooting topics. Boot into recovery and let it flash completely. Should be good.
Or... U have a bad emmc and it is toastito's...
How do I flash the phone once I boot into recovery? do I drag and drop the IMG file somewhere on the SD card?
Sorry for the noobness.
When I plug the phone into the PC, a drive letter appears in My Computer - but nothing happens when I click it. Once I put it in recovery, the drive letter disappears.
How would I go about flashing if I don't have access to the files on the SD card?
Okay I got access to my SD card by plugging my SD card into a different phone then the computer.
There is no root folder available when doing it this way - so where would I install the flash file to?
**** never mind, I get what they mean by root...sorry, I'm retarded *****
I think I got it, I'll give this a try.
Okay. All it does is in Hboot, it checks and loads PDIMG15.ZIP, but then it just takes me back to the Hboot menu and the phone is still stuck on the boot screen.
it says...
"SD Checking PD15IMM.ZIP
No image or wrong image!"
Then reverts back to Hboot menu. Tryed formatting the SD card. Will try a different SD card next.
Different 8gb SD card = same results. No image or wrong image.
Appreciate it if anyone has a fix on this.
If anyone else is having this issue, I found a solution:
Go to T-Mobile and buy a SG2.
Problem solved.
This is supposed to a big Android site? thanks for nothing, guys!
I ended up just getting a new phone. Appreciate no one helping. Awesome awesome.
RussianSpring said:
This is supposed to a big Android site? thanks for nothing, guys!
I ended up just getting a new phone. Appreciate no one helping. Awesome awesome.
Click to expand...
Click to collapse
Actually you are in the general section question and answers. There is an Android Section Questions and Answers, and better than that...wait for it...A MYTOUCH 4G QUESTIONS AND ANSWERS!!! Imagine that!! Im quite sure you would have gotten the answers you needed had you done a little searching and posted in the correct spot. Good luck with your new phone!
Maybe someone could of directed me there sooner? This site is confusing if it's your first time.
I know this is free...just saying. My post got a lot of views but almost no response.
Whatever. It's all good...thanks for replying.
Etrick said:
Goto the glacier forum. Download the factory img file found in the rooting topics. Boot into recovery and let it flash completely. Should be good.
Or... U have a bad emmc and it is toastito's...
Click to expand...
Click to collapse
This is a great site. This is/was your Answer!
Sent from my MB855 using xda premium
RussianSpring said:
Maybe someone could of directed me there sooner? This site is confusing if it's your first time.
I know this is free...just saying. My post got a lot of views but almost no response.
Whatever. It's all good...thanks for replying.
Click to expand...
Click to collapse
There is a search bar ...there is forums..... each forum sorted out bu the phone you have each of those forums having subforums to "general Q&a development" and so on.... my question is if you didnt have it rooted why not just take it to the store directly??? Problems like that will asure new a new phone regardless....
Just my 2 cents
oh and this is an amazing site....
rooted 100's of phones with out ever joining and ive finally joined
....crazy how the search bar takes you long ways
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
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