Develop Bugs

[Q] galaxy nexus stuck on boot loop screen animation.

I update, my ROM from cyanogenmod ROM 10.1 m1 to 10.1 m2 ROM and know my galaxy nexus is stuck on boot loop animation! I tried, tacking out the battery and then turning it back on no luck in also tried the ( volume button and power button method) and still no luck with that. Is,there a way I could fix it?

wipe data and reflash rom.

Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse

Never, mind i got it working know!

mrcoleminer said:
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse

Zepius said:
mrcoleminer said:
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse

Chamaeleon said:
Zepius said:
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse

Soulaysahmi said:
Chamaeleon said:
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
I was using the ClockworkMod (I don't remember exactly the version number but I updated recently and it was the touch screen one). I'll try to re-install also the recovery with the very last version (6.0.4.7). Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse

Chamaeleon said:
Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
have you tried adb sideload?

Soulaysahmi said:
have you tried adb sideload?
Click to expand...
Click to collapse
Just tried.
On the terminal after the command
adb sideload cm-11-20141115-SNAPSHOT-M12-maguro.zip
it tells me "error: closed"
I also tried to reinstall the Clockwork via bootloader but didn't change the situation (still not able to do a complete factory reset)

you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?

Soulaysahmi said:
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Click to expand...
Click to collapse
You are right, I didn't click "install zip from sideload" before. Now I tried in this way and, effectively, it worked: I managed to send and install the zip apparently without any problem but than after rebooting I'm still not able to turn on the phone completely. Again the same problem. I re-tried to do wipe data/factory reset both from the recovery and using adb but didn't managed to finish the process...
It seems I tried all the options since now.... but my nexus is still unusable...

did you try getting back to stock rom using any guide on this forum?

Soulaysahmi said:
did you try getting back to stock rom using any guide on this forum?
Click to expand...
Click to collapse
I tried but still with the same result. I'll try to follow the guide I found here

I mean through methods other than recovery, through fastboot mode or odin mode.

Soulaysahmi said:
I mean through methods other than recovery, through fastboot mode or odin mode.
Click to expand...
Click to collapse
I tried to Restore Galaxy Nexus to Stock (as described here) with the proper google image but in the last passage I get:
$ fastboot -w update image-takju-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMELC03
Baseband Version.....: xxx
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
FAILED
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'
I put all I need in one folder and I decided to update the bootloader at the PRIMEMD04 version but apparently I didn't managed because doing again the procedure I was getting the same error
ps: I'm using linux so I don't have odin

when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?

Soulaysahmi said:
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Click to expand...
Click to collapse
Yes I have BOOTLOADER VERSION - PRIMELC03
With fastboot I tried to install the PRIMELC04 bootloader
$ fastboot flash bootloader bootloader-maguro-primemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.969s]
finished. total time: 8.278s
$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
But than, after the reboot, on the screen it's still written BOOTLOADER VERSION - PRIMELC03
I think this is the main problem now... if it's not updated the bootloader I can not reinstall the rom probably...

you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img

Soulaysahmi said:
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Tried as you suggested to install the PRIMELC04 bootloader flashing each image.
Apparently is not possible also in this way. After rebooting on the screen is still written BOOTLOADER VERSION - PRIMELC03.
So I tried to install a stable cyanogenmod 10.2.1 (which should work with the bootloader 03).
I used adb sideload and after the "installing updates" message, everything stopped with the message "fixing fs_size in crypto footer". After more than 30 min I rebooted and the situation was the same as before.

[Q] Nexus 7 2013 Problems...

A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!

I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Any other suggestions..?

Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...

PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?

that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?

PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7

Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..

tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later

PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7

i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow

LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?

There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7

Updated to Android N preview - lost root

Hey guys,
I updated to the Android N Developer Preview, expecting to have to root my device again. I tried following the instructions here:
http://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
and my device already shows as unlocked. When I try and flash the custom recovery though, I get this message:
Code:
$ fastboot flash recovery twrp-3.0.0-0-dragon-ryu-02112016-1.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
Am I just out of luck with rooting the Android N version, and if so, is there an easy way to downgrade?

Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.

godzirra said:
Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.
Click to expand...
Click to collapse
Try this, post #4
http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243

Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.
Are you sure to have fastboot/adb tools update ?
Sent from my Pixel C using XDA-Developers mobile app

Read: http://forum.xda-developers.com/pix...al-twrp-2-8-7-0-pixel-c-dragon-t3288243/page4
TLTR, lock and unlock your bootloader to fix the mess.

I did that, and now it just shows the "Bootloader is unlocked" warning and then after 30 seconds, shows the google logo, then reboots into recovery.

ilpolpi65 said:
Even after downgrading, I get the same error, even when trying to follow the instructions on the developer.android.com/preview/download.html site. I get that error when I run the flash-all.sh script as well, when trying to flash the bootloader.
Are you sure to have fastboot/adb tools update ?
Sent from my Pixel C using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, I have the most recent fastboot and ADB.

At this point, I have (I think) Android N installed, and I can boot into TWRP or fastboot or the menu that lets me choose recovery/fastboot, but I can't boot the system itself.

Stuck after trying to upgrade to Pie.. worried I bricked it.

Having an issue with my XL. I've been on LOS 15.1 for a while and wanted to try out the new Pie image. I made a backup and fired up fastboot as usual. I left the -w tag on as I wanted a complete wipe. Fastboot failed while wiping userdata and now bootloops twice before dumping me in stock recovery. I am completely unable to format data while in stock recovery. Same when I boot TWRP through the PC. Stock recovery says it can't write a new EXT4 partition and TWRP says I have no internal storage, then throws a ton of errors. Flashing OEM images from Google (Oreo or Pie) results in the same thing.
Any ideas? For the first time in years I am stumped.

I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.

caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
Is your platform tools updated to the newest one?.
Edit I thought I was on the pixel 2 forum.

Could try to repartition the storage using a method similar to this one for the nexus 7? https://forum.xda-developers.com/nexus-7-2013/general/guide-repartition-nexus72013-to-t3599907
You would need to figure out the proper partition table for the Pixel though.

If you're 100% sure your platform-tools are fresh, you've got me stumped as well. I ran into tons of errors and such due to out of date tools when flashing Pie - obviously updating the tools fixed the issue.

Well I'd try external Type-C USB drive it enables external storage even if internal isn't working and fastboot flash your backup.

caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
i got the same problem, i just downloaded the Platform-Tools and opened it in PowerShell and executed flash-all script and it worked

Flash all script is good but I'd rather use external storage .. it's nice to know that there's more than one way to fix the problem outside of platform tools

I had issues with Pixel before and the multi partition thing screwed me up, but the Unified_Android_ToolKit was able to fix it for me. Worth a try for sure. Download Google Factory Image and use the tool.

Thanks for all the help everyone. Lots of good ideas here that I'll save for next time. Ten years tinkering with phones and I've never gotten this stuck.
In the end I flashed back to the factory Pixel XL image (October 2016). Like the previous attempts, it failed on accessing userdata. I used fastboot to flash a userdata.img file again, which similarly failed but somehow the phone still booted after about 20 minutes.
I found similar threads for other phones where people were in the same situation, but nothing they tried did the trick.
Back up and running now.
Sent from my Pixel XL using Tapatalk

Very odd. Based off your last post I'm going to assume you are not sure what triggered the issue?

Development [RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 6/6 Pro (Qualcomm ONLY)

Official TWRP is now available: https://twrp.me/asus/rogphone6.html
IMPORTANT NOTES:
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2201

It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.

I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed

minazukix said:
I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed
Click to expand...
Click to collapse
The message seems to indicate that your device bootloader isn't unlocked...

Captain_Throwback said:
The message seems to indicate that your device bootloader isn't unlocked...
Click to expand...
Click to collapse
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/

minazukix said:
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/
Click to expand...
Click to collapse
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.

Captain_Throwback said:
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.
Click to expand...
Click to collapse
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.

minazukix said:
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.
Click to expand...
Click to collapse
Then try just
Code:
fastboot flash recovery twrp.img
without the slot suffix and see if that works. That'll just flash TWRP to the active slot.

Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.

tuannghia1985 said:
Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.
Click to expand...
Click to collapse
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.

fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.

fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.

minazukix said:
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.
Click to expand...
Click to collapse
Thanks, that's the best option to push file directly via abd push.

tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
I just flashed the latest raw zip(WW-AI2201-32.2810.2210.220-REL-2210-M2.13.33.24-ASUS_1.1.1-Phone-user-20221109.raw), then everything is working well (e.g. /vendor/factory/COUNTRY is already WW).
I don't use voice typing, Android auto, google pay and fingerprint either, but I just tested the fingerprint features, there is no problems. I pass safetynet and hide root by this Method 2: https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/

tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
Everything is working fine, except these 2 features. Voice typing at first is working but after downloading my configuration (google backup) and my apps, it stops. I can live without it. I've tried several ways: no way of making it work. So I gave up..Maybe with Android 13... as everything was fine on Android 11 on my deceased Rog2. I have Magisk props (safetynet: passed, banking apps ok). But Android auto keeps crashing..Never mind. I have a spare phone to use when I'm driving.

So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?

Einheit-101 said:
So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?
Click to expand...
Click to collapse
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.

Hi guys, I want to flash this but I have 2 quick questions:
1. Can I FOTA after install TWRP ?
2. Do I need to reflash it every FOTA ?

fux1976 said:
It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.
Click to expand...
Click to collapse
hi how to reflash raw rom , i cant run flashh aft my phone stuck stock recovery help

Captain_Throwback said:
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.
Click to expand...
Click to collapse
how to flash raw ? my laptop cant run flash all AFT pls help