Related
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Unlock your bootloader and retry.
Already retried to unlock the bootloader.. But no luck.. Thanks for the tips btw
I have found the solution.. I will post it in the weekend
luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
when u post please tell my in the praivte
[email protected]
Kingroot worked for me bit only after the second try
Tengo10 said:
Kingroot worked for me bit only after the second try
Click to expand...
Click to collapse
can u explain me please how u do it with king root??
eyalyagel said:
can u explain me please how u do it with king root??
Click to expand...
Click to collapse
I coud've offered more direct support if you messaged me or replied to my thread.
Have you found any solution?
Breadcrust said:
I coud've offered more direct support if you messaged me or replied to my thread.
Click to expand...
Click to collapse
can u give me please the link or explain may the way????
thank u very much
eyalyagel said:
can u give me please the link or explain may the way????
thank u very much
Click to expand...
Click to collapse
Did you do fastboot -i ox2b4c oem unlock?
Breadcrust said:
Did you do fastboot -i ox2b4c oem unlock?
Click to expand...
Click to collapse
yes,
FAILED (remote: Oem unlock is not support)
finished. total time: 0.008s
and i allow the oem in the developer option....
also i have the same phone in my home but the difrrent bitween them:
1. have only home press in the bottom
the ather phone have home, back,manu, bottom this phone can be unlocked and i sucsses to instal twrp
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
xnoobx said:
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
Click to expand...
Click to collapse
I'm also facing the same problem with my ZUK Z1
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
Dear
I was using CM12 new version till last week and i have lots of problems, specially with mobile signal during the calls voice is dropping signal is too week as well. So i have decided to move to ZUI version and it's perfect so far i'm not facing any problem. Only the vulnerable is there some kind of malware and GPS having some bugs i have checked with bbs.zuk forms and they are suppose to fix it with next update. so i was trying to install the stagefright fix via recovery.remaining everything is smooth and faster than CM12.
hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
I also tried to boot. But it also denies this action :/.
So with the latest version my boot loader is locked. Sounds wonderful.
luqmanhans said:
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Click to expand...
Click to collapse
In this case, you need flash fw Z1_CN_OPEN_USER_Q4275715.1_L_ZUI_1.0.050_ST_150910 via sd card ( root internal memory/creat sdfuse folder), after turn off fone and boot phone via factory mode recovery ( voulme down + power ). If phone flash ok, version is 1.0.050. So, phone can flash twrp recovery and rom CyanogenMod 12.1 .
Goodluck
{
"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"
}
luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
hristos13gr said:
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
Click to expand...
Click to collapse
First you must downgrade the ZUI from 1.2.040, just search this topic in this forum: how-to-flash-zuk-z1-zui-version-t3265741
After that you can boot with TWRP recovery. But if you failed to flash Cyanogen, use Modaco steps: 375804-convert-z1-from-zukui-to-cyanogen-os/
When your ZUK Z1 already use Cyanogen, you can flash to other recovery or ROMs easier .
First, Unlock Bootloader
Install TWRP for Le X626
Download Magisk or SuperSU
Put Magisk or SuperSU in internal storage
Reboot to TWRP
Install from zip
Choose Magisk (Recommended) or SuperSU
Reboot
source : tickernel.tk
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
How to install TWRP for x626 according to the site the OP recommends.
From the same website, only without the adlinks. No guarantees from me, if you go through the instructions from the OP you will end up getting the same information.
– Make sure your Bootloader is Unlocked, if you don’t know how to Unlock the Bootloader then please go to here and Unlock the Bootloader of your Device.
– Download the Latest TWRP Recovery Image from https://dbr.ee/TKKC
– Reboot into Fastboot/Bootloader Mode.
– Run The Following Command from a Command Prompt in the Same Folder in which you downloaded the TWRP Recovery Image (Change twrp le x626.img to recovery.img):
fastboot flash recovery recovery.img
fastboot boot recovery.img
Click to expand...
Click to collapse
onlytanmoy said:
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
Click to expand...
Click to collapse
I can't, because it's have different chipset
okay, thanks for your response and clarification...cheers to that.
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
tomfoley said:
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
Click to expand...
Click to collapse
Unlock bootloader first
What rom do u use?
Hi Tickernel, and thank you for replying
I unlocked the bootloader as per Step 1 above and that completed successfully.
Moving on to Step 2 I got the recovery image following your links which led me to 'twrp le x626.img' (20MB), which I renamed to recovery.img.
There are two commands to execute in step 2, the first went ok, the second did not succeed
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse
Please see screenshot...
{
"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"
}
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse
tomfoley said:
Please see screenshot...
Click to expand...
Click to collapse
Have u tried boot to recovery?
Press vol up + power
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
tomfoley said:
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
Click to expand...
Click to collapse
After you flash the twrp, then boot into recovery by pressing vol up + power
You don't need update.zip
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
tomfoley said:
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
Click to expand...
Click to collapse
I'm not suggesting to erase all your data, i'm just suggesting after you flash the twrp but don't straight go to recovery then press vol up + power. That's it
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
tomfoley said:
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Command 'fastboot boot recovery.img' is going boot to twrp. If you fail to do that, then just press vol up + power
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
tomfoley said:
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
Click to expand...
Click to collapse
Yeah, you're welcome
Don't suppose kingroot or similar works? I'm very lazy lol
I also have this problem were it fails in "fastboot boot recovery.img" but not in commanding "fastboot flash recovery recovery.img"
what to do?? :crying:
thanks for the help
Hi, yesterday i have unlock bootloader of my moto g4, xt 1622 , i have flashed twrp and this is perfect, but after i have flashed zip of magisk.zip for root permission, when i reboot i obtain only black screen and led white ( intermittence led) .
The device is recognize by windows 10 (in test mode and no signature driver verify ) but not in tray bar..
Mode recognized by pc are:
in fast boot like " fastboot athene_13mp S " in "other device"
In adb mode " sideload" ( from stock recovery) like "Moto g4 plus " in device manager/usb devices"
I have stock recovery and can't start blank flash because the device isn t recognized by pc like qualcomm device..
What can i do??? Thanks a lot my friends!!
The problem is that magisk is not compatible with the Stock kernel, so if you want magisk you need to flash a custom kernel, i recomend this: https://elementalx.org/devices/moto-g4/ you need to flash the kernel and after this flash magisk.
Regards
Wow! So the phone is save? ?
And what can i flash pther kernel, can i have a guide plz? Can i flash with sideload? Thanks!
Yes, you need to enter un recovery, conect your phone to pc and with adb put in the cmd adb sideload nameofyourzip.zip and then flash magisk with sideload if hoy wanr
Unfortunately i recive this error.. what can i do? Thanks!!
{
"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"
}
Ok, first you need to install twrp: https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Then you need to go in twrp to avanced and adb sideload and flash it.
Hmm, can you confirm if you have stock Marshmallow (6.0.1) or Nougat (7.0) on your device? I see from the stock recovery version that it's 6.0.1/MPJ24.139-23-4 (a really old build of Marshmallow).
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
scossa1994 said:
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
Click to expand...
Click to collapse
Thanks, as Ismael034202 pointed out above, if you were on stock Nougat, then you will need to flash a custom kernel, as rooting on the stock Motorola Nougat kernel will cause a boot failure. If you were still on Nougat, then you could have followed this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 with flashing magisk instead of SuperSU.
As you've re-flashed the old Marshmallow stock ROM, then you do not need a custom kernel (Marshmallow stock ROM kernels are less strict about rooting), flashing TWRP and then flashing magisk should work on Marshmallow.
However, you need to be very careful if you revert back to full stock - as you've appeared to have downgraded from Nougat, taking OTA updates may hard brick your device. If you can remember what Nougat stock ROM you had before unlocking your device, I would recommend downloading a copy of that stock ROM and using the stock ROM to update. Try not to use stock OTA updates.
Very well explained echo92. +1 ?
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
scossa1994 said:
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
Click to expand...
Click to collapse
Hmm, in that case, the easiest way may be to flash the latest stock ROM to your device and start over again. As an alternative, do you have a TWRP backup of your device?
For XT1622, you'll likely want NPJS25.93-14-13 (Nougat, 7.0 stock, December 2017 security patch) firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Download and extract as directed in the post, and to flash to repair your device, use the following flashing commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
This should not re-lock your bootloader. Next, download TWRP, ElementalX and magisk and flash as I suggested in the guide above. The basic guide for rooting on Nougat is:
a)Flash/boot TWRP. Backup your device.
b)Flash ElementalX.
c)Flash magisk or SuperSU.
d)Wipe cache/Dalvik in TWRP.
e)Reboot and wait for boot.
f)Any issues, revert to your backup made in a)
Can i use fastboot within debug usb off? Because i recive an error, i m tryng and post a pic.
Thanks
This is my situation after try to use fastboot
Hace you installed Motorola drivers for pc, you can use fastboot without USB debugging
https://mobilesupport.lenovo.com/rola/es/solution/MS89882 This os the link for the fastboot drivers
Thanks guys!! I had write the stock 7.0!! Now the phone is perfect!! Thanks!!
I had wrong driver and pc not recognized the phone!! Now yes ??
Now install twrp, elementalX Kernel, magisk and enjoy
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Moto Singh said:
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Click to expand...
Click to collapse
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
scossa1994 said:
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
Click to expand...
Click to collapse
No nothing is working.
Moto Singh said:
No nothing is working.
Click to expand...
Click to collapse
I don t know.. the problem is the corrupted bootloader ( i think..)
I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311
Hi, it feels so good to see that I'm not the only one suffering (suffered in your case) with this problem. I just have a doubt.
We are erasing bootloader in your steps but while again installing all these files we are neither installing any bootloader img nor it is there in the rom package. Now I that that if your bootloader is gone, your device is as good as a brick, for real. Could you shed some light on this?
Awaiting your reply.
Thanks and regards.
EDIT:
I think my tab just died, while flashing tos from minimal adb and fastboot, I noticed the screen was pulsing, fastboot logo was still there but like flickering and fastboot message came back that it failed to write. I disconnected usbcable and reconnected and tab isnt detected, fastboot says target didnt report max download size and windows doesnt see the tab.
I switched off and tried to reboot to fastboot but the tab wont respond anymore. Screen doesnt come on.
What to do?
It is working
The guide was working, although flashing the dtb file wasn't succesfull its working. Later I will update to Custom ROM.
Thanks a lot, got my Pado back to life. As Guy.brush said dtb fails but it still works.
Failed Flashing DTB
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
---------- Post added at 03:31 PM ---------- Previous post was at 03:01 PM ----------
C4DXYZ-XDA said:
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
Click to expand...
Click to collapse
but it still work.. my mipad is back to life..
adi4u4882 said:
I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311
Click to expand...
Click to collapse
Thanks, where could I find rom to get dtb file? Thanks
Wow it is working
Even i got the same error
"sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))"
then I did flash ,using Mi flash tool..
Now it is working fine..
after (2015-2019)so many years.. Today 31st May 2020 device came back to normal..
I tried many methods.. Nothing works..
Thank you so much for this post..
I went to three different MI service center..and many other mobile repair shop..no one did..
You did big help..
Thank you so much..
I followed all the instructions one by one. The process was completed successfully too, except dtb (which error many others have faced). Rebooted. Then flashed the same ROM using MiFlash tool. BUT still my tab is stuck in mi logo. I don't know what to do. Is there anything I am missing during following the instructions? I can still enter into fastboot mode and also recovery; so the tab isn't completely hardbricked though. Please help. I am just stuck in the mi logo.
In my case even it doesn't go to fastboot mode neither recovery. Stuck in mi logo. Please someone help me
While flashing I found that recovery.img and tos.img exists in both the fastboot file and the blobs file. Which one should I use? I tried using the fastboot files but it didn't work out and i'm stuck on the mi logo.
Also while flashing via miflash, got an error :
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done.
which I found out is to be ignored and the flash will still work. It is just a checkpoint fail because the device wasn't locked during the flashing process. Could it be the issue ?
My Mipad is bricked now,,so I'm working on short mydevice using the memory card slot,.. its kind of tricky to get it back to life again,,hihihihhi,,
Just registered an account to say thank you. I tried flashing original fastboot rom thousands times but no luck. Your guide helped.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm trying like this,, and it worked..
It worked for me.
The "tegra124-mocha.dtb" file can be found within the fastboot rom package that I downloaded named "Xiaomi_Mi_Pad_V8.1.2.0.KXFCNDI_20161128_China_4.4_XFT"
via:
Xiaomi Mi Pad Stock ROM Firmware (Fastboot Flash File)
Download the official Xiaomi Mi Pad Stock ROM Firmware (Flash File) for your Xiaomi Smartphone. We also provide Stock ROM for other Xiaomi devices.
xiaomistockrom.com
Intend to move onto custom rom LOS15 or later...
Wish me luck, read that camera is broken in LOS15-16 for mocha
Now to reinstall TWRP
via:
Download twrp-3.4.0-0-mocha.img
Download page for twrp-3.4.0-0-mocha.img
dl.twrp.me
Then re-merge the partitions.
"Repartition_MI_Pad_1_2GB_zardMi3.zip"
via:
Repartition_MI_Pad_1_2GB_zardMi3.zip | by ANHTUAN9791 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Miui 8 : How To?
Hi, On the recent post, miui 8 is available for the mipad. But before update we need to merge the both partitions. "For Xiaomi MiPAD 1 is required to merge both system partitions" We are invite to follow à link : http://en.miui.com/thread-118294-1-1.html Ok.....but I just understand...
xiaomi.eu
[GUIDE][HOW TO]Flash TWRP And Merge Partitions on Mi Pad 1 (Mocha)
Screenshots will be added later on /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have...
forum.xda-developers.com
LineageOS 16.0 | 19.04.2020 | Shield blobs
LineageOS 16.0 Requirements: 1) active system1 2) merged system partition 3) BRAIN, READING SKILL and presence of basic knowledge about firmware (in the absence need learn to independently) Instruction 1) download TosForPSCI-0.1.zip...
forum.xda-developers.com
This thread & the blob saved my device. Thanks a lot.
Thank you sooo much! It helped to revive my Mi Pad!
(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.