I have read the tutorials and attempted to install TWRP to no avail. My computer does recognize my oneplus x when connected but it is not recognized when I tried adb? No device attached. I put the device in fastboot manually, but the computer still won't recognize it. I think maybe my first error was trying to flash the recovery with rashr. It said it was a successful flash, but when I boot into recovery the device just stays on the oneplus logo. It is rooted by kingroot. Any new ideas would be helpful.
Thank you!
kjtay said:
I have read the tutorials and attempted to install TWRP to no avail. My computer does recognize my oneplus x when connected but it is not recognized when I tried adb? No device attached. I put the device in fastboot manually, but the computer still won't recognize it. I think maybe my first error was trying to flash the recovery with rashr. It said it was a successful flash, but when I boot into recovery the device just stays on the oneplus logo. It is rooted by kingroot. Any new ideas would be helpful.
Thank you!
Click to expand...
Click to collapse
did you unlock your bootloader? If so did you get a chinese confirmation page for unlocking bootloader or english?
joho5 said:
did you unlock your bootloader? If so did you get a chinese confirmation page for unlocking bootloader or english?
Click to expand...
Click to collapse
Unlocked bootloader and the message was in English.
kjtay said:
Unlocked bootloader and the message was in English.
Click to expand...
Click to collapse
If it's not recognizing the phone then its a driver issue. Can you boot into Android?
joho5 said:
If it's not recognizing the phone then its a driver issue. Can you boot into Android?
Click to expand...
Click to collapse
I can boot into Android (if you mean just the phone booting). I installed drivers from that were on the phone and downloaded the drivers at my work computer. Both computers recognize the phone, but not in adb or fastboot.
Use the drivers in the thread a to root and unlock bootloader, it works
Related
My phone is stuck on bootloop. I have cyanogenmod 13 installed on my moto g 3rd gen(2015). I can't seem to get into my system recovery either, which is now twrp and it just shows the logo for twrp recovery. I also for some dumb reason disabled my usb debugging mode, so i can't flash my phone either. Help plzz
Maybe go to bootloader and reflash TWRP
minimale_ldz said:
Maybe go to bootloader and reflash TWRP
Click to expand...
Click to collapse
Doesn't work, can't connect to bootloader
znyght said:
Doesn't work, can't connect to bootloader
Click to expand...
Click to collapse
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
minimale_ldz said:
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
Click to expand...
Click to collapse
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
znyght said:
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
Click to expand...
Click to collapse
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
http://forum.xda-developers.com/showthread.php?p=48915118
and if it doesn't install correct drivers for you, you can get them here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
first thing to do is check what fastboot returns after this command:
Code:
fastboot devices
if it shows your device ID you're good to go
I'd suggest downloading stock firmware first and flashing it before messing with custom recovery. Just remember Motorola often updates bootloader with new firmware so don't flash anything older than you had on your phone before.
Good luck
EDIT: you can also use RSD Lite to flash a new software, it basically automates fastbooting proccess, so theres no risk of misspelling or doing other stuff wrong
EDIT2: firmware is here:
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
also, the OP (lost101) is a great, helpful guy who may give you some advice if you need
Thanks I'll give them a try
Originally Posted by minimale_ldz
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
Click to expand...
Click to collapse
I've tried these but they didn't seem to work
Dear All,
Please help, today i flash my device via twrp into xiaomi.eu global rom from cm13.
Flashing done succesfully, but my device can't boot into system and just stuck at cm logo.
When i press volume - and power button the phone are boot into fastboot mode with big cm logo.
When i press volume - and connect it to computer, it shown my phone are connected into diagnostic mode.
Please help how to unbrick this device. Thanks in advance.
Ps. Device unlock officially, twrp which i use to flash miui.eu rom is twrp with f2fs support. Seems that's i use wrong twrp version.
Edit: solved
https://www.youtube.com/watch?v=NNhdQT9Ivu0
Please google before you post threads..
abihary said:
Dear All,
Please help, today i flash my device via twrp into xiaomi.eu global rom from cm13.
Flashing done succesfully, but my device can't boot into system and just stuck at cm logo.
When i press volume - and power button the phone are boot into fastboot mode with big cm logo.
When i press volume - and connect it to computer, it shown my phone are connected into diagnostic mode.
Please help how to unbrick this device. Thanks in advance.
Ps. Device unlock officially, twrp which i use to flash miui.eu rom is twrp with f2fs support. Seems that's i use wrong twrp version.
Edit: solved
Click to expand...
Click to collapse
How did u solve it?
Rudraneil said:
How did i solve it?
Click to expand...
Click to collapse
I solved it follow guidance at this Link.
After my phone enter edl mode, i just simply flash it using miflash beta for windows 32 bit due to urgent situation. I still on personal trip during when this situation happened and can't access my pc and laptop.
abihary said:
I solved it follow guidance at this Link.
After my phone enter edl mode, i just simply flash it using miflash beta for windows 32 bit due to urgent situation. I still on personal trip during when this situation happened and can't access my pc and laptop.
Click to expand...
Click to collapse
You could just have rebooted ur phone to fastboot mode and unlock the bootloader using mi unlock too to make the phone workl
It would have been way easier
Rudraneil said:
You could just have rebooted ur phone to fastboot mode and unlock the bootloader using mi unlock too to make the phone workl
It would have been way easier
Click to expand...
Click to collapse
Unfortunately, my phone already entering diagnostic mode during that's time. Did miflash unlock can solved it?
Thoght that i am missing one important step after flashing those miui eu rom. Reboot to fastboot prior the phone reboot into system and unlock the bootloader.
Anyway, thanks for your info.
abihary said:
Unfortunately, my phone already entering diagnostic mode during that's time. Did miflash unlock can solved it?
Thoght that i am missing one important step after flashing those miui eu rom. Reboot to fastboot prior the phone reboot into system and unlock the bootloader.
Anyway, thanks for your info.
Click to expand...
Click to collapse
If you were using twrp alka and had unlocked officially, mi unlock could definitely save ur device
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.
What's needed:
latest Android Pie firmware for Xperia XZ1 (I used 47.2.A.4.41_R4C UK or any version of the 47.2.A.6.30) from XperiFirm
newflasher_v13 tool here
Minimal ADB and Fastboot
TWRP Recovery here
last Magisk.zip here
first copy Magisk.zip to the sd card and insert it into the device
Install TWRP:
launch flashtool and download the latest firmware 47.2.A.4.41_R4C with XperiFirm ....
follow the path C: users / name / .flashTool / firmwares / Download
locate the unzipped firmware, open the folder and delete all the .ta files; then open the boot and partition folders and do the same thing
search the internet or XDA newflasher_v13 tool and place all 7 files in the C: users / name / .flashTool / firmwares / Download / 47.2.A.4.41_R4C folder
connect the device in flash mode
launch the .exe command
press "n" and again "n"
finished the firmware flash unplug the phone
When the first ignition is finished, open the debug and connect the mobile phone to the PC
open the folder Minimal in the path C: Program / Minimal and paste in the folder the recovery.img, run cmd.exe type the following commands
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery namerecovery.img
fastboot reboot
finished the start of the phone, turn it off and go into recovery mode (volume down + power button)
flash Magisk from the sd
turn on the cell phone and the root is done
Special thanks
oF2pks for the TWRP
munjeni for the newflasher
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
I have pie stock...can i start guide from point 10 ?
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
look at this thread for backup/restore your DRM keys
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
In my experience I can tell you that nothing is lost on the camera neither in the sound effects nor the color effects on the photos ...
ilblago81 said:
I have pie stock...can i start guide from point 10 ?
Click to expand...
Click to collapse
Absolutely yes
From the use I note that the recovery doesn't read the internal data, but only the sd card. I still don't understand if it's the firmware that has bugs or the twrp that still isn't calibrated for Adroid Pie.
Edit: I found in the XDA site the recovery for the new firmwre and everything works fine here
Would this work on SOV36 (AU XZ1)?
sinkoo1979 said:
Would this work on SOV36 (AU XZ1)?
Click to expand...
Click to collapse
Honestly I don't know, but if in your device install the firmware that we install in the g8341 means that you can. I'm thinking it's the same thing!
Sorry, but the requirement is always with unlocked bootloader?Thanks
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
lilbrat said:
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
Click to expand...
Click to collapse
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
dwang040 said:
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
Click to expand...
Click to collapse
What OS is on your computer?
lilbrat said:
What OS is on your computer?
Click to expand...
Click to collapse
Windows 10
dwang040 said:
Windows 10
Click to expand...
Click to collapse
Did you disable the driver verification signature?
(https://www.howtogeek.com/167723/ho....1-so-that-you-can-install-unsigned-drivers/) then reinstall min adb fastboot drivers and Sony companion and let it detect your phone..
chiacla said:
Sorry, but the requirement is always with unlocked bootloader?Thanks
Click to expand...
Click to collapse
you have to unlock the bootloader
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
theflanker said:
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
Click to expand...
Click to collapse
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
theflanker said:
you have to unlock the bootloader
Click to expand...
Click to collapse
He won't be able to unlock his bl till he figures out the issues with his drivers.. whether he uses the ones in flashtool, installs min adb and fastboot drivers or the android sdk..
---------- Post added at 05:34 PM ---------- Previous post was at 05:29 PM ----------
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Once you get your driver's fixed, just follow the directions given by Sony.. Your phone screen will remain black as all info will be done on your computer..
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Absolutely no, flashtool doesn't need to unlock the bootloader, rather serves to re-lock it in some xperia devices. To unlock it you have to use cmd commands in adb & fastboot, but you can find it here in the XZ1 section.
The cell screen remains black and a blue led appears if you connect in fastboot mode, if you connect in flash mode the screen remains black, but a green LED appears.
if you have problems with the recognition of the device on your PC I can link my guide, it's in italian but if you use google translator you understand it well here
arslancn said:
look at this thread for backup/restore your DRM keys
Click to expand...
Click to collapse
I've checked out the thread but it appears only a few with the xz1 have tried it and they didn't report the outcome, well except one who somehow managed to turn his device in an expensive paperweight.. But I will check it out this weekend..
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL