Develop Bugs

Stock unrooted and bricked? Help

So today I had a problem with an app not opening correctly so I rebooted the device. The device was stuck in the kit kat boot sequence. I turned it off and charged it. Tried booting to no avail. So I go into stock recovery mode and wiped cache and then proceeded to wipe/factory reset. It then got stuck on factory reset. I let it sit there on the charger for awhile and it was still stuck on factory reset. So i rebooted to attempt again. Now it won't even go into recovery mode. It'll boot to the fastboot screen but when trying to go into recovery it gets stuck on the white Google logo. Is there anything I can do or do I need to send it back? I bought it in July-ish so it should still be on warranty.

It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor

Pandae said:
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
when trying any commands in adb it says waiting for device and hangs on that.

Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.

Pandae said:
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Click to expand...
Click to collapse
fastboot devices does nothing. I am in the fastboot directory. I thought I had the drivers installed, but in device manager it shows up as Android with an exclamation mark

OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.

Pandae said:
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Click to expand...
Click to collapse
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command

wildside84 said:
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
Click to expand...
Click to collapse
Couldn't you just try to boot a recovery IMG?
fastboot boot recovery path/to/recovery.img
That will let you run recovery without flashing it
Sent from my Nexus 7 using Tapatalk 4 Pro
{
"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"
}

Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.

Pandae said:
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Click to expand...
Click to collapse
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely

I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock

Pandae said:
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
no and whats funny is I just got done trying that before i read your message. i restarted the device and my computer and just decided to see if it would dirty flash the flash-all.bat and it was actually going through not giving the write errors but did say bootloader is locked. so i typed fastboot oem unlock and the screen popped up on the device to say yes or no. i selected yes and it, again, got stuck for 10-15 minutes on erasing data...rebooted the device, unlock appears to have failed. argh

If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?

Pandae said:
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Click to expand...
Click to collapse
it says the bootloader is locked. i am trying again right now. i get to the yes no screen, select yes and on the command prompt it is stuck on erasing userdata

I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?

Pandae said:
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Click to expand...
Click to collapse
ill let it sit, but i think there is something wrong with the device. i had a similar prob with a gs2 and it wouldnt erase or write anything to partition. would usb debugging have to have already been enabled? i cant remember if that was checked or not. or does that matter?

USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.

Pandae said:
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Click to expand...
Click to collapse
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.

wildside84 said:
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
Click to expand...
Click to collapse
use usb jig and flash via odin nice work :good:

wildside84 said:
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
Click to expand...
Click to collapse
Is Google writing the book "How Not to Stand Behind Your Product"? Sheesh!
Sorry I couldn't be of more help. Good luck and speedy repairs to you. I must admit that with the touchscreen problems, and that it took someone who isn't a Google employee to fix it for a lot of people, all while Google is still silent, I myself don't care to buy another product by Google and/or Asus.
---------- Post added at 12:24 AM ---------- Previous post was at 12:18 AM ----------
VerlyAnanda said:
use usb jig and flash via odin nice work :good:
Click to expand...
Click to collapse
Odin is for Samsung devices, unless something's happened I didn't hear about.

ASUS ZE551ML bought abroad and can't update

Good day,
sorry for going direct to the point but, i'm having trouble with my ze551ml, as it was not yet available in my country a few months back, i bought it online, and it seems the original firmware was CN, and it was just converted to WW before it was shipped to me, as i bought it via CC, i didn't return it to the online store. now the problem is that, i want to update the software but it always fails, even if i did manual update.
Device info:
-device is rooted(it was rooted already when i got it
Build number:
LRX21V.WW-ASUS_Z00A-2.13.40.13_20150401_8390_user
044030427_201501060109
0010000500001
Kernel Version:
[email protected] #1
Wed Apr 1 00:31:25 CST 2015
Baseband Version
1509_5.0.18.00_0320,1509_7.0.10.0_0320
CPU-Z
also wondering, this was supposed to be a 64 bit phone right? but in the cpu-z it says
Processor: Intel(R) Atom(TM) CPU Z3560 1.83GHz
Cores: 4
Architecture: x86
CPUID: 6.5a.0
Codename: Moorfield
Process: 22 nm
P.S: is it possible to update if i flash the latest firmware?
BTW: Are these info safe to share?? Thanks

Yeah it's OK to share, you fail to update in recovery right? but you get the ota notification right? To me it looks like your build version is too old and it fails to update since newer updates require newer recoveries. Does ADB sideload fails too?

sorry can't understand much
ota doesn't see new updates, haven't tried adb, current computer has no android sdk installed, hopefully answered everything? but will install it now, also will finish latest stock rom in a minute
BTW: i'm willing to lose all data just to fix this problem

dwynez03 said:
ota doesn't see new updates, haven't tried adb, current computer has no android sdk installed, hopefully answered everything? but will install it now, also will finish latest stock rom in a minute
BTW: i'm willing to lose all data just to fix this problem
Click to expand...
Click to collapse
You have to try with adb, go in the recovery and you should see the adb sideload option, press it and connect to the PC, now download this http://forum.xda-developers.com/zen...l-windroid-universal-android-toolkit-t3206907 and go to command section and the sideload file. Now choose the lastest update available on asus site http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.168-user.zip (here is a direct link), now your update should start it will take a long time so don't unplug the usb!!

ElmirBuljubasic said:
You have to try with adb, go in the recovery and you should see the adb sideload option, press it and connect to the PC, now download this http://forum.xda-developers.com/zen...l-windroid-universal-android-toolkit-t3206907 and go to command section and the sideload file. Now choose the lastest update available on asus site http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.168-user.zip (here is a direct link), now your update should start it will take a long time so don't unplug the usb!!
Click to expand...
Click to collapse
ok, will try this, i'll get back to you, thanks

dwynez03 said:
ok, will try this, i'll get back to you, thanks
Click to expand...
Click to collapse
help, always rebooting into fastboot mode, how do i disable this? it won't enter twrp/recovery...

dwynez03 said:
help, always rebooting into fastboot mode, how do i disable this? it won't enter twrp/recovery...
Click to expand...
Click to collapse
You can't boot the system? Or the phone reboots in fastboot and you cant enter in recovery?

ElmirBuljubasic said:
You can't boot the system? Or the phone reboots in fastboot and you cant enter in recovery?
Click to expand...
Click to collapse
the phone reboots into fastboot and can't enter recovery, i tried reboot to recovery option in fastboot but it just boots again to fastboot..

dwynez03 said:
the phone reboots into fastboot and can't enter recovery, i tried reboot to recovery option in fastboot but it just boots again to fastboot..
Click to expand...
Click to collapse
You softbricked it, but that's OK, can you follow this guide please http://www.asus-zenfone.com/2015/12/how-to-re-lock-bootloader-asus-zenfone-2.html and after point 18 use the file you downloaded from asus site

ElmirBuljubasic said:
You softbricked it, but that's OK, can you follow this guide please http://www.asus-zenfone.com/2015/12/how-to-re-lock-bootloader-asus-zenfone-2.html and after point 18 use the file you downloaded from asus site
Click to expand...
Click to collapse
btw, when i try normal boot it boots properly into the system, i can use it normally, is that still softbricked? thanks

when i try to reboot to recovery it always returns to this
{
"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"
}
when i select recovery mode it reboots the the same fastboot mode image,
this doesn't show up

dwynez03 said:
btw, when i try normal boot it boots properly into the system, i can use it normally, is that still softbricked? thanks
Click to expand...
Click to collapse
Ahh then it's not, some people can't boot in the system and only in the fastboot, i want you to flash a recovery and let's see if works, http://www.mediafire.com/folder/setyy42t2cymy#3puweqngpjspc download all this files and put them in your adb folder(if you have any if not download this folder(https://drive.google.com/file/d/0B8Zi6Xs3FmZlSkl5NUFFNmZxOE0/view?usp=sharing i know it's for root but it will do just fine)) and after you have booted in bootloader type this commands
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
1 at time and then try to go into recovery

ElmirBuljubasic said:
Ahh then it's not, some people can't boot in the system and only in the fastboot, i want you to flash a recovery and let's see if works, http://www.mediafire.com/folder/setyy42t2cymy#3puweqngpjspc download all this files and put them in your adb folder(if you have any if not download this folder(https://drive.google.com/file/d/0B8Zi6Xs3FmZlSkl5NUFFNmZxOE0/view?usp=sharing i know it's for root but it will do just fine)) and after you have booted in bootloader type this commands
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
1 at time and then try to go into recovery
Click to expand...
Click to collapse
i think it got bricked, now all it shows up is usb symbol....

dwynez03 said:
i think it got bricked, now all it shows up is usb symbol....
Click to expand...
Click to collapse
That error is a bi***, follow this to fix all your problems http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256

haha, ok, it's not bricked, just jumped to conclusion., here's what happened, i can boot normally, but when i try to boot into fasboot or recovery it shows up the usb symbol....

dwynez03 said:
haha, ok, it's not bricked, just jumped to conclusion., here's what happened, i can boot normally, but when i try to boot into fasboot or recovery it shows up the usb symbol....
Click to expand...
Click to collapse
Here is what i think, the guy who sold your phone have put the wrong recovery in your phone, by flashing the files i give you(in my good will i thought the recovery was the same as firmware version) you bricked the bootloader, to fix this you must perform the guide i give you (http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256), so i suggest you to do is backup all your internal storage to PC, backup everything you might need and do that operation when you have time, then you can update OTA

ElmirBuljubasic said:
Ahh then it's not, some people can't boot in the system and only in the fastboot, i want you to flash a recovery and let's see if works, http://www.mediafire.com/folder/setyy42t2cymy#3puweqngpjspc download all this files and put them in your adb folder(if you have any if not download this folder(https://drive.google.com/file/d/0B8Zi6Xs3FmZlSkl5NUFFNmZxOE0/view?usp=sharing i know it's for root but it will do just fine)) and after you have booted in bootloader type this commands
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
1 at time and then try to go into recovery
Click to expand...
Click to collapse
hmmm, i think i made a mistake here, i entered this commands in fastboot mode...

ElmirBuljubasic said:
Here is what i think, the guy who sold your phone have put the wrong recovery in your phone, by flashing the files i give you(in my good will i thought the recovery was the same as firmware version) you bricked the bootloader, to fix this you must perform the guide i give you (http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256), so i suggest you to do is backup all your internal storage to PC, backup everything you might need and do that operation when you have time, then you can update OTA
Click to expand...
Click to collapse
thanks, will try again tomorrow, i'm ready if it means losing all data... thanks again,, i'll update you tomorrow or later, when i get back online.

dwynez03 said:
thanks, will try again tomorrow, i'm ready if it means losing all data... thanks again,, i'll update you tomorrow or later, when i get back online.
Click to expand...
Click to collapse
Sure! This is part of everyone experience when modding the phone

dwynez03 said:
thanks, will try again tomorrow, i'm ready if it means losing all data... thanks again,, i'll update you tomorrow or later, when i get back online.
Click to expand...
Click to collapse
hi, followed this one, and now, i can't seem to boot normally now, haha, i think it is softbricked now, but everytimer i try to flash any image, it's alwast flash failed..

Error while flashing twrp from PC

I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )

vib$$$ said:
I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )
Click to expand...
Click to collapse
Try official recovery it worked

kash2freedom said:
Try official recovery it worked
Click to expand...
Click to collapse
it is the official one

vib$$$ said:
it is the official one
Click to expand...
Click to collapse
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this
{
"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"
}
​2. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second picture​

Shahitto said:
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this View attachment 4494056​2. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second pictureView attachment 4494060​
Click to expand...
Click to collapse
Yes. My bootloader is unlocked. So oem is also ticked. I'll try using this software. Do you have the proper steps for it?

type fastboot devices and see if it shows a device
maybe try using anothar usb port on laptop
if fastboot devices is not showing anything, its coz adb and fastboot drivers are not installed properly, are u using a windows 10 laptop??? they tend to give some problems while installing drivers.. google up and u will find ways

I had the same issue. Its coz windows 10 driver issues. I tried the same method in a windows 7 pc and it worked.

Shahitto said:
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this View attachment 4494056​2. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second pictureView attachment 4494060​
Click to expand...
Click to collapse
is it for redmi note 5 pro

vib$$$ said:
is it for redmi note 5 pro
Click to expand...
Click to collapse
i used this toolkit and it does not recognise my device in fastboot mode. it recognises that the device is in fastboot. but shows no device found. When i tried installing the adb files. it showed 0 files copied. maybe thats why it is. any solution to the 0 files copied thing

vib$$$ said:
i used this toolkit and it does not recognise my device in fastboot mode. it recognises that the device is in fastboot. but shows no device found. When i tried installing the adb files. it showed 0 files copied. maybe thats why it is. any solution to the 0 files copied thing
Click to expand...
Click to collapse
It's OK not to show device name in the toolkit if the toolkit only shows fastboot as green color that means you device has been recognized and you don't have to install adb driver again so now you just need to click on the button Recovery Flash and a new box will appear and then check my second Pic file and find the twrp file and flash it, it's very simple
And I have done this method for my Redmi Note 5 AI(China)

Same thing happened with me. I can't even flash anything via fastboot. I updated from 8.4.25 to 8.5.2 global beta on my Redmi Note 5 Pro and this happened.
Also, I noticed that if I try to flash anything from MiFlash, the phone would disconnect itself even if I would flash from CMD.
After disconnecting from itself, the screen stays on fastboot and immediately a text appears "Press any key to shut down" on the top left corner.
Now I'm on Miui 9.2.4.0 Global Stable flashed through EDL mode still the fastboot is broken
confused what the heck happened! Tried reinstalling all drivers but no luck.
p.s In the image I was just testing the flashing state using userdata.img and twrp files

vib$$$ said:
I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )
Click to expand...
Click to collapse
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%

Easiest solution is to go with linux!
You can make this even form freshly created ubuntu live USB drive. Just go in terminal, install adb and fastboot and voila, no need for "drivers", here You work in "native" environment!
Then, agin in terminal go with:
sudo fastboot flash recovery recovery.img
or for ROM flashing, when You are in recovery, activate sideload option an again in terminal go with:
sudo adb sideload rom.zip
That's it!
Works every time!

nikhil jain984 said:
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%
Click to expand...
Click to collapse
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT

nikhil jain984 said:
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%
Click to expand...
Click to collapse
That's what I've been doing bud... :/ No luck.
---------- Post added at 03:19 AM ---------- Previous post was at 02:58 AM ----------
vib$$$ said:
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT
Click to expand...
Click to collapse
Use this link.
https://drive.google.com/file/d/18QNEWcwgoMP1HPth8VxiI0DgCVe3My8L/view?usp=drivesdk

vib$$$ said:
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT
Click to expand...
Click to collapse
U can try but in My case the 9.2.7 boot image worked

gavi7566 said:
That's what I've been doing bud... :/ No luck.
---------- Post added at 03:19 AM ---------- Previous post was at 02:58 AM ----------
Use this link.
https://drive.google.com/file/d/18QNEWcwgoMP1HPth8VxiI0DgCVe3My8L/view?usp=drivesdk
Click to expand...
Click to collapse
This is the boot image of which Rom?

vib$$$ said:
This is the boot image of which Rom?
Click to expand...
Click to collapse
9.2.7.0

I had same problem , Yesterday i fixed it somehow .

S_Arya said:
I had same problem , Yesterday i fixed it somehow .
Click to expand...
Click to collapse
How??

How To Guide [ROOT] [PSYCHE] Root Xiaomi 12x with Magisk

{
"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"
}
Sources used: link
1. First unlock your bootloader. This thread does not cover this. I suggest you do not try to tamper with the 1week~ time gate you will encounter else it may get longer should you fail.
2. Enable Developer mode and adb from Developer settings again.
3 Download the appropriate Fastboot files for your device . See the About section in your phone's settings to know what you are currently running.
4. Download latest Magisk-vXX.Y.apk and install it on your device. Magisk developer only provides files from Github, do not download it from anywhere else.
5. Extract(Install 7-zip if needed) the fastboot .tgz archive and copy the boot.img from it to your phone's sdcard through adb (or other means):
Code:
adb push psyche_eea_global_images_V13.0.3.0.SLDEUXM/images/boot.img /sdcard/
6. Open up Magisk on your phone, press Install and use the patch option to navigate to the boot.img you just copied. Select that, next next next.
7. Read the output to see where the patched boot.img got saved. Pull that.
Code:
adb pull /sdcard/Download/magisk_patched-24300_D2K9V.img
8. Reboot phone to fastboot.
Code:
adb reboot fastboot
9. Flash the modified boot image
Code:
fastboot flash boot recoveryxy.img
10. Flash dtbo (found inside rom zip)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. Say your prayers and reboot, your device should now have functional root with Magisk
Code:
fastboot reboot

This did not work for me. Seemingly flashed okay, but phone is now bootlooping.

weggy101 said:
This did not work for me. Seemingly flashed okay, but phone is now bootlooping.
Click to expand...
Click to collapse
im sorry forgot step 10. flash vbmeta image. updated guide.

nofx161 said:
im sorry forgot step 10. flash vbmeta image. updated guide.
Click to expand...
Click to collapse
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5.0.SLDCNXM/miui-blockota-psyche-V13.0.4.0.SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.

I think it worked here, I patched the boot.img from the EEA ROM I'm running (V13.0.3.0.SLDEUXM_20220528.0000.00_12.0_eea) and the Magisk App says it's installed. The only problem is that I'm not able to edit files and/or paste new ones in the root/system folder.
I'm trying to edit build.prop but it says there's not enough space to complete the operation (using SolidExplorer), I tried to disable my nav buttons with FNG too, but that also won't work.

hey you can use my boot image which is rooted with magisk 25.0
magisk_patched-25000_WA0wW.img
drive.google.com
also the original boot if you messed up
boot.img
drive.google.com

Did anyone solved CTS profile ?

Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.

bjs339 said:
Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.
Click to expand...
Click to collapse
What ROM do you use? Stock or xiaomi EU or which one? Which modules have you tried? Thanks!

I'm on the stock rom and really haven't done much with it yet, so not much to report at this point.

An alternative way for installing magisk is to install twrp ( https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/ ) and then choose "install twrp" from the advanced menu in twrp. Then restart system and tap on the magisk button. The magisk manager will be loaded from web and your good to go with root.

shortek said:
Did anyone solved CTS profile ?
Click to expand...
Click to collapse
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.

bjs339 said:
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.
Click to expand...
Click to collapse
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517

bjs339 said:
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517
Click to expand...
Click to collapse
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).

HikL said:
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).
Click to expand...
Click to collapse
Looks like it if I'm reading that right.

bjs339 said:
View attachment 5699583
Looks like it if I'm reading that right.
Click to expand...
Click to collapse
Great news! Thank you!

Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
boot.img
drive.google.com

kiknalex said:
Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
Click to expand...
Click to collapse
I patched boot.img with another phone (huawei or smth) repeated all steps and now it's just stuck in fastboot bootloop...
I tried this
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5....SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.
But my Mi PC Suite doesn't detect phone when I plug cable, although the icon on phone shows that it's plugged in. Please help me...
Edit: issue was fixed in this thread
Please Help Me. Xiaomi 12x. Bricked Phone after trying to root. Stuck in fastboot bootloop.
Hello. I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/ only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available...
forum.xda-developers.com

Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla

Voodoojonny said:
Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla
Click to expand...
Click to collapse
Thank you for your answer. I already fixed issue in another thread, will edit my comment.

Question Can not boot any more

Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz

Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler

Moritz_pro said:
Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz
Click to expand...
Click to collapse
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot

hey Idk Who can help me for SPOOF(Change by random TEXT) Any android 5.1 to Android8's BASEBRAND Version and KERNEL Version ? How I can change it ? Phone ROOTED and XPosed module ready(not Virtual xposed) ? Please find it or Create new Xposed APK or SUPERuser(ROOT right) APK for Change BASEBRAND and Kernel Version,You know it writes under settings/about phone,Everything changing exclude these.Please Helpme,or if i can do this manually from which file /system or where ?

ineedstoplaggerwatchers said:
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot
Click to expand...
Click to collapse
I'm not sure if I am understanding all what you are saying right, so please tell me more detailed so I dont't make it worse.

turn of ur phone by holding power button 15 second then wait and be sure phone will not try reboot,then
Press and hold the Power, Volume Down and Home buttons for seconds;
{
"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"
}
Then the device will be the fastboot mode.
get this file then open it (Try open it by 7zip or winrar then extract it there),then click startCMD then type fastboot commands that i talked about it. but first type "fastboot devices" for be sure if it see your fastboot mode phone....... download this https://dl.twrp.me/a72q/twrp-3.6.2_11-1-a72q.img then rename it recovery(Right click on file then click properties and be sure if it says type of file: img file , so fullfile name must be recovery.img then put it into Adb&FastbootCommnderPrayForMe folder then enter this command "fastboot flash recovery recovery.img" then type fastboot reboot then remove cable quick,try power on ur phone, if it still stuck on boot then Poweroff by holding power button 15 second then 2 second later press power button by Volume Up Button together after 3 second later unpress power then continue holding volume up button,If twrp menu opened,swipe right adn go Wipe menu and ONLY chose Clear Cache , then restart phone . if still stuck then go Adb&FastbootCommnderPrayForMe folder and copy recovery.img file to same place and rename it boot(full file name must be boot.img), then go open command then type "fastboot flash boot boot.img" after enter it,Then type fastboot reboot and enter it. if still do same . then Find ur firmware's actual boot.img from your phone device model's firmare version File(firmware versions around 2GB to 10GB)'s boot.img . u can find it in internet too.Hope all works and i will be happy for u too

when I type Fastboot devices my Phone is not regionized what should I do?

Normally PC does not find your device as MTP device while you Hold POWER+home+volumeDown button(I mean fastboot mode without phone bootup).Coz it Shows device as MTP device after Phone bootedup(online).Maybe you tried install its driver as MTP by chosing manual install ? first download and install real usb driver(Adb&fastboot driver) of your samsung phone. https://developer.samsung.com/android-usb-driver then install it. then replug ur phone. Then go Device Manager of your PC,then replug your usb cable,and if you see New Device found like "unknow device or fastboot" then click them then click Properties on it, then click Update driver then click browse for Driver then click Let me pick from list then UNCHECK(unclick) "Show compatible hardware" then find your SAMSUNG ADB driver(if u cant see then click PORTS maybe it installed under Ports drivers) then click next to update it as Fastboot driver . but You can change your PC language to English for See same words in your Pc menus for I help you better coz im not German . but if already your secreen opens ? then you need go phone Settings / about phone/ Tap your phone Firm version 10 times and enable developer menu then enable USB ADB debug for install adb driver easily.if your phone screen not showing anything on screen . then you must just do fastboot mode by fastboot mode keys for install fastboot(samsung android usb driver or ADB driver another name)

When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.

Moritz_pro said:
When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.
Click to expand...
Click to collapse
Ignore what the other guy said above, fastboot is not a thing on Samsung phones. You can make it work with some patches however, but by default there is no fastboot.

ok can you tell me in detail so what do you think is the problem and wehre can I find these patches

Simon1511 said:
Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler
Click to expand...
Click to collapse
There should be no issues if properly following the XDA thread's instructions.
Moritz_pro said:
ok can you tell me in detail so what do you think is the problem and wehre can I find these patches
Click to expand...
Click to collapse

Thank you for remaining me this option I forgot about it, but I installed a custom Rom, but I'd like to run again on the original software can I install it again. If not, it doesn't matter, but it would be better.

The Rom won't start, the start sign appears but doesn't finish loading.
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com