hello , after unlocking bootloader and rooting phone i had a real hard time getting s-off so i just left that part , i installed a few custom roms that just stayed on the htc boot logo but i backed up my stock rom so i could go back to it if needed , but now when i click restore in cwm it gets to white htc screen then reboots back to recovery , ive tried flashing boot.img but it says "error: cannot load 'boot.img'" so im just stuck at the minute so any help would be great , my phone is >>>>
UNLOCKED
VIVO PVT SHIP S-ON IRL
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
eMMC-boot
May 22 2012,14:22:08
http://bit.ly/RZr2S8
hmmmmm
ive tried searching for it and found ways to do it but its not working for me so i came in here looking for help only to get sarcastic reply , not helpfull at all
You should not be attempting something that you obviously have no knowledge about. Your reply that you have searched and have found ways but they are not working is proof enough of this. The first hit of my "sarcastic" reply is a method that will definitely work on our phone, there are also guides in this very section as well as many other noobs asking this very same question countless times.
You may have "searched", but you obviously have not "looked" or "read".
oh lord
Nonverbose said:
You should not be attempting something that you obviously have no knowledge about. Your reply that you have searched and have found ways but they are not working is proof enough of this. The first hit of my "sarcastic" reply is a method that will definitely work on our phone, there are also guides in this very section as well as many other noobs asking this very same question countless times.
You may have "searched", but you obviously have not "looked" or "read".
Click to expand...
Click to collapse
ive rooted , unlocked bootloader , gained s-off on lots of android devices before its this one is throwing up problems that i cant figure out i came here for a bit of friendly advice nothing more , and everyone started out having no knowledge of this at one point but had to start somewhere !! please dont reply you've had your say now ty
DJxDECKSTAR said:
ive rooted , unlocked bootloader , gained s-off on lots of android devices before its this one is throwing up problems that i cant figure out i came here for a bit of friendly advice nothing more , and everyone started out having no knowledge of this at one point but had to start somewhere !! please dont reply you've had your say now ty
Click to expand...
Click to collapse
Make sure you change to your fastboot directory and your boot.img file exists in your fastboot directory....
Once entered command
fastboot flash boot boot.img
it should work, even I had got the same error, so I just pulled cable, connected back and entered same command.. It worked..
Psst: make sure that its written fastboot usb in the bootloader screen. If not written, then USB is faulty
Rah0ol said:
Once entered command
fastboot flash boot boot.img
it should work, even I had got the same error, so I just pulled cable, connected back and entered same command.. It worked..
Psst: make sure that its written fastboot usb in the bootloader screen. If not written, then USB is faulty
Click to expand...
Click to collapse
When you're in fastboot you can do
"Fastboot devices" to see of its connected properly
You will see your serial number.
Sent from my Nexus 7
Related
I have a Cricket HTC Desire C and I tried to root it but I know I messed up because the adb thing never worked and now I cant even factory reset my phone.I tried looking for Stock recovery/kernels but I only found found a recovery.img that allowed me to open Recovery;
After I boot my phone or try to Recover or Factory Reset, I get a red message under the giant HTC saying
Code:
This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action.
I've been up for over 8 hours trying to just restore my phone to stock...I really need help.
Bootload info:
GOLFC PVT SHIP S-ON RL
HBOOT-1.63.0000
RADIO-0.92.00.0903
eMMC-boot
exAera said:
I have a Cricket HTC Desire C and I tried to root it but I know I messed up because the adb thing never worked and now I cant even factory reset my phone.I tried looking for Stock recovery/kernels but I only found found a recovery.img that allowed me to open Recovery;
After I boot my phone or try to Recover or Factory Reset, I get a red message under the giant HTC saying
Code:
This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action.
I've been up for over 8 hours trying to just restore my phone to stock...I really need help.
Bootload info:
GOLD PVT SHIP S-ON RL
HBOOT-1.63.0000
RADIO-0.92.00.0903
eMMC-boot
Click to expand...
Click to collapse
That is a normal message for the splash screen in which we get for unlocking our bootloaders, as far as i'm concerned, the cricket Desire C is CDMA so the usual recoveries wont be compatible with it. Does the phone boot? The best person to ask for assistance on this matter is @soupmagnet as he also has the CDMA Desire C, prehaps he will be able to help you.
penguin449 said:
That is a normal message for the splash screen in which we get for unlocking our bootloaders, as far as i'm concerned, the cricket Desire C is CDMA so the usual recoveries wont be compatible with it. Does the phone boot? The best person to ask for assistance on this matter is @soupmagnet as he also has the CDMA Desire C, prehaps he will be able to help you.
Click to expand...
Click to collapse
The phone boots to an extent; It will load bootloader just fine but that message shows for Recovery, Factory Reset, and normal Boot
Please guys? I really need my phone working again, I just wanna beable to factory restore it so Its usable again
exAera said:
Please guys? I really need my phone working again, I just wanna beable to factory restore it so Its usable again
Click to expand...
Click to collapse
http://d-h.st/uUA
This is the stock recovery, but I don't think it will do you much good. A factory reset only wipes user data. What happens when you select normal boot? Does it give you adb access?
soupmagnet said:
This is the stock recovery, but I don't think it will do you much good. A factory reset only wipes user data. What happens when you select normal boot? Does it give you adb access?
Click to expand...
Click to collapse
It gives me the message displayed in the first post; and No, my computer never did the adb setup; that always failed when I tried to root.
Okay I used my father's phone to make a video;
I'm gunna upload the video
OP, check your inbox
Might have pushed the gsm version like I did the first time
Please guys, I was thinking about buying a new one but the price jumped up from $60 to $100...I really dont wanna spend $40 more than what I paid for my phone. I'll gladly send $40 to the person who helps me get my phone fixed
exAera said:
Please guys, I was thinking about buying a new one but the price jumped up from $60 to $100...I really dont wanna spend $40 more than what I paid for my phone. I'll gladly send $40 to the person who helps me get my phone fixed
Click to expand...
Click to collapse
I haven't forgotten about you. I just need to find time to work on it...
soupmagnet said:
I haven't forgotten about you. I just need to find time to work on it...
Click to expand...
Click to collapse
Well I better inform my mom not to buy it then cause I sent her the money last night
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
help me
lastrastuff said:
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
Click to expand...
Click to collapse
Did this work? my first has been in a boot loop for months. I can't get ADB, Fastboot or RUU to recognize the device.
sara_groves said:
Did this work? my first has been in a boot loop for months. I can't get ADB, Fastboot or RUU to recognize the device.
Click to expand...
Click to collapse
Well I have a working phone if that's what you mean. If you are able to get your phone into fastboot you can go through with an RUU usually.
lastrastuff said:
Well I have a working phone if that's what you mean. If you are able to get your phone into fastboot you can go through with an RUU usually.
Click to expand...
Click to collapse
I with it some more last night. I did finally get ADB to work, but still no fastboot. Shop i was able to push in filters... i just have no way of flashing.
bootlaoder block you should have before making the ruu to lock the bootloader needs to enter fastboot, in fastboot type this command fastboot oem lock, try it on mac as it would not need to install drivers.
Ok this guide works for me!
the problem is this traslate for spanish, a don't speak english, i hope you fix your phone...
http:/ /www. htcmania. com/ showthread. php?t=548748
lastrastuff said:
Let me just start by saying I have spent basically a week scanning forums on this problem and none of their solutions worked for me, despite this being a fairly common problem. Regardless, here is where I am.
My phone was acting strangely last week so I decided I should just reflash the ROM and kernel to see if it fixed any problems. When I did that I got stuck in a bootloop that I was unable to come out of. I wiped the cache as well, but that didn't seem to help either. Once I had flashed the images both zips seemed to disappear from my phone's storage so I had to use fastboot to flash a new boot.img but that also didn't help. I eventually gave up and had to do an RUU which at least got my phone working only after I relocked it. My phone before said it was moonshine s-off, which was true, but after the RUU it reads "ship s-off RL." It seems that may be where the problem lies in not being able to flash any new boot images to it. I should also mention some of the RUU attempts failed as well before eventually succeeding at the part where it flashes the boot.img. Thanks in advance for your help!
Click to expand...
Click to collapse
It seems your phone stuck in a bootloop after flash a rom and kernel,are you sure the rom and kernel is ok?
http://forum.xda-developers.com/showthread.php?t=2685284
please read the bottom part of what i wrote in the thread ,, basically i went back to 4.3 and it worked and fixed the mms but it took away my 4g so i thought it was easy enough lets try the 4.4 version of that rom and maybe have the bes tof both worlds and now as u read i cant do anything , but get into bootloader but anything i try goes back to a frozen htc screen , it will go to recovery it will show cwm for a few seconds go blank and back to htc screen frozen , i cant sync to the computer , but i can power down and charge it please help , thanks so much for the help
ok ive been working on it all night and morning long , so here is what i have now , i managed to get twrp working , problem is i think that last one wiped out everything it says no OS to reboot and i cant get it to recongnize device on my computer , i have everything saved in my harddrive just in case i needed to got back but i cant get it to recongnize it on my computer but twrp all works and i can navigate on it and fastboot usb is working cause twrp got put on ,, now how to install all the saved OS back on the phone via twrp or fastboot usb is the question?
thanks
not sure many people care, let alone to create another thread pointing to your old thread.
bloodrain954 said:
not sure many people care, let alone to create another thread pointing to your old thread.
Click to expand...
Click to collapse
if u dont have anything nice or helpful to say then shouldnt u just shhh? u took the time to say nothing ,im sure that is what everyone cares to read ?
im going to use this to help other noobs like myself that gets courageous enough to try rooting , customer roms unlocking etc. seems easy to the tech guys but some of the lingo is not so easy and u can make one bad move , i hope i didnt
at any rate here is where im at , i did get twrp setup in fastboot mode so all i have is fastboot mode to do anything atm ,, it appears like i said i somehow wiped my whole operating system , how i dont know but i have one more thing i think from the help of others may work and that is use a micro usb otg cable to hopefully flash the rom back on the phone , wish me luck , unfortunately im not sure locally where to buy one , i will go look this evening , but in the meantime i did order one for a couple of bucks on ebay just in case i couldnt find one locally , i will update
anymore input would be thankful and helpful
Boot into boot loader and flash RUU that matches your cid as I take it your s-on still.
Do not flash anything does. Not match your cid in your case Att = CWS__001
Sent from my HTC One using XDA Premium HD app
ac3kill said:
Boot into boot loader and flash RUU that matches your cid as I take it your s-on still.
Do not flash anything does. Not match your cid in your case Att = CWS__001
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
there is no flash ruu ? can u show me or copy and paste what i need ? remember i can not hook up to the computer , so im going to try a micro otg cause twrp supposed recognizes it so then i was hoping to get it in my phone that way ?
madi05 said:
there is no flash ruu ? can u show me or copy and paste what i need ? remember i can not hook up to the computer , so im going to try a micro otg cause twrp supposed recognizes it so then i was hoping to get it in my phone that way ?
Click to expand...
Click to collapse
why cant you hook it up to a computer? i see that your getting fastboot and TWRP? if you can get either you should be able to sideload from the computer what you need to boot up again.
if you only have fastboot. then load TWRP via fastboot and then from TWRP, use sideload/command prompt to pump a rom on and then voila you should be good. if you already have TWRP just start from there..
syaoran68 said:
why cant you hook it up to a computer? i see that your getting fastboot and TWRP? if you can get either you should be able to sideload from the computer what you need to boot up again.
if you only have fastboot. then load TWRP via fastboot and then from TWRP, use sideload/command prompt to pump a rom on and then voila you should be good. if you already have TWRP just start from there..
Click to expand...
Click to collapse
i thought the same thing but my computer says now it doesnt recognize the device and i reinstalled all the new htc drivers smh its like my phone is completely wiped clean
i am assuming sideload is in twrp but it doesnt do anything i dont think when i go there but i will try it again hooked tot he compouter ,, i got twrp to download on my phone via the fastboot usb np but it never recognized it i just did it and it was on it
madi05 said:
i thought the same thing but my computer says now it doesnt recognize the device and i reinstalled all the new htc drivers smh its like my phone is completely wiped clean
i am assuming sideload is in twrp but it doesnt do anything i dont think when i go there but i will try it again hooked tot he compouter ,, i got twrp to download on my phone via the fastboot usb np but it never recognized it i just did it and it was on it
Click to expand...
Click to collapse
i see an adb sideload but it says could not mount?
Have you looked here?
http://forum.xda-developers.com/showthread.php?t=2318497
namaste74 said:
Have you looked here?
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
yes sir i did this and i got the 100% but then it just goes back into the twrp and i still have no OS it says ? im installing arhd 31.6 is that not the right zip?
i would try sideloading something else to see if it could be the ARHD. also what TWRP version are you using?
syaoran68 said:
i would try sideloading something else to see if it could be the ARHD. also what TWRP version are you using?
Click to expand...
Click to collapse
twrp v2.7.0.0 and can you please link me to the one u suggest? basically i think i need everything like the factory puts in there ? , i just want it back working again , pretty much i think i need more than a rom , there is nothing in anything in the phone via twrp that i can see, i can sideload i tried pushing arhd and i tried pushing all the folders and all i saved from the whole phone before i did this and it does its thing , and when finished nothing happens ? i sideloaded got 100% still nothing , is there something i do other than reboot afterwards? thanks for helping me its frustrating
A big big big thanks to Crushalot
This guy is not only awesome for lending me his time and making my phone even better than it was but he is just a nice guy in general and helped a stranger for nothing but to help , a big asset to xda imho and he knows his stuff thank u thank u thank u my friend !!!!!
madi05
madi05 said:
This guy is not only awesome for lending me his time and making my phone even better than it was but he is just a nice guy in general and helped a stranger for nothing but to help , a big asset to xda imho and he knows his stuff thank u thank u thank u my friend !!!!!
madi05
Click to expand...
Click to collapse
Yes if you want to mention someone use the @crushalot tag and they get the message...... I support htc1Guru.com ever chance i get
Thanks for that and again this guy is a class act!
Sent from my HTC One using Tapatalk
I dont know where yo are currently at but if you recieved your phone back with kitkat that means your bootloader was upgraded. Your phone will not boot unless you either flash a 4.3 kernel or you flash a kitkat ROM. Let me know if this info helps
bdorr1105 said:
I dont know where yo are currently at but if you recieved your phone back with kitkat that means your bootloader was upgraded. Your phone will not boot unless you either flash a 4.3 kernel or you flash a kitkat ROM. Let me know if this info helps
Click to expand...
Click to collapse
thanks for your input ,, crush got me sorted and i felt i made a new friend in the process , go giants lol
madi05 said:
twrp v2.7.0.0 and can you please link me to the one u suggest? basically i think i need everything like the factory puts in there ? , i just want it back working again , pretty much i think i need more than a rom , there is nothing in anything in the phone via twrp that i can see, i can sideload i tried pushing arhd and i tried pushing all the folders and all i saved from the whole phone before i did this and it does its thing , and when finished nothing happens ? i sideloaded got 100% still nothing , is there something i do other than reboot afterwards? thanks for helping me its frustrating
Click to expand...
Click to collapse
after your sideloading the rom onto the phone is it running and are you going through the installation? if you are and its still not loading properly then you may have a corrupted SD. you can try running a RUU. i think you have an ATT phone? if your S-OFF you can try this file ATT Android 4.3 RUU EXE file
that is the full RUU. it should ask you to start in a fully booted mode. just go ahead and start in Fastboot. when you press start it just sends the command to restart phone into fastboot so you can inject from there. i might be able to find something else for you but for now try this(assuming your s-off XD)
A friend of mine has a T-Mobile HTC One and he bricked it, he asked me for help, knowing I'm very good with tech and android. But the thing is that I know everything but from Samsung, I always try to read a lot and learn from new devices to fix them or even try something because I'm always asked for help from my family, sure you guys know about that, but sadly I'm in finals and I'm barely sleeping and I've read a little but not enough but need I to help him so that's why I ask you guys for help urgently. Here are the things I know:
The phone is trapped in a bootloop after the Cyanogenmod logo and restarts itself after a minute
It is S-ON but unlocked
It is the M7_UL T-Mobile model
It is on HBOOT 1.56
The Radio is on 4A.24.32.63.09
The OS 4.19.531.10
It can still enter recovery and is recognized by my PC
From what I've read that has been a little bit, I can restore it completely with a RUU (kind of like a .tar in ODIN for Samsung), but it has to be Relocked and in other sites it says that it has to be S-OFF, needless to say that I don't know what tools to use and then I've seen that that Hboot 1.65 is not supported and well right now I have to create my SQL project, sorry to ask you guys as I hate when other do it just to not read but I swear this is not the case.
Help to fix this will be very appreciated
*GalaxyDev* said:
A friend of mine has a T-Mobile HTC One and he bricked it, he asked me for help, knowing I'm very good with tech and android. But the thing is that I know everything but from Samsung, I always try to read a lot and learn from new devices to fix them or even try something because I'm always asked for help from my family, sure you guys know about that, but sadly I'm in finals and I'm barely sleeping and I've read a little but not enough but need I to help him so that's why I ask you guys for help urgently. Here are the things I know:
The phone is trapped in a bootloop after the Cyanogenmod logo and restarts itself after a minute
It is S-ON but unlocked
It is the M7_UL T-Mobile model
It is on HBOOT 1.56
The Radio is on 4A.24.32.63.09
The OS 4.19.531.10
It can still enter recovery and is recognized by my PC
From what I've read that has been a little bit, I can restore it completely with a RUU (kind of like a .tar in ODIN for Samsung), but it has to be Relocked and in other sites it says that it has to be S-OFF, needless to say that I don't know what tools to use and then I've seen that that Hboot 1.65 is not supported and well right now I have to create my SQL project, sorry to ask you guys as I hate when other do it just to not read but I swear this is not the case.
Help to fix this will be very appreciated
Click to expand...
Click to collapse
First thing, try this
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
Then reboot.
(you may need to try 2 or 3 times to get it right)
What recovery do you have?
CWM has problems with 4.4.2.
The rom bootloops
Install twrp 2.6.3.3
Make sure it's for your phone.
If that doesn't work, do you know how to post a fastboot getvar all.
Sent from my HTC One using Xparent Skyblue Tapatalk 2
bored_stupid said:
First thing, try this
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
Then reboot.
(you may need to try 2 or 3 times to get it right)
If that doesn't work, do you know how to post a fastboot getvar all.
Click to expand...
Click to collapse
Yeah I've tried that. The thing that I forgot to tell is that when I go into Recovery mode it shows all partitions in 0mb including Internal Storage and says it doesn't have any OS installed although the Cyanogenmod Logo appears at startup
Find stock recovery for Tmobile. Flash it. Factory reset from bootloader menu and reflahs custom recovery. You should be ok to proceed
sent from my mobile device
Thanks!
SaHiLzZ said:
Find stock recovery for Tmobile. Flash it. Factory reset from bootloader menu and reflahs custom recovery. You should be ok to proceed
sent from my mobile device
Click to expand...
Click to collapse
thanks!! it actually worked and it booted right up, you just saved me lots of time to work in my project. Time to continue really thanks
Hey guys,
Long time lurker and only been doing the whole rom thing since I bought my HTC One last year.
I've been happy and enjoyed the phone.
Through a drunken stupor last night I made some mistakes and need to get the phone back in action.
I don't believe that what I've done to it has bricked it.
However, it is currently inoperable.
I'll try and break down exactly what happened and what I've done in the past few days that have caused this mess.
Thanks for your patience and understanding and most of all help up front, it's much appreciated.
So here we go!
I've been running an antiquated version of Viper ROM for the majority of the last year.
At this point I'm not even sure the exact release, though I believe it to be 5.6 or 5.7...
Having said that I went and updated finally and was able to successfully flash 6.20, and the OTA that followed.
My phone was running fantastic at that point and was super happy at the new features, etc.
Silly me, I had to believe that USB Fast Charge was not only a privilege but a necessity.
In my hazy recollection of mishaps I went ahead and tried to boot into recovery and flash ElementalX .17 on top of Viper.
Flashed with v2.6.3.3 of TWRP and things went smoothly or so I thought.
After successfully flashing upon booting I was hit with a black screen and only the capacitive buttons being lit.
In my rage and frustration I tried several things and it wouldn't boot.
Stuck in a loop.
So I did the stupid mistake up restoring a super old back up on my phone...
On top of that I messed around and thought I could some how bring it back to the dead.
It was my original Viper installation from all that time ago and this time there was absolutely no connection to WIFI.
The 6.20 version had been cleaned off the phone and now I'm sitting here at TWRP v2.6.3.3 wondering what to do next.
ADB is responsive, but drag and dropping files into the HTC One on my Windows Explorer has proven unsuccessful.
I'm going to post my basic related stuff below.
Let me know if any type of picture upload or what not will help in the process.
Thanks for being there XDA!!!
:good::good:
TAMPERED
BOOTLOADER UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013,16:04:18-1
Once again - my thanks to you people out there smarter and more clear headed than I am.
I raise my glass to you...
SyntheticDynamics said:
Hey guys,
Long time lurker and only been doing the whole rom thing since I bought my HTC One last year.
I've been happy and enjoyed the phone.
Through a drunken stupor last night I made some mistakes and need to get the phone back in action.
I don't believe that what I've done to it has bricked it.
However, it is currently inoperable.
I'll try and break down exactly what happened and what I've done in the past few days that have caused this mess.
Thanks for your patience and understanding and most of all help up front, it's much appreciated.
So here we go!
I've been running an antiquated version of Viper ROM for the majority of the last year.
At this point I'm not even sure the exact release, though I believe it to be 5.6 or 5.7...
Having said that I went and updated finally and was able to successfully flash 6.20, and the OTA that followed.
My phone was running fantastic at that point and was super happy at the new features, etc.
Silly me, I had to believe that USB Fast Charge was not only a privilege but a necessity.
In my hazy recollection of mishaps I went ahead and tried to boot into recovery and flash ElementalX .17 on top of Viper.
Flashed with v2.6.3.3 of TWRP and things went smoothly or so I thought.
After successfully flashing upon booting I was hit with a black screen and only the capacitive buttons being lit.
In my rage and frustration I tried several things and it wouldn't boot.
Stuck in a loop.
So I did the stupid mistake up restoring a super old back up on my phone...
On top of that I messed around and thought I could some how bring it back to the dead.
It was my original Viper installation from all that time ago and this time there was absolutely no connection to WIFI.
The 6.20 version had been cleaned off the phone and now I'm sitting here at TWRP v2.6.3.3 wondering what to do next.
ADB is responsive, but drag and dropping files into the HTC One on my Windows Explorer has proven unsuccessful.
I'm going to post my basic related stuff below.
Let me know if any type of picture upload or what not will help in the process.
Thanks for being there XDA!!!
:good::good:
TAMPERED
BOOTLOADER UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013,16:04:18-1
Once again - my thanks to you people out there smarter and more clear headed than I am.
I raise my glass to you...
Click to expand...
Click to collapse
Please post a fastboot getvar all (except imei and serialno). That way we can take a look and see if there is a RUU available, that will reset you back to stock.
majmoz said:
Please post a fastboot getvar all (except imei and serialno). That way we can take a look and see if there is a RUU available, that will reset you back to stock.
Click to expand...
Click to collapse
Roger that, let me go ahead and get that for you.
majmoz said:
Please post a fastboot getvar all (except imei and serialno). That way we can take a look and see if there is a RUU available, that will reset you back to stock.
Click to expand...
Click to collapse
It's hanging at the Viper One bootup screen now - even though the device is recognized in windows explorer.
here is what adb is showing -
c:/adb>fastboot getvar all
< waiting for device >
SyntheticDynamics said:
It's hanging at the Viper One bootup screen now - even though the device is recognized in windows explorer.
here is what adb is showing -
c:/adb>fastboot getvar all
< waiting for device >
Click to expand...
Click to collapse
What is your MID & CID? If you are in the States what carrier?
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
SyntheticDynamics said:
It's hanging at the Viper One bootup screen now - even though the device is recognized in windows explorer.
here is what adb is showing -
c:/adb>fastboot getvar all
< waiting for device >
Click to expand...
Click to collapse
Turn phone completely off. Then press and hold the PWR button + Vol Down button, it should boot into bootloader. Select Fastboot the screen should change to FASTBOOT USB, now try the commands.
majmoz said:
What is your MID & CID? If you are in the States what carrier?
Click to expand...
Click to collapse
Can't get the phone booted to get the MID and CID - really wish that I had copied down my fastboot getvar all information before all this happened.
I'm on ATT though.
majmoz said:
Turn phone completely off. Then press and hold the PWR button + Vol Down button, it should boot into bootloader. Select Fastboot the screen should change to FASTBOOT USB, now try the commands.
Click to expand...
Click to collapse
I'm able to get into the bootloader.
After selecting Fastboot though I don't see any option for FASTBOOT USB.
majmoz said:
Turn phone completely off. Then press and hold the PWR button + Vol Down button, it should boot into bootloader. Select Fastboot the screen should change to FASTBOOT USB, now try the commands.
Click to expand...
Click to collapse
Actually now I do see the FASTBOOT USB...
The command still hangs though at < waiting for device >.
Ouch, maybe I did brick it after all.
I'm doing as much research as possible from my end.
Thanks for being patient with me.
Hopefully I haven't bricked this thing.
I've added my thanks to your posts thus far for your assistance!
Cheers and a few more energy drinks and maybe we can get this thing going again, lol!
:laugh:
-SD
SyntheticDynamics said:
I'm doing as much research as possible from my end.
Thanks for being patient with me.
Hopefully I haven't bricked this thing.
I've added my thanks to your posts thus far for your assistance!
Cheers and a few more energy drinks and maybe we can get this thing going again, lol!
:laugh:
-SD
Click to expand...
Click to collapse
Here is an AT&T RUU 4.18.502.7. In order to run it you will need to lock your bootloader with the command:
Code:
fastboot oem lock
Are you using Win 8.1? If so, fastboot will not work with a hboot 1.44. You need Win 7 or Ubuntu/Linux. You can run Ubuntu on a USB FAQ Q#5 and you would not have to install it on your computer.
majmoz said:
Here is an AT&T RUU 4.18.502.7. In order to run it you will need to lock your bootloader with the command:
Code:
fastboot oem lock
Are you using Win 8.1? If so, fastboot will not work with a hboot 1.44. You need Win 7 or Ubuntu/Linux. You can run Ubuntu on a USB FAQ Q#5 and you would not have to install it on your computer.
Click to expand...
Click to collapse
I'm using Windows 7.
Will I still be able to lock my bootloader with it being unrecognized?
It's worth a shot!
SyntheticDynamics said:
I'm doing as much research as possible from my end.
Thanks for being patient with me.
Hopefully I haven't bricked this thing.
I've added my thanks to your posts thus far for your assistance!
Cheers and a few more energy drinks and maybe we can get this thing going again, lol!
:laugh:
-SD
Click to expand...
Click to collapse
If you use Ubuntu, you just need it to lock the bootloader. You will need go back to Win 8.1 to run the RUU.exe. Ubuntu can not run .exe files.
majmoz said:
If you use Ubuntu, you just need it to lock the bootloader. You will need go back to Win 8.1 to run the RUU.exe. Ubuntu can not run .exe files.
Click to expand...
Click to collapse
Windows 7 and good to go!
SyntheticDynamics said:
I'm using Windows 7.
Will I still be able to lock my bootloader with it being unrecognized?
It's worth a shot!
Click to expand...
Click to collapse
Check out this FAQ Q#2, it might help you get your phone recognized.
majmoz said:
Check out this FAQ Q#2, it might help you get your phone recognized.
Click to expand...
Click to collapse
Went through and tried all of that and it's still not getting recognized unfortunately!
SyntheticDynamics said:
Went through and tried all of that and it's still not getting recognized unfortunately!
Click to expand...
Click to collapse
This is a long shot, but run the RUU anyway. It should fail but it might reset some things to allow the PC to recognize the phone.
majmoz said:
This is a long shot, but run the RUU anyway. It should fail but it might reset some things to allow the PC to recognize the phone.
Click to expand...
Click to collapse
How can I get the RUU on the phone though since it's unresponsive.
Do I need to push it somehow, or sideload...
What would be the best method to approach doing that?
SyntheticDynamics said:
How can I get the RUU on the phone though since it's unresponsive.
Do I need to push it somehow, or sideload...
What would be the best method to approach doing that?
Click to expand...
Click to collapse
With the phone connected to the PC. Double click the RUU file. It will start and walk you through the process. Some people have found that the file should be in the adb folder.
majmoz said:
This is a long shot, but run the RUU anyway. It should fail but it might reset some things to allow the PC to recognize the phone.
Click to expand...
Click to collapse
Device is recognized again - went ahead and dragged and dropped Viper Rom 6.0 onto it.
Right now it's flashing it and looks to be working smoothly thus far.
Fingers crossed!
You have been a gentlemen and a scholar for helping me through this.
I really do appreciate it man - you have been really great.
Much <3!
*PS*
6.20 Viper Rom in the house, huzzah...
This is a dream come true!
Now in the future I need to be more careful to keep this from happening again, hahaha.
Thank you, thank you, thank you!
I tip my hat to you sir...
SyntheticDynamics said:
Device is recognized again - went ahead and dragged and dropped Viper Rom 6.0 onto it.
Right now it's flashing it and looks to be working smoothly thus far.
Fingers crossed!
You have been a gentlemen and a scholar for helping me through this.
I really do appreciate it man - you have been really great.
Much <3!
*PS*
6.20 Viper Rom in the house, huzzah...
This is a dream come true!
Now in the future I need to be more careful to keep this from happening again, hahaha.
Thank you, thank you, thank you!
I tip my hat to you sir...
Click to expand...
Click to collapse
Glad to see it worked out for you! Happy Flashing!!!