Related
Michael Hall writes about how you can win an OPPO Find 5 by porting Ubuntu Touch to it!
http://mhall119.com/2013/08/win-an-oppo-find-5/
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
RaspberryJam said:
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
Click to expand...
Click to collapse
-True, but during XDA: DevCon we had 3 people without a phone produce images for it, and it's not a one-chance thing, you can resubmit as often as you like.
-How about this, if you already have a Find 5, give me the same of somebody who you think should get this one instead. Could be a friend, or somebody who's work in the XDA community you think should be rewarded.
Despite having three separate developers build images and flash them onto the phone, none were able to boot into Ubuntu Touch.
Click to expand...
Click to collapse
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
paperWastage said:
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
Click to expand...
Click to collapse
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Testers needed
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
mhall119 said:
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Click to expand...
Click to collapse
Throw your files and what youve done so far over here. Im willing to continue work on it.
Androguide.fr said:
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf_2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
Click to expand...
Click to collapse
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
SystemErrorOne said:
Throw your files and what youve done so far over here. Im willing to continue work on it.
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
Click to expand...
Click to collapse
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Androguide.fr said:
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Click to expand...
Click to collapse
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Androguide.fr said:
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Click to expand...
Click to collapse
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
SystemErrorOne said:
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
Click to expand...
Click to collapse
From your error message, you simply didn't add the .img extension to the twrp image
Also, you can't fastboot a zip, don't try.
But, did you try to simply do the following?
Code:
adb reboot recovery
There's absolutely no reason why it would have overwritten your recovery, my guess is you can't reboot to recovery using the button combination.
Anyway, if the above doesn't work, follow these steps to reflash your recovery:
Open a terminal on your pc
Make sure you cd to the directory where your twrp image is
issue the following command:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-find5[COLOR="DarkRed"].img[/COLOR]
Reboot to recovery using:
Code:
adb reboot recovery
Are you on windows or linux?
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
+Franco Colomba I had no such issues with drivers. The only thing was ADB needed an extra USB VID added.
Click to expand...
Click to collapse
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
SystemErrorOne said:
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
Click to expand...
Click to collapse
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Androguide.fr said:
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Click to expand...
Click to collapse
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
SystemErrorOne said:
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
Click to expand...
Click to collapse
Try this:
Download a CM build
Open it with winrar and extract the boot.img from it
hold shift and do a right-click in the folder where you extracted the boot.img, and select "open a terminal here" (or whatever the header is)
Issue this command
Code:
fastboot flash boot boot.img
Now try again to reboot to recovery using the buttons combination
hurray so i managed to get the phone working by using a script found in that one thread you linked me too.. never the less i managed to get into TWRP and from there i had already made a backup (THANK GOD) and i restored and the phone is up and running perfectly. Now what Im going to do is what you instructed to do first.
1. the build first
2. then the ubuntu base afterwards
with
factory reset, wipe dalvik-cache
i will post back my results wish me luck
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
mhall119 said:
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
Click to expand...
Click to collapse
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
SystemErrorOne said:
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
Click to expand...
Click to collapse
Yeah, Michael Hall reported to me that the build doesn't boot either.
I'm working on a new build using a different toolchain, as with the stock Google TC I had to hack my around -Werror flags and this might be the problem.
I'll post the progress here.
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
matteosaeed said:
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
Click to expand...
Click to collapse
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Also check this out, it might help
matteosaeed said:
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Also check this out, it might help
Click to expand...
Click to collapse
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Why don't you just go to Heisenberg's guide in the general section and flash the latest stock images from Google via Fastboot and start from there? This way you'll at least have a working phone to boot into. From there you can reflash custom recovery and even systemless root. This is what I have always done when the phone wouldn't boot, or I had a backup handy and flashed that. When in trouble just flash latest images.
Asmodic said:
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
Click to expand...
Click to collapse
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sounds like you need to update you drivers if your computer is not recognizing it
Asmodic said:
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Click to expand...
Click to collapse
Any Luck?
it's because you don't have the NEWEST version of TWRP.
Even the simplest of searches would've come up with this answer.
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
pankajste said:
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
Click to expand...
Click to collapse
No it won't, not in this situation.
Heisenberg said:
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Asmodic said:
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Click to expand...
Click to collapse
So this should be marked "Solved?"
It should be marked as "when in trouble revert to Heisenberg's guide."
Hello,
I don't have PC to use adb and I would like to know if it's possible to boot the TWRP image with Android Terminal Emulator? Boot to the image and flash the TWRP zip file.
Please?
You might have luck with this guide and another Android device.
_mysiak_ said:
You might have luck with this guide and another Android device.
Click to expand...
Click to collapse
Yes thanks but this is for my device, I don't have a second device to do that. I would like to boot directly to the recovery image from my phone, you know?
We7dy said:
Yes thanks but this is for my device, I don't have a second device to do that. I would like to boot directly to the recovery image from my phone, you know?
Click to expand...
Click to collapse
Sorry, not possible. You have to have a second device to issue fastboot commands.
Was on Rooted device (Magisk), phone got OTA updated, lost root and TWRP, I tried flashing via cmd "twrp-3.2.3-x_blu_spark_v9.86_op6.img" in fastboot mode. Now the phone is forever stuck on the fastboot screen. It won't even switch off. Please tell me how to get out of this situation.
Literally had this happen to me today. Hold volume up and power button worked for me eventually
anthonyg45157 said:
Literally had this happen to me today. Hold volume up and power button worked for me eventually
Click to expand...
Click to collapse
I tried this, the screen goes off for 0.5 seconds and the same Fastboot screen shows up again.
Edit: Never mind, it finally worked after few tries, thanks.
jokerooney said:
I tried this, the screen goes off for 0.5 seconds and the same Fastboot screen shows up again.
Edit: Never mind, it finally worked after few tries, thanks.
Click to expand...
Click to collapse
The device is finally booting, please tell me how do I get my TWRP back now?
jokerooney said:
The device is finally booting, please tell me how do I get my TWRP back now?
Click to expand...
Click to collapse
I used my computer to boot twrp.img then flash twrp.zip
I still don't understand why so many people are using blue spark TWRP..... Nearly all posts in the last few days talking about issues related with twrp were with this one out with outdated versions of mauronaufrio's.
The TWRP to use is latest mauronaufrio's one there is a whole thread about it.
You don't 'flash' twrp in fastboot mode. You temporarily boot the phone with TWRP: 'fastboot boot twrp.img'
And THEN only you flash twrp installer from within this booted twrp.
Striatum_bdr said:
I still don't understand why so many people are using blue spark TWRP..... Nearly all posts in the last few days talking about issues related with twrp were with this one out with outdated versions of mauronaufrio's.
The TWRP to use is latest mauronaufrio's one there is a whole thread about it.
You don't 'flash' twrp in fastboot mode. You temporarily boot the phone with TWRP: 'fastboot boot twrp.img'
And THEN only you flash twrp installer from within this booted twrp.
Click to expand...
Click to collapse
Can you please share mauronaufrio's thread link here? Thanks
jokerooney said:
Can you please share mauronaufrio's thread link here? Thanks
Click to expand...
Click to collapse
Man, there is a whole thread in ROM section.... It's called TWRP
Hi, I've been using a Motorola Moto G6 Plus for quite a long time now. However, I can't figure out why it doesn't show any boot logo at startup, getting a black screen but a USB signal to my PC in fastboot mode (PC detects it at Fastboot evert S, which is good). Can anyone tell me or help me figure out why this phone isn't giving me boot logo's and fastboot?
First of all i wanna make clear that:
1. Can you reboot to system?
2. Can you reboot to recovery?
3. You have Root access in your phone?
Please consider answring.
ai.Sanaul said:
First of all i wanna make clear that:
1. Can you reboot to system?
2. Can you reboot to recovery?
3. You have Root access in your phone?
Please consider answring.
Click to expand...
Click to collapse
Yes, the system works as normal. It runs stock Android 9, not rooted. It doesn't have any recovery installed, and when I try to reboot to ADB, it gives the same black screen as the boot logo and bootloader. The screen is slightly lighting up, so I know it powers up, but it doesn't give the screen I want, the default bootloader screen.
DaHolyBlobfish said:
Yes, the system works as normal. It runs stock Android 9, not rooted. It doesn't have any recovery installed, and when I try to reboot to ADB, it gives the same black screen as the boot logo and bootloader. The screen is slightly lighting up, so I know it powers up, but it doesn't give the screen I want, the default bootloader screen.
Click to expand...
Click to collapse
OK, try flashing stock boot.img through Fastboot or TWRP, this should work.
ai.Sanaul said:
OK, try flashing stock boot.img through Fastboot or TWRP, this should work.
Click to expand...
Click to collapse
TWRP already isn't an option, and I don't know how to do it with fastboot. Could you guide me through that?
OK, so first of all i wanna make clear that you don't use this phone as primary phone because unlocking bootloader and Flashing have chances that your data might be erased, so BACK Up all of your DATA to a safe place before doing this.
If everything is set, Lets move ahead by unlocking your phone's bootloader and flashing. Watch this this tutorial:
Download boot.img file of your phone &
After that boot your phone in fastboot mode connect it to PC and, type this command in CMD fastboot flash boot (boot.img path)
Hope this helps!
ai.Sanaul said:
OK, so first of all i wanna make clear that you don't use this phone as primary phone because unlocking bootloader and Flashing have chances that your data might be erased, so BACK Up all of your DATA to a safe place before doing this.
If everything is set, Lets move ahead by unlocking your phone's bootloader and flashing. Watch this this tutorial:
Download boot.img file of your phone &
After that boot your phone in fastboot mode connect it to PC and, type this command in CMD fastboot flash boot (boot.img path)
Hope this helps!
Click to expand...
Click to collapse
I didn't read your message fully, so didn't back up my phone... Lucky me this isn't my primary phone and it didn't erase anything. It didn't help me though.
Edit: Now that I try booting into Android, it gives the same black screen as the bootloader and logo. I'm starting to think that it unfortunately erased my phone.
Maybe try flashing full stock?
Arealhooman said:
You said Orem unlocking isnt on? How about Adb debugging?
Click to expand...
Click to collapse
I unlocked the bootloader 2 years ago, and ADB is on, but idk if ADB works without android showing up on the screen
Arealhooman said:
Maybe try flashing full stock?
Click to expand...
Click to collapse
Let's try that. How do I flash that with fastboot or adb?
DaHolyBlobfish said:
I unlocked the bootloader 2 years ago, and ADB is on, but idk if ADB works without android showing up on the screen
Click to expand...
Click to collapse
It doesnt. You need a custom recovery or be booted or booting.
DaHolyBlobfish said:
Let's try that. How do I flash that with fastboot or adb?
Click to expand...
Click to collapse
watch this video tutorial (turn on auto translate captions)