hey folks, yesterday i flashed a new rom, during flash i got an error (dont rember which one). i flashed a few other roms didnt work also, so i flashed a new recovery. i rebooted to recovery but i dont get anything except the oneplus logo. i dont have a recovery or os. i can get into fastboot. i already flashed a few recoverys with fastboot. my recovery flashed succesful with fastboot. the problem is i cant boot into recovery. not with commands with fastboot, not with the volume buttons. so please help me because my phone is unsuable now.
i used this guide (i cant post links) so youve just bricked your oneplus one, reddit
i did all the steps of soft brick cant acces recovery. everything goes succesfully except booting to recovery.
nathan_b87 said:
hey folks, yesterday i flashed a new rom, during flash i got an error (dont rember which one). i flashed a few other roms didnt work also, so i flashed a new recovery. i rebooted to recovery but i dont get anything except the oneplus logo. i dont have a recovery or os. i can get into fastboot. i already flashed a few recoverys with fastboot. my recovery flashed succesful with fastboot. the problem is i cant boot into recovery. not with commands with fastboot, not with the volume buttons. so please help me because my phone is unsuable now.
i used this guide (i cant post links) so youve just bricked your oneplus one, reddit
i did all the steps of soft brick cant acces recovery. everything goes succesfully except booting to recovery.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B-ikULjZZlloNHpOdVBrTzQxZzQ/view
Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.Disable any antivirus otherwise you'll get false alarms.The program should automatically boot your device to recovery.
im amazing
wow im so glad. i unzipped a rom and flashed each file one by one and it works its fixed!!
Related
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
First for the One XL it is suggested you use TWRP and not CWM
You can get it here from their website .
It tells you how to fastboot flash it.
If you did an OTA to 2.20 or your device came with 2.20 you probably need to flash the boot.img /kernel
So in your CM10 zip, extract the boot image.
and use fastboot to flash the boot img with the command
fastboot flash boot boot.img
and that should help you out.
I also suggest reflashing the rom with TWRP just in case. Hope this helps.
Can adb see the phone?
FrustratedAndConfused said:
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
Click to expand...
Click to collapse
This is the one xl correct, not the international on x?
If you can get anything on your screen, your phone isn't hard-bricked.
First, which phone do you have? ClockworkMod Touch Recovery does not work on the AT&T One X (One XL). If you tried flashing a ROM through it, it's not going to work and it's probably not booting up because the ROM is corrupted.
I would start with flashing a new recovery in adb. Use TWRP, because even the basic CWM is not supported for this phone and can cause issues.
Can you get into recovery? If so is the SD card mountable?
First time I flashed i had a similar issue where the SD couldn't mount. I ended up having to run the factory RUU after relocking the bootloader & then start again. I waited for a later nightly to come out. Also seems to go better if you flash a different rom first like viper.
NismoR31 said:
Can you get into recovery? If so is the SD card mountable?
Click to expand...
Click to collapse
Doesn't matter. He flashed the wrong recovery (not for our phone). There is not Touch CWM for our version.
i should really refresh pages before replying
Question on rooting.(Not bricked lol),so about a week ago I got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before rezipping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
WhatTheAndroid? said:
So about a week ago I rooted my phone,got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before recapping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
Click to expand...
Click to collapse
I know it happened for me -- Sometimes it wont enter recovery for me even in the bootloader and I have to Power+Vol Down to get it back into the bootloader. But it makes sense this would be a normal process because if you flash the boot.img without any OS files to load after it will just boot-loop.
Once I get back into bootloader and can get back into recovery and flash the ROM everything goes well after -- although I'm not sure if you would classify this as the "norm" but it certainly happens for me
WhatTheAndroid? said:
Question on rooting.(Not bricked lol),so about a week ago I got into bootloop because I flashed boot.img when I took it out of the Rom file. I want to know if bootloop is normal when you flash the image file before rezipping the Rom and installing the Rom via teamwin recovery. I'm unrooted and boot is locked so I don't need any help with that. so I just wanted to know if I followed the right process. I have read many threads and never seen anything about bootloop being a normal process when flashing boot.IMG before getting into recovery and installing a ROM. Thanks in advance for anyone providing me an explanation.
Click to expand...
Click to collapse
I didn't have a bootloop. Mine just sat on the first htc bootscreen and did nothing. I had to do a simlated battery pull to get it to shut off. Generally I flash the rom in recovery then reboot to fastboot and flash the boot.img. This way you don't have to worry about the bootloop or simulated battery pull.
your just supposed to extract the boot.img not the whole rom. you should never be rezipping anything. if you are on windows i hope your using a real archive utility like 7-zip or winrar. just open the zip and drag the boot.img out which extracts it. flash the boot.img in fastboot then flash the rom in recovery.
getting into recovery from bootloader can be a problem at times but i haven't had this problem once since changing over to twrp 2.3.1.0.
hi,
i unlocked the htc one s c2 s3. i got twrp 2.5.0.0 recovery....i tried to flash a custom rom. bootloop....tried again but now with factory reset...all files are deleted. i only got a rooted device with a custom recovery, but no rom at all.
what can i do now? i found a tut here, how to push a rom via adb. i cant do that, cause i havent got cwm on my device and i cant find this at all. (ville only, ville2 cant find it )
tried to flash the ville cwm...recovery doesnt boot.
what can i do now guys
so long
taker-` said:
hi,
i unlocked the htc one s c2 s3. i got twrp 2.5.0.0 recovery....i tried to flash a custom rom. bootloop....tried again but now with factory reset...all files are deleted. i only got a rooted device with a custom recovery, but no rom at all.
what can i do now? i found a tut here, how to push a rom via adb. i cant do that, cause i havent got cwm on my device and i cant find this at all. (ville only, ville2 cant find it )
tried to flash the ville cwm...recovery doesnt boot.
what can i do now guys
so long
Click to expand...
Click to collapse
do you have access to fastboot mode?
if yes flash the right recovery.img for the S3 Variant which you can get here
http://teamw.in/project/twrp2/100
if you flashing a rom, flash the boot.img afterwards.
you can do it with
fastboot flash boot boot.img
should be adviced in the instructions..
i got it now. thx m8
yea, i flashed now twpr 2.5.0.0 over cmd with adb. than i mounted in the recovery the sdcard, on windows i formated the storage in fat32. than copied my rom onto it. now i got my flashable zip on the device again. i done a factory reset, flashed the rom, rebooted to the bootloader, clicked on fastboot and flashed the boot.img over cmd with adb.
works like charm
best regards!
Good evening!
Just wanted to update my girlfriends mi4i from an Kitkat Ferrari rom to a newer one. I had an older twrp on the phone, the one that came with the toolkit for mi4i. For the newer rom i should have at least twrp 2.8.7.. . I found a ferrari twrp 2.8.7 and flashed it per flashify. All went fine. Rebootet all worked. So i wanted to install new rom. In recovery i did n factory reset, which didnt finish. I had to abort it after 15min.
Since then, device wont boot beyond bootscreen. When i try to boot into reovery, i just enter fastbootscreen.
I thought, ok t least fastboot. But when i try to flash any recover through the toolkit, it seems lime all is going well (no errors) but it does not upload the file.. It says in 1,4seconds.. File was sent.. Which is definately wrong 30 mb in 1,4seconds.
Is there anything left i can do?
No working recovery and no working fastboot does sound fuctup?
Thanks for reading
Flash MIUI via Fastboot, it should be fine.
BTW You can never install MIUI via Custom Recovery.
Just to finish. Was able to do a fastboot rom flash.
Worked. Solved
:crying:
phone wont enter recovery mode I dont know what to do i flashed N based rom it went into bootloop. I was on 3.0 TWRP. Flashed M based ROM, it worked. I decided to give N ROM another chance it didnt flash gave me some error
I tried to enter Recovery again now I just cant. it get stuck on OPO Logo. I can reboot normally and use the M ROM but I cant boot into recovery to flash anything.
Here's a list of stuff I tried and didnt work
1. Flashing Old versions of TWRP through fastboot and flashify and TWRP Manager
Ive tried these versions
twrp-2.7.0.0-bacon
twrp-2.8.0.0-bacon
twrp-2.8.5.0-bacon
twrp-2.8.6.0-bacon
twrp-3.1.0-0-bacon
I even checked to find that the bootloader is unlocked. I was really relieved cos i didnt wanna lose all my data.
2. I've tried Fastboot boot recovery command which gives "Failed (remote: DTB not found)". i googled and flashing older recovery was the only answer I found. which I already did. Any other ideas?
EDIT: I would like to add and clear the fact that the recovery flashes without errors but it just wont boot.