Related
So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Yes, it does.
What I would do if I was stuck in a bootloop (well thats what I did when I soft bricked my phone "NO OS INSTALLED" now it works again )
is go here https://cyngn.com/products/oneplusone/ download the cm-11.0-XNPH38R-bacon-signed-fastboot.zip extract it in your fastboot folder (make sure you have the latest sdk tools from google or else with an older version it will say that system.img is too large when you flash the zip), open a cmd (run as administrator). check if your bootloader is still unlocked (mine got locked so I was facing a similar situation) type fastboot oem device-info ....it should say unlock true.... then
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
hope it works
hermunn123 said:
So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!
Click to expand...
Click to collapse
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
And voila you are good to go.:good:
vamshi88 said:
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
And voila you are good to go.:good:
Click to expand...
Click to collapse
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?
hermunn123 said:
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?
Click to expand...
Click to collapse
What is your phones status now?
vamshi88 said:
What is your phones status now?
Click to expand...
Click to collapse
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.
hermunn123 said:
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.
Click to expand...
Click to collapse
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Fastboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.
vamshi88 said:
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Flashboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.
Click to expand...
Click to collapse
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon
timmaaa said:
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon
Click to expand...
Click to collapse
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.
vamshi88 said:
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.
Click to expand...
Click to collapse
He could try unlocking the bootloader, but my guess is that it will fail with his phone in the current state. Failing to uncheck the 'update cm recovery' option in Developer Options shouldn't pose a problem until an update is taken.
Transmitted via Bacon
Stuck in bootloop
th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Hey there,
My OPO is stuck in bootloop and believe me, i just took it out of the box (though it was 4 months without charge).
I cannot put it in to fast boot and I tried power cycling too by discharging it for 12 hours & charging for 6+1 hour. Its just the same.
Can you help?
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
@nickizm, when you boot to fastboot and enter the command "fastboot devices", can you see your device listed on the screen?
Thanks for the reply.. The fastboot work fines apart from when I try to unlock the devices and it reboots into recovery, it crashes and doesn't unlock.. the rest of the phone works fine apart from the recovery... my bootloader is also locked and I can't unlock it due to crashing
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screem enabled: false
I can't be certain but I'm pretty sure I read a similar issue to this a few days ago that was caused by not having the latest fastboot software, the user resolved it by downloading the latest android sdk and trying again.
Worth a shot.
Hope it helps.
Powered by Bacon
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
nickizm said:
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
Click to expand...
Click to collapse
Did you try with the latest android sdk?
Powered by Bacon
I'm sure I did.. It wasn't that old.. I can try again, but the problem is I won't be able to unlock my phone??
is this the right link? http://developer.android.com/sdk/installing/index.html?pkg=studio
New drivers, exactly the same
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Rkr87 said:
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Click to expand...
Click to collapse
Yea i have also tried the tool kit V2
My problem is that the recovery is damaged in some way and my device is locked. i can't "fastboot oem unlock" as it just crashes when it goes to reboot.. is there a way to unlock my device with another method or can the recovery be repaired some how? i'm such noob
patstar5 said:
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
Click to expand...
Click to collapse
Ye i tried that as well.. can't unlock the device as it just crashes when it goes to reboot into recovery
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Rkr87 said:
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Click to expand...
Click to collapse
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
nickizm said:
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
Click to expand...
Click to collapse
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Rkr87 said:
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Click to expand...
Click to collapse
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
nickizm said:
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
Click to expand...
Click to collapse
No worries! Let me know how it goes good luck!
Rkr87 said:
No worries! Let me know how it goes good luck!
Click to expand...
Click to collapse
Definitely! cheers again
nickizm said:
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
Click to expand...
Click to collapse
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
adb reboot recovery
Click to expand...
Click to collapse
there you can got into recovery.
Gh05tShie1d said:
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
there you can got into recovery.
Click to expand...
Click to collapse
That doesn't work as my device crashes when it goes into recovery..
eg: "fastboot oem unlock", factory reset, or a boot recovery all crash as my recovery isn't working. When my device goes to reboot in recovery the 1+ logo comes up, fades out to like a blueish from the white 1+ logo and crashes.. so basically it's looked and I can't get into recovery.. thanks for trying
Need some help.
I am usually pretty good with working with firmware and software issues.
I have a friends OPO which they had issues with and somehow got it into a state where the only thing it seems I can possible do is get it into the stock Cyanogen Recovery.
I tried going into fastboot (Vol Up. + Power) but this yields no result it always ends up booting into cyanogen recovery.
As far as I know (with this friend not being very technical) i doubt it had an unlocked bootloader, or even USB debugging on prior to the crash.
The only way I can get the PC to recognize the phone in ADB mode is to enter the Apply update section and hit apply from ADB which puts me into ADB for sideloading.
If I could get it into Fastboot I would be able to move forward.
When it boots, I see a quick flash of some sort of error/failure screen but it is so quick I cannot identify the image.
Try this:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
I actually came across that thread while waiting for a reply to my own. In the state that it is in the msm tool is the only thing that can help me?
Well without fastboot you're going to find it very difficult to get anything done. CM recovery isn't really of any help because it can't actually flash anything that you need it to flash. I find it very odd that you can't get to fastboot. Have you tried adb commands while in recovery?
Transmitted via Bacon
I tried the button configurations to get into fastboot to no avail, it just boots into cyanogen recovery. As for adb while connected, only way I can use it is by going into the section to sideload an update. Within there I can adb, but most commands give me "error: closed".
Adb reboot bootloader doesn't work?
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
Sent From Lollipopified Bacon Goodness!
I am in the same state, my phone always boots to Cyanogen Recovery and no fastboot and even adb side load says closed. I am stuck here. Any help is greatly appreciated.
androidmah said:
I am in the same state, my phone always boots to Cyanogen Recovery and no fastboot and even adb side load says closed. I am stuck here. Any help is greatly appreciated.
Click to expand...
Click to collapse
Has anyone made any progress on this issue?
androidmah said:
I am in the same state, my phone always boots to Cyanogen Recovery and no fastboot and even adb side load says closed. I am stuck here. Any help is greatly appreciated.
Click to expand...
Click to collapse
Tried flahsing the stock rom? Or just the bootloader?
Sent from my Xiaomi Mi 5 using XDA Labs
i've got the same problem, did you manage to solve it?
Thank you
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
I ****ed up and flashed the wrong boot.img. I can't boot and I somehow lost my authorization for the PC so it won't let me issue the commands I need to flash the right boot.img, is it possible to fix?
Pasini said:
I ****ed up and flashed the wrong boot.img. I can't boot and I somehow lost my authorization for the PC so it won't let me issue the commands I need to flash the right boot.img, is it possible to fix?
Click to expand...
Click to collapse
It's a poor description to get a good helping attempt.
Anyway, generally speaking the way to fix this is using the official tool or a tool that works with your device and flash the official stock ROM.
SubwayChamp said:
It's a poor description to get a good helping attempt.
Anyway, generally speaking the way to fix this is using the official tool or a tool that works with your device and flash the official stock ROM.
Click to expand...
Click to collapse
Sorry, I'm not very good at this obviously. I am using platform-tools right now. I am getting "device unauthorized" when issuing adb reboot bootloader. I can boot to fastboot through recovery but when I try to flash the boot.img it just says < waiting for any device >. Earlier I fixed this by issuing "adb reboot-fastboot" and then flashing. But now I just get "$ADB_VENDOR_KEYS is not set" returned. That's why I'm wondering if theres any way to authorize the pc without a successful boot.
Pasini said:
Sorry, I'm not very good at this obviously. I am using platform-tools right now. I am getting "device unauthorized" when issuing adb reboot bootloader.
Click to expand...
Click to collapse
Not sure if you are mixing some things there, you are saying that you have "unauthorized device" through ADB commands but ADB works when device is on...but if you flashed a wrong boot image, could you boot to system some way?
Pasini said:
I can boot to fastboot through recovery but when I try to flash the boot.img it just says < waiting for any device >. Earlier I fixed this by issuing "adb reboot-fastboot" and then flashing.
Click to expand...
Click to collapse
You can't flash the boot image through recovery.
Pasini said:
But now I just get "$ADB_VENDOR_KEYS is not set" returned. That's why I'm wondering if theres any way to authorize the pc without a successful boot.
Click to expand...
Click to collapse
Because of a wrong (and also an unsigned image for your device) you have this message.
Which device you have? And have the bootloader unlocked?