Hello friends,
I have an OPX and I did some mistakes with it during my attemp to update it to the latest Oxygen 3.1.3.
I had stock rooted 2.1.2 Oxygen OS with Kingroot and TWRP installed. I downloaded the zip of the ROM
for 3.1.3 from Oneplus and tried to flash it. It came up an error so I wiped system cache and data and tried again
but the same errors came up. Then I tried to flash the stock recovery .img file from TWRP to get the stock recovery
and try to flash the ROM from there. When I attempted to flash the stock recovery it asked me about the partition
I wanted to install it and I chose recovery.Installation seemed successfull and I rebooted to recovery.After that I had
no recovery and no system to boot.When I try to boot to recovery I only get the oneplus logo. When I try to boot to
system I get oneplus logo and "Powered by android" at the bottom. Fastboot mode seems ok. So I thought i could flash
everything back with adb BUT no tool or program recognizes correctly in any mode.In device manager of windows 10
the device is listed under "Kedacom Usb device" section with name "Android Bootloader Interface".
Please Help me.
zafiris said:
Hello friends,
I have an OPX and I did some mistakes with it during my attemp to update it to the latest Oxygen 3.1.3.
I had stock rooted 2.1.2 Oxygen OS with Kingroot and TWRP installed. I downloaded the zip of the ROM
for 3.1.3 from Oneplus and tried to flash it. It came up an error so I wiped system cache and data and tried again
but the same errors came up. Then I tried to flash the stock recovery .img file from TWRP to get the stock recovery
and try to flash the ROM from there. When I attempted to flash the stock recovery it asked me about the partition
I wanted to install it and I chose recovery.Installation seemed successfull and I rebooted to recovery.After that I had
no recovery and no system to boot.When I try to boot to recovery I only get the oneplus logo. When I try to boot to
system I get oneplus logo and "Powered by android" at the bottom. Fastboot mode seems ok. So I thought i could flash
everything back with adb BUT no tool or program recognizes correctly in any mode.In device manager of windows 10
the device is listed under "Kedacom Usb device" section with name "Android Bootloader Interface".
Please Help me.
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
cva_kabil said:
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
Click to expand...
Click to collapse
I have already tried to do this guide. Windows says the best drivers are already installed for this device and will not install the qualcom ones. Also the program just waits for a device to be connected to start the process of unbricking.Thanks for answering
zafiris said:
I have already tried to do this guide. Windows says the best drivers are already installed for this device and will not install the qualcom ones. Also the program just waits for a device to be connected to start the process of unbricking.Thanks for answering
Click to expand...
Click to collapse
But still u can acess fastboot right? Without any problem?
cva_kabil said:
But still u can acess fastboot right? Without any problem?
Click to expand...
Click to collapse
I think so, yes. When I enter fastboot mode there is the oneplus logo and "fastboot mode" written under it.
zafiris said:
I think so, yes. When I enter fastboot mode there is the oneplus logo and "fastboot mode" written under it.
Click to expand...
Click to collapse
Yes it is fastboot. now connect ur mobile to pc and type "fastboot devices" in adb cmd screen.. if it shows your device info,then u can flash stock recovery and make a fresh start.
cva_kabil said:
Yes it is fastboot. now connect ur mobile to pc and type "fastboot devices" in adb cmd screen.. if it shows your device info,then u can flash stock recovery and make a fresh start.
Click to expand...
Click to collapse
Yes i know. Whenever I type fastboot devices nothing happens. No device gets listed.
I had the same problem, but the Guide to Unbrick worked well.
Now, I cannot flash anything, because Fastboot doesn't recognize my phone. I'm stuck in stock.
cva_kabil said:
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
Click to expand...
Click to collapse
thank you very much this guide finally worked!! It was my mistake.I was booting first on fastboot mode and then plugging in the usb cable
whereas the guide says to keep pressing volume up and then plug it in which is was made it work!
zafiris said:
thank you very much this guide finally worked!! It was my mistake.I was booting first on fastboot mode and then plugging in the usb cable
whereas the guide says to keep pressing volume up and then plug it in which is was made it work!
Click to expand...
Click to collapse
Glad u did ?
Related
Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand
SOMEONE HELP ME PLZ
I was trying to flash rr rom but every time i flashed it it would appear a eeror 7 message so i tried to update twrp flashimg a .img file after that i reboted into recovery and now im stuck in the Leeco Recovery screen i ve already tried to flash it using prompt but still doesnt work and im stuck at bootloader too
Tekkerz said:
SOMEONE HELP ME PLZ
I was trying to flash rr rom but every time i flashed it it would appear a eeror 7 message so i tried to update twrp flashimg a .img file after that i reboted into recovery and now im stuck in the Leeco Recovery screen i ve already tried to flash it using prompt but still doesnt work and im stuck at bootloader too
Click to expand...
Click to collapse
I also have a problem with the latest version but I flashed the previous one and everything works now
LameMonster82 said:
I also have a problem with the latest version but I flashed the previous one and everything works now
Click to expand...
Click to collapse
i cant even with adb on my computer it says device null not found and i only can get into fasboot mode
Tekkerz said:
i cant even with adb on my computer it says device null not found and i only can get into fasboot mode
Click to expand...
Click to collapse
You can use fastboot to install an older version of the recovery
The command is
"fastboot flash recovery twrp-x.x.x.x.x.img"
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
maybe the bootloader got locked check otherwise erase and flash the whole rom using fastboot mi flash tool
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
asifzbaig said:
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
Click to expand...
Click to collapse
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Than it seems like yoir bootloader is locked.
Try using Xiaomi's Unlock Tool again, beware, it will wipe all of yoir internal storage as well.
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try edl mode to flash the full file and beware of anti rollback
karthik03 said:
Try edl mode to flash the full file and beware of anti rollback
Click to expand...
Click to collapse
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Doesn't try the fastboot flash recovery recovery.img, try fastboot boot recovery.img ,that can help
mjskraju said:
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
Click to expand...
Click to collapse
Use fastboot to edl it is present on xda or try shorting of pins
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Have you tried different PC? Mine works on Intel and have same error code on AMD.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
tnsmani said:
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
Click to expand...
Click to collapse
Seems like ryzen is the problem brother! I used another pc as i had no other options left
I am using Asus zenfone 3. And I have installed TWRP in it. But the phone is not booting to system (os) . And the TWRP I installed , the touch does not work for it. If I boot to system, it shows the boot logo and turns off. What can I do now?
LavanTech said:
I am using Asus zenfone 3. And I have installed TWRP in it. But the phone is not booting to system (os) . And the TWRP I installed , the touch does not work for it. If I boot to system, it shows the boot logo and turns off. What can I do now?
Click to expand...
Click to collapse
To me it seems that phone's boot-loader is got corrupted. Not unusual when installing TWRP.
jwoegerbauer said:
To me it seems that phone's boot-loader is got corrupted. Not unusual when installing TWRP.
Click to expand...
Click to collapse
Do u have any solution??
LavanTech said:
Do u have any solution??
Click to expand...
Click to collapse
Did you have enabled in Developer Options the USB debugging & OEM unlock features before the device bricked.?
LavanTech said:
I am using Asus zenfone 3. And I have installed TWRP in it. But the phone is not booting to system (os) . And the TWRP I installed , the touch does not work for it. If I boot to system, it shows the boot logo and turns off. What can I do now?
Click to expand...
Click to collapse
Also I cannot install with flash tool , I'm getting unhandled exception error!
jwoegerbauer said:
Did you have enabled in Developer Options the USB debugging & OEM unlock features before the device bricked.?
Click to expand...
Click to collapse
Ya! I eabled usb debugging , unlocked bootloader also OEM unlock.
LavanTech said:
Also I cannot install with flash tool , I'm getting unhandled exception error!
Click to expand...
Click to collapse
Re--flash Stock Recovery.
jwoegerbauer said:
Re--flash Stock ROM.
Click to expand...
Click to collapse
Both are enabled!!!
LavanTech said:
Both are enabled!!!
Click to expand...
Click to collapse
I've edited the cited post. Re-read.
jwoegerbauer said:
Re--flash Stock Recovery.
Click to expand...
Click to collapse
I have stock rom downloaded, which software can I use to flash ?? Pls give any link to download.
jwoegerbauer said:
I've edited the cited post. Re-read.
Click to expand...
Click to collapse
Pls provide me link for downloading stock recovery and software to flash!
LavanTech said:
I have stock rom downloaded, which software can I use to flash ?? Pls give any link to download.
Click to expand...
Click to collapse
To get rid off of TWRP you flash Stock Recovery.
I think the correct command sequence is
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery <STOCK-RECOVERY-IMAGE-FILE>
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
Search for the appropriate Stock Recovery image by yourself. GIYF ...
If you instead want to re-flash Stock ROM then the correct command sequence would be
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
fastboot flash-all <STOCK-ROM-IMAGE-FILE>
fastboot reboot
Try going back to stock (Fastboot/download mode/Odin, depending on the device)
Thank You!
I have successfully went to fastboot mode and flashed the stock rom! Thank you for your support!! ?? The phone is working now in the Android 7.
BUT,
now if i install twrp custom recovery, i don't know what happens, after restarting to system i cannot boot to system , it just shows the boot animation and just goes off or sometimes it boots to fastboot mode.
then if i flash the stock rom again using the sd card in the the default recovery mode after flashing that stock recovery, it works again.
Also if I install TWRP recovery, TWRP could not install any Roms ! it just says that Updater process ended with error 6 or 7 randomly.
So, how do I install custom recovery and roms in it now?
LavanTech said:
So, how do I install custom recovery and roms in it now?
Click to expand...
Click to collapse
Assumed the TWRP.IMG you use is the correct one, then there is no need to install TWRP recovery, booting into it is fully enough - this will preserve device's Stock Recovery
Code:
fastboot devices
fastboot boot <TWRP.IMG>
The TWRP is booting perfectly! But if I install any zip file i.e ROM or Mods, it says that Updater process ended with error 6 or 7!!
This is the problem with TWRP.
And, if install TWRP in the phone, then restart the phone , if I restart to system, it doesn't work ,just it shows the boot animation and turns off.
LavanTech said:
The TWRP is booting perfectly! But if I install any zip file i.e ROM or Mods, it says that Updater process ended with error 6 or 7!!
This is the problem with TWRP.
Click to expand...
Click to collapse
This is not TWRP recovery related, but it's related to the Custom ROM zip-file you try to flash: The ROM zip-file you try to flash isn't made for your device.
jwoegerbauer said:
This is not TWRP recovery related, but it's related to the Custom ROM zip-file you try to flash: The ROM zip-file you try to flash isn't made for your device.
Click to expand...
Click to collapse
I'm trying to flash ASUS ZENFONE 3 LINEAGE OS 16
MY DEVICE : ASUS ZENFONE 3 ZE552KL
THE FILE : https://mirrorbits.lineageos.org/fu...age-16.0-20200727-nightly-zenfone3-signed.zip
I am using the file which is for my device only! But it is not working, what should I do?
LavanTech said:
I'm trying to flash ASUS ZENFONE 3 LINEAGE OS 16
MY DEVICE : ASUS ZENFONE 3 ZE552KL
THE FILE : https://mirrorbits.lineageos.org/fu...age-16.0-20200727-nightly-zenfone3-signed.zip
I am using the file which is for my device only! But it is not working, what should I do?
Click to expand...
Click to collapse
Start a new thread ...
Here is the new thread
Here is the new thread :- https://forum.xda-developers.com/android/help/twrp-issues-asus-zenfone-3-t4145317
I recently found my old HTC desire 526g and I decided to flash a custom ROM, but its volume buttons aren't working so I had to use adb, I am not really an good in these types of things. I tried to flash TWRP on my htc using adb (Followed a YouTube tut) but this is coming up.
I have attached a screenshot below.
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Rajveer chauhan said:
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Click to expand...
Click to collapse
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
YourLocalClown69 said:
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
Click to expand...
Click to collapse
So if you're rooted so you can flash recovery via twrp app on playstore, or if magisk installer for twrp exists for your phone or by flashfire if you have your working recovery
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
LR7875 said:
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
Click to expand...
Click to collapse
This comes later now lol, Due to my lack of knowledge and not enough patience, I tried to flash custom recovery through TWRP app, and I didn't found my phone model on device list, SO i just selected random htc model phone and now it is restarting over and over again, Is there any fix to this? I am obviously a complete noob in this field.
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Rajveer chauhan said:
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Click to expand...
Click to collapse
Even If I find the this whatever you said, how am I supposed to fix it, as I mentioned,Volume buttons aren;t working and its stuck in bootloop, it won't past its manufacturers logo, so adb is no help in it, Only way to fix it would be to fix sound buttons. sad me, Well, R.I.P. HTC Desire 526g dual sim 2015-2021
I hope that this phone is not your primary driver
YourLocalClown69 said:
I recently found my old HTC desire 526g
Click to expand...
Click to collapse
Rajveer chauhan said:
I hope that this phone is not your primary driver
Click to expand...
Click to collapse
He unearthed his phone from some drawer, so this is not his daily driver.