Phone Potentially Bricked Please Help - OnePlus 3 Questions & Answers

So I've had a read through other threads on different sites and youtube videos etc.
Basically I was trying to root my phone using magisk following the video where TK roots a oneplus 5, but was switching out the software for the oneplus 3 version of twrp.
All was going well, connected phone to pc, unlocked it, copied the files across, flashed and installed twrp then when it rebooted after installing twrp it came up with an error saying that "dm-verirty" is not started in enforcing mode, and the phone wouldn't boot past that.
I relocked the OEM, as I couldn't get it to recovery mode (stock) so tried that and now I can get it into recovery mode.
It will happily go into fastboot mode, have tried reflashing stock recovery and trying to update the os via adb.
Have been looking at the Mega Unbrick Guide - but can't get my phone to show up on my pc to even begin there.
Would appreciate any and all help, plus tips for what to do after I get it back to stock as I'm still keen to root my phone but don't want to screw it up again and have to go through all of this again.

The Mega Unbrick guide is your best hope. Did you install all the drivers on your PC? Specially the Qualcomm ones? Also, make sure to press the volume up button like it says in the instructions for 40 seconds. Otherwise it doesn't show up. If all fails, try using a different PC.

Related

Bootlooping Galaxy Nexus

I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
rs18 said:
I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
Click to expand...
Click to collapse
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Jubakuba said:
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Click to expand...
Click to collapse
Thank you. I'm an idiot. It's been a long while since I've put this into recovery via physical buttons.
By the way, your guide is excellent. How have I not stumbled across this?

Galaxy Note 2- Stuck In TWRP After Factory Reset

Phone stuck in TWRP, can't access download mode after factory reset
Hello all,
My Samsung Galaxy Note II is stuck in TWRP 2.8.7 after I did a factory reset.
I initially followed this guide (wiki dot cyanogenmod dot org/w/Install_CM_for_t0lte) to install CM, which worked fine. I ran into a slight issue and decided I'd try to flash again as it was pretty easy. Turned out to be a mistake as I can't seem to do anything right now and am stuck in TWRP. Every combination of button and reboots I try just bring me back into TWRP. Plugging the phone in the computer recharges the battery, but the computer (running Windows 7) does not recognize the phone. ADB doesn't detect any device.
I tried a few times to reinstall the roms, to no avail as I was unable to boot into anything else than recovery. I then followed some guide and accidentally wiped the roms from the phone. As stated above, I can't access the phone through ADB so I am unable to push them back on the phone.
Please help, I would be immensely grateful. Thanks to all in advance.
UPDATE : I managed to get into download mode but adb says error:device not found when I try to push the roms in.
Thanks again
Are you stuck in TWRP (with access to the TWRP menu) or stuck ON the TWRP boot screen?
genuflex said:
UPDATE : I managed to get into download mode but adb says error:device not found when I try to push the roms in.
Thanks again
Click to expand...
Click to collapse
Download mode does not use adb you need odin or heimdall.

Phone soft bricked after applying software updates

Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.

Phone no longer bricked (yay!), but not fastboot

The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?

Blocked on Fastboot mode, please help

hello everyone,
After months and months of using different ROMs, I tried yesterday the RR rom, followed as always different steps & wipe, did install the ROM & Gapps, there was an error message, don't recall which one, but after it rebooted directly and arrive to:
Fastboot mode started
udc_start()
Now i'm unable to go back to recovery mode nor entering the Download mode with vol-/+ and USB or do anything else. Have i bricked it?
can anyone give me advice please?
What I'd try first - make sure your battery is charged (100 per cent preferable). If you can get it to communicate whrough ADB using some key combos, you basically won. You can just flash a stock ROM from there.
If your PC recognizes it as a G-Pad, yay for you. Use the LG Flash Tool to recover and flash a stock ROM (I assume you have the software, in case not just google it). If it's only connected to the PC discovered as a QHSUSB_DLOAD - refer to this thread and follow step by step - it might help you:
https://forum.xda-developers.com/lg-g-pad-83/help/how-recovered-lg-g-pad-detected-t3207079.
Really tho. Most problems can be helped by prperly and fully charging the tablet and trying the LG tools.
Cheers.

Categories

Resources