I tried googling this many times but anyway, here I go. I installed bkbtnmenu.zip from here http://forum.xda-developers.com/showthread.php?p=41129973&highlight=backup#post41129973 and my phone wouldn't pass the HTC One logo. I tried nobkbtn.zip and then I even tried getting out the settings.apk and build.prop from Slim and Skinny 4.3 and making a flashable zip which i used ADB sideload to sideload. Still hasn't passed the HTC One logo. Please help me out. Thanks.
swordsx48 said:
I tried googling this many times but anyway, here I go. I installed bkbtnmenu.zip from here http://forum.xda-developers.com/showthread.php?p=41129973&highlight=backup#post41129973 and my phone wouldn't pass the HTC One logo. I tried nobkbtn.zip and then I even tried getting out the settings.apk and build.prop from Slim and Skinny 4.3 and making a flashable zip which i used ADB sideload to sideload. Still hasn't passed the HTC One logo. Please help me out. Thanks.
Click to expand...
Click to collapse
You are going to have to run a RUU to put your phone back unless you have a nandroid backup to use. Here is the latest RUU for T-Mobile.
Related
i dont have very much free time atm. i have a nexus s 4g running cm7 nightly #65... the situation is i was flashing a new rom and ended up hitting my phone off the arm of the chair.. needless to say the battery came out and now im stuck with the cm7 bootloop.. i can hboot but when i try to enter recovery i get a loop on the google screen with the unlocked logo... i have downloaded adb but im not familiar with it at all. my sdk file is under C:\documents and settings\temp\desktop\android-sdk
ive spent all my free time the past week searching for a solution... my phone was used for work and i recieved all my fire calls on it now its usless and about to go out the window and visit verizon.... if someone could help me fix it i will donate. i used to love trying to figure this stuff out but being so rushed around its just frustrating
Might be able to help
A couple questions to start off:
What method did you use to root your phone?
Have you tried flashing the recovery image again or know how to do it on your phone?
I have a Nexus S 3g and pieced together different tutorials for using ADB to flash the recovery image. I just read a tutorial that seems exactly the same for the 4g model. If you can get into the bootloader you might be alright if you just flash the recovery image again from there. But, setting up ADB can be tricky from my experience. Let me know.
Maybe if you follow the guide in the cyanogenmod wiki to install the recovery.
Heres the link:
http://wiki.cyanogenmod.com/wiki/Nexus_S_4G:_Full_Update_Guide
i cant get into recovery it gets stuck looping the bootlogo and if i go threw hboot/recovery it loops the google screen.
fastboot flash recovery recovery-clockwork-3.1.0.1-crespo4g.img... i have this in the sdk file with fastboot. and it just reloads the adb commands when you start adb
that command should work. maybe its how you input it
i highly doubt it if this will work but try fastboot flash recovery "recovery-clockwork-3.1.0.1-crespo4g.img"
Yeah fastboot should work as it is a different partition than the recovery one. And since cm7 flash doesn't touch that partition (I hope) you shouldn't have any problems with it. Make sure you follow the instructions very carefully on that link I posted. Start over if you have to. I've spent hours on things like this, and you will get frustrated but if you keep at it, you'll get it eventually.
it doesnt effect it that it was the kernel flashing when the phone fell? i was running cm7 for awhile before this happened
Sorry Ive been really busy and haven't been able to get on I used the pdanet method I've tried reflashing but still no luck I think I'm doing it wrong
Sent from my HTC Glacier using XDA App
Guess I have a new paper weight. Just ordered a new phone from Verizon
Sent from my HTC Glacier using XDA App
Hello, my Droid DNA is currently stuck in a bootloop. I was stupid and flashed a wrong version of a rom on my droid dna. (NOS M7 verizon patch on gsm version) The DNA currently has super cid, is s-off, unlocked bootloader. HBOOT 1.33.0001. It has TWRP v2.6.0.0.
I tried to use adb sideload but my device isn't recognized? Stuck on "starting adb sideload." I also tried adb through recovery and fastboot but the device is not recognized either. The phone was running Beastmode reloaded kernel with NOS M7 v3.0.3 before I flashed the verizon patch onto it. I currently have no idea how I can fix the phone as almost all the solutions require me to get the device to recognize.
Also, I'm not sure if USB debugging is on? Does USB debugging stay on after a factory reset?
What I did:
1. Factory reset phone
2. Found out my pictures/music/other things were still on it after so I went into TWRP and wiped everything[including my working rom.zip :crying: ] except the system. Phone booted up fine. I found out that all the google applications were missing so I decided to maybe reflash the rom. I was careless and accidentally flashed on the verizon version on my gsm device. Now stuck with the bootloop problem etc.
I turned on USB debugging before all this factory reset/wipe business so will it still be on after all this? If so, I can maybe try and reinstall drivers etc and all that stuff to maybe get it recognize but so far nothing is recognizing it so I'm starting to doubt whether USB debugging is still on. Sorry for the long text! Just wanted to make have as much detail.
UPDATE:
Phone has been fixed! The phone wouldn't be recognized on any of my windows computers but was instantly seen on my friends macbook pro. I just went adb sideload and flashed on the new rom and its all good now. This thread can be closed now. Thank you!
I had this issue at one point where I didn't have anything to flash after rooting and flashing the recovery and all. The ad sideload did not recognize my phone either. What I was able to do is an ruu flash to stock. I am not as experienced with it so I would suggest asking someone else for specific instructions on it.
Sent from my dlx using xda app-developers app
maceprimus said:
I had this issue at one point where I didn't have anything to flash after rooting and flashing the recovery and all. The ad sideload did not recognize my phone either. What I was able to do is an ruu flash to stock. I am not as experienced with it so I would suggest asking someone else for specific instructions on it.
Sent from my dlx using xda app-developers app
Click to expand...
Click to collapse
Thank you so much for your help but I managed to fix it with my friends mbook pro!
I got the one Max on saturday and went online sunday to root it and maybe get a rom installed on it.
Got it rooted, then was getting ready to go to sleep when I restarted the phone now it has S-off, but no root and will only boot up to a picture of a battery with the red triangle and exclamation point on it.
I got Clock work mod and I can sometimes get ADB to work-- I push a rom over, it says it installed, but then at restart it goes back to the red triangle.
any help would be greatly appreciated.
Got Nusense as the only ROM to install-- tried VZW stock recovery adn also the ViperRom, but they error out after waiting 30+ minutes to adb transfer/ sideload.
Thanks for any help.
Zimoss said:
I got the one Max on saturday and went online sunday to root it and maybe get a rom installed on it.
Got it rooted, then was getting ready to go to sleep when I restarted the phone now it has S-off, but no root and will only boot up to a picture of a battery with the red triangle and exclamation point on it.
I got Clock work mod and I can sometimes get ADB to work-- I push a rom over, it says it installed, but then at restart it goes back to the red triangle.
any help would be greatly appreciated.
Got Nusense as the only ROM to install-- tried VZW stock recovery adn also the ViperRom, but they error out after waiting 30+ minutes to adb transfer/ sideload.
Thanks for any help.
Click to expand...
Click to collapse
how come you got s-off but just rooting it? dont make sense.
abd push rom? why? install twrp recovery and boot in recovery, mount usb with usb lead and copy rom to phone and then use recovery to flash rom!
Hello,
I have an S-on 4g LTE unlocked with bootloader and running Viper 2.2. I've been getting those annoying update messages, so I thought I'd try a different ROM. I tried to switch to the Avatar ROM on the forums: http://forum.xda-developers.com/showthread.php?t=2207395, but I couldn't get it to take. I read somewhere that I needed to extract and load the boot.img file through ADB first, so I did that but it still didn't take. I could install the ROM, but I can't get it to boot past the "HTC: This build is for development purposes only" screen. It hangs there for a while, then the screen goes black, and eventually it loops back.
So then I decided to just go back to Viper 2.2, but that won't take. It's doing the same loop-back. I did a full backup before starting, so I tried restoring that but it made no difference. I thought maybe I needed to do the adb boot.img thing again using the boot.img file from the viper 2.2 file, but there's no boot.img in any of the viper files I have. So I tried looking on the forums, but all the boot.img file links I found were expired/dead/long gone.
So I need some help in figuring out how to get this phone back. I can get it out of the bootloop by pulling the battery and then do hboot via the downvolume + power button, and then I can get into teamwin recovery from there. But after that, I don't know what to do. Any advice/help to get back on my feet would be greatly appreciated!
Nevermind...got it! I tried installing the stock kernel from here http://forum.xda-developers.com/showthread.php?t=1770978 and it booted back up finally.
I kind of thought that's what I needed to do, but I was at the point where I didn't want to keep touching (or more like breaking!) more stuff until I knew what to do. Thanks anyway!
I made a stupid mistake when unlocking my DNA and flashing a custom ROM (ViperDNA 4.1). I ran the rumrunner S-OFF which seemed to go without flaw. The mistake I made was checking to see if root installed which I'm assuming now it didn't. I installed Clockwork Recovery on it and booted into recovery and installed ViperDNA which gave errors. When I rebooted I was stuck at the boot splash. I tried an unbricking method posted on YouTube that required going into Fastboot USB and running an OEM Lock command and then using HTC's ROM update utility to reflash stock back to it which failed. I've rooted and flashed recovery to a lot of devices so I wouldn't consider myself to be a total noob but I'm at a loss here. Any help would be greatly appreciated! :fingers-crossed:
Black htc screen with triangles on each corner
Man I really need help. ...I tried to flash and something went wrong to where I erased the entire os and I continued to fix this issue because all I had access to was twrp(custom rom) and bootloader. then what was crazy is that it appeared that based on the fact that I was on 4.4.2 kit kat that I was unable to fix it. after researching I found a ruu that didn't have the boot image so I flashed the factory ruu with no boot image and my htc scrren with the status bar filled all the way up but it never moved off of that screen I assume because that ruu didn't have the boot image so I thought that common sense would be to at one of the boot images that I had to the zip file of the ruu without the boot image....that's when I made things worst and now im stuck on this htc screen with the four triangles...my pc wont detect my device and im in need of some serious help....can you help? can anybody help?
I believe i can help!!!
jazoon said:
i made a stupid mistake when unlocking my dna and flashing a custom rom (viperdna 4.1). I ran the rumrunner s-off which seemed to go without flaw. The mistake i made was checking to see if root installed which i'm assuming now it didn't. I installed clockwork recovery on it and booted into recovery and installed viperdna which gave errors. When i rebooted i was stuck at the boot splash. I tried an unbricking method posted on youtube that required going into fastboot usb and running an oem lock command and then using htc's rom update utility to reflash stock back to it which failed. I've rooted and flashed recovery to a lot of devices so i wouldn't consider myself to be a total noob but i'm at a loss here. Any help would be greatly appreciated! :fingers-crossed:
Click to expand...
Click to collapse
look at my situation (right below yours) i just got myself out of that situation everything is back to stock and at least i have a fresh start...whats your current status?
CHRIST STARZ said:
look at my situation (right below yours) i just got myself out of that situation everything is back to stock and at least i have a fresh start...whats your current status?
Click to expand...
Click to collapse
I had the same problem last night. I couldn't get fastboot to work properly and thought I was screwed. Here is what I did:
I downloaded a stock rooted rom and put it on a flash drive. I used my USB OTG cable and booted into recovery. I then mounted the external drive and flashed the stock 4.1 rom back on it and that cleared it up. I haven't re-tried to flash the ROM I tried, but I think my issue was an old recovery version.
Once you get back to stock, update or change your recovery to a new one and then try again would be my suggestion.
If you don't have an OTG cable, I'd suggest at a minimum order one for when it happens again