ok so i had my hero on the stock fresh rom from his kitchen and i decided to try out the new dc2.08.1 to see if there were still bugs that made me not want to use the older 2.1 roms. after flashing it no audio worked at all not even when talking on the phone. so i did a nandroid restore of a backup i made right before flashing DC. everything seemed to be back to normal but then i realized my audio is still not working but in calls it is working. i figured the restore messed up so i tried again and it didnt work for some reason. then i downloaded gumbo1.5c from my phone and flashed that and everything was perfect once again. the whole day my phone was flawless until last night at 2am i went to set an alarm clock and for some reason that triggered the audio to go off again. so i restarted my phone and figured it might fix itself but it didnt and i already deleted gumbo off my sd. i downloaded it again and then my phone seemed to start getting sluggish and finally completely froze after a while. i removed the battery and tried to turn it back on but it got stuck at the htc screen. then i tried to get into recovery but that doesnt work either now... fastboot does boot up and i tried to ruu from it but when the ruu is rebooting to bootloader my phone just stays off and doesnt reboot.. i did notice on fastboot it says "touch panel-fail".
before installing or restoring any roms i did wipe everything does anyone know what i have to do to restore my hero or am i just completely screwed D:
do a search for ruu error 110. try doing what it says and you should be able to get back to stock, and either take your phone in or flash again.
alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response
dylan6879 said:
alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response
Click to expand...
Click to collapse
What's he's saying is that if your phone has hardware issues, then you need to do the RUU to put it back to stock or sprint might not fix it under warranty.
I agree with the above, sounds like a hardware issue although the timing of the issue with a flash sounds strange.
yea i thought it might be a hardware issue but it just seems odd how it happened after flashing 2.1 and then reverting to 1.5. I want to bring it back to sprint but dont want to get screwed over because of it being rooted. i want to ruu but the phone just seems to be dead and doesnt want to do anything besides fastboot and show the htc screen
Some people have problems with the RUU, but the steps to fix the Error 110 after RUU'ing, should work anytime regardless if you RUUed or not. Your recovery could have gotten deleted. Try flashing it from fastboot. There are directions in this forum on how to do it from fastboot.
ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.
dylan6879 said:
ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=674788
EVERYTHING, including the 110 fix is in that post.
i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot
dylan6879 said:
i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot
Click to expand...
Click to collapse
Did you try following his procedure? it should resolve your issue.
otherwise: fastboot flash recovery recoveryimagefilename
Pro tip: in a windows command prompt if you go to your androidsdk\tools directory and type 'fastboot' it will give you all the options.
alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".
dylan6879 said:
alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".
Click to expand...
Click to collapse
You don't need the < > in there.
fastboot update update.zip should work.
thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
dylan6879 said:
thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
Click to expand...
Click to collapse
What exactly are you trying to flash? What's the filename, and what's it for?
If this is a ROM you don't want update.
If it's a recovery image:
fastboot flash recovery recoveryimagename.zip
oh yeah i was trying to flash a rom. i thought u could do that from there. where should i have the recovery img before i flash it. and is it possible to flash a rom through here?
ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".
dylan6879 said:
ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".
Click to expand...
Click to collapse
It's probably possible to flash a rom through fastboot, but I've never done it.
What recovery image are you using? And what is the exact name of the recovery image file? Where exactly did you put the recovery image file?
i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried
dylan6879 said:
i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried
Click to expand...
Click to collapse
Never used it, and 1.5.2 is old. I suggest downloading AmonRA's 1.6.2
You can't use zip files with fastboot...it wants the actual image (at least in this case, because those zip files aren't updates, they're just zip files).
So you should put the 152.img in the same directory as fastboot (Android-sdk-windows\tools)
Then you should do: fastboot flash recovery 1.5.2.img
What happens when you do that?
i tried flashing the 1.6.2.img and got the same result it says "sending 'recovery' <3720 KB>... FAILED <remote: not allow>".
Related
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
halr9000 said:
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
Click to expand...
Click to collapse
Tried that, already... That method only works for the stock T-Mobile G1's which have a different SPL. The Dev G1's come with engineering SPL and I have no idea how to flash the .nbh image from that. All it does I think is enable Fastboot, I cant get it to do anything else.
This fails?
fastboot flash recovery recovery.img
Nope... No luck, it says:
sending 'recovery' <4456kb>.... OKAY
writing 'recovery' <4456kb>.... OKAY
and then I reboot using "fastboot reboot", wait till the homescreen loads, and then go back into recovery and it still shoes the the triangle and the !.....
Bump...
Anyone?? Right now we just have a reallly expensive paper-weight in our hands ANY help/thoughts/comments would be very appreciated...
This thread is meaningless since there is NO SUCH THING as a "DEV G1".
alilbitanuthin said:
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
Click to expand...
Click to collapse
Pretty sure there is...
http://developer.htc.com/adp.html
Bump...
anyone?
alilbitanuthin said:
Pretty sure there is...
http://developer.htc.com/adp.html
Click to expand...
Click to collapse
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
lbcoder said:
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
Click to expand...
Click to collapse
lol, no need to nitpick, about the name no less. Thats the least of my worries
As long as you get the message across...
jackslim said:
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
Click to expand...
Click to collapse
That maybe it I'll give it a try as soon as I get back home. Thanks a lot for the help!!
Thanks a lot jackslim, finally got it to work!
Ok, I know I'm going to catch all kinds of hell probably for posting this. But, I'm stuck. This is the first question I have asked on this forum, and have literally spent days on end searching, and trying new things. What happened is I think I tried flashing a GSM rom (the new android revolution 30.0) onto my Sprint HTC One. I just got this phone two weeks ago, and unfortunately upgraded to the 4.3 with the 1.55 hboot. So, S-on. I was using slimbean as my dd, but wanted to give revolution a try. When I dl the rom, it stated for m7wls, so thought I was good. Well, went into a kind of bootloop where it would upgrade android like 41 out of 120, then it would restart. When it finally would boot up, I had about fifteen seconds before it would reboot again. I tried to wipe and restore, but same thing was happening. I read that the partitions may have been screwed up from the gsm to cdma so, I wiped data and everything. I was going to relock and flash an RUU. Then I find out that there isn't one yet for the 4.3. I tried the Guru reset, updating drivers, sideloading, flashing cwm from twrp, pushing and had a rom boot up once, but no service or gapps. In cmd fastboot, my phone is recognized. But, when I use adb, it can't find it.I can get into recovery, and I have the official android 4.3 stock rom on my laptop ready to flash, but just can't get it to the phone. I am a noob, so I am sorry for that, but we all were at one time or another. I researched, tried to learn as much as I could before I took the plunge. I've read thread upon thread here and in other forums trying to find a fix. Everything that I've tried from some of these posts just didn't work for me. I don't know what I'm doing wrong, and I am not sure what you guys would need from me as far as more info. But, I would be grateful if someone could steer me in the right direction. Thanks in advance, and again apologies if I'm not doing things right for you guys. Just trying to learn and do.
C:\Users\Guest\Desktop\Fastboot>fastboot devices
FA38DS904955 fastboot
C:\Users\Guest\Desktop\Fastboot>fastboot flash rom.zip Dev-3.22.1540.1-Stock-Roo
ted-DE-ODEX.zip
target reported max download size of 1526722560 bytes
sending 'rom.zip' (1061169 KB)...
OKAY [ 47.135s]
writing 'rom.zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 169.469s
This is what cmd tells me when I try to flash the rom.
Dev-3.22.1540.1-Stock-Rooted-DE-ODEX.zip
Click to expand...
Click to collapse
Is not a Sprint rom
bigdaddy619 said:
Is not a Sprint rom
Click to expand...
Click to collapse
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
bbjay351 said:
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
Click to expand...
Click to collapse
Installed universal usb drivers, got sideload working. But now after installing the rom it is in bootloop.
Installed slimbean, I can get into the rom, but only for a minute or two. I have no service at all. When I go into about phone phone status it shows unknown network, out of service, unknow phone number etc. How do I get that back up and running? And, how do I get it to stop rebooting after a few minutes? Thank you guys
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Tried sideloading this and fails saying zip file is corrupt.
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
I hate to say it but use the Format Data option within TWRP to format your sdcard the try to sideload
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
Check PM
Get a signed download of the firmware and flash thru fastboot if nothing else.
Sent from my HTCONE using XDA Premium 4 mobile app
Big thanks
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
bbjay351 said:
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
Click to expand...
Click to collapse
Updated steps for below
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
bigdaddy619 said:
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader (not sure if it was needed but...)
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
Click to expand...
Click to collapse
Ok so I am in a similar position with one of my Sprint devices (I have 2 my kids and mine...) Anyway the device is s-off and had gone into TWRP and formated everything in anticipation of loading a new ROM that 4.3 based so wiped everything and then was going to push the rom with ADB... Problem I am having is that ADB doesn't see the device.
Now it shouldn't be a driver issue as I connected my other device to it with no problem and adb sees it fine.
@bigdaddy619.
I followed steps 1-4 except I used the zip for s-off and received no errors so I went back to twrp and attempted to sideload and still won't work.
Thanks for the assistance.
MG
EDIT: Well looks like it was a driver issue, odd since I wasn't having trouble connecting with my other Sprint HTC One but I changed to the Universal Windows ADB Driver listed here in this post. I also updated to the latest Android-SDK and was able to sideload... Thanks all for the info in this thread!
MG
Hi guys. Was just trying to install a 4.4 custom rom on my HTC One using CWM. I got into rrecovery mode and started trying to install the rom but it came up with an error saying it had aborted. I realised I hadn't made a backup so I thought I best do it in case anything goes wrong. I tried doing that and rebooting the phone. Now the HTC logo flashes on screen before flashing off and then the phone puts me back in recovery. Have I bricked this phone? If anyone can help me I can answer any more necessary questions.
krisdeaco said:
Hi guys. Was just trying to install a 4.4 custom rom on my HTC One using CWM. I got into rrecovery mode and started trying to install the rom but it came up with an error saying it had aborted. I realised I hadn't made a backup so I thought I best do it in case anything goes wrong. I tried doing that and rebooting the phone. Now the HTC logo flashes on screen before flashing off and then the phone puts me back in recovery. Have I bricked this phone? If anyone can help me I can answer any more necessary questions.
Click to expand...
Click to collapse
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and install the ROM again.
nkk71 said:
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and install the ROM again.
Click to expand...
Click to collapse
Sorrry if I seem like a complete fool but how to I flash the recovery image. I'm in the fastboot usb menu now but there doesn't appear to be any option to flash.
krisdeaco said:
Sorrry if I seem like a complete fool but how to I flash the recovery image. I'm in the fastboot usb menu now but there doesn't appear to be any option to flash.
Click to expand...
Click to collapse
from you PC
open a command prompt, go to the folder where adb is (also put the downloaded recovery there), then on your PC, type commands in bold above.
nkk71 said:
from you PC
open a command prompt, go to the folder where adb is (also put the downloaded recovery there), then on your PC, type commands in bold above.
Click to expand...
Click to collapse
Again, rreally sorry. Where will I find ADB? Where would it typically be?
EDIT: I've downloaded minimal ADB and Fastboot and out the recovery image in there. I've tried typing in the top command but had no luck. A little more help, please? Thank you for your help so far by the way
krisdeaco said:
Again, rreally sorry. Where will I find ADB? Where would it typically be?
Click to expand...
Click to collapse
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
nkk71 said:
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
Click to expand...
Click to collapse
Ah yes thanks. I've found it all and put it where you said. I've tried to flashing it but I'm getting the message:
"unknown partition 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
error:cannot deterrmine image filename for 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
krisdeaco said:
Ah yes thanks. I've found it all and put it where you said. I've tried to flashing it but I'm getting the message:
"unknown partition 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
error:cannot deterrmine image filename for 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
Click to expand...
Click to collapse
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
please be careful with things like these, you don't want to mess up your phone, reading and staying calm, not rushing things, IS A MUST!!
nkk71 said:
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
Click to expand...
Click to collapse
nkk71 said:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
please be careful with things like these, you don't want to mess up your phone, reading and staying calm, not rushing things, IS A MUST!!
Click to expand...
Click to collapse
Sorry I'm just panicking an awful lot. I'm a bit calmer now though so I'll crack on. I've got TWRP back up and I've tried to install the ROM but it keeps saying failed. Is therre any way to make my phone available to transfer to so I can try a different ROM?
EDIT: It seems I did make a backup with TWRP, I'm assuming that wouldn't show up on CWM? That seems to be working so I'll count myself lucky. I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
By the way THANK YOU SO MUCH for everything. I completely panicked and I would never have figured any of this out without your help. Thank you.
krisdeaco said:
Sorry I'm just panicking an awful lot. I'm a bit calmer now though so I'll crack on. I've got TWRP back up and I've tried to install the ROM but it keeps saying failed. Is therre any way to make my phone available to transfer to so I can try a different ROM?
Click to expand...
Click to collapse
yes plenty, now please go get a glass of water and I'll post back in a minute, you need to relax, we'll have your phone up and running soon.
Which ROM would you like to have? post, then get that water/coffee/beer/scotch whatever makes you calm down :laugh:
krisdeaco said:
EDIT: It seems I did make a backup with TWRP, I'm assuming that wouldn't show up on CWM? That seems to be working so I'll count myself lucky. I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
Click to expand...
Click to collapse
Unfortunately, TWRP and CWM backups aren't interchangeable but you can always flash back the proper recovery for the backup, and restore.
krisdeaco said:
I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
Click to expand...
Click to collapse
Details please , GPE or Sense, any one in particular, best post a link to the one you'd like to have.
krisdeaco said:
By the way THANK YOU SO MUCH for everything. I completely panicked and I would never have figured any of this out without your help. Thank you.
Click to expand...
Click to collapse
Feel free to hit the thanks button
Anyone have an official HTC first/Myst firmware they are willing to post. I recently lost my system image and need another rom file to get it back working.
Joshxlr8 said:
Anyone have an official HTC first/Myst firmware they are willing to post. I recently lost my system image and need another rom file to get it back working.
Click to expand...
Click to collapse
i dont have a rom file but i have a twrp recovery?
its somewhere around here on the forums and if you need it just click the link and ill let you download it.
its pretty much stock rom with some mods (4.1.2 clock and bloatware missing).
Right I saw that and its a .win file. I'll just try downloading it and sending it to my phone.
Edit: Hmm. After I tried pushing it to the phone, the file failed to install. The prompt reads something like "Checking for MD5 file" "No MD5 file found" and "Zip signature verification failed"
Alright, so I tried something else. After I couldnt download the files that you sent I tried to install another rom made for the HTC First. It's called the JmzJBSenseMyst_v3. All seemed to go well, everything was installed and I went through the install process very easily. But, the phone is now stuck in boot-loop. As in, I cant get into my system because it only loads into TWRP.
You can use RUU to restore stock firmware. And relock bootloader to solve boot-loop state.
I've tried the RUU... any more tips?
Hulo_ said:
You can use RUU to restore stock firmware. And relock bootloader to solve boot-loop state.
Click to expand...
Click to collapse
My First has been stuck for months. I've tried everything.
It's not visible to ADB or Fastboot or the RUU prog.
Please someone, anyone, PLEAAAASE help.
restore to stock rom
relock bootloader,install stock recovery and run RUU
Edit:
no need to flash stock recovery,just revert to stock RUU
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
CyrodiilSavior said:
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
Click to expand...
Click to collapse
First, you need to Relock your bootloader, Unroot, then S-ON your devide , Then flash RUU rom via Command in PC ( fastboot , ADB )
Finaly : if you want Flash a custom Rom , you should unlock bootloader , Root your HTC ONE , Flash recovery and then Flash custom Rom
Hope this can help you , sorry for my bad in english , I'm VietNamese
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
CyrodiilSavior said:
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
Click to expand...
Click to collapse
Make sure you're running it on a Windows 7 PC.
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
I'm sorry for not being more descriptive, I have a pretty strong background in linux and android but this issue has really stumped me.
CyrodiilSavior said:
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
Click to expand...
Click to collapse
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
StormyNight said:
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
Click to expand...
Click to collapse
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
CyrodiilSavior said:
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
Click to expand...
Click to collapse
Flash the latest radio/baseband founf HERE
BD619 said:
Flash the latest radio/baseband founf HERE
Click to expand...
Click to collapse
I didn't notice this till now but the sdcard is not mounting. I have the ability to mount it in recovery but when booted into system no luck. I am thinking reflashing a new boot.IMG would correct the issue.
Good news, I did an adb push and flashed the radio and that fixed it, I now can connect to sprint and my Sdcard is now mounting.
Thanks so much to everyone for the help. I really appreciate it!