using Oneplus 3t.
TWRP 3.0.3-1
I've attempted to flash a custom ROM to my device, after I've installed using TWRP it says install successful; yet when I go to restart the phone I thrown into a loop between fastboot and a screen saying my oem bootloader needs to be locked.
when I go to unlock the bootloader after it locks I get into another loop where the device turns on, vibrates and then turns off and repeats this.
any help or ideas would be greatly appreciated, thanks.
Related
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
I had this issue, if you boot into bootloader does it say tampered? If not turn your phone completely off and then boot it into bootloader. Then you should be able to enter recovery. I ciuldnt enter recovery until my bootloader read tampered.
Sent from my HTC One using Tapatalk 4 Beta
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
blackplague1347 said:
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
Click to expand...
Click to collapse
Yeah it took me more then 10 tries until I just shut it off and then went into bootloader and there was the tampered. Glad it worked out for you.
Sent from my HTC One using Tapatalk 4 Beta
I had the same problem. I just did "adb reboot recovery" once and it worked, and it boots to recovery from the phone now every time.
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
im still having the same problem after allot of tries is there some sort of fix ?
Fastboot Tampered?
im still having the same problem after allot of tries is there some sort of fix ?
Click to expand...
Click to collapse
At the top of your devices when at the fastboot screen does it say Tampered?
Corey.C said:
At the top of your devices when at the fastboot screen does it say Tampered?
Click to expand...
Click to collapse
Yes mine says that. I am a new to this, what do i need to do
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted
So a while ago, I rooted my nexus 6 phone and along with it TWRP. So, today, I tried unrooting it, and in the process of doing this, I didn't notice something failed and after this, I locked the OEM, so now I can't unlock it. After doing this, my phone starts to boot, and the image for TeamWin Just keeps flashing, and when I try to go to recovery mode from the fastboot, it just tries to go to teamwin and the image for it just keep flashing as well. I have no idea what to do and I am really panicking. Could anyone please direct me to something that could fix this? I am limited in my knowledge involving fastboot and flashing custom ROM's so I need specific steps as to what to do. I really need help.
*Also, when I mean the image for teamwin keeps flashing, I mean the literal picture of the teamwin bootup keeps flashing on screen and nothing happens.
If you didn't select the lock bootloader option in Developer Options, then you should still be able to do the fastboot oem unlock. If you have, then I think you are out of luck...
Hello,
I've got a Wiko Jerry 2.
Wanted to root the device because the apps it comes with used up more then half the space.
So, Had some experience with Flashing, ADB and Fastboot with a other device.
Searched a tutorial and followed it.
Unlocked the bootloader, flashed and restarted the device.
It rebooted and showed the Android logo and Wiko logo, with orange code: warning your boot is unlocked and can't be trusted, reboot in 5 seconds. (It didn't reboot)
It stayed in this boot, removed the battery and went back into fastboot to flash the factory rom back.
After flashing the stock rom it ended in a bootloop with the same logo's and code orange.
Meaning it went wrong again. The problem I'm facing now is that I can't get the device in fastboot. not even with ADB.
ADB doesnt recognize the phone.
EDIT: The phone is showing in device manager. But it's refreshing the device manager every 2 seconds meaning the device is getting connected/disconnected every 2 seconds.
A bit lost here, someone got some ideas to try?
Thanks in advance,
Floeske.
recovery custom rom from wiko site official
Floeske said:
Hello,
I've got a Wiko Jerry 2.
Wanted to root the device because the apps it comes with used up more then half the space.
So, Had some experience with Flashing, ADB and Fastboot with a other device.
Searched a tutorial and followed it.
Unlocked the bootloader, flashed and restarted the device.
It rebooted and showed the Android logo and Wiko logo, with orange code: warning your boot is unlocked and can't be trusted, reboot in 5 seconds. (It didn't reboot)
It stayed in this boot, removed the battery and went back into fastboot to flash the factory rom back.
After flashing the stock rom it ended in a bootloop with the same logo's and code orange.
Meaning it went wrong again. The problem I'm facing now is that I can't get the device in fastboot. not even with ADB.
ADB doesnt recognize the phone.
EDIT: The phone is showing in device manager. But it's refreshing the device manager every 2 seconds meaning the device is getting connected/disconnected every 2 seconds.
A bit lost here, someone got some ideas to try?
Thanks in advance,
Floeske.
Click to expand...
Click to collapse
if your phone brick at restart try to download wiko Jerry 2 recovery custom rom you can find in the wiko official site web i resolve it but i have a problem twrp recovery touch dont respond
Hi All,
I am currently in the phone repair business. Well i buy as much as i can fix and sell on. Its all fun. I have a very nice one currently and looking to see if anyone has ideas. All i want to do is boot to recovery that is my current goal.
So phone clearly has corrupt installation, likely a flash Rom or update gone wrong. It boots to Huawei logo then reboots and that's all it does. Tried de-powering and all sorts including removing battery cable but to no luck.
There is no recovery mode
No download mode
Can get to fastboot but unable to run commands it seems due to FRP lock. I am not worried about FRP lock at this time, i only want recovery back.
Tried:-
All flash commands and all fail
Any attempt to get to receovery or download mode fails
All three buttons to force SD card boot fails
Currently trying to boot using SD card but seems i need to change boot devices from within recovery. Well it has no recovery mode so no luck there.
So it is pretty much a brick at this point and could be a write off but before I give up does anyone have any other ideas? maybe a FB command i can run with FRP lock and bootloader lock on?
Thanks
Karl