Hey,
I accidentally wiped my operating system using TeamWin recovery, and every time I try to click boot it says, "no operating system are you sure you want to reboot?" Suddenly, though, when I tried to boot into TWRP to use adb sideload to install the system images, the TeamWin home screen just started to blink. I cannot access TeamWin or access my phone's operating system, not being installed.
If you're on the latest 2.8.2.0 TWRP, flash to the previous version.
Computer doesn't recognize
rootSU said:
If you're on the latest 2.8.2.0 TWRP, flash to the previous version.
Click to expand...
Click to collapse
Since I cannot access the TeamWin recovery, I cannot connect the phone to a computer at all to flash TWRP.
drabestdart said:
Since I cannot access the TeamWin recovery, I cannot connect the phone to a computer at all to flash TWRP.
Click to expand...
Click to collapse
no idea what you're talking about.
You dont use fastboot flash from recovery. Fastboot works only in bootloader
No USB debugging
rootSU said:
no idea what you're talking about.
You dont use fastboot flash from recovery. Fastboot works only in bootloader
Click to expand...
Click to collapse
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
If you have any precious data on sd card try first to flash fresh, but with "no wipe" option. Using Wugfresh toolkit is good choise. You can put the phone in bootloader manually and tick the option "phone in bootloop" before starting.
Regards, Zagor
drabestdart said:
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
Click to expand...
Click to collapse
Have you even tried to boot into the bootloader and connect it to your computer?
USB debugging is an android setting and has absolutely nothing to do with fastboot which is used in the bootloader.
If you don't understand fastboot, please go to the sticky thread in general then read "adb and fastboot. What is it?" Thread.
To clarify, you don't need USB debugging except for when you are using adb when booted into android. It has no relevance when using Adb in recovery or fastboot in the bootloader.
If you're having trouble connecting in bootloader you have maybe an issue with your drivers which again, my thread will help you with.
drabestdart said:
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
Click to expand...
Click to collapse
Flash the factory image with fastboot. Boot into the bootloader and run the flash-all.bat from your pc. It will wipe your device so be forewarned
Sent from my Nexus 5 using XDA Free mobile app
drabestdart said:
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
Click to expand...
Click to collapse
I think you already know this to be untrue since you were attempting to adb sideload a rom. Please don't be argumentative with knowledgeable people trying to help you.
Wakamatsu said:
I think you already know this to be untrue since you were attempting to adb sideload a rom. Please don't be argumentative with knowledgeable people trying to help you.
Click to expand...
Click to collapse
I don't think he is intentionally being argumentative. I think he just lacks some basic knowledge. Hopefully my thread will help with that
Worked!
jd1639 said:
Flash the factory image with fastboot. Boot into the bootloader and run the flash-all.bat from your pc. It will wipe your device so be forewarned
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks very much to all of you that helped me.
This response worked, though I had to use the flash-all.sh since I'm a mac user. All in all, you guys were a great help and I realize that I were lacking some knowledge about the topic I was talking about. Again, thanks, not only to jd1639, but also superSU, and various other people.
Worked!
jd1639 said:
Flash the factory image with fastboot. Boot into the bootloader and run the flash-all.bat from your pc. It will wipe your device so be forewarned
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks this worked! Thank you all who have helped me, including rootSU and this user to whom I am replying. I realize that I lacked some knowledge of the topic I was talking about, and apologize if I may have frustrated you. Since I am a mac user, however, I had to use the flash-all.sh instead of the .bat file.
Related
Hi, I've got a Nexus S 4g. I recently tried to flash it with the stock Jelly Bean image from Google's developer page - developers.google.com/android/nexus/images. While I was running flash-all.sh, the flash appeared to finish, and my terminal just said <waiting for device>. The device does boot up, and is functional, however, I can't get this thing to connect to any of my PCs via USB.
I've plugged it into my 12.10 Ubuntu laptop, and run lsusb. The device isn't listed at all, so adb doesn't work. I've also booted the phone into fastboot, and lsusb still doesn't list it (so fastboot devices doesn't list anything either). I've also plugged it into my Arch box, and tried the same steps with the same results. Before I flashed the phone, I was able to debug just fine on both machines.
Has anyone seen this behavior before? Is there any way to fix it? I've spent a bunch of time searching around for this problem, and haven't seen much. Thanks.
Well, crap. It looks like I flashed the wrong image to my phone. I've got a Nexus S 4G (d720), and it appears I flashed the i9020 image. That's what has probably caused my issue. Does anyone know if there's any way to recover from this?
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
kwibis said:
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
no need to have debbuging mode on
kwibis said:
Rephrase: Do you have unlocked bootloader?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have adb and fastboot drivers installed?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
Yes
The problem is that I flashed the wrong image to my device. I'm pretty sure it's hosed. The phone works fine - it boots up, I can get on wifi, but I just can't connect via USB. The image I flashed must have different USB drivers than what my device has. It looks like I'm stuck with it, or I will see if someone can "unbrick" it, and flash the proper image to it.
Well since you have unlocked bootloader I guess you have custom recovery and are rooted as well. You can download a custom rom, safe your app data with titanium backup, factory reset and wipe cache in recovery and flash proper rom. Then the drivers should work again and you can flash the correct image if wanted.
Sent from my Nexus S
hey,
i followed the tutorial in general to flash a factory image to my device, and all went well but now i want to install twrp again and it tells my my device is offline.tried it both in osx and windows7... is there a way to fix this?
thank you in advance
kind regards
You dont need adb to install a recovery. Go into the bootloader (volume down + power) and run "fastboot devices". If youre device shows up you are good to go.
You don't flash recovery with adb, you use fastboot. So do as chromium said to get to the bootloader, then "fastboot flash recovery recovery.img", where recovery.img is your renamed twrp recovery image.
Sent from my Nexus 5 using Tapatalk
pre10c said:
hey,
i followed the tutorial in general to flash a factory image to my device, and all went well but now i want to install twrp again and it tells my my device is offline.tried it both in osx and windows7... is there a way to fix this?
thank you in advance
kind regards
Click to expand...
Click to collapse
Make sure that you go back and enable USB debugging again after flashing the factory image. Locking, unlocking, and flashing firmware images all will turn off developer options and USB debugging.
Oh, and when you connect your phone you will need to watch your phone for the security popup and allow the phone to trust and connect to the computer.
Sent from my Apple ][e using ProTERM 2.2
Thanks for clearing that up, but what can I do to fix adb anyway in case if I ever need it??
Kind regards
pre10c said:
Thanks for clearing that up, but what can I do to fix adb anyway in case if I ever need it??
Kind regards
Click to expand...
Click to collapse
Did re-enabling developer access, USB debugging and allowing access from the phone's popup screen work?
Here is a forum thread to check out.
http://forum.xda-developers.com/showthread.php?t=2514396
Diagnosing USB Driver and ADB issues in Windows
Sent from my Apple ][e using ProTERM 2.2
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
What is the best way to root this device with the stock firmware, the latest SuperSU.zip, Magisk, other?
loner. said:
What is the best way to root this device with the stock firmware, the latest SuperSU.zip, Magisk, other?
Click to expand...
Click to collapse
I'm using bad boys Rom atm, it works pretty well assuming your in the US
ticklemepinks said:
I'm using bad boys Rom atm, it works pretty well assuming your in the US
Click to expand...
Click to collapse
is that a pre-rooted ROM ?
just flash and done?
AllGamer said:
is that a pre-rooted ROM ?
just flash and done?
Click to expand...
Click to collapse
yes
Unlock bootloader via HTCDev (Select all other models)
Flash TWRP
Flash Magisk
Profit
Galactus said:
Unlock bootloader via HTCDev (Select all other models)
Flash TWRP
Flash Magisk
Profit
Click to expand...
Click to collapse
And store stock recovery matching firmware mid/cid/ version somewhere for later OTA, right? This still needed for official ota, isn't it?
tbalden said:
And store stock recovery matching firmware mid/cid/ version somewhere for later OTA, right? This still needed for official ota, isn't it?
Click to expand...
Click to collapse
No clue, I backed up the recovery by booting TWRP first rather than flashing but I have no idea what mid/cid is lol, I haven't used a HTC device in 4 years
Galactus said:
No clue, I backed up the recovery by booting TWRP first rather than flashing but I have no idea what mid/cid is lol, I haven't used a HTC device in 4 years
Click to expand...
Click to collapse
Can anyone provide a sample /command line for booting TWRP in MS Windows to back up before flashing?
loner. said:
Can anyone provide a sample /command line for booting TWRP in MS Windows to back up before flashing?
Click to expand...
Click to collapse
I just did
fastboot boot twrp.img
Galactus said:
I just did
fastboot boot twrp.img
Click to expand...
Click to collapse
Simple and all these years messing with fasboot I never even thought of it.
loner. said:
Simple and all these years messing with fasboot I never even thought of it.
Click to expand...
Click to collapse
Happens to all of us lol
Did you guys find HTC drivers for ADB to get USB debugging to work?
My fastboot (Google's as well as HTC's) says "Waiting for device."
"fastboot.exe devices" sees no device, but the Win10_x64 PC sees it. I have enabled developer mode, selected "Enable Bootloader Unlock" and "Enable USB Debugging." Usually this is all I need.
BoulderGeek said:
Did you guys find HTC drivers for ADB to get USB debugging to work?
My fastboot (Google's as well as HTC's) says "Waiting for device."
"fastboot.exe devices" sees no device, but the Win10_x64 PC sees it. I have enabled developer mode, selected "Enable Bootloader Unlock" and "Enable USB Debugging." Usually this is all I need.
Click to expand...
Click to collapse
i get the token but my computer keep copying everything
BoulderGeek said:
Did you guys find HTC drivers for ADB to get USB debugging to work?
My fastboot (Google's as well as HTC's) says "Waiting for device."
"fastboot.exe devices" sees no device, but the Win10_x64 PC sees it. I have enabled developer mode, selected "Enable Bootloader Unlock" and "Enable USB Debugging." Usually this is all I need.
Click to expand...
Click to collapse
If you already have HTC sync manager, uninstall it and download and install the updated one. This should update your HTC drivers.
tbalden said:
And store stock recovery matching firmware mid/cid/ version somewhere for later OTA, right? This still needed for official ota, isn't it?
Click to expand...
Click to collapse
TWRP can install the system part of an official OTA - the firmware portion just has to be pre-extracted and flashed manually.
Knuckle Head Here
Hello all.
I'm waiting for my HTC U11 (my first HTC phone) to be delivered.
I'm new to this and reading through the posts I'm somewhat overwhelmed.
It would be great to have a sticky "fastboot for dummies" for HTC phones for those like me that are clueless.
Download mode
Bootloader Mode
Fastboot Mode
Flash
Reboot and on and on.
Holy Smoke!
Wouldn't have to be an encyclopedia (I see there are many) just something explaining usage for the most common commands.
I hope this is the correct place for this post, if not, apologies in advance.
Thanks,
Scooter
Scoot805 said:
Hello all.
I'm waiting for my HTC U11 (my first HTC phone) to be delivered.
I'm new to this and reading through the posts I'm somewhat overwhelmed.
It would be great to have a sticky "fastboot for dummies" for HTC phones for those like me that are clueless.
Download mode
Bootloader Mode
Fastboot Mode
Flash
Reboot and on and on.
Holy Smoke!
Wouldn't have to be an encyclopedia (I see there are many) just something explaining usage for the most common commands.
I hope this is the correct place for this post, if not, apologies in advance.
Thanks,
Scooter
Click to expand...
Click to collapse
it's not too difficult...what are you trying to do? these are the minimum steps for root:
1. create account @ https://www.htcdev.com/
2. follow steps to unlock bootloader, choose "all other supported models"
3. install fastboot either from step 4 or from HERE
4. continue to follow steps until bootloader is unlocked, it will factory reset the device
5. boot into download mode, flash twrp, use cmd fastboot flash recovery nameofrecovery.img
6. boot to bootloader, then recovery
7. I would advise u to keep read only for /system, then immediately do a system & boot img backup
8. flash/install either supersu or magisk (my preference)
Captain_Throwback said:
TWRP can install the system part of an official OTA - the firmware portion just has to be pre-extracted and flashed manually.
Click to expand...
Click to collapse
Does your TWRP permit booting to TWRP from stock aboot/recovery (so that stock can be backed up).
hgoldner said:
Does your TWRP permit booting to TWRP from stock aboot/recovery (so that stock can be backed up).
Click to expand...
Click to collapse
That's not a TWRP function - it's dependent on the bootloader. And yes, fastboot boot works fine on the U11 from bootloader mode.
GAH! I'm an idiot. RTFM, I should have done, to quote Yoda.
Totally failed to see:
Required Resources
Please make sure all items are installed and up to date.
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync Manager:
http://www.htc.com/hsm
Thank you, @Loner!
I am coming from an LG, and haven't had an HTC since the Thunderbolt, so I am rusty.
OK, now my fastboot works!
Tried rooting my pixel 3 with XDA instructions. Phone bootlooped and went into recovery. Tried restarting, same issue. Tried factory reset, same issue.
I can still boot to fastboot, recovery, barcodes etc.
When the pixel 3 is in bootloader the device is not recognized by adb on mac or pc. Can someone help? Prefer to solve the issue through mac if possible but if PC is the only option I'll greatly appreciate your help too.
Solved
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
I'm love you??????
suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Thank you thank you thank you. The last part still got me confused, because I actually pulled from the zipped image file I had. I had an image file on hand, but it just wouldn't work. And I had no idea about the radio, so I just skipped since it didn't seem all that pertinent. This is the second time I've had to get it back to stock, but I couldn't remember for the LIFE of me how I did it. Even though it was literally two hours before this time. Hey! I just don't know when to quit!
suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you
robertoancini51 said:
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you
Click to expand...
Click to collapse
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Click to expand...
Click to collapse
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.
robertoancini51 said:
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.
Click to expand...
Click to collapse
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.
bobby janow said:
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.
Click to expand...
Click to collapse
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.
bobby janow said:
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.
Click to expand...
Click to collapse
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was included in that first time I saw it. lol. Slight panic but the Google helped me out of it. Even knowing what to do it can be a little finicky.
jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked? Have you tried flashing the factory image?
abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
What happened exactly? If your bootloader unlocked, and have fastboot access, then you should be able to fastboot the factory image.
LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
You using sudo for fastboot and adb commands?
How'd you install platform tools? I know for me the only thing that worked on Mac was using Homebrew . All other methods were finicky at best