HTC One-S US version. Wow. I will try to keep this short and would really appreciate any input I can get. I should probably resolve myself to it being bricked but who knows.
I updated my device last night to the latest Cyanogen mod (was already running the last release). I factory reset before. While reloading the new version the device froze on the white HTC screen.
I was able to get back to the bootloader and at times the Clockwork Recovery screen. Somehow in the process the SD card became unmounted. I followed the *numerous* threads here on how to resolve it but to no avail. At one point I reformatted the SD card and, for some reason, repartioned the flash ROM allocation to a size much to small to run Cyanogen (I tried to reinstall the stock software from .exe file after relocking the device and this is how I determined the allocated size was to small.
So I am now stuck on the bootloader screen. Is it possible from either ADB commands or ? to correctly partition the drive again? I have Googled and Googled and probably spent more time flying solo on this than I should of (at least past my expertise). I have tried the usuals, factory reset, clear storage, etc. When I tried to use the HTC software to reload the original build, it showed no existing OS on the device. So I am stumped and will provide any information as needed to clarify this confounding problem. Thank you.
michaelsean
It seems like you might have to go back to a stock RUU, What version of HBoot are you on?
Related
Hi there,
as you may know, some owners of a desire have an issue with their USB/BT/FM functions. For example only fastboot works but no adb / mass storage ...
So, i thought opening this thread to collect your issues, please post the following informations:
Bootloader Infos
Rooted or not
Which rom
Have you used mass storage switch in recovery
Do you use a2sd or a2sd+?
If there are enough answers i will send the collected infos to paul from modaco, who tries to adress the issue.
no usb-bt-fm
bootloader 0.75
original rom 1.15.405.4
when does it happen for you
Also posted om Modaco
Bootloader 0.75
Stock ROM 1.15.405.4 Rooted + App2sd + dalvic
Yes, I used Mass storage in recovery
Issue startet when I transfered the MCR custom fra PC to phone via recovery
I loaded a rom amended with root permissions, not happy I restored everything to its original state with the 1.15.405.4 but now no longer works usb-bt - FM ... and access to most recovery so I can not load the rom recovery .. . Help
From what i know the guys looking into this have problems to dress the trigger of the brick, so all infos on how and when ar great
Bare in mind that the rooting process was at your own risk: no-one (HTC or Paul) will take responsibility if features are no longer working.
Personally, everyone works fine on mine including adb/mass storage. I don't actually see why it'd break.
OP, what OS are you using? I had to add some udev lines into Ubuntu as otherwise adb would work but Mass Storage would fail (on my netbook, even adb wouldn't function without adding the android rules).
I know it's our risc, but hey without some investigation no progress, right?
Btw. Paul is looking into this but no ETA for now
I had exactly the same issue as you lot, only difference was that my new rom flash was interrupted by me knocking the phone and the battery falling out!
I was on evil's 1.0 and decided to change to his 1.1. In the middle of the phone formatting during the flash, I knocked the phone and the battery dislodged causing it to lose power. I had the sd card formatted and was already using a2sd. Turning it back on and restarting the root process from step 1 on Tiny Core Linux got me back with a semi working phone. I had no BT, no SD card, and didn't check the FM radio. It also started to lose signal and would require a reboot to get it back.
I tried unrooting it using paul's method and it was still the same. I just took it back to the shop and acted stupid. They gave me a brand new boxed one, no questions asked I'm scared to try flashing again now though lol.
0.75
Modaco R2 with A2SD+
Yes i have used USB-MS (still works)
no usb connectivity from within android.... but adb works
Bootloader 0.75, tried a few different ROMs (primarily eViL's, tried some MoDaCo), and I've definitely mounted the SD from within recovery. Every single ROM swap I've done was accompanied with a full wipe and SD partition afterwards.
So far I guess I've just been lucky. USB still works, though it can take a long damn time to get recognized in Windows if I'm syncing through the Desire; if I take the SD card out and pop it in a reader, it pops up instantly.
So: .75, lots of ROMs, definitely mounted SD from recovery, always full wipe and format. No issues. Supremely lucky, apparently. :/
Hboot 0.80 o2 Germany ModacoCustomRom r3.
Today after reflashing MCR3! Before all was very well the only thing was that iwasnt able to mount my sdcard without a witget!
Bootloader 0.75
MoDaCo r3 Rom with app2sd+
I used Mass storage in recovery
Issue startet after I flash the jit patch,it can't use recovery again
Can you all confirm that you had a boot loop at some point during your flashing?
The conversations on Modaco now have me convinced that this is triggered when you go through a boot loop of three cycles.
Loccy said:
Can you all confirm that you had a boot loop at some point during your flashing?
The conversations on Modaco now have me convinced that this is triggered when you go through a boot loop of three cycles.
Click to expand...
Click to collapse
yes,I think it's,but have a solution now?
miyu-hitori said:
yes,I think it's,but have a solution now?
Click to expand...
Click to collapse
No, not for those who've been bitten, but I think the rule for those of us still flashing is:
1) Flash rom (or update.zip for kernel, make changes to system, etc) in recovery
2) reboot
3) immediately do adb logcat on your PC and watch first boot like a hawk
4) if logcat reveals that your device is bootlooping, PULL THE BATTERY IMMEDIATELY. Reboot into recovery (which should count as a "successful" boot, and reset the counter) and flash a known good ROM, restore your backup, whatever.
Fixing those phones that are dead is unfortunately a task for a greater mind than mine.
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
-sigh- Alright, so I'm thoroughly confused. My Sensation has been constantly showing the boot screen, and then promptly shutting itself down and restarting the process. I can access recovery, but not sure what to do there. Here's some background info:
So, I've been using Virtuous Inquisition since version 1.0, including the original firmware, and I haven't updated the firmware since. I recently decided it was too buggy and decided to switch back to MIUI (the latest build), which is naturally Gingerbread, and not ICS. Everything force closed and the phone constantly shut itself down, so I assumed it was the admittedly very test/alpha-y ICS firmware that was the problem, so I updated to 3.24 (not Revolutionary), which people said should be compatible. At this point, I couldn't even boot up properly anymore. I removed the SD card to delete the firmware update, and now I can access recovery.
The weird thing is, I've tried many things, and all to no avail. Using recovery, I attempted to restore my stock Sensation, and so then I could see the "Quietly Brilliant" screen before rebooting, as well. Why didn't this work? I then removed the battery for ten minutes or so, Super Wiped (a la ARHD), and reflashed MIUI. Still nothing.
Is my phone hopelessly lost? ;_; Is the firmware still the issue? What on Earth can I do to save my irreplacable phone? Thanks in advance; I will be forever grateful if it can be salvaged.
invalid473d said:
-sigh- Alright, so I'm thoroughly confused. My Sensation has been constantly showing the boot screen, and then promptly shutting itself down and restarting the process. I can access recovery, but not sure what to do there. Here's some background info:
So, I've been using Virtuous Inquisition since version 1.0, including the original firmware, and I haven't updated the firmware since. I recently decided it was too buggy and decided to switch back to MIUI (the latest build), which is naturally Gingerbread, and not ICS. Everything force closed and the phone constantly shut itself down, so I assumed it was the admittedly very test/alpha-y ICS firmware that was the problem, so I updated to 3.24 (not Revolutionary), which people said should be compatible. At this point, I couldn't even boot up properly anymore. I removed the SD card to delete the firmware update, and now I can access recovery.
The weird thing is, I've tried many things, and all to no avail. Using recovery, I attempted to restore my stock Sensation, and so then I could see the "Quietly Brilliant" screen before rebooting, as well. Why didn't this work? I then removed the battery for ten minutes or so, Super Wiped (a la ARHD), and reflashed MIUI. Still nothing.
Is my phone hopelessly lost? ;_; Is the firmware still the issue? What on Earth can I do to save my irreplacable phone? Thanks in advance; I will be forever grateful if it can be salvaged.
Click to expand...
Click to collapse
You have to downgrade your firmware to 3.17 or lower in order to re-flash any gingerbread rom like MIUI. The 3.24 is NOT compatible with GB and will bootloop, in which you are experiencing.
Take the sd card out, delete the 3.24 img file and replace it with the 3.17. Boot into hboot and flash the downgraded firmware. Then go reboot. If you can get up and running go and delete the img file immediately. IF not, remove the card again and delete it with a card reader.
If you are already on a GB rom, the downgraded firmware should have booted up.
Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great
Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?
-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though
Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.
-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol
If this doesn't help get Thor's hammer and flash your appropriate RUU (again).
Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!
--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu
Aye, captain. Glad to read this.
My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
Next step is to use the Eclipse debugger and read the debug output once it crashes/reboots. The output from the debugger will provide more information about what happened so you can start narrowing the problem down more.
It's a memory or cpu problem (i guess) . Try the cpu a bit lower. I hope it will help you
If you have flashed your phone allot, and you have under clocked your CPU first, it may be a NAND issue. It has been a problem on my end with the HTC HD2 after like 1000+ flashes. You should be able to use a tool to check for bad NAND blocks, don't remember off the top of my head what it was called when I used it but that's something you could do. That is all (if) you have not tried to under-clock your CPU first and make sure the ROM is not bugging out like it sounds like it is.
Another way to test your NAND is to try a SD ROM that runs on your MicroSD card.