Database Users

[SOLVED] [Q] fastboot issue

Hi all,
I am currently playing around a bit with my KF and used in the beginning KFU to root with Burrito3. TWRP is functioning + CM9 already installed. BUT now, where I want to use Ravens Kernel with SDK and entering the commands he proposed for the beginning for fastboot, my KF reboots and stops in yellow triangel.
used command:
adb shell
su
idme bootmode 4002
reboot
How to go back to normal boot mode is o.k. and working, but I could no where find what to do/the reason might be, that my KF stops in triangle and how to sort it out. Drivers manually installed with SDK incl. adaption of ini and inf.
Any suggestion?
Thanks and regards
Etam1tlu

Etam1tlu said:
Hi all,
I am currently playing around a bit with my KF and used in the beginning KFU to root with Burrito3. TWRP is functioning + CM9 already installed. BUT now, where I want to use Ravens Kernel with SDK and entering the commands he proposed for the beginning for fastboot, my KF reboots and stops in yellow triangel.
used command:
adb shell
su
idme bootmode 4002
reboot
How to go back to normal boot mode is o.k. and working, but I could no where find what to do/the reason might be, that my KF stops in triangle and how to sort it out. Drivers manually installed with SDK incl. adaption of ini and inf.
Any suggestion?
Thanks and regards
Etam1tlu
Click to expand...
Click to collapse
It's in fast boot mode, just issue the remaining adb commands and you'll be fine.

what do you want to do ? this is the normal behavour when you switch to fastboot ...
---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------
airmaxx23 said:
It's in fast boot mode, just issue the remaining adb commands and you'll be fine.
Click to expand...
Click to collapse
adb commands don't work in fastboot - only fastboot commands

that is what I tried, because I checked if the device is in fastboot and yes it is shown, but if I follow the next command:
fastboot -i 0x1949 boot bootnew.img or
fastboot -i 0x1949 boot cm9bootnew.img
which I placed on the internal sdcard, I get the feedback of the system:
cannot load 'xxxxbootnew.img'
any help with that?

Etam1tlu said:
that is what I tried, because I checked if the device is in fastboot and yes it is shown, but if I follow the next command:
fastboot -i 0x1949 boot bootnew.img or
fastboot -i 0x1949 boot cm9bootnew.img
which I placed on the internal sdcard, I get the feedback of the system:
cannot load 'xxxxbootnew.img'
any help with that?
Click to expand...
Click to collapse
They need to be in the tools folder where you launcher adb from.
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
b63 said:
what do you want to do ? this is the normal behavour when you switch to fastboot ...
---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------
adb commands don't work in fastboot - only fastboot commands
Click to expand...
Click to collapse
I meant fast boot commands, my bad.

as far as i know these commands are to load a image from your computer
would try to do the img files in the same folder as fastboot.exe and retry

thanks very much for your help, after putting the img files into the folder where the fastboot.exe is, all went well.
very cool and now I learned a bit more regarding ADB stuff

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Your device is corrupt. It can't be trusted and may not work properly. help!

Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.

red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked

gd6noob said:
red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked
Click to expand...
Click to collapse
Its just a red triangle with an exclamation mark inside.
I can't post an image because i am a new member and need at least 10 posts.

https://support.google.com/nexus/answer/6185381?hl=en - It says it should dismiss by itself.

chichu_9 said:
- It says it should dismiss by itself.
Click to expand...
Click to collapse
The red logo does disappear and the device transitions to the black and white google boot logo.
It is here where the device becomes hung, i assume it is because the boot.img or boot files have been damaged, but i'm just guessing. What i am confused about is if the boot files are damaged, the nandroid restore should fix this problem (shouldn't it?), but it doesn't.

radaga5t said:
Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.
Click to expand...
Click to collapse
After a root went bad I had the same thing happen. I just used SkipSoft ToolKit and restored back to a stock image (MDB08L).
The corruption message disappeared.

Take a look at this guide By Heisenberg as it will help with some details.
The few times I flashed/reset the phone, I accidentally muddled up some steps. Specifically the flashing the boot and bootloader images.
Code:
[U]fastboot flash bootloader X:/bootloader.img[/U]
fastboot reboot bootloader
fastboot flash radio X:/radio.img
fastboot reboot bootloader
[U]fastboot flash boot X:/boot.img[/U]
fastboot erase cache
fastboot flash cache X:/cache.img
fastboot flash recovery X:/recovery.img
fastboot flash system X:/system.img
fastboot flash vendor X:/vendor.img
I would accidentally flash the bootloader.img image over the boot.img and cause the error, specifically the one you mentioned. I had to go through the flashing process VERY carefully again, and when flashing .imgs for root acess over to the stock ones.
I know is sounds trivial and I'm not saying you don't understand it, but give it a try and see if this resolves the issue. double check your lines and triple check your images (make sure there are NO spaces in the bootloader/boot img file directories. or_replace_spaces_with_underscores). I don't know how many times I have screwed up and it was because of a dash in the wrong spot or space in the .img directory. Let us know how you go.

Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.

I hoped it worked out for you

urbanpitch said:
I hoped it worked out for you
Click to expand...
Click to collapse
Yep i was able to restore the phone via the heisenberg guide. Thanks!

radaga5t said:
Yep i was able to restore the phone via the heisenberg guide. Thanks!
Click to expand...
Click to collapse
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.

Heisenberg said:
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.
Click to expand...
Click to collapse
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
radaga5t said:
Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.
Click to expand...
Click to collapse
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.

barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
Click to expand...
Click to collapse
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.

Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.

barondebxl said:
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.
Click to expand...
Click to collapse
You'll need to find a program that can extract the "tar.gz" compression format.

Heisenberg said:
You'll need to find a program that can extract the "tar.gz" compression format.
Click to expand...
Click to collapse
Ok thank you. 7zip works

barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.
Click to expand...
Click to collapse
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.

radaga5t said:
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.
Click to expand...
Click to collapse
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating

barondebxl said:
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating
Click to expand...
Click to collapse
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location, therefore you need to type the commands so that they include the path to where the files are actually located on your PC.
There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.

Heisenberg said:
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location.
You need to type the commands so that they include the path to where the files are actually located on your PC. There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.
Click to expand...
Click to collapse
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
---------- Post added at 01:48 AM ---------- Previous post was at 01:36 AM ----------
barondebxl said:
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
Click to expand...
Click to collapse
One last question, whats the best method to root MDB08L? I want that chroma rom

No OS Installed While Flashing Android N OTA In TWRP

So yeah I accidentally wiped my partitions as if I were installing a rom. Am I screwed until I get to a pc?
P.s. Out of all days to delete my backup rom file ?

Just set it to boot loader mode and flash stock images...I'm sure there's a tutorial on how to do it..I have the program installed on my computer ready for any time I brick my phone lol but I don't remember the name of the program right now
Edit: heres the link to the method I use http://forum.xda-developers.com/showthread.php?t=3258493

I'm assuming the OP doesn't have a PC due to the last statement he made. I would say yes, nothing you can do until you can get to a PC and flash stock images via Fastboot. Unless you have a ROM zip on your phone that is....which I'm assuming you don't.

You're kinda stuck, you need a PC to flash the factory images. TWRP can't flash OTA's anyway, so don't try that again either. I'd strongly recommend not using a toolkit to flash the factory images too. I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.

Snakielols1984 said:
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Click to expand...
Click to collapse
Can fastboot see your device when you're in bootloader?

Yes fastboot is able to reconize my device.

Snakielols1984 said:
Yes fastboot is able to reconize my device.
Click to expand...
Click to collapse
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.

I've actually tried flashing stock images but every time I tried to run fastboot command I get these errors, "command not found" and I believe the other erro is "file path not found". There's another error that I can't remember off the top of my head what it. When I get home I'll try to run the commands again and see what errors I get
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
elfrosto said:
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
Click to expand...
Click to collapse
on another note I have not flashed Android N OTA. I downloaded that and install via OTA.

wrong thread

so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!

Snakielols1984 said:
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Click to expand...
Click to collapse
What bootloader version are you on currently? Although updated bootloader is recommend, you should be able to skip this step without any issues.

Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader

Snakielols1984 said:
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Click to expand...
Click to collapse
Please post the entire command you are using, as written in your terminal prompt. "No command" sounds like an unrecognized command is being issued. We must use ./ in addition to the fastboot or adb command in order for OSX to execute the action. If following Heisenberg's guide for fastboot, the lone change you need to make for OSX is:
./fastboot devices
./fastboot flash
./fastboot reboot
./ADB devices
Try this out and post your results.
Sent from my Nexus 5X using Tapatalk

Just throwing this out there, it is possible to flash an OTA in TWRP. You still need a PC but its do-able.... I flashed Android N Final to my 6P yesterday by copying the OTA zip (uploaded thanks to another member) to SD, Wiped device as I normally would with any other ROM (left SD intact obviously), Flashed OTA ZIP, rebooted straight to bootloader after flash, fastboot erase boot, fastboot erase recovery, fastboot flashed DECRYPTED BOOT.img (which can be found easily), fastboot flashed TWRP 3.0.2-1 (version just released for N), fastboot format userdata, fastboot format cache, reboot from bootloader directly into TWRP, flashed superSU 2.74, reboot system..... Phone runs beautifully. Not a single issue. Entire process from start to finish was less than 10 minutes.
Its not the most practical route but it does indeed work. OTA just hes to contain the entire Image. I should also mention that this was a jump from a Marshmallow based rom (RR) so you don't have to be on an N preview in order to do this....

May Factory Image now available MXC89F

For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions

Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine

redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.

Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?

Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP

redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!

Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate

Change log ? Or its just a security update

Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.

After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...

rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk

houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?

rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck

m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!

rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!

hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.

"soft-brick" on Essential Phone PH-1

Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)

Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?

Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.

BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again

Azpre said:
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Click to expand...
Click to collapse
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

dirtyreturn said:
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
Click to expand...
Click to collapse
thanks for the thread man, helped alot
I managed to flash twrp by some miracle, I remember my device entering a bootloop once I tried to access the bootloader menu, but now its all good. I waited for the Essential run out of battery, then I plugged-in my pc the fastboot commands were working once again
going to try install a boot image now

dirtyreturn said:
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
oh my god Im such a dumbass, sorry

I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.