Develop Bugs

[Tutorial] Flash/Root/update elephone P8000

I know what you are thinking: "Another root/flash tutorial??, it's already explained multiple times right?"
Yes that's true. But for some reason it did not work when I followed the exact steps described (I tried it on 2 different elephone P8000 phones), and I believe I'm not the only one so i created this post to help others.
I folled these step: bbs.elephone.hk/thread-6616-1-1.html#.VkcZqL8WCnN (the guide link in the "Eragon v.5.9.2" thread.
Flashing instructions:
1. Install the usb drivers and reboot your PC.
(Download link: mega.co.nz/#!55BQkKiR!OPBrnj7SXxsUbuchAjV8orT9SMAOMpbDesYTMO2DDHY)
2. Check if the drivers are installed correctly.
Go to "Device manager" on your windows PC and check if there are no yellow question marks appearing when connecting the phone to the PC​3. Download the flashtool and firmware you would like to flash:
Latest version of the Flash tool: (androidmtk.com/smart-phone-flash-tool)
Stock Rom from official forum: (bbs.elephone.hk/forum-270-1.html#.Vkcc878WCnM)
Eragon ROM: (forum.xda-developers.com/elephone-p8000/development/rom-06-9-eragon-1-0-android-5-1-t3195007)
Philz recovery Touch 6.59.0 Port P8000 Version 2: (forum.xda-developers.com/elephone-p8000/development/recovery-philz-touch-6-59-0-port-p8000-t3224478)
?CWM Recovery (didn't work for me): (bbs.elephone.hk/thread-6616-1-1.html#.VkceZL8WCnN)
4. Open the flash tool and select the scatter download file included in your firmware you downloaded.
!the next steps differ from every tutorial I've read but seem to work perfectly.
5. Turn your phone on (normal no recovery).
6. Click on the download button in the flash tool.
7. turn your phone off (the normal way)
8. The flashing should automatically start while the phone is turning off.
9. Wait for the conformation in the flash tool (green check mark).
10. Remove the usb cable from the phone and hold to power button till the phone boots.
To root:
Just install superSU from the playstore and root. (confirm with rootchecker app, also from the playstore).
If that does not work for you. Install a custom recovery following the flash instructions above. Put de SuperSU binary's on your sd card. Boot into recovery by turning off your phone. Now hold the power and volume up buttons till you see a selection menu. Select "recovery" with the volume up button and confirm using the volume down button. In recovery use the install from zip function to install the superSU binary's.
To install latest stock firmware:
Follow the flash instructions and flash the stock ROM. I recommend doing this instead of updating from the phone itself. Because I updated the firmware from the phone itself to the latest firmware using the updater on the phone and there were some small bugs. After flashing everything worked perfectly.
(sorry the links are not clickable, Because I'm a new user with <10 post I can't add clickable links in the threats i create)

I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?

elerraoind said:
I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?
Click to expand...
Click to collapse
Please use google.
"Flashing a custom ROM" basically means to load a different version of the Android OS. This site actually explains it very well. A custom ROM is the full Android OS customized by the ROM builder usually to make it faster, provide better battery-life or add new features.
AOSP ROMs like CyanogenMod offer stock Android which will remove things like HTC's Sense or Sprint's Apps. CyanogenMod's ROM is one of the more popular ROM.
Other Roms like Fresh 3.5 offer a ROM very similar to the default experience (with added speed and battery-life) by leaving Sense (or whatever skin your device has) and incorporating over the air updates into an updated version of the ROM.
In order to flash a custom ROM you must first root your device. For information about rooting see Matt's comment on the OP or my original answer below:
When I had the same question this is where I found it: .talkandroid.com/7686-what-is-rooting-and-why-should-i-do-it-the-pros-cons-of-android-rooting
Depending on what device you have the rooting method will be different though. Personally I suggest reading up on your device at XDA.
Click to expand...
Click to collapse
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom

vetkak said:
Please use google.
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom
Click to expand...
Click to collapse
Appreciate your detailed response. Thanks.

Flashing Problem
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris

xhris1337 said:
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris
Click to expand...
Click to collapse
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000

bjbirch said:
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000
Click to expand...
Click to collapse
Cheers for the reply, I should have mentioned that I tried that also and it still says "there is no SU binary installed, and superSU cannot install it" I found OEM unlocking yesterday and it got my hopes up then shot me straight back down, I was hoping that it OEM unlocking was the reason I could not access recovery,
Thanks again, Chris

To access recovery, switch phone off completely, then press power and volume UP together, you will see three options in tiny white writing,use the volume UP to move marker to recovery which is the first option, then press volume DOWN to choose recovery, you will get a screen with a green android man with a red triangle, you then have to press power and then volume up this should get you into recovery

If recovery is broken. Turn off the phone, connect to PC. Open flashtool. Load philz recovery. Click in download. Turn phone on and flashing should start automaticly. Hope this helps
Verstuurd vanaf mijn Elephone P8000 met Tapatalk

I think it's easier when you use Kingroot for root and Flashify for the recovery

ok sp flash tools wont let me flash just a recovery. It wants me to format and flash the whole phone which wipes out my imei. any suggestions?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

No matter what I try, my computer will not install the drivers. I keep getting "A service installation section in this INF is invalid". Any ideas on what to do?

LG Phone returned from repair without OS

Hello,
I received my phone back from LG to fix the motherboard issue and it did not have an OS. Actually it did have an OS called Mini OS. The boot loader is locked and it won't verify proper google firmware when I adb sideload because it's using "test keys".
I was able to get root and adb into the device. Two questions:
1. Considering that I have root to the device, how can (is it possible) I put firmware to get back to a working state?
2. Because I have root on my device which is loaded with their keys and pre-OS flashed firmware, is there any value for the community here'?
Please forgive me if this is forbidden discussion and remove this post. I haven't been on XDA for more than a couple of years and don't know how things have changed.
Thank you.

FYI I fixed this issue. If you have this problem you can fix it by pushing twrp or other recovery to the device and dd-ing it to the boot loader block.
Let me know if you want help on this.
Also let me know if you want the system image I pulled from the stock weird LG manufacturer device.

Would be interesting to see, doubt it would be all that useful but interesting nonetheless
https://www.reddit.com/r/LGG3/comments/4g8d0p/g3_flash_tool_stuck_on_mini_os_screen_please_help/ This seems to be it running on a G3
https://www.youtube.com/watch?v=k8VWVzJJ0-U and on a G Flex2

This happened to me when i flash tot and unplug it before.
Sent from my Pixel using Tapatalk

Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.

AFK269 said:
Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification

konceptz said:
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification
Click to expand...
Click to collapse
I think that you will need to make a call to the service center to tell your situation.

I followed this and it booted just fine.

I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .

picodot said:
I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .
Click to expand...
Click to collapse
Hi @picodot , which bullhead image version did you use?

Trying To Recover Data - recovery and system partitions wont boot

Hey all,​
Question: Can anyone offer any help recovering my data partition?
Problem: system and recovery partitions wont boot.
Why: I failed to fix a boot loop problem I was having. I tried to restore my system and recovery partition that I had backed up through TWRP. The restore failed and now I cannot boot into recovery mode (let alone system).
What I've Tried:
1. booting into a TWRP (booting TWRP image via fastboot off my desktop PC). FAILED
downloading boot.img completes ok.
I get an error when it tries to boot the image: "FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)"
my guess is my recovery partition system is broken.
Thoughts:
Can I flash my bootloader and recovery partitions from a stock ROM without interfering with my data?
can i do a partial flash (not a flashall.bat)? How?
I am not super familair with doing a partial flash. I have only ever ran flashall.bat on Google's stock ROMs.
Question: Does anyone have any ideas?
If you can help me out, I would love to buy you a 6 pack of beer!

I am recreating this thread in its proper place.
@XDHx86
XDHx86 said:
Can you boot to bootloader? Does fastboot detect your device?
Yes, fastboot detects the device. It lists my Pixel 3 XL a fastboot device and the Pixel 3 XL properly executes commands like fastboot reboot bootloader.
Other things I just tried:
I also tested the connection and I was also able to fastboot a TWRP.img (sailfish version--Pixel 1) for my Pixel 1 just now. So everything looks good on my desktop end. However, when I boot a TWRP.img (crosshatch version--Pixel 3) on the Pixel 3, the boot fails and gives the error i posted above.
I also tried three different TWRP.img revisions (including the oldest and newest revisions for the Pixel 3XL). None of the twrp.img images will load.

Here is the fastboot command and error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.

pritchfest said:
Here is the fastboot command and error.
View attachment 5254701
I also have the latest platform-tools installed.
I was able to flash the bootloader for latest Pixel 3 XL build for Android 9 (the version I had installed). However, I still cant boot into the TWRP image.
Click to expand...
Click to collapse
I used this script when I ran into a similar issue before, you can use it to flash TWRP or sovle your bootloop.

@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.

pritchfest said:
@XDHx86
Thanks for the tip.
I will definitely bookmark this and give it a try if I run into a bootloop issue. I am not sure what was wrong but I ended up doing a falsh-all.bat. the worst part about modding your phone is that when it goes out, you really needed to get fixed asap
This might or might not have worked, i'm not sure. I thought it was also weird that the yellow triangle with the exclamation mark on the fastboot screen was red. I've never seen it change colors. Not exactly sure what that means.
Click to expand...
Click to collapse
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.

XDHx86 said:
"This might or might not have worked". As in "I already got my device to the point of no return"?
If your device is bricked, there is no way to unbrick it that I'm aware of. As you can't find firehose files for google devices. So you can't boot to EDL mode.
Your options are to boot to bootloader and flash stock ROM, you can also use the script to flash TWRP and see if ti works.
Needless to say, flashing a ROM means loosing all your data.
Click to expand...
Click to collapse
oh, no. As in, your suggestion might have worked but I didn't get to try it because I really needed to have my phone working for work. I didn't get to try your suggestion because in my haste I opted to just flash-all.bat and forefit the opportunity to recover my data.
After trying to flash several partitions separately and failing, including just the bootloader--and later just the recovery partition--, I kept getting the same error I wrote about above.

So you still get this error?? Even though you used the script, you still get the error?
Are you sure you have latest adb tools and device driver?
What about setting active partition first?
Try fastboot set_active a
Then fastboot boot twrp.img

As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
I can confirm I had the latest ADB setup.
I did not try your fastboot set_active a command before trying to fastboot into twerp.img. I can't say this wouldn't have worked.
The only other information I have is that on the fast boot screen, The triangle with an exclamation mark in it was colored red. Normally this triangle is a yellow color.
Hope that helps.

pritchfest said:
As I said, I never ran the script because I ran Google's flash-all.bat (factory image) before seeing your post.
I don't know if it would have worked. I wish I didn't need my phone to work so badly so that I could have waited a little bit longer.
Click to expand...
Click to collapse
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.

XDHx86 said:
Oh you already solved it.
In this case write "[SOLVED]" in the beginning of the thread title and edit the first post to include the solution.
Click to expand...
Click to collapse
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.

pritchfest said:
No, I did not solve it.
I never came up with a solution to recover my data. The question was how can I recover my data. Instead, I had to wipe my whole phone and lose all my data by running flash-all.bat because my boss was getting mad I didn't have a phone.
Click to expand...
Click to collapse
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.

Y
XDHx86 said:
Yeah I meant the bootloop, I mean looking at the bright side I saw worse. So just be happy with what you got, of course this is just my opinion.
Click to expand...
Click to collapse
Yeah, it could be worse :/

Question Bricked Pixel 6 Pro Help needed

My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.

There's another software on here called pixel flasher try that if they don't work see of more knowledgeable people message
might have to speak to Google and also were you bought it from
I had the 6 pro put on charge then turned on did restore from back up and it was like 5 to 100 of apps and then it did the march update and it boot looped that was on Saturday
I got into the safeboot mode or whatever it restated as that what I clicked then got into mode again then from there it's froze
I didn't get a replacement till Tuesday lol that was ee had no problems with new one

How about using the android flash tool to reflash the latest beta that you were on?

Also...flashing without a bootloader unlock is like Android No-No ...no.1 ...

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.

opz187 said:
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.
Click to expand...
Click to collapse
Thanks for this, I will give it a go. I have used ADB before, so should be fine with that

Alekos said:
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).
Click to expand...
Click to collapse
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
You mention power button but you never said you held the volume down button as you were powering on. you must hold the volume down button.

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
I understand it won't boot into Android. Your phone is fine. If you want help, dm me, I will get you sorted. You just need to re-flash Android using the above Flash tool.

Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
That's good to hear - it's hard to brick a Pixel.
Best options to resolve issues is the Flash Tool, OTA Update or cli image. The OTA can be tricky when using platforms tools (adb/fastboot).

Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?

anasmhds said:
Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?
Click to expand...
Click to collapse
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such as Android 13 Beta 3, 4, and final release.

roirraW edor ehT said:
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such and Android 13 Beta 3, 4, and final release.
Click to expand...
Click to collapse
Thanks for your feedback.... just bad luck

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

radioxmen said:
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot modeView attachment 5618033
Click to expand...
Click to collapse
Select recovery mode.
When you see No Command, press power and volume up at the same time (quickly). Then try factory reset. If that doesn't work, choose ota update and follow the links above.

Have same exact issue here.
When I try to sideload, I constantly get "cannot read" error.
I tried Large Address Awareness but even that didn't work.
Any help is appreciated

So this tool cant fix your problems?
Android Flash Tool
flash.android.com

No, I keep getting error that OEM is not unlocked

Found my old note 10.1 and did something stupid... need help...

I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Why don't you try flashing stock firmware?
Check for drivers issue.

mvikrant97 said:
Why don't you try flashing stock firmware?
Check for drivers issue.
Click to expand...
Click to collapse
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
Your device should show up like this in device manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing like this

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
It is P605. And from this post looks like you are not the only one https://forum.xda-developers.com/t/q-galaxy-note-10-1-2014-not-recognized-in-download-mode.2494886/

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Also watch this video

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Please try to get into download mode for odin to recognize your tablet

Ok, so using another PC and yet another cable, I was finally able to see this pop up on the device manager when in the "update with adb" option:
Unfortunately, I cannot get the tablet to stay in download mode. As soon as I confirm to go to download with the vol+ button, it immediately starts to boot loop.
On the other hand, when in the adb mode, the PC does recognize the device when it's attached and I can see it with "adb devices" command.
But unless there's a way to get it to go to download mode, I'm screwed, right?

mvikrant97 said:
Also watch this video
Click to expand...
Click to collapse
Yes, but that is my problem. I cannot get to the download screen. I can press up to select it, but then poof, it goes to cycle again. Unlike the guy in the video:

OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!

erkme73 said:
OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!
Click to expand...
Click to collapse
Now you are good to go. Odin will detect and you can flash it.

Thanks... doing it now. I'll let you know how great you are as soon as it starts working! Thanks...

Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
That's great to see your device is working now.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
If you really wanna stay on stock you can use Chainfires Autoroot for this device.
Anyway, my P605 is on LOS17.1 running stable.