The story begins when I had twrp. i flashed the oneplus_x_oxygenos_3.1.1_community_build usb debugging turned on, and oem unlocking. I was successful, I had stock oxygen OS but I lost twrp in doing so.
retried to install twrp, it did not work, when i tried going to recovery it's stuck on oneplus logo. i tried to fix it with this , did't notice it was for Oneplus 2, so.... hard bricked my phone, i was able to recover with this but i could not install twrp. so i installed the stock recovery MM which works now. OS does not work anymore. for some reason when i try to flash the oxygenos_3.1.1 with stock recovery, it still fails. even when i tried installing a lower version rom.
Can anybody help me? this is my daily driver phone. currently using my nokia feature phone for calls and texts......
what I have:
Stock recovery
nandroid backup that i cannot use because i don't have twrp,
usb debugging turned off,
and oem unlocking off.
can access fastboot, sideload.
no access to OS.
Hatred for Pokemon Go
yay it's alive!!
this worked for me! http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
moderator kindly delete my post. Thanks!
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Exodusche said:
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Click to expand...
Click to collapse
I guess some confusion might have been caused when it was posted on the OnePlus forums (and apparently a quote from a OnePlus rep) that the new build was "compatible" with TWRP. This was later clarified (by a poster, not OnePlus) to mean V41 of the blu-spark TWRP.
Chat with support confirms.
Kashaila said:
Sorry to keep you waiting. I apologize for the confusion. I have just confirmed from the specialist that TWRP is compatible with the new rollout.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...nity-beta-for-oneplus-x.464812/#post-15231909
Perhaps the mistake arises because it is not clear was that whilst TWRP is compatible, you couldn't actually flash the new community build with it! TWRP is only compatible (like you say) AFTER the flash!!
https://tapatalk.com/shareLink?url=...share_tid=3464987&share_fid=3793&share_type=t
[guide] unbrick device
This should help...
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
tjeus said:
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
Click to expand...
Click to collapse
Change computer.
Try with an old windows 7.
Or, try this: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Iirc, it's the same for Windows 10.
Sent from my ONE E1003 using Tapatalk
Himanshu Gusai said:
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Click to expand...
Click to collapse
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache etc.
Then i went to flash sultan(with twrp, can't remember the version but i think it was new one), i had to change update script in .zip file to ONE before i could flash it.
Then when it flashed i tried to restart but it said no system.
I decided not to restart and flash OOS 3.1.3, it flashed and restarted...but it was constantly restarting, logo would show and 1 sec after it would restart, and it stuck in a loop. No recovery, no fastboot...
With a guide above i managed to get it to install recovery and rom, but when booting, after loading android apps, it would just say finishing boot and restart again...
So i had recovery and tried to flash a new recovery but bootloader is locked, and cannot be unlocked because, oem unlock is disabled....
I tried to flash OOS 3.1.3 with stock recovery but after clicking YES for flashing phone turned off. When i tried to turn it on it only shows logo, nothing booting....
And now when i try to use MSM Download tool everything is done but phone still doesn't boot anything at all......now it won't even get to the part with loading android apps.....
Can anyone help?? Could someone please upload recovery.img and system.img that i could put in MSM folder, maybe if it would flash that files it would work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Ovakisan said:
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Click to expand...
Click to collapse
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Exodusche said:
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Click to expand...
Click to collapse
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Ovakisan said:
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Click to expand...
Click to collapse
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Exodusche said:
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Click to expand...
Click to collapse
The problem is that after going through guide, MSM downloader would say that its done, and it wouldn't boot in android, sou you can't get into developers options to enable OEM unlocking. And throught fastboot you can't do anything because its not enabled...
anyway if anyone is reading this that has same issue, just don't stop restarting, this little fu**** just managed to boot into android and i managed to get into dev options(after 3-4 restart, and 1 wipe cache data in stock recovery). after setting OEM unlock to enabled i tried to shut down phone through normal shutdown procedure but it got stuck, but force shut down with button worked and it saved OEM unlocking option on enabled. so i managed to unlock bootloader with fastboot.
So im with stock recovery now, lollipop ROM, should i try to flash OOS 3.1.3 now, or do i have to do something else prior to flashing????
I'm kind of scared now to do anything :'D
EDIT: ok, i ran into problem again -.-
twrp is flashed, latest. now when i try to flash cm13 or sultans cm13 i get this error.
http://imgur.com/a/BSpK1
I know there is few hundered threads with "unbrick" in title but I read them all and nothing seems to work.
Friend brings me kenzo that he gets since his cousin brick it while trying OTA.
When I power phone its start to load system and it has 3 stages:
1. Show screen with "powered by Android" and 3 dots in the bottom, usualy about 4 min and restart
2. After restart just get black screen with Mi logo in the middle, for about 30 sec and restart
3. Instead of Android with dots bottom have white line progres bar, it takes 4 to 5 min and restart again.
After that stage 2 and 3 repeat for long as you have nervs to wait .
Phone can get in recovery and fastboot mode. And when I put him in test mode just show test screen and cant do anything.
In fastboot mode MiFlash recognize phone but report "device is locked" (try with 20160401 and 20160830).
After that i put him in EDL mode (fastboot reboot-edl) and MiFlash report successful flash. But nothing changes.
I try flashing global stable v8.0.5.0, china stable v8.0.4.0, global dev v6.10.13 and at the end global stable v7.2.5.0.
Any idea welcome. Thx
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
banana_bender said:
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
Click to expand...
Click to collapse
Cant do that. Even unofficial unlock need phone to be working to enable USB debbuging and accept RSA kay from PC.
Edit: Right now looking for ways to edit boot.img to unlock bootloader in attempt to get any useful recovery.
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
abihary said:
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
Click to expand...
Click to collapse
I will try... but dont think it will do the job. Will post result little later.
EDIT
It dose not work, just as I think.
All that kind of method/advice need 2 things:
1. Enabled USB debbuging - You cant do that on bricked phone even if you edit boot.img ( ro.debuggable=1 ) because fastboot will not execute command since you will not have option to accept RSA kay from PC on your phone and complete that action.
2. Dev ROM - since you have to enable OEM unlock and that option you have only in dev ROMs. Even Xiaomi official unlock requires that you must do it on dev ROM and that is a reason for "stuck on 50% in unlocking".
I try all that I can think: edit boot.img file, use patch emmc_appsboot.mbn, use edited flash_all.bat and rawprogram0.xml, insert sTWRP and ZCX TWRP in fastboot ROM... and all combination of that. Did it on 7.2.5.0 and 8.0.5.0 stable and 6.8.18 dev (since its last 5.1 ROM that I have).
Most of this attempts ends with "3 stages" explained in the first post. Some just show Mi logo for few sec and restart, once even power off phone. And once I even get phone to go directly to sideload/recovery state showing picture of the phone and usb cable.
Only thing left now is to find info is there difference in accessing to EDL mode between software (reboot-edl), deep flash cable and testpoint. IMHO there is none or little difference. Since software and deep flash can be troubled with bad USB cable or connector or USB board in phone.
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
rohanzakie said:
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
Click to expand...
Click to collapse
If you can boot into bootloader, you can fastboot flash the images from https://developers.google.com/android/images (or just try running the entire N9F27N script) from your fastboot folder in cmd prompt or the Mac equivalent if you use Apple.
Sent from my Nexus 9 using Tapatalk
usb-debug is not enabled.
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Can you still access TWRP, if it was already on the device.
Flash any custom rom, enable the option and flash stock again (if you want).
If it is stock recovery, sideload an OTA image instead.
https://developers.google.com/android/ota
Manually boot recovery and you shouldn't need usb-debug enabled, I hope.
A bit of research and it is required unfortunately
Edit: You don't need usb-debugging for fastboot flashing.
Also Nexus Root Toolkit might prove helpful to setup drivers on your pc and restore your device to working order.
^^^ It is out of date software, so hesitant to recommend it.
rohanzakie said:
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Click to expand...
Click to collapse
Boot to bootloader and use fastboot commands. Fastboot flash system system.img
Etc.
Use the files extracted from factory image.
rohanzakie said:
the cmd prompet say ""
Click to expand...
Click to collapse
I've definitely had this experience. You can try disconnecting the cable then reconnecting. When that doesn't work, you have to remove all the drivers or at least run through "updating" the Android drivers in hardware settings. You won't actually be updating drivers just re-installing from the PC. Wug's toolkit mentioned above may be your best choice if you don't have TWRP. The toolkit will provide you with an exe called usbdeview which enables driver removal. I didn't mention an OTA sideload because I thought you did need ADB for that. If you can get PC to recognize the device in cmd, then you can fastboot flash images.
Sent from my Nexus 5X using Tapatalk
Hi,
my Note 5 (which is standard with latest software updates) hangs on the Mi screen when starts up. I can get it into FASTBOOT mode.
And when I connect to PC/Windows 10 and go through adb and enter this:
fastboot devices
gives this result:
fcef713c0904
But I'm not sure what to do now? I guess I need to flash some sort of recovery but not being super tech savvy I'm a bit nervous.
thanks Phillip
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
SubwayChamp said:
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
Click to expand...
Click to collapse
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
phil170258 said:
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
Click to expand...
Click to collapse
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
SubwayChamp said:
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
Click to expand...
Click to collapse
Wipe data worked!
Thanks, and yes, i will enable USB debugging
thanks, Phil
I want to install TWRP on my Umidigi F1 so I can root it and install custom roms and all that
I am using the latest version of SP Flash Tool from here and the most recent stock rom from here to flash this TWRP 3.2.3 Image.
Everything works fine, but after flashing, if I try to boot into recovery (which I think is Power + Volume Up) it says
Code:
Red State
Your device has failed verification and may not work properly
Please download recovery image with verified signature or disable verified boot
Rebooting in 5 seconds....
And then it just reboots into normal Android.
From there on, it acts as if I hadn´t done anything and booting into recovery again just shows me the Android thingy and says
Code:
No Command
Booting with Volume Down always brings me to some chinese things I don´t understand but that very much looks like some kind of recovery to me as well.
Note that I have enabled USB Debugging and OEM unlocking in the settings and that SP Flash Tool states "Download OK" like it does after successfully flashing.
Now can someone help me installing TWRP on my F1?:angel:
Thank you for any help
Oh btw I just noticed this somehow didn´t end up in the Umidigi F1 section and I can´t figure out how to put it there either
So if you could tell me how, that´d be awsome