Related
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 (WILL ALSO WORK FOR 4.2, just use the correct file that I link to) on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Thank you =) will try
-Google
I hope people actually watch and learn from this tutorial instead of waiting around for some point and click tool powered by unicorn blood and hamsters. It's an excellent tutorial and gets you in touch with your device by using the exact tools Google provided you to use for this exact thing.. Use them, they are invaluable.
This means we can't use the old method of putting update.zip file in the root folder and let the system upgrades by itself.
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
Click to expand...
Click to collapse
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
I've been plugged in to both a charger and the PC. Come on, if I've fired off adb recovery reboot, doesn't that automatically suggest that I'm connected to the computer? I press Power+Volume Up and it does NOT instantly go to the screen it should, but brings up a Google logo and sits there forever.
styckx said:
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
Click to expand...
Click to collapse
Doesn't work in either case, it just hangs until the hard reboot kicks in.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
Click to expand...
Click to collapse
Omega360 said:
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Click to expand...
Click to collapse
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
ShannonMS81 said:
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
Click to expand...
Click to collapse
THIS WORKED!!!!!!
OMFG!!! I burned the time I was going to watch the making of Prometheus Blu-ray trying to get this stupid thing to work! Where were you hours ago, man?!?!? Thank you!!! Better late than never.
Glad you got it.. BTW.. I did-misread what you said and yes, you would have had a USB cable in. All these posts are running together of people asking for help and having issues. Mah poor brain is getting em all mixed together.
Nexus 7 needs a coffee maker attachment!
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
Great video! I might just be using this in the near future. I plan on waiting for the factory image (I just like having a full install on my devices when possible) instead of using just the zip file (that is if I dont get the update). Although if the update isnt showing up sometime soon then this is going to work for me just fine.
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
can't enterthe stock recovery since i instaled CWM. removing it would bring the stock back ?
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
While in stock recovery and in the "apply update from adb" screen, type in the command window "adb devices". It should say:
<your device serial number> sideload
If it does not, check the drivers in device manager. You may need to manually install it. I had to on mine.
Cheers qbking77, worked a treat.
First time I pushed using adb & after following your tut life is good. Thanks again!
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
You may be using an older version of adb that does not support the sideload command.
Jwoc12 said:
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Click to expand...
Click to collapse
It should say 8sdgfs3JKSDBFkjk3 device or something like that. If it does not, you need to install the the correct driver.
My computer did not recognize my tablet at first. I went to this thread and installed PDAnet which installed the driver.
http://forum.xda-developers.com/showthread.php?t=1809195
[ re-posted here in QA forum. should not have posted originally in the General forum. ]
Hi,
I desperately need help.
Short version: How can I boot into recovery when my volume buttons don't work?
Longer version:
My HTC One has been dropped one too many times (this is not new ... I've been living with it like this for a month or two) ... most functions which live on the daughter card don't work. Proximity sensor, front-facing camera, headphone jack, and VOLUME BUTTONS.
I could live with all that, until I screwed up loading a new ROM.
Now it isn't bootable. Whenever I try to turn it on, it sits stuck at the "HTC" white screen, because there's no valid ROM loaded.
I have TWRP recovery loaded, but with no VOLUME button, I cannot boot to recovery!
Is there some magic trick? "fastboot devices" and "adb devices" do not see the phone.
"lsusb" *does* see the phone.
Help please!!!!!!!
McSurly said:
[ re-posted here in QA forum. should not have posted originally in the General forum. ]
Hi,
I desperately need help.
Short version: How can I boot into recovery when my volume buttons don't work?
Longer version:
My HTC One has been dropped one too many times (this is not new ... I've been living with it like this for a month or two) ... most functions which live on the daughter card don't work. Proximity sensor, front-facing camera, headphone jack, and VOLUME BUTTONS.
I could live with all that, until I screwed up loading a new ROM.
Now it isn't bootable. Whenever I try to turn it on, it sits stuck at the "HTC" white screen, because there's no valid ROM loaded.
I have TWRP recovery loaded, but with no VOLUME button, I cannot boot to recovery!
Is there some magic trick? "fastboot devices" and "adb devices" do not see the phone.
"lsusb" *does* see the phone.
Help please!!!!!!!
Click to expand...
Click to collapse
Theirs no trick, thiers only 2 ways into custom recovery
one is from the bootloader and the other is from a booted up phone using adb reboot recovery
McSurly said:
[ re-posted here in QA forum. should not have posted originally in the General forum. ]
Hi,
I desperately need help.
Short version: How can I boot into recovery when my volume buttons don't work?
Longer version:
My HTC One has been dropped one too many times (this is not new ... I've been living with it like this for a month or two) ... most functions which live on the daughter card don't work. Proximity sensor, front-facing camera, headphone jack, and VOLUME BUTTONS.
I could live with all that, until I screwed up loading a new ROM.
Now it isn't bootable. Whenever I try to turn it on, it sits stuck at the "HTC" white screen, because there's no valid ROM loaded.
I have TWRP recovery loaded, but with no VOLUME button, I cannot boot to recovery!
Is there some magic trick? "fastboot devices" and "adb devices" do not see the phone.
"lsusb" *does* see the phone.
Help please!!!!!!!
Click to expand...
Click to collapse
Your phone Is s-off right, last hope is getting to the bootloader although I don't know how you would do that without working volume keys.
You could run an ruu then at least.
But it doesn't sound good only thing I can think of, and I've never tried this so your a guinea pig here.
Type this in the command window and connect and reboot the device
Code:
adb wait-for-device reboot bootloader
or
Code:
adb wait-for-device reboot recovery
Maybe, Hopefully it will catch the right point during boot and land you in the bootloader or recovery. Very slim and last hope I'd say.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
I would be happy to boot to bootloader. It doesn't have to be boot-to-recovery.
Unfortunately, it doesn't boot far enough to start adbd. Frankly I don't know that anything valid is loaded in there at all. The ARHD installer completed, but when I told TWRP to reboot it warned me that no OS was loaded, am I sure I want to reboot? Should have said no!
So, adb wait-for-device will be endless.
My only hope is that there's something you can do when device is plugged in but not "on", over USB. When "lsusb" shows the device is connected to the computer, but "fastboot devices" still doesn't show it yet (same for "adb devices").
Last recourse may be opening up the phone and hoping for a loose wire. Though that's more likely to cause damage than repair it
Thanks for your thoughts.
Hey guys,
hope you can help me. Have a little problem: After trying to root my fire, it is in a bootloop and i don't know what to do. Hope you can help me. I guess it is bricked.
Thanks
EDIT:
I tried to sideload the software bin, but it didn't worked. Also my computer doesn't show the devices with "adb devices".
Also my computer doesn't show the devices with "adb devices".
Click to expand...
Click to collapse
Others have found that the fire will only show up on your pc after you select the sideload option on the fire. If it still doesn't show, try unplugging / replugging the usb. It seems to help some people to get it to appear. Also note that some devices will intentionally not allow you to flash bin if the battery level isn't high enough. It's a safety measure since running out of battery during a flash = brick. Be sure you're fully charged.
thanks, but..
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do
cl.lio said:
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do
Click to expand...
Click to collapse
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow
EVOL-LOVE said:
Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow
Click to expand...
Click to collapse
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
sd_shadow said:
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Click to expand...
Click to collapse
:good: Awesome thank you very much, I thought about doing just that but figured I better ask the pros first.
I somehow missed that post on unbricking... :silly:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse
jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.