Hi all,
I have a brand new OPX imported from China. I tried installing TWRP 3.0.2.0 through fastboot, and apparently the installation went fine. Except that when I try to boot on recovery, I'm stuck on the OP splash screen and nothing happens.
I tried with CM14 recovery, and I get the exact same issue.
So I installed CM13 recovery (latest version), and then CM13, and everything is working fine. But I can't update to CM14 (CMrecovery just tells me "install failed", and the recovery log shows one apparently relevant line, which is "[ 1.282239] failed to stat /data/media/0/cmupdater/cm-14.1-20161221-NIGHTLY-onyx.zip: No such file or directory").
I also tried installin the latest CM14 through CM13 recovery, but I get the same problem I got with TWRP: stuck on splash screen, nothing happens.
Don't know if relevant, but as I'm stuck on splash screens, the phone does not respond to ADB but it does respond to fastboot.
I would really like to install the latest CM14 on it, but for the moment I'm stuck with CM13. Any ideas?
Thanks!
avilqu said:
Hi all,
I have a brand new OPX imported from China. I tried installing TWRP 3.0.2.0 through fastboot, and apparently the installation went fine. Except that when I try to boot on recovery, I'm stuck on the OP splash screen and nothing happens.
I tried with CM14 recovery, and I get the exact same issue.
So I installed CM13 recovery (latest version), and then CM13, and everything is working fine. But I can't update to CM14 (CMrecovery just tells me "install failed", and the recovery log shows one apparently relevant line, which is "[ 1.282239] failed to stat /data/media/0/cmupdater/cm-14.1-20161221-NIGHTLY-onyx.zip: No such file or directory").
I also tried installin the latest CM14 through CM13 recovery, but I get the same problem I got with TWRP: stuck on splash screen, nothing happens.
Don't know if relevant, but as I'm stuck on splash screens, the phone does not respond to ADB but it does respond to fastboot.
I would really like to install the latest CM14 on it, but for the moment I'm stuck with CM13. Any ideas?
Thanks!
Click to expand...
Click to collapse
Can you please describe which build date of cm 13 you are using right now?
I am using the latest CM13 available for my device (onyx), which is CM-13.0-20161219-NIGHTLY-onyx.
The next CM for this device is a CM14.
avilqu said:
Hi all,
I have a brand new OPX imported from China. I tried installing TWRP 3.0.2.0 through fastboot, and apparently the installation went fine. Except that when I try to boot on recovery, I'm stuck on the OP splash screen and nothing happens.
I tried with CM14 recovery, and I get the exact same issue.
So I installed CM13 recovery (latest version), and then CM13, and everything is working fine. But I can't update to CM14 (CMrecovery just tells me "install failed", and the recovery log shows one apparently relevant line, which is "[ 1.282239] failed to stat /data/media/0/cmupdater/cm-14.1-20161221-NIGHTLY-onyx.zip: No such file or directory").
I also tried installin the latest CM14 through CM13 recovery, but I get the same problem I got with TWRP: stuck on splash screen, nothing happens.
Don't know if relevant, but as I'm stuck on splash screens, the phone does not respond to ADB but it does respond to fastboot.
I would really like to install the latest CM14 on it, but for the moment I'm stuck with CM13. Any ideas?
Thanks!
Click to expand...
Click to collapse
if you unlock your bootloader then definitely latest twrp 3.0.3 works fine and flash cm14 and arsenic kernal using it.
first you install the rom using twrp 3.0.3, then install arsenic kernal, after that flash gapps. This works fine for me. Maybe you can`t unlock your bootloader check using : fastboot oem device-info in the fastboot mode. Or you are using older bootloader. See this
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Arsenic kernel:http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
This is what 'fastboot oem device-info' tells me:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
And I still can't install any TWRP. I mean fastboot will tell me the install is successful, but trying to boot TWRP (or CM14 recovery) gets stuck on Android [1+] logo.
Related
I upgraded my OnePlus X today with the community build OxygenOS 3.1.0 using TWRP. There was an error saying that my device was not "OnePlus" but "ONE". So I edited the updater-script and replaced the word "OnePlus" by "ONE" in getprop line and successfully installed the ROM.
Then I connected my phone to PC, enabled OEM unlock and USB debugging, booted into fastboot and typed -
Code:
fastboot oem unlock
It said Okay, done...but there was not action on the phone screen. It stayed in Fastboot mode. I rebooted the phone and it was the same as before. I thought it was okay and continued with the process by booting into fastboot again and flashing TWRP with the command -
Code:
fastboot flash recovery twrp-3.0.2-0-onyx.img
It was successful. Then something weird happened when I typed -
Code:
fastboot boot twrp-3.0.2-0-onyx.img
The output was downloading image, okay. Then booting and the error FAILED(remote: dtb not found).
I tried manually entering the recovery mode, first by volume down + power button and then by advanced reboot menu -> recovery. All that happens is that it stays stuck in Oneplus Logo screen with powered by android written at bottom. I am able to boot into the OS.
I am sure that the image file is not corrupted as I have used the same before a couple of times. Still I tried flashing Stock recovery and a few other image files of the same version of TWRP. The same error comes up every time. Flashing is successful but booting is not. What should I do?
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is my recovery or bootloader corrupt?
I tried this code -
Code:
fastboot oem device-info
Output was -
...
(bootloader) Device tampered : false
(bootloader) Device unlocked : true
(bootloader) Charger screen enabled : false
(bootloader) Display panel :
(bootloader) console_enabled : 0
(bootloader) exec_console_unconsole : 0
OKAY [0.017s]
finished. total time : 0.018s
The problem is when I type -
Code:
fastboot oem unlock
Nothing pops up on my phone.
Maybe the reason is that I had a rooted version of OxygenOS 2.2.2 with TWRP but when I flashed the community build of OxygenOS 3.1.0 somehow TWRP was missing...
What should I do now? I am back at 2.2.2 now as the beta build didn't suit me. This error still persists. The first link above was stock recovery which did work. But I need TWRP back...
....................
Sorry to bother. Issue solved. It was already unlocked and this time flashing and booting in the image worked idk why...
arunmohan16 said:
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Thank you dude, i have been looking for this all day
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
tirlibibi said:
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
Click to expand...
Click to collapse
This guide will help you. http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 Use this mini tool, http://forum.xda-developers.com/showpost.php?p=64344611&postcount=4
Hi !
Recently, I noticed that I couldn't boot into recovery anymore (it gets stuck on twrp's logo). It's quite strange as everything else works just fine (normal works, fastboot too).
I tried to reflash recovery (from twrp 3.0.2-1 to 3.1.0-0), but still can't.
I'm running Resurrection Remix (based on Android 7.), rooted.
Someone had this issue too?
Nobody?
SamuelLeVentilateur said:
Nobody?
Click to expand...
Click to collapse
It's all OK in the dev options menu (usb deb ON and Unlock )?
Do you have a back up of the boot partitions?
Did you tried to flash OOS MM recovery ? Then TWRP again?
I tried both (USB debugging is on as flashboot works fine)
Nothing new :/
You might have a bootloader mismatch when you updated it for Nougat. Maybe try flashing it again?
I tried to find a link to download the bootloader, without success, do you have any?
I found the file of the new bootloader, but it seems that I can't flash it without TWRP :/
I tried many things, still can't boot in recovery one, nobody had this problem?
on which android version currently you are?
Hi, I know that's kind of a really big up...
Now, my phone is bricked (boot loop), and I still can't boot in recovery (flashboot still works).
Is my phone dead, or is there any chance to bring it to life again?
Thanks, and sorry again for this up :/
SamuelLeVentilateur said:
Hi, I know that's kind of a really big up...
Now, my phone is bricked (boot loop), and I still can't boot in recovery (flashboot still works).
Is my phone dead, or is there any chance to bring it to life again?
Thanks, and sorry again for this up :/
Click to expand...
Click to collapse
Via fastboot what's the output :
"fastboot oem device-info"
If unlocked = true , did you tried to reflash TWRP from here?
If = false : Megaunbrick guide..
Kéno40 said:
Via fastboot what's the output :
"fastboot oem device-info"
If unlocked = true , did you tried to reflash TWRP from here?
If = false : Megaunbrick guide..
Click to expand...
Click to collapse
It says "Device unlocked: true"
I tried flashing multiple versions of twrp, without success (the logo changes, so I guess the flashing worked), maybe I flashed wrong versions?
EDIT :
If it can help :
OS : Resurrection Remix v5.8.0 based on Android 7.1.1
Kernel : 3.4.0-Feather-X
Recovery : TWRP 3.0.2-1
Direct After flash twrp, reboot to recovery via power and vol - button
Use 3.1.1 official version
I'll try this
Still stuck on TWRP's logo (flashing seems to have worked as '3.1.1' is on the screen)
I guess my phone is actually dead so :/
Finally ! After looking on every corner of the internet, I tried to format cache and userdata via fastboot, reflashed twrp and it worked !
I really hope that this will help someone
Okay guys, I'm in full panic mode. I was just getting ready to reinstall my X with Lineage OS. I had CM 13.0 up until now. I've backuped everything, then powered off my phone (simple, normal power down).
After that I was trying to get into TWRP (I had 2.x.x.x installed), but VolDown+Power got me in a boot loop. The OnePlus Logo flashes, phone vibrates short then reset and it flashes/vibrates again. I tried booting normally, that doesn't work either.
The only thing I can do is get into fastboot, but I can't flash anything! The phone says it's locked (though I unlocked it before I put CM 13.0 on it)
Code:
c:\Android>fastboot flash recovery twrp-3.1.1-1-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (16002 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.509s
c:\Android>fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
c:\Android>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
Help! I can't boot my phone and I can't flash anything either. Is there anything I can do or missed?
After 2 hours of trying everything I found I'm now at a point where I could install the original (?) recovery via the MSM DownloadTool 2.0.2. Now I have a recovery which looks like stock... I can "Install from local" and "Install from USB". Tried the latter and I get the "adb sideload" mode. Tried to upload the latest Lineage OS Nightly through this sideload, but it fails after 47%.
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
intoxicated.mad said:
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
Click to expand...
Click to collapse
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Anyway you got out of trouble ??
I have the exact same problem, only I am running Sultan's ROM. Unfortunately, my phone is not backed up, because I wasn't going to install a new rom or anything. Is there any way to restore my phone without losing data. I downloaded the MsmDownloadTool V2.0, and am wondering if I could replace the stock recovery.img in there with the one for my ROM, or would this not work?
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
drunken_m said:
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Click to expand...
Click to collapse
I also faced that issue too and it happens when you have installed custom rom or recovery without first unlocking the bootloader. Do It Now If you haven't
Actually the bootloader was already unlocked (I needed that to install CM in the first place), but I think I accidentally re-locked it when I tried to remove root (to install a banking app).
As I wrote I already fixed the issue by installing the original bootloader/recovery and OOS over a serial link, then unlocked the bootloader again and installed the latest TWRP And Lineage. So all is fine now.
adamantiumXT said:
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
Click to expand...
Click to collapse
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
drunken_m said:
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
Click to expand...
Click to collapse
I have to agree, but I wasn't flashing when the phone decided to brick itself , so I didn't have a recent backup. In the bricked state I could only access fastboot mode, not recovery . I ended up copying what I could from the internal storage partition (which basically had everything I needed anyway), then clean installing a new ROM, and restoring my files.
For anyone else who gets into the same situation, I recommend that you make sure to not turn on WiFi or mobile data after you dirty flash OxygenOS, and remove your Google account. This will mean that Google's backup of your phone and apps (if you turned that feature on) will be of your working setup. As I tried to use Google Play in the messed up system, Google decided to replace my backup with the bad config so I couldn't restore in the new ROM - although looking at the Google Drive app now, the good setup is backed up, only I have no way to restore it
Maybe I have the same problem, not sure. I can't boot the phone. Holding vol down + power only makes the phone reboot over and over until I let go. It turns off afterwards, never enters recovery mode. I can access fastboot mode, but my bootloader is locked so I can't flash anything. Any suggestions?
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
All, I got a cheap LG G5 (H850) recently which was declared bricked by the previous owner. LineageOS and TWRP were previously installed but something seems to have gone wrong during an upgrade. It boots only into the fastboot menu and is not recognized by "adb devices". I can "fastboot flash recovery twrp-3.5.2_9-0-h850.img" just fine (at least, without an error message), but can't seem to get it to boot to TWRP using Volume down - Power (tried many times - the device is known for being a bit picky about the timing).
Any idea what I can do to save the thing from getting scrapped? TIA!
In fastboot, adb commands won't work (hence "fastboot").
Have you tried fastboot boot twrp-3.5.2_9-0-h850.img, to get the device to boot TWRP for you (without installing)?
Didgeridoohan said:
In fastboot, adb commands won't work (hence "fastboot").
Have you tried fastboot boot twrp-3.5.2_9-0-h850.img, to get the device to boot TWRP for you (without installing)?
Click to expand...
Click to collapse
Yes - it says
Code:
downloading 'boot.img'...
OKAY [ 0.598s]
booting...
FAILED (remote: unknown command)
flurryman said:
.... - the device is known for being a bit picky about the timing).....
Click to expand...
Click to collapse
It really is.
Had to flash several times the TWRP before I could access it.
Each time you try but aren't successful the old recovery gets revived and then you need to flash TWRP again.
Keep on trying.
Btw it's easier if you rename the "twrp-3.5.2_9-0-h850.img" to just "recovery.img".
Hm... Maybe that's not possible on your device then (I know nothing about LG, unfortunately).
@flurryman just another hint:
after flashing TWRP I usually just pull the battery to have in my hand when it restarts.
OK I finally managed to reboot into TWRP again, re-flashed LineageOS, OpenGApps and Magisk, and now I get the dreaded TWRP bootloop.
flurryman said:
OK I finally managed to reboot into TWRP again, re-flashed LineageOS, OpenGApps and Magisk, and now I get the dreaded TWRP bootloop.
Click to expand...
Click to collapse
What about if you don't flash Magisk? It's a possible source of error... Start with a clean system, to eliminate as many variables as possible.
flurryman said:
OK I finally managed to reboot into TWRP again, re-flashed LineageOS, OpenGApps and Magisk, and now I get the dreaded TWRP bootloop.
Click to expand...
Click to collapse
You took the 64bit and pico version of OpenGapps?
Problem also if you flashed one at a time with intermediate reboots an testings?
On mine I took NikGapps64 +Magisk but it's on DotOS.
That's 64 bit nano, and I flashed LineageOS and OpenGApps in TWRP first, and then adb sideloaded Magisk without an intermediate reboot. OK I'll clean first one more time.
Oh wow. I explicitly wiped Dalvik, System, Data, Cache, and flashed LineageOS (09-25) and OpenGApps, and the thing booted! Please keep your fingers crossed!