So yesterday I tried flashing this tweak on my HTC One. Sadly it crashed my phone somehow and I ended up wiping the phone, and now it's telling me each time I reboot that it has no OS. I decided to try to flash stock Sense 5, but I realized I don't have a backup or anything. I've been trying to use Android File Transfer to make the OS available in recovery. Sadly it seems when it's on recovery I can't use file transferring. I would turn it on, but it won't boot any further than the "HTC Quietly Brilliant" loading screen.
Anyone have any ways I can get the OS back on the phone? Please help!
parkerfriend said:
So yesterday I tried flashing this tweak on my HTC One. Sadly it crashed my phone somehow and I ended up wiping the phone, and now it's telling me each time I reboot that it has no OS. I decided to try to flash stock Sense 5, but I realized I don't have a backup or anything. I've been trying to use Android File Transfer to make the OS available in recovery. Sadly it seems when it's on recovery I can't use file transferring. I would turn it on, but it won't boot any further than the "HTC Quietly Brilliant" loading screen.
Anyone have any ways I can get the OS back on the phone? Please help!
Click to expand...
Click to collapse
Are you using TWRP? Cause I've been wondering the same thing lately.
Sent from my HTC One using xda app-developers app
whitetiger_0603 said:
Are you using TWRP? Cause I've been wondering the same thing lately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So I figured out how to fix it- using adb I sent stock Sense back to my phone and flashed it, worked like a charm.
parkerfriend said:
So I figured out how to fix it- using adb I sent stock Sense back to my phone and flashed it, worked like a charm.
Click to expand...
Click to collapse
What command did you use?
Sent from my HTC One using xda app-developers app
whitetiger_0603 said:
What command did you use?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Sent from my HTC One
GermanGuy said:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Sent from my HTC One
Click to expand...
Click to collapse
Haha thanks. I was dumb and didn't think of the command used in SuperCID until right before you posted this.
Sent from my HTC One using xda app-developers app
Related
I havent used my aria in almost a year now but decided to pull it out as a backup phone. I was rooted at one point but i think i did and ota update while i was rooted. Since I quit using the phone I formatted the sd card for it. I went to use the phone and it just boots up into recovery. I try installing Cm7 and a few other roms and they dont work. CM7 just sits on their loading screen the whole time. I looked at the HBoot screen and it says S-on. I cannot figure out how to get passed any of this at all. Is my phone pretty much done?
1) Use Revolutionary to obtain S-OFF. Follow all the directions from the site.
2) Use this method to install and/or update Clockworkmod Recovery. The latest version of CWM for Aria is here, though older versions should work fine also.
3) Flash ROM.
I know how to make it have s-off but those are applications for the computer and my phone wont connect to the computer since it only boots to recovery.
Sent from my Desire HD using XDA App
It looks like my usb port isn't working. My computer says it malfunctioned.
After the tenth time installing cm7 it started. I went back into recovery to install the Google apps but then it wouldn't start again. And now after another attempt at re installing it doesn't work.
Sent from my Desire HD using XDA App
What version of CWM do you have right now? Also, what is your HBOOT version? (if you can get to that screen)
Hboot says 0.57? Not sure if that's right and cwm is 2.5.0.1
Sent from my Desire HD using XDA App
Try installing the official AT&T 2.2.2 ROM using the alternative method that I've explained in this post: http://forum.xda-developers.com/showpost.php?p=18541475&postcount=145 . This method does not require using the USB connection at all so it might solve your problem.
It will overwrite CWM, but you can go through the S-OFF process to install CWM afterward.
The phone keeps aborting the installation of the Android 2.2.
Sent from my Desire HD using XDA App
pmariolo said:
The phone keeps aborting the installation of the Android 2.2.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Try using the RUU directly (while in fastboot).
pmariolo said:
The phone keeps aborting the installation of the Android 2.2.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Is there an error message?
Error message is can't open /sdcard/HTC_ aria....update.zip (bad)
Sent from my Desire HD using XDA App
Also I can't do anything in fastboot unless I'm doing it wrong.
Sent from my Desire HD using XDA App
pmariolo said:
Error message is can't open /sdcard/HTC_ aria....update.zip (bad)
Click to expand...
Click to collapse
You aren't following the directions from the post I linked to, please re-read them. You don't install the update through Clockworkmod.
Try this method as well as the method Theonew is telling you to do. One of them should work.
pmariolo said:
Also I can't do anything in fastboot unless I'm doing it wrong.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Download the RUU from here: http://www.htc.com/us/support/aria-att/downloads/ (link is under "HTC Aria ™ for AT&T Android 2.2 ROM Update | 02.25.2011"). After that, boot your device into fastboot, connect it to your PC and run the RUU.
Ohhh I got it. I'll try it in.a couple hours. I understand what it was saying I just for some reason wasn't doing it right.
Sent from my Desire HD using XDA App
Hey guys thanks a lot it worked!
I have a MoPho with unlocked bootloader running 2.3.4 and everytime I try to flash back to my saved stock backup from any custom rom I keep getting an "error while flashing boot image" I tried to do an advanced restore and picked the files one at a time but I keep getting the same result. Can someone please help, thank you in advance...
Sent from my MB855 using xda app-developers app
Are you restoring using the same utility you did the nandroid backup with? Joker recovery vs twrp vs cwm recovery
Sent from my MB855 using Tapatalk 2
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Are you using a working recovery? Jokers? Twrp? Photon3? Or the ROM manager one? ROM manager version does not work.
Sent from my MB853 using XDA
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
as mentioned previously the ROM Manager one DOES NOT WORK. 5.0.2.8 DOES NOT WORK! you NEED to user Jokers, TWRP or the 5.0.2.7-photon3 recoveries ONLY. you can find the working recoveries on my site. choose which one suits you best! don't use Jokers V4 because it won't flash google apps properly.
http://www.motosunfire.com/clockworkmod-recovery/
Ok thanks a lot, I will try the two you just recommended...
Sent from my MB855 using xda app-developers app
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
na7q said:
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
Click to expand...
Click to collapse
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Stray2thaB said:
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
Click to expand...
Click to collapse
Stray2thaB said:
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Click to expand...
Click to collapse
hmmm... CDMA user? or GSM? i remember that bug being around in the very early builds of CM7. are you on the latest nightly or stable release?
i might also recommend changing some build prop info (which could be causing this?) to make sure it tells the radio to operate in the correct mode. gsm or cdma. if you look for ro.telophony.default_network=? the ? should be a 4 for CDMA or a 7 for GSM. change to your liking. then reboot. this was an issue in CM9 for the longest time and this is how it was resolved. it's possible it could be the same for CM7.
another option is to of course start over. wipe the cache,data,system partitions, possibly even twice. flash cm7. twice to be safe. then gapps. twice to be safe. then give it another shot.
other than that it might be a bad download or a bad build. so try another if it doesn't work. hope this helps you!
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Stray2thaB said:
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
there will never be any officials releases unless somehow Motorola decides they want to give us drivers/source for ICS or JB. which is never. unless we get a leak.
I had some issues with various roms for unknown reasons, so I kept trying out new roms. Well the problem persisted, and as I was attempting to flash a new Rom, recovery just kind of failed. Whenever I attempt to enter recovery, a titled triangle with and exclamation mark and a droid figure pop up and I have to do a battery wipe. My phone still starts and runs, but I'm currently stuck on a problematic rom with no way of getting to recovery. I'm fairly new to all of this so I have no idea what's happening and I'm ultimately scared of attempting anything and messing up more. So any and all suggestions are beyond welcome.
FoxMarsden said:
I had some issues with various roms for unknown reasons, so I kept trying out new roms. Well the problem persisted, and as I was attempting to flash a new Rom, recovery just kind of failed. Whenever I attempt to enter recovery, a titled triangle with and exclamation mark and a droid figure pop up and I have to do a battery wipe. My phone still starts and runs, but I'm currently stuck on a problematic rom with no way of getting to recovery. I'm fairly new to all of this so I have no idea what's happening and I'm ultimately scared of attempting anything and messing up more. So any and all suggestions are beyond welcome.
Click to expand...
Click to collapse
Have you tried reinstalling CWM?? Or maybe using another recovery....
I had that to after updating to 236 first time had to install recovery couple times to get it to work.
Sent from my HTC One X+ using xda premium
Complication in my situation : I don't have a computer. I can get to one with the needed programs on it, but are you sure this will fix it?
I had that to after updating to 236 first time had to install recovery couple times to get it to work.<br />
<br />
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
So just install cwm multiple times..? Like install it, turn phone on, then install again if problem persists or isn't fixed immediately?
You're looking for some magical recipe that will 100% surely fix your phone. There isn't one. You will just have to play and be creative. You can report back here for more advice if needed.
FoxMarsden said:
So just install cwm multiple times..? Like install it, turn phone on, then install again if problem persists or isn't fixed immediately?
Click to expand...
Click to collapse
Like what ravilov mentioned, its more of a trial and error process and not a 100% quick fix. Not having a computer will make things much more difficult.
I'm not looking for a magic easy route, (though it'd be nice if there was one), I'm just asking for literally any advice on the situation.
Use the android sdk 'fastboot' command to push recovery to the device via USB. This should solve your issue with a borked recovery partition.
Sent from my MB860 using Tapatalk 2
Try ROM manager and install cwm with it free on market install it a few times it will work
Sent from my HTC One X+ using xda premium
markwoo said:
Try ROM manager and install cwm with it free on market install it a few times it will work
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
How do I install cwm on it? I have an idea but I don't want to mess up anymore than I already have
FoxMarsden said:
How do I install cwm on it? I have an idea but I don't want to mess up anymore than I already have
Click to expand...
Click to collapse
In rom manager just follow the prompts.
Sent from my MB860 using Tapatalk 2
jjwatmyself said:
In rom manager just follow the prompts.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Should I do Clockwork Mod Touch, or just cwm recovery?
FoxMarsden said:
Should I do Clockwork Mod Touch, or just cwm recovery?
Click to expand...
Click to collapse
No need for touch. If you ever damage your screen, touch recovery will make it impossible to use. Once you've flashed it with rom manager, you can download th3bill's recovery for Atrix and install over the top of it.
Sent from my MB860 using Tapatalk 2
Thanks man, I got it all fixed yesterday and everything is running fine. Thanks for all your help
I am running the Cyanogenmod 11 Nightly from the 11th, and also running crpalmers kernel 5.4.2. I had ART turned on, and was running Gravitybox Xposed Modules. While I was using the phone, while on the charger, it randomly rebooted, and showed the splash screen. The phone was just about dead when it was being used on the charger. While on the charger, the phone repeatedly shows the splash screen, followed by a black screen, and then a vibration like it had just been powered on, and shows the splash screen. This cycles while plugged into the computer. When first plugged into the computer, the computer (Windows 7) makes noises like it is connected and then removed. The phone is not recognized in fastboot or adb. I was able to access the bootloader menu by holding the power and volume down keys. Usually I can not navigate through it by using the volume keys, and it reverts back to the bootloop within 30 seconds. I don't know what is causing this problem, so I tried to give as much info as possible. Any help is appreciated. Thank you in advance.
Hope someone can get you sorted out. Never experienced that particular issue.
Sent from my HTC6435LVW using Tapatalk
Can you get to your recovery or factory reset in the bootload
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
Can you get to your recovery or factory reset in the bootload
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When I access the bootloader I am unable to select anything before the phone returns to the bootloop. I can't get to recovery or factory reset. I also believe that running an RUU would be unsuccessful because the phone is in neither ADB and Fastboot mode.
zach p said:
When I access the bootloader I am unable to select anything before the phone returns to the bootloop. I can't get to recovery or factory reset. I also believe that running an RUU would be unsuccessful because the phone is in neither ADB and Fastboot mode.
Click to expand...
Click to collapse
I'd just get a replacement then.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
I'd just get a replacement then.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to stop the bootloop somehow. Must have been a combination of attempting to charge it all day and the constant attempts to reboot into recovery. Now I'm in recovery, and there is no partitions. I am unable to factory reset or format data of any kind. I had pushed a ROM to the device in the recovery. I was unable to flash this rom, or the stock splash screen.
zach p said:
I was able to stop the bootloop somehow. Must have been a combination of attempting to charge it all day and the constant attempts to reboot into recovery. Now I'm in recovery, and there is no partitions. I am unable to factory reset or format data of any kind. I had pushed a ROM to the device in the recovery. I was unable to flash this rom, or the stock splash screen.
Click to expand...
Click to collapse
Can you use adv and fastboot. If so I'm going to send you a link to 3.06 ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
Can you use adv and fastboot. If so I'm going to send you a link to 3.06 ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fastboot and ADB are working properly, and that would be great!
zach p said:
Fastboot and ADB are working properly, and that would be great!
Click to expand...
Click to collapse
just remember to backup everything u want to keep this will delete everything and put your pho e back to the current 3.06 it will also install latest radio and hboot so it might lock your bootloader but all you'll half to do is run rumrunner.
http://forum.xda-developers.com/showthread.php?t=2570548
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
just remember to backup everything u want to keep this will delete everything and put your pho e back to the current 3.06 it will also install latest radio and hboot so it might lock your bootloader but all you'll half to do is run rumrunner.
http://forum.xda-developers.com/showthread.php?t=2570548
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much you have been a great help
Let me know if it fails. You half to b s off to flash it threw fastboot.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
Let me know if it fails. You half to b s off to flash it threw fastboot.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It failed at first, but I tried using jailbird's workaround mentioned in the thread, and it worked like a charm. Thank you again for all your help!
zach p said:
It failed at first, but I tried using jailbird's workaround mentioned in the thread, and it worked like a charm. Thank you again for all your help!
Click to expand...
Click to collapse
Now you may half to rerun runrummer before anything. Then install custom recovery.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
So i had a similar problem last evening, left phone over night in bootloop off charger till it died and woke up this morning reconnected bootloop continued for 10 mins then phone booted up, relocked bootloader, flashed stock ruu, unlocked bootloader and installed nusense working fine so far.
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Extract the boot.img from the ROM zip file, flash ROM, reboot into bootloader and start Fastboot, then flash boot.img via fastboot on a PC, should clear it up...
In the future I would recommend going S-OFF via rumrunner, no more need to worry about flashing boot partitions separately ever again.
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, your good.
Sent from my Nexus 4 using Tapatalk
Just made a backup in TWRP and rebooted and all is well, you're awesome man. Thanks again
Sent from my Rezound on Tachyon using XDA Premium 4 mobile app