Hi!
Yesterday my msging app wouldn't open so I rebooted the phone, something I do at least once every 2 days, and it booted into recovery without me touching anything.
This error would also show up:
E:Can't read MISC:
(No space left on device)
I can't do ANYTHING. It ALWAYS goes to recovery mode. reboot bootloader goes into recovery. power + camera button goes into recovery. letting it boot goes into recovery.
--all with the same error in recovery, the can't read misc thing.
Did anyone have this problem? I didn't even flash anything, i was just rebooting the phone like I always do and it just appeared. Any ideas? Is this bricked? I don't want to get a new phone until I know I've tried everything. I've already scoured the net for this error with no results.
Thanks!
What recovery do u have? Do u know your phone info? Running a custom Rom? What have u done to the phone before now?
Not bricked btw if u can get into recovery it's fixable
Sent from my HTC Magic SparksMod using XDA App
Hey, thanks for replying!
I'm using RA 1.7 recovery, not sure what phone info you want, its a G1, I'm using CM 6.0 RC1 and have been using for a month now, and before that I've just been using CM, keeping my phone up to date with the stable releases (I don't flash the nightlies)
I'm glad that its not bricked. The problem is that it ONLY boots into recovery, even if I don't press anything...
Thanks!
johnson8cyl said:
What recovery do u have? Do u know your phone info? Running a custom Rom? What have u done to the phone before now?
Not bricked btw if u can get into recovery it's fixable
Sent from my HTC Magic SparksMod using XDA App
Click to expand...
Click to collapse
Ok. I'm looking for spl and radio. Do u have danger spl? Or firerat mtd patch? Sounds like u ran out of internal memory somehow and now won't boot into os is why I ask
Sent from my HTC Magic SparksMod using XDA App
Oh Gotcha - yeah I followed the guide on the CM wiki, so I have danger SPL i believe, and yes, I used firerat's MTD patch
If i remember correctly I used the "all" thing so it went through everything in that patch.
I did that maybe around the time I got CM 6 - so I've been using CM6 and firerat's patch for maybe a month before this happened.
thanks!
johnson8cyl said:
Ok. I'm looking for spl and radio. Do u have danger spl? Or firerat mtd patch? Sounds like u ran out of internal memory somehow and now won't boot into os is why I ask
Sent from my HTC Magic SparksMod using XDA App
Click to expand...
Click to collapse
Interesting. U don't need danger and mtd patch they do the same thing. I'm confused but maybe u have conflicting internal memory partitioning and that's causing it. Do u have a nandroid backup u can go back to that will boot into the os?
Sent from my HTC Magic SparksMod using XDA App
I do but it gives me the same error:
"Can't read MISC: etc etc etc"
This happens when I try to do anything, data wiping, wiping the cache, anything!
I don't even know if it acutally restored the image or not or if the wipe actually happened, because the progress bar is always present for whatever I'm trying to do, its just at the end the error comes up.
In terms of wiping I've tried wiping everything and installing CM6, to no avail. I can't re-reroot the device or downgrade it because recovery always comes up instead of fastboot... I'm stuck!!
Thanks for your insight!
If u plug your phone into the computer and select USB toggle does your sdcard show up on your computer?
Sent from my HTC Magic SparksMod using XDA App
Yep! I can select that MOUNT SD thing and I can transfer files over. Thats what I did to try and flash the rom again, but like always it just gives me that error after its done.
Well i hope you have a spare phone for the time being. I will try to figure something out and keep you informed. Or someone smarter than me will come along and give you the answer. It seems several people have had this prob. but i have not found the solution. Has to be something you can do from a shell in recovery mode to create some space or something to get back into the os. Ill get back with you hopefully with some good news.
johnson8cyl said:
Well i hope you have a spare phone for the time being. I will try to figure something out and keep you informed. Or someone smarter than me will come along and give you the answer. It seems several people have had this prob. but i have not found the solution. Has to be something you can do from a shell in recovery mode to create some space or something to get back into the os. Ill get back with you hopefully with some good news.
Click to expand...
Click to collapse
yeah hopefully something like that will be a solution.. thanks!
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=669019
It would appear that you can run adb commands while in recovery using a shell. Maybe you can do that and use df to see what has low space. When you find that out you can cd to that directory and type ls and get a list of what is in that directory. Maybe delete a few things to clear some space? Can anyone confirm this?
johnson8cyl said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=669019
It would appear that you can run adb commands while in recovery using a shell. Maybe you can do that and use df to see what has low space. When you find that out you can cd to that directory and type ls and get a list of what is in that directory. Maybe delete a few things to clear some space? Can anyone confirm this?
Click to expand...
Click to collapse
Yeah I saw that post but I didn't try what the guy suggested - I will definitely try this when I get home. Too bad that post ended up having no resolution.
johnson8cyl said:
Well i hope you have a spare phone for the time being. I will try to figure something out and keep you informed. Or someone smarter than me will come along and give you the answer. It seems several people have had this prob. but i have not found the solution. Has to be something you can do from a shell in recovery mode to create some space or something to get back into the os. Ill get back with you hopefully with some good news.
Click to expand...
Click to collapse
If your in recovery, can't you just do a full wipe ?
crz6662 said:
If your in recovery, can't you just do a full wipe ?
Click to expand...
Click to collapse
He tried. Doesn't seem to be working. Gets same error. Need more help. Lol. Fun fun.
Sent from my HTC Magic SparksMod using XDA App
johnson8cyl said:
He tried. Doesn't seem to be working. Gets same error. Need more help. Lol. Fun fun.
Sent from my HTC Magic SparksMod using XDA App
Click to expand...
Click to collapse
Yeah, when I do a full wipe it says wipe completed and then right after I get the same error.
What could be wrong!!
Ok, looks like you are in the elite group....this issue is not that common...
See below thread...some useful information from Lbcoder and ezterry....check and see if this can help..
http://forum.xda-developers.com/showthread.php?p=7225151
harryema said:
Hi!
Yesterday my msging app wouldn't open so I rebooted the phone, something I do at least once every 2 days, and it booted into recovery without me touching anything.
This error would also show up:
E:Can't read MISC:
(No space left on device)
I can't do ANYTHING. It ALWAYS goes to recovery mode. reboot bootloader goes into recovery. power + camera button goes into recovery. letting it boot goes into recovery.
--all with the same error in recovery, the can't read misc thing.
Did anyone have this problem? I didn't even flash anything, i was just rebooting the phone like I always do and it just appeared. Any ideas? Is this bricked? I don't want to get a new phone until I know I've tried everything. I've already scoured the net for this error with no results.
Thanks!
Click to expand...
Click to collapse
Yeah I found that thread already... but like me they didn't find a solution either. Plus I do not have a backup misc image so me deleting it would be rather disasterous.
Any other ideas or things I could try?
I'm just about ready to wait for the desire Z or the galaxy S instead of trying to tinker with this old phone...
Related
When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?
irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up
I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823
Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.
I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.
Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.
Did you ever figure this out?
So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App
okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.
i tried also and still no luck .. i hate this
to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.
i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!
sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™
Yeah I'm using clockwork 2.5.0.1.
sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH
Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).
got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?
sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!
There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.
mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.
touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help
Well after installing few games and reflashing my recovery after accidentally putting an older version on, I somehow in turn corrupted my boot loader, system files, data etc, so much so that my backups would boot once but never a second time, clearing my cache and dalvik only made it stuck on htc screen and afterwards it just repeatedly booted into clockwork over and over. This all happening after trying to also make a new nand backup where it hung at system for 30 minutes only to eat up my battery from 100 to 10.
it does charge, I tried using the buttons to boot into fastboot and hboot but it doesn't seem to work, but fastboot usb comes up with I turn it on while connected to the computer but sadly I keep getting error 171 when I try to RUU it.
Have you tried the ruu in zip format??? .
Found here
forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
laie1472 said:
Have you tried the ruu in zip format??? .
Found here
forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
When I try to go into hboot mode I get no change on the screen it stays at the htc logo.
try this then try RUU
http://forum.xda-developers.com/showthread.php?t=843544
il Duce said:
try this then try RUU
http://forum.xda-developers.com/showthread.php?t=843544
Click to expand...
Click to collapse
my doesn't get past htc screen, how would I use that?
gigermunit said:
When I try to go into hboot mode I get no change on the screen it stays at the htc logo.
Click to expand...
Click to collapse
If your not s-off flash darch's eng/spl. Then try the ruu in zip format. Look in hero dev section for darchs method. I posted a working zip on that thread.
Darchs spl s-off
http://forum.xda-developers.com/showthread.php?t=765237
ruu in zip format
http://forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
laie1472 said:
If your not s-off flash darch's eng/spl. Then try the ruu in zip format. Look in hero dev section for darchs method. I posted a working zip on that thread.
Darchs spl s-off
http://forum.xda-developers.com/showthread.php?t=765237
ruu in zip format
http://forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
no recovery to flash a zip.
if you mean something else mind linking me? Ive been searching through xda and ppcgeek along with google since 10am est, it's 3:49pm now.
gigermunit said:
no recovery to flash a zip.
if you mean something else mind linking me? Ive been searching through xda and ppcgeek along with google since 10am est, it's 3:49pm now.
Click to expand...
Click to collapse
I hope you're not making time sensitive demands.....
Try this link and the zip near the end of the thread, if it doesn't work try the other link I put up earlier.
http://forum.xda-developers.com/showthread.php?t=958968
EDIT: are you s-off, and if so which method did you use?
il Duce said:
I hope you're not making time sensitive demands.....
Try this link and the zip near the end of the thread, if it doesn't work try the other link I put up earlier.
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I'm not and I am having the exact same issues as
http://forum.xda-developers.com/showthread.php?t=788894
I called sprint and was told since I have had the phone for less than a year I can get a free one from htc just need to go to sprint and let them fiddle with it, if they can fix it then it's a free repair if they can't its a free replacement, I am supposing no traces of rooting can even be seen the phone literally has nothing on it, it nuked itself while I went to take a leak, left it on updating 10 applications, backing up the others and flashing my cw3 recovery, after that it was acting up, kept booting to recovery than after flashing things and formatting it nuked everything else recovery and all.
gigermunit said:
I'm not and I am having the exact same issues as
http://forum.xda-developers.com/showthread.php?t=788894
I called sprint and was told since I have had the phone for less than a year I can get a free one from htc just need to go to sprint and let them fiddle with it, if they can fix it then it's a free repair if they can't its a free replacement, I am supposing no traces of rooting can even be seen the phone literally has nothing on it, it nuked itself while I went to take a leak, left it on updating 10 applications, backing up the others and flashing my cw3 recovery, after that it was acting up, kept booting to recovery than after flashing things and formatting it nuked everything else recovery and all.
Click to expand...
Click to collapse
Well, maybe you have a brick. Cool you have the warranty. And if xda can't find a way to fix it, sprint almost surely cannot, lol. I would say get the new one sent to you, that way when you send the old one back it will be too late for them to tell at you - IF they figure it out.
sent from a series of tubes.
il Duce said:
Well, maybe you have a brick. Cool you have the warranty. And if xda can't find a way to fix it, sprint almost surely cannot, lol. I would say get the new one sent to you, that way when you send the old one back it will be too late for them to tell at you - IF they figure it out.
sent from a series of tubes.
Click to expand...
Click to collapse
Yeah, I may not post alot but that's due to college and church, otherwise I would be making guides and helping out in Q&A instead of asking for it now haha, I tried so many things and nothing worked so I concluded a brick, sadly I'll never know why my phone randomly nuked itself, I didn't do anything I normally don't was so odd.
Update: they couldn't fix it so they are sending me a new phone.
I just bought a used Hero as a temporary phone and I'm trying to get off the stock rom. I rooted the phone and flashed a MIUI rom. It got stuck on the splash screen during boot. Not feeling like dealing with it, I just ended up RUUing it. Then I rerooted it and tried another rom...same deal. Now I back to stock again. Any thoughts on how to fix this?
Thanks
You didn't firate anything, did you?
Try manualy flashing the boot.img in the rom from fastboot. Sometimes thats the problem.
Regards
Sent from my Galaxy Nexus using XDA
oohaylima said:
You didn't firate anything, did you?
Click to expand...
Click to collapse
Urban dictionary tells me that means fake pirating...? If that's the case, no. I haven't even installed anything let alone log into my google account.
EDIT: I'm guessing you meant firerat. Nope, I haven't messed with anything.
flakesdk said:
Try manualy flashing the boot.img in the rom from fastboot. Sometimes thats the problem.
Regards
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Good idea. I'd need abd for that though to run the commands right? I'm really trying hard to avoid installing it on my computer.
Why ?? If your going to be modding your phone s-off,eng-bootloader & adb are all tools you will definitely need. If not then you may have a few headaches down the line if something goes wrong.
#Root-Hack_Mod*Always\
laie1472 said:
Why ?? If your going to be modding your phone s-off,eng-bootloader & adb are all tools you will definitely need. If not then you may have a few headaches down the line if something goes wrong.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I won't be doing anything beyond flashing a custom rom.
I just dug up my Hero. It had CM6 previously. I tried flashing an updated ROM and it does not get past the HTC logo. I tried 4 different ROMs. Using CMW recovery. Wipe/Format all...and nothing.
Yeah I'm completely out of ideas. I may just have to suck it up and install adb.
Which version of CWM are you running? I've used 2.5.0.1 for all of my ROMs and never had a problem. I should have the zip to flash through recovery and the HERCIMG flashable through HBOOT if you wanna try.
Sent from my PC36100 using xda premium
Adb is a breeze to install. Takes less than 20 min. Pm me if and when you wanna set it up, and believe me when I say you will not regret it. Adb makes modding your phone a little easier.
#Root-Hack_Mod*Always\
scl23enn4m3 said:
Yeah I'm completely out of ideas. I may just have to suck it up and install adb.
Click to expand...
Click to collapse
What radio do you have? I remember people having issues when using the older radio (.27) instead of the newer (.29). Then again, it might not make a difference at all either. Just a thought.
i second drunkpilots radio idea, thats what gave me a headache for an hour the other night wondering why my cm7 wouldnt boot, updated to newest sprint radio and bam booted right up
Alright I just upgraded my radio. What's the best/easiest way to root it from here since I'm back to stock now?
HTC One
Sprint
HBOOT 1.55
S [ON]
OS 3.04.651.2
Problem: Friend thought it would be cool to put Android Revolution HD on my HTC One since he did it on his and wanted to surprise me with it...
Long story short he did, and now I have a soft bricked device. I've tried pushing a stock and a custom ROM through ADB sideload and I end up with a phone that acts like it is going to work, gets to the lock screen and freezes. It has no service but that's irrelevant because I can't even get past the lock screen. I can however use my volume key to raise and lower volume.
Can anyone get me past this or am I screwed till a new RUU comes out/way to get S [OFF] after hitting 1.55?
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
bigdaddy619 said:
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
Click to expand...
Click to collapse
Thanks so much for the reply, I'll give it a shot. I'm desperate right now willing to try anything.
Also forgot to mention the boot animation does fine, the phone acts like it's going to work fine then it just plain freezes where it would normally give you the "sign into google account" and name your phone. So I'm not sure what's missing if anything, if anyone has solved this and is willing to help I would greatly appreciate it.
Your partitions are messed up because he flashed a GSM rom on your CDMA device
bigdaddy619 said:
Your partitions are messed up because he flashed a GSM rom on your CDMA device
Click to expand...
Click to collapse
Yeah, exactly. Is there any way I can go about fixing that? I'm checking out that guys thread, and it sounds promising... but I can't figure out how to get my drive to sync with my PC to transfer it to TWRP to install it. I'm going to try to ADB it but I doubt that will work. Starting to lose hope at the moment lol but trying to stay optimistic.
Asosaki said:
Yeah, exactly. Is there any way I can go about fixing that? I'm checking out that guys thread, and it sounds promising... but I can't figure out how to get my drive to sync with my PC to transfer it to TWRP to install it. I'm going to try to ADB it but I doubt that will work. Starting to lose hope at the moment lol but trying to stay optimistic.
Click to expand...
Click to collapse
Only way to fix the partitions is to run an RUU which we don't have.
Is your phone seen by your PC when it's plugged in and booted to the rom? I know it doesn't boot correctly but maybe you can move the file to your phone.
You could also try adb push nameoffile.zip /sdcard/ most likely won't work because of the partitions
Format with TWRP first to get partitions clean, then adb push Rom/sideload
Sent from my HTCONE using XDA Premium 4 mobile app
I'm pretty sure the radio partition get overwritten as well so I would say format sd in twrp, flash a radio in fastboot then sideload your Rom and flash it
Sent from my HTCONE using XDA Premium 4 mobile app
18th.abn said:
I'm pretty sure the radio partition get overwritten as well so I would say format sd in twrp, flash a radio in fastboot then sideload your Rom and flash it
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the replies guys, going to try that now. It feels like entire ROM would work fine and there was just "something missing" from my phone. It may very well be a radio. I know something got wiped that shouldn't have because I had to do partition reset due to... well I'm sure you know. Also had to side load TWRP. Learning experience for me, not frustrated at least I'm getting knowledge to help others with it if I can solve it on my own.
Okay so, reporting back that FIXED my no service issue, and it's bringing up updates in the notification bar, only problem is I can't use the touch interface. I don't think my phone is broken, I think it just lacks everything that makes it a smartphone.
Anyone have an idea as to what I can flash to get it back up and running? It feels like it's missing touch interface, and whatever is needed to initiate the "factory" setup screens. Shouldn't the ROM include all of that? I put Viper ROM 1 on there. Progress was made, but it's missing something lol.
The radio also stopped it from resetting and turning itself off after 30 seconds like it was doing previously. Is there a flash-able touch interface I can throw on it? Heh...
Also noticed after it was plugged in for a couple of minutes it's detected by my PC now so I don't need to side-load anymore. Not that it was hard to, just a step forward I think. Just need to figure out what's missing from the boot screen and what I need to put on it to be able to use the touch screen. Any ideas?
Asosaki said:
Okay so, reporting back that FIXED my no service issue, and it's bringing up updates in the notification bar, only problem is I can't use the touch interface. I don't think my phone is broken, I think it just lacks everything that makes it a smartphone.
Anyone have an idea as to what I can flash to get it back up and running? It feels like it's missing touch interface, and whatever is needed to initiate the "factory" setup screens. Shouldn't the ROM include all of that? I put Viper ROM 1 on there. Progress was made, but it's missing something lol.
The radio also stopped it from resetting and turning itself off after 30 seconds like it was doing previously. Is there a flash-able touch interface I can throw on it? Heh...
Also noticed after it was plugged in for a couple of minutes it's detected by my PC now so I don't need to side-load anymore. Not that it was hard to, just a step forward I think. Just need to figure out what's missing from the boot screen and what I need to put on it to be able to use the touch screen. Any ideas?
Click to expand...
Click to collapse
Looks like you just need to flash a 4.3 rom
bigdaddy619 said:
Looks like you just need to flash a 4.3 rom
Click to expand...
Click to collapse
Really? That's the only problem you think? I'mma try that out I'll give you a message as soon as I do. Thanks again.
Also, is there any way I can get a MOD or someone to un-lock my account? This 5 minute wait is for the birds lol I got hardware on the line here :angel: Need all the posts/help I can get hahaha.
bigdaddy619 said:
Looks like you just need to flash a 4.3 rom
Click to expand...
Click to collapse
You are the MAN my phone's fixed now. BoO YaH. Now I can go beat my buddy up with peace of mind knowing my phone is in good working order.
Now running Stock with goodies, guess the other custom ROMs I put on it were just lacking 4.3 stability. You rock broski.
Asosaki said:
guess the other custom ROMs I put on it were just lacking 4.3 stability.
Click to expand...
Click to collapse
New firmware had updated touch drivers. That's why your touch screen wasn't working right.
bigdaddy619 said:
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
Click to expand...
Click to collapse
Your the man bigdaddy, good to know there is a glimmer of hope for those with 4.3 and s-on.
Sent from my HTCONE using xda app-developers app
Since you're on the newest firmware you can only flash 4.3 sprint roms..the touchscreen firmware has been updated. You can't downgrade or s-off because you're on hboot 1.55. Just sideload a 4.3 Rom and you'll be up and running fine
Sent from my HTCONE using XDA Premium 4 mobile app