(edit: is my device bricked? it won't load Android now, but is in fastboot
also should i have updated Android first?
i'm thinking of keeping it stock at this point, or maybe finish rooting if possible.)
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
I also downloaded drivers from Google but i'm not sure how to install the DLL file until the device is out of Fastboot?
I tried using the menu to boot to Recovery. Didn't work.
In Device Manager, should i select Android Bootloader Interface to update to this driver?
Or wait until i can select it as a normal Android device after if it's possible to boot it normally?
And what about the website Flash.Android.com? could that get me to stock safely? but not rooted.
Sanman99 said:
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
Click to expand...
Click to collapse
If the next thing you did was
Sanman99 said:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
Click to expand...
Click to collapse
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Sanman99 said:
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
Click to expand...
Click to collapse
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
Sanman99 said:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
Click to expand...
Click to collapse
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?
V0latyle said:
If the next thing you did was
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?
Click to expand...
Click to collapse
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.
Sanman99 said:
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
Click to expand...
Click to collapse
When it says OKAY, that means it successfully flashed.
Sanman99 said:
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
Click to expand...
Click to collapse
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
Sanman99 said:
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
Click to expand...
Click to collapse
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
Sanman99 said:
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Click to expand...
Click to collapse
One step at a time, I think fixing this should be pretty easy.
Sanman99 said:
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.
Click to expand...
Click to collapse
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.
V0latyle said:
When it says OKAY, that means it successfully flashed.
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
One step at a time, I think fixing this should be pretty easy.
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.
Click to expand...
Click to collapse
tried the (unpatched) factory boot image now
with a different USB cable (both are USB-A to USB-C)
C:\path>fastboot flash boot "C:\path\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.627s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.506s]
Finished. Total time: 2.465s
Yes i followed the steps
Here is what i originally did
Yes i downloaded a Magisk apk from the guide I mentioned which links to Github
and i updated the app after opening it
then patched the Boot.img and copied to my computer
I'm reading your thread now, which directed to this
[GUIDE] Pixel 4 "flame": Unlock Bootloader, Update, Root, Pass SafetyNet
If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4XL Pixel 4a Pixel 4a (5G) Pixel 5 Pixel 5a Pixel 6 Pixel 6 Pro For best results, use the latest stable Magisk release. Discussion...
forum.xda-developers.com
Yes i downloaded the correct Factory image
I had enabled USB Debugging
and
yep i did the
fastboot flashing unlock
and this is where the problem happened
(well unrelated, i didn't rename the patched-boot.img)
fastboot flash boot <drag and drop master root.img here>
as i copied the output...it took like 2 seconds and gave that message saying something about the OS version
and i can't get ADB working...
Should I have used the PixelFlasher tool?
I don't know what went wrong or what to do now. As I said, some others have had this same error.
i just tried again with fastboot from the SDK directory
C:\Users\path\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot "C:\Users\path\Downloads\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.617s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.491s]
Finished. Total time: 2.457s
It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.
V0latyle said:
It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.
Click to expand...
Click to collapse
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
i don't know what vbmeta is.
I can't boot into anything but fastboot.
If I go on the Flash.Android.com website, should i flash to Android 12?
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
how can i check which one this is?
i know you said check if it says Flame
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
---
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
so i just have to flash the Boot.img from this
and then patch it again, right?
Sanman99 said:
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
Click to expand...
Click to collapse
Yeah, that's a pretty common problem.
Sanman99 said:
i don't know what vbmeta is.
Click to expand...
Click to collapse
Don't worry about it
Sanman99 said:
I can't boot into anything but fastboot.
Click to expand...
Click to collapse
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Sanman99 said:
If I go on the Flash.Android.com website, should i flash to Android 12?
Click to expand...
Click to collapse
Just update to the latest version, if you haven't already.
Sanman99 said:
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
Click to expand...
Click to collapse
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
Sanman99 said:
how can i check which one this is?
i know you said check if it says Flame
Click to expand...
Click to collapse
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Sanman99 said:
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
Click to expand...
Click to collapse
Yeah that's the wrong one
Sanman99 said:
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
Click to expand...
Click to collapse
Yep
Sanman99 said:
so i just have to flash the Boot.img from this
Click to expand...
Click to collapse
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
{
"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"
}
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
In this folder will be the various images for the system update; the one you need is boot.img:
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Sanman99 said:
and then patch it again, right?
Click to expand...
Click to collapse
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.
V0latyle said:
Yeah, that's a pretty common problem.
Don't worry about it
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Just update to the latest version, if you haven't already.
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Yeah that's the wrong one
Yep
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
View attachment 5812273
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
View attachment 5812283
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
View attachment 5812285
In this folder will be the various images for the system update; the one you need is boot.img:
View attachment 5812289
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.
Click to expand...
Click to collapse
yeah yeah sorry i didn't reply
and thanks so much for the explanation
i was busy setting up my phone
but realized GrapheneOS isn't supposed to have root anyways
so now i have to decide if I want a custom ROM or just Stock with root, or maybe GrapheneOS and whether to put Google services on it and a bunch of apps defeating its purpose in some ways
flashing the phone went very smoothly. Then i put GrapheneOS on it.
if you have any advice about which ROM to do, i'd appreciate it
lots of features are built into Stock now anyways
in that case, i'd just reflash the Magisk patched boot image and then lock the bootloader in settings again?
or i have to reinstall Stock entirely
maybe Android Flash Tool and not that Flash.Android.com
i've done this for multiple phones over the years but i guess i've never understood it thoroughly
i can check for a guide....(and follow it carefully lol)
awesome help. this saved me a bit of stress today.
Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.
V0latyle said:
Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.
Click to expand...
Click to collapse
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.
Sanman99 said:
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.
Click to expand...
Click to collapse
Well, GrapheneOS sets a custom root of trust, so as long as nothing is modified, you can relock the bootloader. You won't be able to have root, though. I generally advise against locking the bootloader unless you're on bone stock firmware.
As for ROMs, I don't have a lot of experience with custom ROMs, especially not in the past 6 years or so. My daily is a Pixel 5, and I'm pretty happy with the OEM firmware. I do have a Samsung tablet that I'm running an AOSP Developer Preview GSI on; I had tried LineageOS first, didn't like it that much, then figured out how to install a GSI. The Pixel 3 and newer should be Project Treble compliant, so you could potentially use a GSI if you wanted.
By the way, GSI = Generic System Image. The idea is that it can run on almost any device, utilizing the stock kernel, and does not require porting or any other customizations to get it to run on other devices.
Related
Guide for installing new security update with fastboot and with a bootloader-unlocked Pixel XL.
This is basically the same thing as usual but with the new structure.
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This is the solution.
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
I assume you already have anything to do fastboot command. If not, see this good thread.
1) Download your system image for Marlin (Pixel XL) on google website.
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
2) Unzip the file marlin-nde63v-factory-a66866ba.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-nde63v.zip
4) Reboot into bootloader
Code:
adb reboot bootloader
5) Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot flash bootloader bootloader-marlin-*.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Here we go, you have a fresh unrooted vanilla android with latest security patch.
6) To add TWRP and Root:
Code:
fastboot boot /path/to/twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Root thread for more information.
TWRP thread for more information.
** Reserved **
cam30era said:
@firewave,
Thanks for posting the guide. Just like Nexus devices except for the slot files. After unzipping the factory image, I do notice 15 additional files (other than boot, system, vendor, etc) that I've never seen before on a Nexus device. Do you happen to know what those are for, and why we don't flash them if doing a manual fastboot flash?
Thanks, in advance....
Click to expand...
Click to collapse
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
firewave said:
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
Click to expand...
Click to collapse
aboot is actually part of the bootloader.
death2all110 said:
aboot is actually part of the bootloader.
Click to expand...
Click to collapse
yep, it's why I'm unsure what to do with. Probably nothing.
I will loopmount the file at home and see.
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
wx9kvh said:
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
Click to expand...
Click to collapse
In the op in bold, he said it will not erase your data or apps
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
dablitzkrieg said:
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
Click to expand...
Click to collapse
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
chapelfreak said:
In the op in bold, he said it will not erase your data or apps
Click to expand...
Click to collapse
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
wx9kvh said:
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
Click to expand...
Click to collapse
That makes sense, our posts are an hour apart or so.
Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
I appreciate the help. The link you provided me, I've downloaded it, but for some reason cant launch the app after I unzip the file. I've been at this for like 4 hours. I've tried so many different things and can't get past the Google screen. Please help
I was able to utilize the old tool. I'm all set. Thanks
chapelfreak said:
That makes sense, our posts are an hour apart or so.
Click to expand...
Click to collapse
Lol. No big deal haha.
Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
Scott...can I flash the radio.img from V to the Verizon X. This radio is horrible
ADB Sideload Works too
Alternatively, use the instructions found on this page followed by a re-flash of your preferred kernel and a fastboot boottoroot to regain root.
https://developers.google.com/android/nexus/ota
So i just followed all of these instructions, and when going into about phone, it shows that i am now on an N build and still with the October security patch. What did i miss?
Update :
I believe I fixed the issue. The little window with the commands in it for some reason had scrolled up and I missed the flashing the "bootloader-marlin-*" step.
Update 2 :
I am now on X with the November security update. GREAT GUIDE!
Followed it to a T and soft bricked mine so now trying to find a way to fix or toss it out the windows haha. Just a heads up guys.
Ended up using the skipsoft tool and pushing a factory update same results but lost data/apps no biggie.
This is odd i followed the instructions trying to flash X to my phone coming from NDE63P and somehow ended up on NDE63N (Ignore this i missed a command)
What steps do I need to add if I want to completely restore back to factory settings (format userdata)? Or would it be the same to just factory reset through the newly restored stock recovery?
Hi,
I am currently flashing my Nexus 6P with OS 7.1.1
After executing flash-all.bat as suggested on Android factory images i get the below error:
"sending 'bootloader' (3532 KB)...
OKAY [ 0.103s]
writing 'bootloader'...
OKAY [ 0.202s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.081s]
finished. total time: 0.084s
sending 'radio' (48728 KB)...
OKAY [ 1.086s]
writing 'radio'...
OKAY [ 2.175s]
finished. total time: 3.267s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.018s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1473177068 bytes
error: update package missing system.img
Press any key to exit..."
Can anyone help out in this? Not sure what does failed to allocate -1473177068 bytes means? How can I solve this.
Try flashing each IMG file manually.
Don't use the flash-all.bat program. Manually type in your fastboot commands.
Extract that big ZIP you have in the same folder with your flash-all.bat. You'll see a bunch of img files called vendor.img, system.img, etc.
Once extracted, run the following commands in order. Replace "partition" with the img file name. Example: fastboot format system
fastboot format partition (if it gives an error, try fastboot erase partition).
fastboot flash partition imgfile
fastboot format cache
fastboot reboot-bootloader
Examples of what things should look like:
fastboot format system
fastboot flash system system.img
fastboot format cache
fastboot reboot-bootloader
<once rebooted, shouldn't take more than 2 seconds>
fastboot format vendor
fastboot flash vendor vendor.img
fastboot format cache
fastboot reboot-bootloader
<again, reboot, ~2 seconds>
If at any time it says it can't format memory type or something similar, usually this is for bootloader, radio and boot partitions, use fastboot erase boot (fastboot erase bootloader, fastboot erase radio).
Do this for each of the files, except for userdata - don't even flash that, just format userdata and skip the flash userdata part.
Also, flash your recovery of TWRP, the latest, and make sure that you boot to recovery first, before you boot the phone all together.
Did you verify the checksum of the image?
DON'T DO THAT...
Wiltron said:
fastboot erase bootloader
Click to expand...
Click to collapse
This will be your last fastboot command... Phone bricked.
To the OP, you should solve your flash-all problem as this script is the recommended way to flash factory images. You need some disk space (like 4 or 5GB)
rchtk said:
DON'T DO THAT...
This will be your last fastboot command... Phone bricked.
Click to expand...
Click to collapse
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Wiltron said:
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Click to expand...
Click to collapse
I find it way too risky tbh and don't see any added value in doing this.
rchtk said:
I find it way too risky tbh and don't see any added value in doing this.
Click to expand...
Click to collapse
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
RoyJ said:
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
Click to expand...
Click to collapse
Thank you RoyJ.....it worked
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
wormbaby11 said:
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
Click to expand...
Click to collapse
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Thanks Roy, that did the trick.
RoyJ said:
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Click to expand...
Click to collapse
Glad to hear you got it working!
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
I've tried to update my 6T (it was unlocked, used TWRP and Magisk rooted) to the new version following the guide here but I had errors doing it like described here.
So, now I can only boot into fastboot mode (I can't even access recovery mode ). I tried to use the Tool All In One but it returns me the error that my "phone is not in Adb mode".
It seems not giving me errors when I use fastboot boot command:
Code:
PS C:\adb> fastboot devices
203cbc6e fastboot
PS C:\adb> fastboot boot .\twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.384s]
booting...
OKAY [ 0.091s]
finished. total time: 0.477s
but the phone just exit fastboot, display OnePlus logo and stop! :crying:
Please I just wish to recover the phone from the beginning. Anyone could help me? :angel:
RikiBez said:
I've tried to update my 6T (it was unlocked, used TWRP and Magisk rooted) to the new version following the guide here but I had errors doing it like described here.
So, now I can only boot into fastboot mode (I can't even access recovery mode ). I tried to use the Tool All In One but it returns me the error that my "phone is not in Adb mode".
It seems not giving me errors when I use fastboot boot command:
Code:
PS C:\adb> fastboot devices
203cbc6e fastboot
PS C:\adb> fastboot boot .\twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.384s]
booting...
OKAY [ 0.091s]
finished. total time: 0.477s
but the phone just exit fastboot, display OnePlus logo and stop! :crying:
Please I just wish to recover the phone from the beginning. Anyone could help me? :angel:
Click to expand...
Click to collapse
You can use the msm tool like starting from scratch. Make sure to use 9.0.11 if you're on T-Mobile
https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
Or you can follow this video. I just went from 9.0.13 rooted and twrp back to 9.0.11.
https://www.youtube.com/watch?v=Mh-tjPPz2Ws
Now you'll be on stock OOS 9.0.11. If you want to oem unlock, root with magisk and install twrp.
Follow this guide but instead of using the provided TWRP and magisk on this guide:
https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Use the latest which at this moment is 3.2.3-2 and magisk v19.0
https://twrp.me/oneplus/oneplus6t.html
Download:
twrp-installer-fajita-3.2.3-2.zip and twrp-3.2.3-2-fajita.img
Place both of those in the adb folder. For me mine is C:/adb/
Download Magisk zip and apk.
https://magisk.me/
Place Magisk 19 zip into adb folder.
Now follow the guide and when you get to step 3. Use the new commands for the new twrp and magisk.
Use these commands:
fastboot boot twrp-3.2.3-2-fajita.img
adb sideload twrp-installer-fajita-3.2.3-2.zip
adb sideload Magisk-v19.0.zip
Once your phone boots up transfer the magisk apk from your computer to your phone
or download it from your phone and install the apk.
Now you're good to go!
Sent from my OnePlus 6T using XDA-Developers Legacy app
i7vSa7vi7y said:
You can use the msm tool like starting from scratch
https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I’ll give it a try. Thanks i7vSa7vi7y
UPDATE: Perfect, this worked and now the device is working. I'm going to try to root it again and I'll hope the OnePlus Switch backup will be restorable. Thanks again i7vSa7vi7y
RikiBez said:
I've tried to update my 6T (it was unlocked, used TWRP and Magisk rooted) to the new version following the guide here but I had errors doing it like described here.
So, now I can only boot into fastboot mode (I can't even access recovery mode ). I tried to use the Tool All In One but it returns me the error that my "phone is not in Adb mode".
It seems not giving me errors when I use fastboot boot command:
Code:
PS C:\adb> fastboot devices
203cbc6e fastboot
PS C:\adb> fastboot boot .\twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.384s]
booting...
OKAY [ 0.091s]
finished. total time: 0.477s
but the phone just exit fastboot, display OnePlus logo and stop! :crying:
Please I just wish to recover the phone from the beginning. Anyone could help me? :angel:
Click to expand...
Click to collapse
i've had that happen to me a time or two, good news is that it is an easy fix. Here is a post with the file you're gonna need, make sure you get 3.3.0-2 image and installer, you are gonna need them for this. Also, if you don't have adb and fastboot tools go ahead and get them. You will also need a working rom.
From fastboot, use the following commands:
Fastboot boot twrp-fajita-3.3.0-2.img
when it boots up go into Advanced > ADB Sideload
adb sideload twrp-fajita-3.3.0-2-installer.zip
Reboot recovery
Factory reset (DONT wipe the system)
Adb sideload rom.zip
If you want magisk,
adb sideload magisk.zip
reboot
You have successfully avoided nuclear rage.
RikiBez said:
I've tried to update my 6T (it was unlocked, used TWRP and Magisk rooted) to the new version following the guide here but I had errors doing it like described here.
So, now I can only boot into fastboot mode (I can't even access recovery mode ). I tried to use the Tool All In One but it returns me the error that my "phone is not in Adb mode".
It seems not giving me errors when I use fastboot boot command:
Code:
PS C:\adb> fastboot devices
203cbc6e fastboot
PS C:\adb> fastboot boot .\twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.384s]
booting...
OKAY [ 0.091s]
finished. total time: 0.477s
but the phone just exit fastboot, display OnePlus logo and stop! :crying:
Please I just wish to recover the phone from the beginning. Anyone could help me? :angel:
Click to expand...
Click to collapse
The obvious reason why this was failing was that you were trying to boot the installer zip file, not the TWRP image. The correct file you were supposed to use was twrp-3.2.3-2-fajita.img.
He's right. You want to boot the img which allows twrp to show on your phone but isn't installed. Then you use twrp to sideload and use fastboot to install the twrp zip and it will install on your phone. I edited my post and added the commands and files you need.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Working method to update your rooted op6t
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
ReBoot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
sanjeev7 said:
Working method to update your rooted op6t
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
Click to expand...
Click to collapse
Even easier. Install full ROM with updater, install Magisk from manager, reboot. Voilá! No need for TWRP. Unless you want TWRP of course.
CazeW said:
Even easier. Install full ROM with updater, install Magisk from manager, reboot. Voilá! No need for TWRP. Unless you want TWRP of course.
Click to expand...
Click to collapse
Yo! Yeah I want TWRP so I follow that
I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311
Hi, it feels so good to see that I'm not the only one suffering (suffered in your case) with this problem. I just have a doubt.
We are erasing bootloader in your steps but while again installing all these files we are neither installing any bootloader img nor it is there in the rom package. Now I that that if your bootloader is gone, your device is as good as a brick, for real. Could you shed some light on this?
Awaiting your reply.
Thanks and regards.
EDIT:
I think my tab just died, while flashing tos from minimal adb and fastboot, I noticed the screen was pulsing, fastboot logo was still there but like flickering and fastboot message came back that it failed to write. I disconnected usbcable and reconnected and tab isnt detected, fastboot says target didnt report max download size and windows doesnt see the tab.
I switched off and tried to reboot to fastboot but the tab wont respond anymore. Screen doesnt come on.
What to do?
It is working
The guide was working, although flashing the dtb file wasn't succesfull its working. Later I will update to Custom ROM.
Thanks a lot, got my Pado back to life. As Guy.brush said dtb fails but it still works.
Failed Flashing DTB
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
---------- Post added at 03:31 PM ---------- Previous post was at 03:01 PM ----------
C4DXYZ-XDA said:
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
Click to expand...
Click to collapse
but it still work.. my mipad is back to life..
adi4u4882 said:
I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311
Click to expand...
Click to collapse
Thanks, where could I find rom to get dtb file? Thanks
Wow it is working
Even i got the same error
"sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))"
then I did flash ,using Mi flash tool..
Now it is working fine..
after (2015-2019)so many years.. Today 31st May 2020 device came back to normal..
I tried many methods.. Nothing works..
Thank you so much for this post..
I went to three different MI service center..and many other mobile repair shop..no one did..
You did big help..
Thank you so much..
I followed all the instructions one by one. The process was completed successfully too, except dtb (which error many others have faced). Rebooted. Then flashed the same ROM using MiFlash tool. BUT still my tab is stuck in mi logo. I don't know what to do. Is there anything I am missing during following the instructions? I can still enter into fastboot mode and also recovery; so the tab isn't completely hardbricked though. Please help. I am just stuck in the mi logo.
In my case even it doesn't go to fastboot mode neither recovery. Stuck in mi logo. Please someone help me
While flashing I found that recovery.img and tos.img exists in both the fastboot file and the blobs file. Which one should I use? I tried using the fastboot files but it didn't work out and i'm stuck on the mi logo.
Also while flashing via miflash, got an error :
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done.
which I found out is to be ignored and the flash will still work. It is just a checkpoint fail because the device wasn't locked during the flashing process. Could it be the issue ?
My Mipad is bricked now,,so I'm working on short mydevice using the memory card slot,.. its kind of tricky to get it back to life again,,hihihihhi,,
Just registered an account to say thank you. I tried flashing original fastboot rom thousands times but no luck. Your guide helped.
{
"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'm trying like this,, and it worked..
It worked for me.
The "tegra124-mocha.dtb" file can be found within the fastboot rom package that I downloaded named "Xiaomi_Mi_Pad_V8.1.2.0.KXFCNDI_20161128_China_4.4_XFT"
via:
Xiaomi Mi Pad Stock ROM Firmware (Fastboot Flash File)
Download the official Xiaomi Mi Pad Stock ROM Firmware (Flash File) for your Xiaomi Smartphone. We also provide Stock ROM for other Xiaomi devices.
xiaomistockrom.com
Intend to move onto custom rom LOS15 or later...
Wish me luck, read that camera is broken in LOS15-16 for mocha
Now to reinstall TWRP
via:
Download twrp-3.4.0-0-mocha.img
Download page for twrp-3.4.0-0-mocha.img
dl.twrp.me
Then re-merge the partitions.
"Repartition_MI_Pad_1_2GB_zardMi3.zip"
via:
Repartition_MI_Pad_1_2GB_zardMi3.zip | by ANHTUAN9791 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Miui 8 : How To?
Hi, On the recent post, miui 8 is available for the mipad. But before update we need to merge the both partitions. "For Xiaomi MiPAD 1 is required to merge both system partitions" We are invite to follow à link : http://en.miui.com/thread-118294-1-1.html Ok.....but I just understand...
xiaomi.eu
[GUIDE][HOW TO]Flash TWRP And Merge Partitions on Mi Pad 1 (Mocha)
Screenshots will be added later on /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have...
forum.xda-developers.com
LineageOS 16.0 | 19.04.2020 | Shield blobs
LineageOS 16.0 Requirements: 1) active system1 2) merged system partition 3) BRAIN, READING SKILL and presence of basic knowledge about firmware (in the absence need learn to independently) Instruction 1) download TosForPSCI-0.1.zip...
forum.xda-developers.com
This thread & the blob saved my device. Thanks a lot.
Thank you sooo much! It helped to revive my Mi Pad!
As the title says, I just finished flashing twrp-3.5.1_9-0-davinci.img unto my phone, and when I fastboot boot into the TWRP file, my screen turns black (doesn't turn off). If I hold my powerbutton the phone restarts again. Yes I have unlocked OEM and unlocked the bootloader and the USB debugger. I am not that familiar with this whole proces in general, so please bear with me, I just want to get rid of MiUI and get the Pixel Experience, that's all.
So, to retrace my steps:
I downloaded platform-tools, put the latest TWRP file in the folder and opened cmd, and typed in:
adb devices
where I got:
List of devices attached
70cc38df device
Then I used
adb reboot bootloader
and it booted into the fastboot correctly.
I checked it with fastboot devices, showing 70cc38df fastboot, and then the following:
fastboot boot twrp-3.5.1_9-0-davinci.img
Sending 'boot.img' (65536 KB) OKAY [ 1.383s]
Booting OKAY [ 0.141s]
Finished. Total time: 1.570s
Next one, to get into the TWRP:
fastboot boot twrp-3.5.1_9-0-davinci.img
Sending 'boot.img' (65536 KB) OKAY [ 1.392s]
Booting OKAY [ 0.139s]
Finished. Total time: 1.576s
But doing this made the screen turn black, as I mentioned before, and I can't do anything.
Retry using adb devices gave:
List of devices attached
My device has disappeared, and I don't know why.
All I want is the pixel experience, and get off MiUI, so please if anyone can help it would be gladly appreciated.
Thanks in advance.
Patikekfad said:
As the title says, I just finished flashing twrp-3.5.1_9-0-davinci.img unto my phone, and when I fastboot boot into the TWRP file, my screen turns black (doesn't turn off). If I hold my powerbutton the phone restarts again. Yes I have unlocked OEM and unlocked the bootloader and the USB debugger. I am not that familiar with this whole proces in general, so please bear with me, I just want to get rid of MiUI and get the Pixel Experience, that's all.
So, to retrace my steps:
I downloaded platform-tools, put the latest TWRP file in the folder and opened cmd, and typed in:
adb devices
where I got:
List of devices attached
70cc38df device
Then I used
adb reboot bootloader
and it booted into the fastboot correctly.
I checked it with fastboot devices, showing 70cc38df fastboot, and then the following:
fastboot boot twrp-3.5.1_9-0-davinci.img
Sending 'boot.img' (65536 KB) OKAY [ 1.383s]
Booting OKAY [ 0.141s]
Finished. Total time: 1.570s
Next one, to get into the TWRP:
fastboot boot twrp-3.5.1_9-0-davinci.img
Sending 'boot.img' (65536 KB) OKAY [ 1.392s]
Booting OKAY [ 0.139s]
Finished. Total time: 1.576s
But doing this made the screen turn black, as I mentioned before, and I can't do anything.
Retry using adb devices gave:
List of devices attached
My device has disappeared, and I don't know why.
All I want is the pixel experience, and get off MiUI, so please if anyone can help it would be gladly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
I'm not using Pixel, but using TWRP (and Xiaomi.eu ROMs)
I think that I tested long ago (at the time I was on A9 or A10 - now I'm on A11, and with an older version of TWRP), and that fastboot boot to TWRP did not work
I have TWRP flashed - IMO, you should also do
fastboot flash recovery ...
fastboot oem reboot-recovery
Btw, there are some guides about installing the custom ROMs, please follow them
zgfg said:
I'm not using Pixel, but using TWRP (and Xiaomi.eu ROMs)
I think that I tested long ago (at the time I was on A9 or A10 - now I'm on A11, and with an older version of TWRP), and that fastboot boot to TWRP did not work
I have TWRP flashed - IMO, you should also do
fastboot flash recovery ...
fastboot oem reboot-recovery
Btw, there are some guides about installing the custom ROMs, please follow them
Click to expand...
Click to collapse
Holy moly I don't know really what happened but it worked, thanks a lot mate.
Btw, just switched from SkyHawk to that new twrp-3.5.1_9-0-davinci, it works fine with Xiaomi.eu A11
Ofc, I always flash custom recoveries
zgfg said:
I'm not using Pixel, but using TWRP (and Xiaomi.eu ROMs)
I think that I tested long ago (at the time I was on A9 or A10 - now I'm on A11, and with an older version of TWRP), and that fastboot boot to TWRP did not work
I have TWRP flashed - IMO, you should also do
fastboot flash recovery ...
fastboot oem reboot-recovery
Btw, there are some guides about installing the custom ROMs, please follow them
Click to expand...
Click to collapse
Hi,
I had the same problem as Patikekfad, but unlike him, I have not yet been able to solve it. I tried the oem recovery reboot, but it had no effect. I can flash the TWRP, but not boot into it. The screen is stuck on that Fastboot bunny. DO you know what I'm doing wrong ? Or, even better, a straight forward way to solve this ? Noob here, please don't tell me to "flash" something as I have no idea what that means. I can "click" and "type" and "press enter"
Wantwrp said:
Hi,
I had the same problem as Patikekfad, but unlike him, I have not yet been able to solve it. I tried the oem recovery reboot, but it had no effect. I can flash the TWRP, but not boot into it. The screen is stuck on that Fastboot bunny. DO you know what I'm doing wrong ? Or, even better, a straight forward way to solve this ? Noob here, please don't tell me to "flash" something as I have no idea what that means. I can "click" and "type" and "press enter"
Click to expand...
Click to collapse
Sorry, I don't feel it us my duty to read old nessages thying to depict what kind of problems somebody had in the past and how it was solved
When you have a problem, precisely describe what is your problem, what/how you do (if you want to know what are you doing wrong), and exactly describe your ROM, TWRP, whatever is relevant for the problem
If your question is something about Pixel XXX custom ROM - sorry, I don't use and let it better answer somebody else familiar with your cutom ROM
zgfg said:
Sorry, I don't feel it us my duty to read old nessages thying to depict what kind of problems somebody had in the past and how it was solved
When you have a problem, precisely describe what is your problem, what/how you do (if you want to know what are you doing wrong), and exactly describe your ROM, TWRP, whatever is relevant for the problem
If your question is something about Pixel XXX custom ROM - sorry, I don't use and let it better answer somebody else familiar with your cutom ROM
Click to expand...
Click to collapse
Pixel... ? No, man, I'm thinking about de-googling the phone more than anything else. Once I get it to run. I literally did what the OP describes. I wouldn't want to insult anybody by copying his message, but apart from the device number, my process was identical.
I saw Lineage 18.1 has been available for a few weeks. Thought about making this my first custom ROM. What do you think, is that a good choice ?
Wantwrp said:
Pixel... ? No, man, I'm thinking about de-googling the phone more than anything else. Once I get it to run. I literally did what the OP describes. I wouldn't want to insult anybody by copying his message, but apart from the device number, my process was identical.
I saw Lineage 18.1 has been available for a few weeks. Thought about making this my first custom ROM. What do you think, is that a good choice ?
Click to expand...
Click to collapse
I'm on Xiaomi.eu MIUI 12.6, A11 beta, didn't try LOS and similar open source ROMs