Related
Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.
mrwizard65 said:
Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.
Click to expand...
Click to collapse
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.
HTC_Phone said:
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.
Click to expand...
Click to collapse
I don't believe the computer is recognizing it at all. I'm not hearing the normal "ding" I get when it reboots.
first turn the phone off by holding power button for a longer time, then turn it on by holding both power and volume down buttons for a couple of seconds to enter bootloader
Did you install the Rom? Or just the boot.img?
Sent from my VENOMized HoxL
Alright, so holding down the volume button did get me into the bootloader. I tried the recovery and was able to recover using TWRP, but when I reboot it brings me back to the same HTC screen. So again, now I am able to do things via the bootloader so hopefully there is a next step to fix this.
To answer your question, I did not get to install the ROM, only the boot.img
Thanks for everyones help so far.
So go to twrp and install the Rom
Sent from my VENOMized HoxL
area51avenger said:
So go to twrp and install the Rom
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Ok, went ahead and loaded up Viper 3.2.2 and it seemed to go fine. Rebooted and am at the same HTC logo screen with the "this build is for development....." It will keep rebooting into this screen several times and will hang.
I did get the tampered/unlocked notice on the bootloader before doing all this. Not sure if that makes a difference or not.
Thanks for any additional help.
Did the ROM install correctly? Flash the boot img in adb again.
pOLLYpOCKET said:
Did the ROM install correctly? Flash the boot img in adb again.
Click to expand...
Click to collapse
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
I thought you wouldn't be able to install RUU if your bootloader is unlocked. But anyway, try this thread instead http://forum.xda-developers.com/showthread.php?t=1732980
I'm glad to report that I was finally able to flash the 3.2.2 Viper ROM. I was having problems unlocking the phone again, but just did it via fastboot command line. Once that was done it was smooth sailing.
I do have a couple of issues with the Viper ROM, but all in all it's fine and I'll post those questions in the Viper thread.
Thanks again for everyones help!
mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
Re-unlocking is a *****. Took me about 80 tries. Reboot phone, reboot pc, keep trying. Eventually it will work. You didn't need to run the ruu.. You may just want to keep the phone in stock state if this seems complex to you.
Sent from my One X using xda app-developers app
go into bootloader manually then plug phone to pc. works first time to unlock.
Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc
To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks
Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.
I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/
Hi everyone,
I am trying to help a buddy out and getting his phone working. The phone is not rooted in any way shape or form.
Here are my issues
The phone will not boot into the stock rom. I can get it into the bootloader. Which I went to htcdev. To unlock the bootloader. Followed the steps and was able to get the phone screen to show unlock bootloader. But when I hit yes it reboots and stays on the white htc screen. Then it will keep rebooting. When I go back into bootloader. It still shows the bootloader as being locked? Any suggestions. I haven't flashed anything in about 3 years. But only Samsung things.
This is my set up
Your best bet is to try latest RUU: http://www.htc.com/us/support/htc-one-sv-boost/news/
I tryed that as well. Thinking it is kinda like Odin for samsungs. But as soon as it try to reboot into bootloader. It stays on the white htc screen
The RUU was running completely through and it still not booting?
I will take a picture of the screen. It does not go all the way through. Also I tryed the Ota. Zip. And changed it to PL80IMG and placed it in my SD card. It looked as if it went through and it told me to reboot. But still nothing.
This is what's happening.
Forget the OTA. It won't solve anything for you.
I also think, your bootloader must be locked to run the RUU.
And i think it is your only chance to get the phone back running, because there is no stock rom or backup for boost (as far as i know).
I am OK with rooting it. But in order for me to do it I have to get the bootloader to unlock which I can't seem to do. It does all the motions to unlock. Until the phone reboots
What i have found in this few minutes, Error 171 should be a driver issue.
So, you should make sure that the correct drivers are running (HTC Sync). Maybe another PC could be also a good try.
And you can't root a phone which is not booting into OS. You need a OS.
Is there different drivers I could try besides tc sync. I have tried both computers that I have one has windows 8. The other has windows vista.both have htc sync on them. Also tried a different cable.
If I type in cmd fast boot devices it shows my device being connected. The error shows up while it is waiting for the boot loader to reconnect
Latest should be this.
I will give it a try thank you for helping me. I'm banging my head against the wall for 2 days trying to figure out why nothing is working on this.
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
old.splatterhand said:
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
Click to expand...
Click to collapse
Yea, my main goal is to get it to boot up. I was hoping it was an easy fix. Like with the Samsung epic I had. Just slap it in with odin and boom. after I couldn't get the RUU to work I figured I would try to root it. but since I can't even get the bootloader to unlock. I am stuck and that's the biggest reason I posted. normally I wouldn't I try to read other post and/or youtube it to find someone with a similar problem.
Quick question. When I go into the RUU can/should be in fastboot?
Yes, you should be in fastboot (USB) mode.
Ok so I downloaded the drivers you recommend. It was different then the ones I had. I also downloaded the RUU from the htc site as well just in case. Will try when I get back home. Thanks again.
So here is what I have. I downloaded driver v4.11.0.001. And installed. Downloaded ruu k2_cl_jb_45_s_sprint_wwe_boost_3.05.653.4......
I went into cmd and type fastboot devices. My device showed up. Ran the ruu. Samething happened. The ruu stops because when the phone reboots. It doesn't reboot to the bootloader.
Also I tried in cmd to get the phone to reboot to bootloader with no luck. Is there any thing else I can try?
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Hmm i installed the latest verison of twrp with my mac via fastboot ( followed directions from twrp site for the commands). I would try to get adb/fastboot to work on your mac first and maybe try to fastboot flash twrp again? and if that does not work i would just do a RUU honestly, but i'm sure someone smarter than me can chime in and get it resolved . For instructions to install adb/fastboot on a mac i followed this http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/ If it does not recognize your device try installing htc sync manager.
darthnix said:
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Click to expand...
Click to collapse
You could go find the ruumode-flashable recovery that I think is in one of dottat's ruu threads (5.0.1 one I think). Then change the name of the file to 0p6bimg.zip and flash it in bootloader. That should flash twrp to a phone without adb/fastboot.
I've followed every guide possible and I end up in the same spot almost everyone else ended up that I can see, and that's after flashing TWRP, it stays stuck on your device is booting up.
I read on TWRP's site that sometimes phones auto write over it so you have to boot into recovery right after typing in fastboot reboot but that never works.
I've seen some TWRP's are dedicated to Honor 8, and that didn't seem to work.
https://twrp.me/devices/huaweihonor8.html
I got
twrp-3.2.1-0-frd.img
I flash it at the white bootloader screen. and that's as far as I can get, it never goes into TWRP.
Am I missing a step here?
My guess is that your bootloader is locked. It's literally a click of a button to install, and the only thing that would block that is a locked bootloader.
Nah, it's the screen that says "your device cannot be trusted because it's unlocked" or something like that and at the bottom it just stays at booting up. I've done everything and it never goes into TWRP as if it never flashed in, even though the adb command screen said it did.
[edit] Well, it finally worked, I just kept doing the same thing over and over and it finally took. No idea why lol. Now it's just not wanting to take SuperSU. It starts flashing then immediately restarts, looks like it stops on the "creating image" part?
I had the same trouble but I installed an older version of TWRP and it worked fine with B405.
zinko_pt said:
I had the same trouble but I installed an older version of TWRP and it worked fine with B405.
Click to expand...
Click to collapse
That's what I ended up doing, supersu wouldn't flash so I used that other new popular one and started right up.
Use Huawei Multitool