Database Info

New to Nexus, stuck in Fastboot! Please Help!

Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???

Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686

Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.

matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?

zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.

matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)

zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.

matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse

Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.

matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.

zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!

matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?

Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!

matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!

Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App

[Q] updating to 4.4.4

I'm searched for an hour tonight, and am probably looking right over it. My phone is currently on 4.4.3 and is very slow to restart. Can someone help me to find a video tutorial on how to flash 4.4.4?
Thanks!!

I did download the 4.4.4 firmware zip file from here. I am very rusty with using the command terminal on my pc though. This is where I'm hoping for a video tutorial.
forum.xda-developers.com/showthread.php?t=2723159&page=4

Are you S-OFF and rooted? Custom ROM and recovery? Stock rooted?
The more info you give about your phones current state the better we can help point you in the right direction.

The Stig 04 said:
Are you S-OFF and rooted? Custom ROM and recovery? Stock rooted?
The more info you give about your phones current state the better we can help point you in the right direction.
Click to expand...
Click to collapse
I'm sorry....yes, I am S-off, and rooted. I currently have a custom ROM on my phone, but my android version is currently 4.4.3

ddodge68 said:
I'm sorry....yes, I am S-off, and rooted. I currently have a custom ROM on my phone, but my android version is currently 4.4.3
Click to expand...
Click to collapse
Cool, just wanted to make sure. There is a video on there from DMX that shows how to flash the firmware. I linked that below. He does it on mac but the commands are the same if you do it on a windows computer. If you open the command window in your fastboot folder (shift+right click, open command window here) you can skip the long command he types at around the 3:40 mark and jump right into the commands at 3:51.
https://www.youtube.com/watch?v=e21qb7iZAOo&feature=youtube&app=desktop
Sorry it took so long to respond, but work calls! If you have any trouble let us know!

The Stig 04 said:
Cool, just wanted to make sure. There is a video on there from DMX that shows how to flash the firmware. I linked that below. He does it on mac but the commands are the same if you do it on a windows computer. If you open the command window in your fastboot folder (shift+right click, open command window here) you can skip the long command he types at around the 3:40 mark and jump right into the commands at 3:51.
https://www.youtube.com/watch?v=e21qb7iZAOo&feature=youtube&app=desktop
Sorry it took so long to respond, but work calls! If you have any trouble let us know!
Click to expand...
Click to collapse
As long as you're being so helpful, again, I've downloaded the zip file from the above link. Do I need any of the other files?

ddodge68 said:
As long as you're being so helpful, again, I've downloaded the zip file from the above link. Do I need any of the other files?
Click to expand...
Click to collapse
You downloaded the 4.4.4 firmware zip (no boot.img, no recovery.img) from Tigerstown thread? Then no, you don't need anything else to update your firmware.
This will only update your firmware. You will be on the same rom with the same recovery and remember to flash it twice as he described it in the instructions.
UNLESS you use the HTC fastboot.exe from here:
http://forum.xda-developers.com/showpost.php?p=56890497&postcount=3
This fastboot version will do everything needed in one flash.
I installed this fastboot version alongside my "normal" fastboot/adb which I use for my other devices and use it for the M8 exclusively.

Droid Ultra Bricked on su6-7.3 4.4.4

i've been trying to unbrick this thing for hours after failed root attempt....i'm trying to use rsd lite to flash back to stock.....i now have access to fastboot and recovery and whatnot.... i cant seem to find the firmware i need to unbrick it. the latest i can find is su6-7.2! if someone found su6-7.3 i feel like that would fix it and id be so happy!!!!!!!rsd fails with 7.2

Su6-7.3 is just the security update.
Just use fastboot to flash the partitions with su6-7.2, you will get the update notification after you're up and running.
I had issues with rsdlite and my ultra when I had it.
Look for Minimal adb and fastboot, you will also need mfastboot to flash the system partition, as its too big for fastboot to handle. If you need instructions on how to manually flash the device, a quick search will reveal easy to follow directions.

Shovales said:
Just use fastboot to flash the partitions. I had issues with rsdlite and my ultra when I had it.
Look for Minimal adb and fastboot, you will also need mfastboot to flash the system partition, as its too big for fastboot to handle. If you need instructions on how to manually flash the device, a quick search will reveal easy to follow directions.
Click to expand...
Click to collapse
but were do i get the stuff im flashing back onto the phone...im pritty sure its system is blank right now

Minimal adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Mfastboot:
https://www.androidfilehost.com/?fid=95916177934532795
Firmware:
http://motofirmware.center/files/file/208-cfc-obake_verizon-user-444-su6-72-release-keysxmlzip/
Instructions:
http://forum.xda-developers.com/showthread.php?t=2580060

Shovales said:
Sorry see the my edited post above
Click to expand...
Click to collapse
ok cool im going to try mfastboot now fyi my bootloader is locked still

You're flashing a stock firmware which is signed for the device, so the bootloader being locked isnt problem.
Also mfastboot is used for the system.img to the system partition, you can use fastboot for the other img's.

Shovales said:
Minimal adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Mfastboot:
https://www.androidfilehost.com/?fid=95916177934532795
Firmware:
http://motofirmware.center/files/file/208-cfc-obake_verizon-user-444-su6-72-release-keysxmlzip/
Instructions:
http://forum.xda-developers.com/showthread.php?t=2580060
Click to expand...
Click to collapse
i downloaded that firmware already and when i go to extract it its corrupted... i downloaded 3 from the website and still all were corrupted wile unzipping the system image... i redownloaded just to make sure....any other places i can get the firmware?

What are you using to extract the files with?

Shovales said:
What are you using to extract the files with?
Click to expand...
Click to collapse
i tried windows native extract and 7-zip

Winrar I've never had an issue with any file from motofirmware
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
Wait, you said the system image? Do you mean the actual system.img file?

Shovales said:
Winrar I've never had an issue with any file from motofirmware
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
Wait, you said the system image? Do you mean the actual system.img file?
Click to expand...
Click to collapse
i downloaded the zips off of that website already and i was wondering if i can just get links to flash everything individually through fastboot

logan71f100 said:
i downloaded the zips off of that website already and i was wondering if i can just get links to flash everything individually through fastboot
Click to expand...
Click to collapse
Unless you can find the individual files somewhere the firmware zip file that you have is all you got. I downloaded and extracted that same file no more than 2 weeks ago, and nev
er had one bit of trouble with it..

Shovales said:
Unless you can find the individual files somewhere the firmware zip file that you have is all you got. I downloaded and extracted that same file no more than 2 weeks ago, and nev
er had one bit of trouble with it..
Click to expand...
Click to collapse
well im downloading the file again and i installed winrar...would you by chance be able to upload that old file you have to google drive i can give you a link to my drive so you can upload it if you have it

logan71f100 said:
well im downloading the file again and i installed winrar...would you by chance be able to upload that old file you have to google drive i can give you a link to my drive so you can upload it if you have it
Click to expand...
Click to collapse
i just downloaded it again this is the winrar error im getting
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: Checksum error in C:\Users\Logan\Downloads\system.img. The file is corrupt
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: The archive is corrupt
both om my pcs get the same error wile extracting

logan71f100 said:
i just downloaded it again this is the winrar error im getting
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: Checksum error in C:\Users\Logan\Downloads\system.img. The file is corrupt
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: The archive is corrupt
both om my pcs get the same error wile extracting
Click to expand...
Click to collapse
I'm having the same problem. I actually need SU6-7 but at this point I'd take SU6-7.2 just to get my phone working again

arcaios26 said:
I'm having the same problem. I actually need SU6-7 but at this point I'd take SU6-7.2 just to get my phone working again
Click to expand...
Click to collapse
do you need the firmware i used to unbrick mine?....btw i got SU6-7.2 to unbrick my SU6-7.3 device.... it is fixed and rooted successfully!

that would work, I bricked mine on 6-7.3
what root method did you use? I'm having a hard time finding one that doesn't require files I can't seem to get downloaded fully

I can try and make a tutorial for you to follow with all files you need in a Google drive for easy access how's that sound?

logan71f100 said:
I can try and make a tutorial for you to follow with all files you need in a Google drive for easy access how's that sound?
Click to expand...
Click to collapse
sounds perfect actually. This phone has given me so many more problems doing this than my old HTC incredible 4g but the phone is far better than that old one.

he only ****ty part us the bootloader is locked and I can't find a way to unlock it. One day there will be a way and I will find it

Help rooting phone received from beta testing.

I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!

I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?

Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed

Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes

bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck

dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?

bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img

dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.

bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.

dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.

bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.

dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com

jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it

Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.

bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it

dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.

dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.

bigroc2223 said:
Nvm
Click to expand...
Click to collapse

dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me

bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said

Plz help me

Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now

Theracerlucky said:
Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
Click to expand...
Click to collapse
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.

V0latyle said:
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.
Click to expand...
Click to collapse
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue

Theracerlucky said:
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue
Click to expand...
Click to collapse
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.

V0latyle said:
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.
Click to expand...
Click to collapse
But bro when I trying to flash with Android flash tool showing this errors

Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
I haven't seen that error before. Your bootloader is unlocked, right?

Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
V0latyle said:
I haven't seen that error before. Your bootloader is unlocked, right?
Click to expand...
Click to collapse
Yes properly unlocked bro

Theracerlucky said:
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
Yes properly unlocked bro
Click to expand...
Click to collapse
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do

Theracerlucky said:
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do
Click to expand...
Click to collapse
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".

V0latyle said:
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".
Click to expand...
Click to collapse
Ok sir i don't installed any custom recovery now my devices all things is stock

Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.

V0latyle said:
Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.
Click to expand...
Click to collapse
Sir i know this process but my tension is this process work properly or i brick my device

Theracerlucky said:
Sir i know this process but my tension is this process work properly or i brick my device
Click to expand...
Click to collapse
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.

V0latyle said:
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.
Click to expand...
Click to collapse
Sir can I download this ota file for sideload or other versions

Theracerlucky said:
Sir can I download this ota file for sideload or other versions
Click to expand...
Click to collapse
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.

Sir you busy now ??

When you free sir reply me i have one more last question answer me plz after that i try to sideload the ota

V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
I see a video on YouTube ithink that is the same issues

V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse

V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
Whe
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you
Click to expand...
Click to collapse
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
When I comented this Youtuber brothers he told me to sideload the latest ota file he created the video on 4 year ago but the latest ota is now Android 11 what can I do sir plz help i am confused he doesn't reply me after this comment reply