Hi,
I have a Revone S-OFF, and TWRP 2.5.0.0 and just tried flashing to d3rpONE Milestone 2 ROM and then the phone started rebooting when it would load into the OS, so I loaded a backup in TWRP I did before the flash, and that is even giving me a reboot whenever I go into the OS, it will work for a minute then reboot. It looks as if the cell and wifi radios won't activate though. Any help would be appreciate.
I updated the firmwares without updating HBOOT and etc. Should I not have done that? Can i flash a 1.31 ROM instead of trying to RUU? When I tried to it said my ROM version was 1.31 which is not the case, I never did a system update.
Any advice or suggestions would be appreciated. Thanks.
Kyusaku said:
Hi,
I have a Revone S-OFF, and TWRP 2.5.0.0 and just tried flashing to d3rpONE Milestone 2 ROM and then the phone started rebooting when it would load into the OS, so I loaded a backup in TWRP I did before the flash, and that is even giving me a reboot whenever I go into the OS, it will work for a minute then reboot. It looks as if the cell and wifi radios won't activate though. Any help would be appreciate.
I updated the firmwares without updating HBOOT and etc. Should I not have done that? Can i flash a 1.31 ROM instead of trying to RUU? When I tried to it said my ROM version was 1.31 which is not the case, I never did a system update.
Any advice or suggestions would be appreciated. Thanks.
Click to expand...
Click to collapse
What rom did you install before d3rpone?
Same problem!
I've been trying to solve this same issue for two days now. I can install custom roms, but they all reboot when I get into the OS and the radios don't work (no service).
I started on OTA 4.2.2. I'm not sure the first rom I tried was meant for the HTC One M7spr. It was called Android_Revolution_HD-One_20.1.
I tried a few other ones that I could get to work either (like InsertCoin). Eventually, I was able to boot up to a 'stock' like one. That's when the reboots and the new service issue began. Same issue with the Rootbox and Avatar roms as well.
I'm using TWRP to sideload all of these different roms.
Any ideas?
rlsl88 said:
I've been trying to solve this same issue for two days now. I can install custom roms, but they all reboot when I get into the OS and the radios don't work (no service).
I started on OTA 4.2.2. I'm not sure the first rom I tried was meant for the HTC One M7spr. It was called Android_Revolution_HD-One_20.1.
I tried a few other ones that I could get to work either (like InsertCoin). Eventually, I was able to boot up to a 'stock' like one. That's when the reboots and the new service issue began. Same issue with the Rootbox and Avatar roms as well.
I'm using TWRP to sideload all of these different roms.
Any ideas?
Click to expand...
Click to collapse
You flashed a GSM Rom on your Sprint CDMA device.
Now to fix it follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Next time read before you flash!
Sent from my HTCONE using xda app-developers app
MrFixit007 said:
What rom did you install before d3rpone?
Click to expand...
Click to collapse
I was on Stock. No custom ROM before that.
Kyusaku said:
I was on Stock. No custom ROM before that.
Click to expand...
Click to collapse
It seems like you need to install ruu and go back to stock and start over. I'd follow http://forum.xda-developers.com/showthread.php?t=2250904 to get things back up and running again.
MrFixit007 said:
It seems like you need to install ruu and go back to stock and start over. I'd follow http://forum.xda-developers.com/showthread.php?t=2250904 to get things back up and running again.
Click to expand...
Click to collapse
Thanks, the problem with that though is RUU thinks I'm on 1.31, I'm guessing I should use this guide?
http://forum.xda-developers.com/showthread.php?p=44243635
Thanks!
Thank you, that did it. Had to go back to 1.29 then the RUU worked.
That put me on true stock.
I'm guessing if I go S-Off now and make sure I use a CDMA build, I can flash a custom rom now.
MrFixit007 said:
It seems like you need to install ruu and go back to stock and start over. I'd follow http://forum.xda-developers.com/showthread.php?t=2250904 to get things back up and running again.
Click to expand...
Click to collapse
I'm trying to make my phone show up as 1.29 in RUU but I'm getting errors in ADB
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
Kyusaku said:
I'm trying to make my phone show up as 1.29 in RUU but I'm getting errors in ADB
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
Click to expand...
Click to collapse
Might work, try the RUU.
Sent from my HTCONE using xda app-developers app
Kyusaku said:
I'm trying to make my phone show up as 1.29 in RUU but I'm getting errors in ADB
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
Click to expand...
Click to collapse
That is the same result I got on my phone and the RUU worked. You should be good to go.
---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------
rlsl88 said:
Thank you, that did it. Had to go back to 1.29 then the RUU worked.
That put me on true stock.
I'm guessing if I go S-Off now and make sure I use a CDMA build, I can flash a custom rom now.
Click to expand...
Click to collapse
You do not have to go s-off. I didn't. All you need to do once you are back at stock is unlock again and then flash recovery again. then you are ready to flash a CDMA rom. MAKE SURE you only get roms from THIS SPRINT HTC ONE forums.
Hmmm
MrFixit007 said:
That is the same result I got on my phone and the RUU worked. You should be good to go.
---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------
Click to expand...
Click to collapse
Thank for all the help everyone, RUU was indeed successful and I'm back with a working stock device. Now to try this path again, maybe I will avoid trying to update the firmwares for now.
MrFixit007 said:
---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------
You do not have to go s-off. I didn't. All you need to do once you are back at stock is unlock again and then flash recovery again. then you are ready to flash a CDMA rom. MAKE SURE you only get roms from THIS SPRINT HTC ONE forums.
Click to expand...
Click to collapse
Ok, that's good to know. Yea, I won't be making that mistake of using the wrong rom again. I've learned a lot in the last few days.
Can you explain why some roms require S-OFF?
rlsl88 said:
Ok, that's good to know. Yea, I won't be making that mistake of using the wrong rom again. I've learned a lot in the last few days.
Can you explain why some roms require S-OFF?
Click to expand...
Click to collapse
My understanding is that the only reason a rom would require s-off would be because of a radio change, however it is not common to do that at this point from what i understand. I have not seen any HTC One roms that require s-off at this point. Requiring s-off is a relic from days of the OG EVO from what I understand. There are several good links that explain the meaning and nature behind s-off. Look here at Q9.
Related
Bricked Sprint phone. I have 1.31.651.2. S-on. Tried running 1.29 Ruus on my computer and ended up getting error140. I tried flashing a stock rom of htc one sprint, and ended up getting the black screen with the only the bar at the top showing and phone reboots every 30 secs. Been trying to revive the phones for a while now. If any1 can help, anything would be much appreciated.
your not bricked if your phone turns on at all.. if it turns on then u should deff be able to fix it
Follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
tmcgrady said:
Bricked Sprint phone. I have 1.31.651.2. S-on. Tried running 1.29 Ruus on my computer and ended up getting error140. I tried flashing a stock rom of htc one sprint, and ended up getting the black screen with the only the bar at the top showing and phone reboots every 30 secs. Been trying to revive the phones for a while now. If any1 can help, anything would be much appreciated.
Click to expand...
Click to collapse
I had the exact same probelm at one point. I was able to get it fixed following the guide listed around the forum. I'd be happy to help out if you still aren't up and running.
Help
MrFixit007 said:
I had the exact same probelm at one point. I was able to get it fixed following the guide listed around the forum. I'd be happy to help out if you still aren't up and running.
Click to expand...
Click to collapse
Im having the exact same issue and Id love if you are willing to help
MrFixit007 said:
I had the exact same probelm at one point. I was able to get it fixed following the guide listed around the forum. I'd be happy to help out if you still aren't up and running.
Click to expand...
Click to collapse
Could you share with me how you were able too or at least direct me to where you found out how to solve this issue? I've been searching endlessly.
chaley80 said:
Im having the exact same issue and Id love if you are willing to help
Click to expand...
Click to collapse
I'm definately willing and able to help. To do so I need to know the current condition of your phone. what happens when you boot it up? can you get into recovery or just the bootloader?
---------- Post added at 08:14 PM ---------- Previous post was at 08:11 PM ----------
Jim8ean said:
Could you share with me how you were able too or at least direct me to where you found out how to solve this issue? I've been searching endlessly.
Click to expand...
Click to collapse
Yes I can share with you, tell you, or direct you; however, the exact steps depend on what stage your phone is at. What is the phone's current condition? Can you access recovery? What does your phone do when you boot it up?
daeldsir0 said:
Here is the site I found it on.
Click to expand...
Click to collapse
no link was included...
S-off your phone using revone. Then run the ruu.
Sent from my HTCONE using xda app-developers app
Want to revone and go back to RUU 1.29 ..but what if you can't ADB?
I can access fastboot and install ANY recovery but no partitions mount..
This all resulted from installing Android HD Revolution (latest version)
rvelajr said:
Want to revone and go back to RUU 1.29 ..but what if you can't ADB?
I can access fastboot and install ANY recovery but no partitions mount..
This all resulted from installing Android HD Revolution (latest version)
Click to expand...
Click to collapse
You should really start your own thread. Answered this one for you already but here goes.
You flashed a GSM Rom on your Sprint CDMA device.
Now to fix it follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Next time read before you flash!
Sent from my HTCONE using xda app-developers app
MrFixit007 said:
I'm definately willing and able to help. To do so I need to know the current condition of your phone. what happens when you boot it up? can you get into recovery or just the bootloader?
---------- Post added at 08:14 PM ---------- Previous post was at 08:11 PM ----------
Yes I can share with you, tell you, or direct you; however, the exact steps depend on what stage your phone is at. What is the phone's current condition? Can you access recovery? What does your phone do when you boot it up?
Click to expand...
Click to collapse
Yes I can access recovery and im unlocked with 1.31 hboot 1.44 only have a status bar when I boot up and can access the settings.
http://forum.xda-developers.com/showthread.php?p=45457470#post45457470 I'm having further help here.
Jim8ean said:
Yes I can access recovery and im unlocked with 1.31 hboot 1.44 only have a status bar when I boot up and can access the settings.
http://forum.xda-developers.com/showthread.php?p=45457470#post45457470 I'm having further help here.
Click to expand...
Click to collapse
Jim8ean, see response at http://forum.xda-developers.com/showpost.php?p=45465305&postcount=30
I might need to send my phone back and it's rooted. Can I just factory reset?
No.
Here's a guide with video and all...
http://forum.xda-developers.com/showthread.php?t=2446515
Thanks. Will it be detectable that it was rooted?
Yes.
Sent from my XT1058 using xda app-developers app
planktoid said:
Yes.
Click to expand...
Click to collapse
So it can't be completely reversed? My phone has multiple physical defects and I dread the thought of having another broken phone for two years.
planktoid said:
Yes.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Slusho said:
So it can't be completely reversed? My phone has multiple physical defects and I dread the thought of having another broken phone for two years.
Click to expand...
Click to collapse
I am not sure what @planktoid was referencing as far as it "being detectable". But if you follow that tutorial and use RSDLite to flash the original firmware you will be able to warranty return your phone without any problem.
---------- Post added at 08:14 AM ---------- Previous post was at 08:07 AM ----------
Which carrier are you with? If you are with a carrier that offers a bootloader unlock and you performed the bootloader unlock and rooted then you are not going to be covered by warranty. They definitely know if you unlocked your bootloader.
If all you did was root via jcase's PwnMyMoto - you will be fine to restore via RSDLite and do a warranty exchange.
thepolishguy said:
I am not sure what @planktoid was referencing as far as it "being detectable". But if you follow that tutorial and use RSDLite to flash the original firmware you will be able to warranty return your phone without any problem.
---------- Post added at 08:14 AM ---------- Previous post was at 08:07 AM ----------
Which carrier are you with? If you are with a carrier that offers a bootloader unlock and you performed the bootloader unlock and rooted then you are not going to be covered by warranty. They definitely know if you unlocked your bootloader.
If all you did was root via jcase's PwnMyMoto - you will be fine to restore via RSDLite and do a warranty exchange.
Click to expand...
Click to collapse
I just used jcase's root. Thanks, I was really worrying about this!
I am talking about the q/e bit.
Sent from my XT1058 using xda app-developers app
planktoid said:
I am talking about the q/e bit.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I've never met a CSR smart enough to check that.
---------- Post added at 12:26 PM ---------- Previous post was at 12:11 PM ----------
Slusho said:
I just used jcase's root. Thanks, I was really worrying about this!
Click to expand...
Click to collapse
planktoid said:
I am talking about the q/e bit.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
thepolishguy said:
I've never met a CSR smart enough to check that.
Click to expand...
Click to collapse
I have to apologize. There is a very small chance that you could get the only CSR smart enough to look for the "tampered flag". I doubt that this is going to be the case. But I would also hate to see you get busted after I advised you to go ahead an return it.
If you want 100% piece of mind you can follow the instruction here...
That Pesky QE
...and reset the flag to 0/1 so that you are absolutely safe for a return.
Again - I apologize and props to Planktoid for bringing it up. I have never had a problem returning a device that has been rooted. But whose to say they won't check. This will solve that small possibility.
Okay, they probably have a procedure that doesn't include checking for the QE, but just to be sure, let me make sure I understand this. Will following these steps work?:
1. Follow the steps in the video.
2. Issue commands "fastboot erase userdata" and "fastboot reboot" using adb, and use "fastboot getvar all" to check the QE status.
Slusho said:
Okay, they probably have a procedure that doesn't include checking for the QE, but just to be sure, let me make sure I understand this. Will following these steps work?:
1. Follow the steps in the video.
2. Issue commands "fastboot erase userdata" and "fastboot reboot" using adb, and use "fastboot getvar all" to check the QE status.
Click to expand...
Click to collapse
I would just follow the instructions from P3Droid's tutorial at AOSP.us... http://aosp.us/?p=901
1) Download the stock firmware for your device. (Check sbf.droid-developers.org)
2) Grab the stock misc image
3) Open a command terminal...
Click to expand...
Click to collapse
Code:
adb shell
su
echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379
exit
exit
3) Make sure your system is stock.
Now to make sure your system is stock:
Code:
fastboot flash boot boot.img
fastboot flash system system.im
You can pull these images from the SBF file by unzipping it with something like 7zip. If they won't flash for you then you'll have to use the other tutorial with RSDLite. They would not flash for me in Fastboot for some reason. Make sure you download the proper SBF for your phone.
If they do flash for you then you can move on to the next step in P3Droids tutorial...
Code:
fastboot erase userdata
fastboot reboot
Okay thanks. You've been hugely helpful, and I will be sure to name my firstborn "thepolishguy".
Slusho said:
Okay thanks. You've been hugely helpful, and I will be sure to name my firstborn "thepolishguy".
Click to expand...
Click to collapse
Don't thank me until it has worked. Hopefully "thepolishguy" doesn't end up becoming a curse word around your house...
Code:
"son of a polishguy"
Code:
"that dirty rotten polishguy"
If you still have problems, and aren't on windows sigh: still having issues with that os), you could check out my thread:
[TOOL] Moto X FXZ Flashing Script (100% back to stock) [10/03/2013]
My new phone should come on Tuesday, so your fate will be determined then. And bhundven, thanks, I did see your thread and I'll be sure to keep that in mind.
Just curious if this would work on a Droid Maxx. I have the 1/1 qe flag in the bootloader. Been doing some google searches, but haven't found anything except this thread, and instructions to reset it to 0/1 on a Moto X. But I'm not sure if the location to reset would be the same. Any ideas?
BMAF said:
Just curious if this would work on a Droid Maxx. I have the 1/1 qe flag in the bootloader. Been doing some google searches, but haven't found anything except this thread, and instructions to reset it to 0/1 on a Moto X. But I'm not sure if the location to reset would be the same. Any ideas?
Click to expand...
Click to collapse
I have no idea but you can try hitting up @P3dRoid on Twitter. He'd know (if he has time to get back to you).
Also there's a G+ community for the MotoX Developer Version - you can ask there and see if someone chimes in.
Sent from my XT1060 using Tapatalk 4
When I get to the part in which I have to type "echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379", I get back "cannot open for write: Permission denied".
Slusho said:
When I get to the part in which I have to type "echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379", I get back "cannot open for write: Permission denied".
Click to expand...
Click to collapse
I asked someone with a lot more intelligence than me to visit your question. Hopefully he does. Sorry.
Just to help with some trouble shooting... after you enter
adb shell
su
what does it return? I believe that you should start with a "$". And then after you input "su" you should get a "#" on the return. Do you?
Slusho said:
When I get to the part in which I have to type "echo -ne “0″| dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=5379", I get back "cannot open for write: Permission denied".
Click to expand...
Click to collapse
you have to be root
Hey guys,
I'm really sorry to bother everyone but I just spent 10 hours straight trying to get my HTC One back to its original state.
I'm really frustrated as I have tried 15 different tutorials and have about 1 million tabs open right now.
- I tried the whole re-locking thing and tried flashing a RUU (tried so many different ones but always some signature error. And with exe's I should get the right utility because it's the wrong bootloader). I don't even know what's the right one. Here's the getvar version-main I get: 1.29.401.12
- I somehow wiped everything and can't even get my phone as an external flash drive.
- I read I should have S Off whatever that is, but for that I needed to re-flash a rom. I can't even get that to work anymore. I tried to sideload it. It worked...but there's nothing on the phone except an ever turning cyanogenmod wheel.
- I took a pic of my bootloader screen, maybe you guys can decipher what there's to be done.
https://www.dropbox.com/s/p013md5fog7t4vn/2013-11-14%2017.34.07.jpg
Any help is SO appreciated! x/
Please go easy on me and speak english...not code lol
I know my way around googling the hell out of things but this is obviously my limit^^
ycianca said:
Hey guys,
I'm really sorry to bother everyone but I just spent 10 hours straight trying to get my HTC One back to its original state.
I'm really frustrated as I have tried 15 different tutorials and have about 1 million tabs open right now.
- I tried the whole re-locking thing and tried flashing a RUU (tried so many different ones but always some signature error. And with exe's I should get the right utility because it's the wrong bootloader). I don't even know what's the right one. Here's the getvar version-main I get: 1.29.401.12
- I somehow wiped everything and can't even get my phone as an external flash drive.
- I read I should have S Off whatever that is, but for that I needed to re-flash a rom. I can't even get that to work anymore. I tried to sideload it. It worked...but there's nothing on the phone except an ever turning cyanogenmod wheel.
- I took a pic of my bootloader screen, maybe you guys can decipher what there's to be done.
https://www.dropbox.com/s/p013md5fog7t4vn/2013-11-14%2017.34.07.jpg
Any help is SO appreciated! x/
Please go easy on me and speak english...not code lol
I know my way around googling the hell out of things but this is obviously my limit^^
Click to expand...
Click to collapse
Okay, your hboot is 1.44 (April 2013), so you should be able to achieve S-Off using revone.
can you please post a "fastboot getvar all" (remove IMEI and serialno), and confirm your bootloader is unlocked
sure, here you go:
https://dl.dropboxusercontent.com/u/56231439/Untitled-1.jpg
nkk71 said:
Okay, your hboot is 1.44 (April 2013), so you should be able to achieve S-Off using revone.
can you please post a "fastboot getvar all" (remove IMEI and serialno), and confirm your bootloader is unlocked
Click to expand...
Click to collapse
as for the unlocked bootloader, i guess it's unlocked as it says unlocked in pink on the picture
ycianca said:
as for the unlocked bootloader, i guess it's unlocked as it says unlocked in pink on the picture
Click to expand...
Click to collapse
my bad, i'll get back to you in a little while.....
---------- Post added at 08:48 PM ---------- Previous post was at 08:07 PM ----------
ycianca said:
as for the unlocked bootloader, i guess it's unlocked as it says unlocked in pink on the picture
Click to expand...
Click to collapse
Sorry for having to rewind a little, but can you let me know your goal?
1- hboot -> OK
2- getvar -> OK
3- you can achieve S-Off using revone with a Sense 5 / Android 4.1.2 based ROM
I need to go now, and may not be back till Saturday, in the meantime, if you need to get you phone up & running just use: http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/ (unselect "stock recovery" during installer) or any other custom ROM out there.
If you think I've helped, hit the thanks button,
and please explain where you want to end up.
nkk71 said:
my bad, i'll get back to you in a little while.....
---------- Post added at 08:48 PM ---------- Previous post was at 08:07 PM ----------
Sorry for having to rewind a little, but can you let me know your goal?
1- hboot -> OK
2- getvar -> OK
3- you can achieve S-Off using revone with a Sense 5 / Android 4.1.2 based ROM
I need to go now, and may not be back till Saturday, in the meantime, if you need to get you phone up & running just use: http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/ (unselect "stock recovery" during installer) or any other custom ROM out there.
If you think I've helped, hit the thanks button,
and please explain where you want to end up.
Click to expand...
Click to collapse
my goal, as stated in my initial post and title, is to get my original phone back (firmware and stuff). i had cm on it, now there's nothing on it except a "useless" fastboot and recovery. i just wish to get my original phone back so i can re-sell it.
ycianca said:
my goal, as stated in my initial post and title, is to get my original phone back (firmware and stuff). i had cm on it, now there's nothing on it except a "useless" fastboot and recovery. i just wish to get my original phone back so i can re-sell it.
Click to expand...
Click to collapse
i just downloaded that zip and now i have absolutely no clue what to do...
Ah I think I know what your problem is ... 1.29.401.12 doesnt have a full RUU file anywhere ... can u tell me the filename you tried running (RUU exe?) ..
So what you need is ...
1. TWRP/CWM Recovery installed and working
2. TWRP/CWM Backup ROM file for 1.29.401.12
I could only google and find CWM backup for your ROM so you need to flash CWM recovery first (I assume you know how)
Download your ROM backup from here -> http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
adb push this to your sdcard and use restore option from CWM... also best if you wipe data/factory reset first since you had CM on it
v-b-n said:
Ah I think I know what your problem is ... 1.29.401.12 doesnt have a full RUU file anywhere ... can u tell me the filename you tried running (RUU exe?) ..
So what you need is ...
1. TWRP/CWM Recovery installed and working
2. TWRP/CWM Backup ROM file for 1.29.401.12
I could only google and find CWM backup for your ROM so you need to flash CWM recovery first (I assume you know how)
Download your ROM backup from here -> http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
adb push this to your sdcard and use restore option from CWM... also best if you wipe data/factory reset first since you had CM on it
Click to expand...
Click to collapse
thanks i will try that. do i need to re-lock it first?
ycianca said:
thanks i will try that. do i need to re-lock it first?
Click to expand...
Click to collapse
No need to relock
i don't know how adb push works. i tried following a tutorial but it says to mount sdcard which i don't have. i only have system, data and cache.
i then re-locked, then tried to flash via fastboot oem reboot and flash zip.
that didn't work because of "signature verify fail".
i'd love to try adb push, if you could be so nice to tell me how i'd have to proceed.
It would be easier if you download a Custom ROM and then in CWM choose Install -> Sideload
And then from PC , adb sideload yourfile.zip
This should load the Custom ROM ... it will be easier to transfer and manage the nandroid backup files once the OS is loaded
v-b-n said:
It would be easier if you download a Custom ROM and then in CWM choose Install -> Sideload
And then from PC , adb sideload yourfile.zip
This should load the Custom ROM ... it will be easier to transfer and manage the nandroid backup files once the OS is loaded
Click to expand...
Click to collapse
yes i tried that but it does not work. and i don't get why.
1. i sideloaded a cm stable file.
2. the file had been renamed sideload.zip
3. i started the install and it said successful.
4. when i boot the phone, the cm wheel turns and turns infinitely.
5. i tried a different rom (infection), it said succesful install, i re-booted but that darned cm wheel was still there turning and turning thinking "you like that huh?"
If you have nothing to save on sdcard , this is what I would do ...
1. Wipe System
2. Wipe Cache
3. Wipe Data
4. Wipe INternal Storage
And CWM Sideload should start the flashing immediately after transferring the zip file unless u r doing it some wrong way
---------- Post added at 05:03 PM ---------- Previous post was at 04:58 PM ----------
Here's another way ..
Download this -> http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Sideload it and follow on screen steps
to save us some time. would you be open for a quick chat session with screen sharing?
we could resolve this in 5 minutes like that.
tell me what you think, thanks!
ycianca said:
to save us some time. would you be open for a quick chat session with screen sharing?
we could resolve this in 5 minutes like that.
tell me what you think, thanks!
Click to expand...
Click to collapse
nevermind! it seriously finally worked.
- i had some issues on the way with guru reset but it finally worked.
i couldn't sideload it it said something about too many emulators...
i sideloaded it via a toolkit and it worked. guru reset gave me another version number than the getvar thought. strange isn't it?
anyways...thanks a lot for helping me out!
ycianca said:
nevermind! it seriously finally worked.
- i had some issues on the way with guru reset but it finally worked.
i couldn't sideload it it said something about too many emulators...
i sideloaded it via a toolkit and it worked. guru reset gave me another version number than the getvar thought. strange isn't it?
anyways...thanks a lot for helping me out!
Click to expand...
Click to collapse
getvar shows your firmware version, settings -> about shows you the ROM version
HTC One rooted a few days ago, was running stock then decided to place a custom rom on it.
Rom failed to install, and every time I turn on the phone it goes straight to recovery mode.
Backups dont seem to be working and I've tried sideloading a different custom rom but that also failed. Pushing backups to the phone has also not solved the issue.
HTC one M7 is/was running latest 4.4.3, international
Any help would be greatly appreciated, I guess this is what you'd call a soft brick but I just can't fix it.
Thanks
Criminall
Criminallyinsane said:
HTC One rooted a few days ago, was running stock then decided to place a custom rom on it.
Rom failed to install, and every time I turn on the phone it goes straight to recovery mode.
Backups dont seem to be working and I've tried sideloading a different custom rom but that also failed. Pushing backups to the phone has also not solved the issue.
HTC one M7 is/was running latest 4.4.3, international
Any help would be greatly appreciated, I guess this is what you'd call a soft brick but I just can't fix it.
Thanks
Criminall
Click to expand...
Click to collapse
probably a wrong recovery version for the ROM you are trying to install
assuming you have an m7_u or m7_ul, use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (the other versions are known to have issues with some roms)
also check the Frequently Asked Question sticky page 3
and don't forget to check MD5 on your downloads!!
nkk71 said:
probably a wrong recovery version for the ROM you are trying to install
assuming you have an m7_u or m7_ul, use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (the other versions are known to have issues with some roms)
also check the Frequently Asked Question sticky page 3
and don't forget to check MD5 on your downloads!!
Click to expand...
Click to collapse
Thanks I did the 2.8.0.1, but now I can't even use adb to flash or anything, the device is essentially unrecognised now. Any tips on how to proceed?
Criminallyinsane said:
Thanks I did the 2.8.0.1, but now I can't even use adb to flash or anything, the device is essentially unrecognised now. Any tips on how to proceed?
Click to expand...
Click to collapse
faq #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
it was also mentioned in the sticky post i linked earlier, reading it helps
nkk71 said:
faq #2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
it was also mentioned in the sticky post i linked earlier, reading it helps
Click to expand...
Click to collapse
Thanks man, very helpful. However, every time I update the drivers and put the phone in sideload it stops recognising it once again.
I was hoping I could just sideload a new rom to the phone and attempt to install it?
Criminallyinsane said:
Thanks man, very helpful. However, every time I update the drivers and put the phone in sideload it stops recognising it once again.
I was hoping I could just sideload a new rom to the phone and attempt to install it?
Click to expand...
Click to collapse
try adb push method instead of sideload
or once in sideload, right-click your PC in Windows device manager, and "scan for hardware changes", that may fix it
Can you flash ROMs without root?
What twrp version is best for this device? Thanks
Tmobilefan906 said:
Can you flash ROMs without root?
Click to expand...
Click to collapse
Yes. You do have to have your bootloader unlocked though. Most custom ROMs come rooted once you flash them.
Tmobilefan906 said:
What twrp version is best for this device? Thanks
Click to expand...
Click to collapse
I'm using 2.8.7.0 and haven't had any issues.
coal686 said:
Yes. You do have to have your bootloader unlocked though. Most custom ROMs come rooted once you flash them.
I'm using 2.8.7.0 and haven't had any issues.
Click to expand...
Click to collapse
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Tmobilefan906 said:
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
Click to expand...
Click to collapse
And is facepalm still working for s off? I heard they stopped deving for it. Thanks again.
Tmobilefan906 said:
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
And is facepalm still working for s off? I heard they stopped deving for it. Thanks again.
Click to expand...
Click to collapse
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Sloth said:
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Click to expand...
Click to collapse
OK. Every time I tried that, it kept saying error. All drivers were installed..drivers for while in BL, normal mode and recovery were installed on my PC. Maybe I typed it wrong. After .zip, there is a space then /sdcard/...right?
coal686 said:
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
Click to expand...
Click to collapse
Yea, the phone has 2.6.4 twrp already on it. I bought it with no o.s
coal686 said:
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
Click to expand...
Click to collapse
I hear rumrunner and firewater still work...true?
Tmobilefan906 said:
Yea, the phone has 2.6.4 twrp already on it. I bought it with no o.s
Click to expand...
Click to collapse
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
Tmobilefan906 said:
I hear rumrunner and firewater still work...true?
Click to expand...
Click to collapse
@Sloth might have kept up with this better. AFAIK, those Rumrunner will still work if you are on an older firmware, but I'm not sure.
EDIT: Fixed due to Sloth's answer below.
coal686 said:
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
@Sloth might have kept up with this better. AFAIK, those will still work if you are on an older firmware, but I'm not sure.
Click to expand...
Click to collapse
Update what? My twrp? I was thinking flashing 3.8.7 like u suggested. Its been a while since I tinkered with htcs. I've hacked quite a few in my days. Thanks again!!
coal686 said:
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
@Sloth might have kept up with this better. AFAIK, those will still work if you are on an older firmware, but I'm not sure.
Click to expand...
Click to collapse
RumRunner might work if it is still on one of the earlier updates, Firewater has been discontinued, if RR does not work you will have to use SunShine to s-off.
Tmobilefan906 said:
Update what? My twrp? I was thinking flashing 3.8.7 like u suggested. Its been a while since I tinkered with htcs. I've hacked quite a few in my days. Thanks again!!
Click to expand...
Click to collapse
Yeah, TWRP. 2.6.x is pretty old. Since you've hacked a few HTC devices in the past, this device isn't much different except without an SD card, you can't use a specially named zip (like PGxxxx.zip) to flash firmware. It must be done with fastboot.
coal686 said:
Yeah, TWRP. 2.6.x is pretty old. Since you've hacked a few HTC devices in the past, this device isn't much different except without an SD card, you can't use a specially named zip (like PGxxxx.zip) to flash firmware. It must be done with fastboot.
Click to expand...
Click to collapse
Why is recovery m7lw and roms zips are m7spr?
Sloth said:
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Click to expand...
Click to collapse
It says no such directory
Tmobilefan906 said:
It says no such directory
Click to expand...
Click to collapse
I had to put .zip in the cmd prompt. Thanks.
Tmobilefan906 said:
It says no such directory
Click to expand...
Click to collapse
Ugh. Stuck at 5%
Every time I flash recovery, it won't stick. I've tried button combos, multiple flashing recoveries. I need help
I think my bootloader is locked. Ugh
On my bootloader it says m7wls. Where can I find ROMs for that? I need to adb push it..I tried the RR ROM named m7spr, and it won't work. Please help!! Lol
Tmobilefan906 said:
Why is recovery m7lw and roms zips are m7spr?
Click to expand...
Click to collapse
Does ".zip" have to be in ROM name to flash? This is my first sprint HTC. Ugh.