Database Users

Can't install CWM or TWRP

So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat

It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk

ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Flashify works pretty well, maybe give it a shot. Also, make sure you have the correct versions.

RikRong said:
It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am using the right files.

Works like a charm. Thanks!

i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.

deathwithafi said:
i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.
Click to expand...
Click to collapse
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.

chuck solid said:
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.
Click to expand...
Click to collapse
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you

deathwithafi said:
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you
Click to expand...
Click to collapse
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.

drenze said:
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.
Click to expand...
Click to collapse
Second link
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Thanks!

ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Link is dead... is there another? TIA!

ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Im having the same exact problem. I cannot get into recovery. I've tried mfastboot to load CWM (recovery-clockwork-6.0.4.4-xt907.IMG) and TWRP (XT901-XT907-TWRP-2.6.3.0-recovery.img) as well as TWRP Manager and Flashify on the phone. My bootloader is UNLOCKED and This is my config:
{
"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"
}
Does it have something to do with the version of KK? TIA

I believe the TWRP built for this phone is still unofficial, so you probably can't flash it with the app. When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery? If you don't do this, the stock recovery will over write.
Sent from my Nexus 5

When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery?
Click to expand...
Click to collapse
I did. I would get a (I dont know how to describe it) but a small "blip" at the bottom of the screen then it boot normal. I tried it several times and the same thing happened, like it was "trying" to get into recovery then just simply boots. I tried different IMG's thinking maybe they were corrupt. Also different USB ports and cables (motorola). NADA. Does it have something to do with the stock KK (I have a verizon phone) is there something in there that is keeping it from "sticking"?

UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~

Update on the update!
KarmaKid said:
UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~
Click to expand...
Click to collapse
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA

KarmaKid said:
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA
Click to expand...
Click to collapse
Though that version will flash to the 907, it's still designed for the 926's screen. You need to find the correct file.
Sent from my Nexus 5

I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/

beeewell said:
I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/
Click to expand...
Click to collapse
FIXED: THANKS! TWRP 2850...no issues!

[FIX] Android Lollipop OTA GPE stuck at bootlogo

For those who are stuck at bootlogo, the problem is the same as the one when we tried before downgrading from 4.4.4 to 4.4.2 it is with the partition table, the version in the ota is older that the one we have on our devices, I dunno how the hell is that but it is what happened to most of us, though the easy fix, flash the attached gpt through fastboot command:
fastboot flash partition gpt.bin
Hope this fixed everything ​

Thanks very much for the information!
I recently tried flashing the 4.4.4 GPE firmware onto my XT1032 and I got an error when trying to flash the GPT.bin partition using mfastboot. It said "failed". I got nervous and went back to the retail US firmware just in case. We need more people to confirm that this fix will work.
OP do you know if it's safe to flash your GPT partition before installing the OTA update on the 4.4.4 GPE ROM?

It works!
I cant flash any rom to my phone and everything failed on half proces and with this file i rescued my phone i flashed 4.4.4 gpe and than 5.0.1 ota (by sideload) !
My Moto Gpe was brick!! And now it works again!!!! Thanks!!!!

Yes I can confirm, I faced this issue myself and used this fix for it )​

Yeah!!! this work very well, you save my phone, thanks man

seriusly that was all? i had 2 moto g at home and when the first one got the ota it got hard bricked, but stupid me got back to 4.4.2 and at the 4.4.4 ota the phone hard bricked, i think that the bootloader is corrupted and now i have to wait for the full 5.0 rom to be aviabable. Thanks man i appreciate it (i had another moto g and just got the ota and booted because of this)

can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?

Bad news
ssalamon said:
can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?
Click to expand...
Click to collapse
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...

So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update

sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
The original GPE firmware has a bootloader version older than that of the 4.4.4 "again I don't know why" the only fix is by flashing the gpt file included, if you flashed the android lollipop and it didn't work, flash this and give it a shot .
"bear in mind also that this fix is for devices stuck at bootlogo not bootanimation, not a fix for bootloop"

ruphert said:
So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update
Click to expand...
Click to collapse
I faced exactly what you are facing now, flash this and everything will go smooth

Rostomania said:
I faced exactly what you are facing now, flash this and everything will go smooth
Click to expand...
Click to collapse
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
{
"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"
}
Phone is stucking after reboot.

ruphert said:
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
Phone is stucking after reboot.
Click to expand...
Click to collapse
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.

Rostomania said:
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.
Click to expand...
Click to collapse
Thanks a lot, you rocks!
Code:
sudo fastboot flash partition gpt.bin 12:02
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.320s]
finished. total time: 0.356s
sudo fastboot reboot
Phone is booting now

boot stuck
Hi, I've stucked on "android logo with unlocked lock icon".
Originally I had xt1033 asian, which was converted to 4.4 GPE one sim. Today I've tried to flash the 5.0.1 lollipop via adb, and as many of you guys, stucked on boot.
I've already tried your fix, and tried to downgrade following this thread http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
but still phone doesn't boot, just "Google" and lock icon...
can you help me, at least boot it, android version doesn't metter
** UPDATE **
So, I've managed to boot phone thatks to this thread http://forum.xda-developers.com/moto-g/general/guide-restore-softbricked-phone-t2965459
Gonna make a backup and try installing 5.0.1 again

sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
Not exactly, my XT1033 had 41.18 bootloader when i applied the 5.0.1 ota, it just worked with the following tutorial. I didn't even use the gpt file here.
http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472

awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?

ghost9685 said:
awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?
Click to expand...
Click to collapse
Look at this tread
http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
1st post
Step 5
Maybe it could work

My Own devices is a XT1032, and this fix has nothing to do with the XT1033 converted to GPE .​

I can also confirm that this works. But my phone was already converted to GPE and had 4.4.4 before I did the OTA update.
Giovani's guide works if you're stuck on the bootlogo after updating to 4.4.4 and then lollipop through OTA (on a gpe converted device of course). I used the second method in that thread.

Bricked 2012 Wifi Only Nexus 7, Please Help

Sorry if this has been addressed but I've been searching and reading and freaking out because I can't find out how to recover my Nexus 7.
I'm trying to manually update my 2012 Wifi Only Nexus 7 to Lollipop and my computer will not see the device any longer in ADB.
I downloaded the latest sdk and the latest image file (Nakasi 5.0.2 (LRX22G).
Ran through the steps found here: http://www.androidcentral.com/how-manually-upgrade-your-nexus
At this step fastboot flash bootloader [bootloader file].img it just sat there for about an hour and didn't do anything.
***Edit- I got it to work and then got the invalidstate error.
I then read that others have had success updating to Lollipop without updating there bootloader here: http://android.stackexchange.com/qu...t-flash-bootloader-failed-remote-invalidstate
***This is because my bootloader was already on 4.23.***
I then proceeded with fastboot -w update [image file].zip
The image failed after wiping everything with an error about too many links.
Now when I try I get "C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot -w upd
ate image-nakasi-lrx22g.ziparchive does not contain 'boot.sig'"
At this point, I can't get any adb commands to work as the device is not showing up as a connected device. I've rebooted my pc and the tablet multiple times. Fastboot keeps crashing as well.
Please help me get my Nexus back up and running. Thanks so much.

The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Alternatively, you could extract all the .img files in the zip file and flash them manually one at a time. This makes things really handy if you're using the factory image to act as an update rather than a complete return to stock. If trying to update using the factory image, extract the .img from the zip file into the same directory as your bootloader and radio img files and execute the following commands in order:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Click to expand...
Click to collapse
Quote taken from here

corkiejp said:
The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Quote taken from here
Click to expand...
Click to collapse
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>

touch_rules said:
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Are you in fastboot mode?
Step 4: Make sure the device is connected to the computer while in fastboot mode. Different devices may require different commands to get into fastboot mode. Make sure the device is powered off and then use the following button commands:
Nexus 7 - Vol Down + Power
Click to expand...
Click to collapse
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.

corkiejp said:
Are you in fastboot mode?
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Yes, I am. Please take a look at this picture. Thanks.
View attachment 3085046

Now I'm getting this At least it's different
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
erasing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 0.176s

corkiejp said:
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Noticed this part after I posted last, seems to be working....I'll let you know. Thanks so much. Wish I would have seen the toolkit earlier today when I started haha.

You rock corkiejp! Working like a champ now! Thanks so much.

I had exactly the same problem and ended up using Wug's toolkit and the individual images.
Sent from my Nexus 7 using XDA Free mobile app

I literally had it restore the factory image and it did it all. Made sure I had force flash checked.

Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device".
{
"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"
}
Any help would be highly appreciated!!!

Your bootloader is locked.
rayandreas said:
Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device". View attachment 3237509
Any help would be highly appreciated!!!
Click to expand...
Click to collapse
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.

GedBlake said:
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.

rayandreas said:
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.
Click to expand...
Click to collapse
Hi again, rayandreas...
If it where my tablet, I'd just fastboot flash the Google factory stock image for your device.
The Google factory stock image for your device can be found here...
https://developers.google.com/android/nexus/images#nakasi
There's little point in my re-inventing the wheel by writing yet another tutorial... full details and instructions can be found here...
[GUIDE] Flashing a Factory Image with fastboot / return to stock
----
But all of this is contingent upon successfully UNLOCKING THE BOOTLOADER.
The bootloader needs to be unlocked, before anything can be fastboot flashed.
Whilst this can be done with toolkits (such as Wugs), I personally prefer to deal with fastboot directly (instead of through a layer of GUI polished menus and dialogue boxes).
----
From power-down state, or to force boot the device into its bootloader...
** Press and hold VOL-DOWN.
** Whilst holding VOL-DOWN, press POWER ON.
** Keep BOTH buttons pressed for a good 30 seconds.
If successful, you should see a GREEN ANDROID lying on its back...
----
USB connect it to your laptop/PC. Ensure you have the correct drivers installed on your laptop/PC as per the instructions detailed in the above link.
The command is as follows...
Code:
fastboot oem unlock
Due to security considerations, this command will wipe the Nexus 7, and you will be advised of this by the Nexus 7 itself, and you'll also need to confirm the bootloader unlock request at the Nexus 7 end via a confirmation dialogue box.
(See the attached screenshot for the sort of thing you should expect to see).
If successful, you should see an unlocked padlock symbol at the bottom of the screen, underneath the Google logo, whenever the device boots.
----
Unlocking the bootloader is critical if you wish to fastboot flash anything. Even official Google factory stock images require an unlocked bootloader to be fastboot flashed. And with the Google recommendation that the bootloader is re-locked afterwards with...
Code:
fastboot oem lock
This is optional of course, and I would generally recommend against it, because if you wish to unlock the bootloader again at some future date, it will wipe/factory reset the device...
General point of advice: Once Unlocked - Leave it Unlocked.
---
Hope this helps... and good luck.
Rgrds,
Ged.

View attachment 3240619
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...

rayandreas said:
View attachment 3240618
View attachment 3240619
View attachment 3240620
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...
Click to expand...
Click to collapse
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)

Fobos531 said:
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)
Click to expand...
Click to collapse
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...

rayandreas said:
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...
Click to expand...
Click to collapse
According to this article, some of bootloaders were corrupted or what. Update NRT masterlists in the toolkit and try flashing the latest bootloader if that is possible through the toolkit. Maybe it will let you to unlock the bootloader afterwards. If the toolkit can't do that for you, download latest factory image(4.4.4 or 5.1, what you desire) and extract the bootloader from the image. It will probably be named "bootloader-nakasi....." Try manually flashing it through CMD/ADB using "fastboot flash bootloader "name of bootloader file". I repeat, I don't have much experience with this tablet, but I'm doing what I can. Try doing what I suggested, maybe it'll work. You can't make it worse after all Good luck!
EDIT: In the link I posted, there are some neat instructions and a link to the new bootloader down the page. Make sure to check that out too.

I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!

rayandreas said:
I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!
View attachment 3242733
Click to expand...
Click to collapse
You actually have a recovery, a stock one. While at that screen, press Volume Up + Power for 1 sec( or only Volume Up, not sure) to access it. You can try doing a factory reset there if that helps anyhow.

Findings after unlocking bootloader

So as far as I know, I am one of the first people to have the bootloader unlocked on the Chinese Mate 9.
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
We can flash small files, can flash recovery, etc. So we need someone to make TWRP in order to do anything with the unlocked BL. Since there's no source out for the Mate 9, I'm worried about that, but hopefully @raimondomartire can get it done!

Update: I've built a preliminary TWRP, but I don't understand TWRP well, and the mount points are incorrect. However, I believe we will have a working TWRP very soon.

Solid info. Thanks. Once more developers start hopping on, I'm sure we'll get to this faster especially after the fact that you managed to already get the bootloader unlock.

Ahh, progress. Almost there.
{
"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"
}

Good job !!!!

Congrats
أرسلت من HUAWEI NXT-L29 بإستخدام تاباتلك

duraaraa said:
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
Click to expand...
Click to collapse
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797

Job well done!

5[Strogino] said:
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
Thank you for the idea. Unfortunately, when I tried this tool, it required that the image size is a multiple of 4096 bytes. So I appended null bytes to the end until it was a multiple, split, and flashed all the files, but it doesn't boot.

An update. I hate TWRP mounting /system, /data, /cache, and so on. The only one that doesn't mount is 3rdmodem (I can't even find it in the filesystem.) The data partition and /sdcard partition seem to be encrypted. USB doesn't work (yet)
When I try to flash supersu, the phone crashes and reboots just after the message that it's trying to do a systemless install and creating space...
I tried flashing the zip from Huawei's google services download. That flash worked.
I can't flash any regular huawei updates without a lot of work, so I haven't made an honest effort at unpacking the update.app's partitions and making them into flashable zip files.
So we're kind of stuck unfortunately, with not very much we can do, despite the bootloader being unlocked.
That's all I've got for you all for now.

How do you do to unlock the bootloader once you got the code

playa77176 said:
How do you do to unlock the bootloader once you got the code
Click to expand...
Click to collapse
If you don't know how to do it you might be better off not doing it because there is some risk involved with it at this point.
If you want to try anyway turn off the phone and plug in a USB cable while holding volume down key.
Then run the command on your computer
fastboot oem unlock CODE
Replace code with your code.

Update. I just figured out how to flash a rom via fastboot. Going to try flashing European newest rom on Chinese mate momentarily.

Update: The error I mentioned in my previous post (sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
)
This error doesn't occur if I'm flashing the Chinese firmware. Only if I flash the European firmware.
Something is not quite right. I'm download other version of Euro firmware to check.

Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.

duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
Maybe you need an updated fastboot files?

It's possible to unlock With srktool ?

playa77176 said:
It's possible to unlock With srktool ?
Click to expand...
Click to collapse
I think it's best you stick to the regular fastboot commands. SRKTool is for the older Mate, so it might want to flash an incompatible TWRP or something like that.

gm007 said:
Maybe you need an updated fastboot files?
Click to expand...
Click to collapse
I've tried every version of fastboot I can find, on every platform. That's not the issue. I'm going to try and find a way though!

duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
The problem is that fastboot does not allow flash very big files.
Solution is to divide file on chunks.
Unfortunately, i don'y have Mate 9.
Try this:
Code:
fastboot -S 256M system path_to_system.img
p.s. You should use actual fastboot version (SDK version)

having some trouble flashing the magisk patched image

(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.