Here were my steps with Razer 2:
SUCCESS: Developer Mode USB Debugging
SUCCESS: (CMD) fastboot flashing unlock
SKIPPED BY MISTAKE: (CMD) fastboot flashing unlock_critical
SUCCESS: (CMD) fastboot flash recovery twrp.img
SOFTBRICKED: TWRP.img flashed on recovery partition alerted Google Security AI
So, I received the error in this picture:
{
"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"
}
RAZER 2 SOFTBRICK ERROR
I did not unlock bootloader partition access, so when I use flash_all.bat, the script does not successfully create the hard drive partitions.
Strangely, it still tries to install system files on both A and B partitions (the Razer 2 uses A-B partitioning).
Of course, since creating the partitions failed, when the system.img flash reaches file 6/6 on partition B it has no partition to send the files to, so the script kicks me out.
Since the phone is softbricked, the phone does not show up on my drivers list either. The computer can flash the script, but it does not recognize the device is there at the same time:
fastboot devices: Visible
adb devices: not visible
It said Razer 2 in device manager prior to bricking, and changed to ADB interface while in bootloader mode after installing the correct USB Drives (Found on the Razer site). now it doesn't even show that the USB port is active.
I found a forum online that suggests using the CMD command to remove the error:adb reboot "dm-verity enforcing"
However, it failed and spit this error out:
adb reboot "dm-verity enforcing" Failed. Error: no devices/emulators found
I'm wondering if it because the computer cannot see the phone in device manager.
Or maybe it's because I don't have the patch they are talking about on the XDA forum. I am still learning and not familiar with what patches are. I know some bug fixes are called patches but aside from that I don't know how to use them. This was the patch link they sent that they said you need for the command to work:
https://github.com/invisiblek/andro...mmit/e1f62399183b854144301ce85f3a33b53ebfdde7
I also tried:
CMD: fastboot flash boot boot.img
CMD: fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This did not erase the error either.
Apparently, some phones did away with the recovery partition post 2016 (my razer is Dec 2020).
They flashed the recovery partition inside of the boot Kernel in newer phones instead of having a separate recovery partition with its own Kernel.
I also discovered that my phone's firmware (Found directly on Razer 2 Site) does not have an existing recovery.img file to even dirty flash to erase the TWRP file.
So naturally I am assuming that there ISN'T a recovery partition to flash the img file onto in the first place. This also explains why I am able to still use recovery mode on the phone even though I bricked it by flashing TWRP and replacing the stock recovery.img.
So CMD: fastboot flash recovery recovery.img is useless (I already tried just in case)
So now I have this TWRP file floating on the hardrive somewhere and do not know how to get rid of it if these 3 methods don't work.
So if the TWRP.img was not successfully flashed onto an existing partition (and bypassed security successfully), then I would imagine that flashing the original boot.img would not help which is why it did nothing.
If anyone knows how to get my device to get recognized while in this error mode that would help. Then I can figure out how to use the patch to get the CMD command to work to wipe the boot error.
I used CMD: fastboot flashing get_unlock_ability, and it spit out a zero (Meaning it can't be). So I need to change that to a 1 somehow with some voodoo tech magic.
Seems like you're making a lot of assumptions here. There is no "Google AI security". This error message means there's a dm-verity corruption error: Android Boot Flow
This is probably because you attempted to flash an image without properly unlocking the bootloader, so what you flashed does not match the verification signature.
I'm not familiar with the Razer 2, but if it's an A/B device (meaning it has A/B slots) it most likely does not have a recovery partition. The recovery kernel is compressed into the boot image, which contains the ramdisk and system kernel as well. It is not possible to directly "flash" portions of the boot image; any image flashed to /boot will completely overwrite the contents of the /boot partition.
It is important to note that due to the compression used for the recovery kernel, there is no custom recovery that can replace the factory recovery unless the entire boot image is replaced - i.e., LineageOS. TWRP does not support the compression necessary.
Remember that adb commands only work in recovery or system. You have to use fastboot commands in bootloader or fastbootd, and you must have the correct driver installed to interface with your device in bootloader/fastbootd mode.
If you're able to boot into bootloader, try the correct command to unlock bootloader on the critical partitions: fastboot flashing unlock_critical
[duplicate post]
V0latyle said:
Seems like you're making a lot of assumptions here. There is no "Google AI security". This error message means there's a dm-verity corruption error: Android Boot Flow
This is probably because you attempted to flash an image without properly unlocking the bootloader, so what you flashed does not match the verification signature.
I'm not familiar with the Razer 2, but if it's an A/B device (meaning it has A/B slots) it most likely does not have a recovery partition. The recovery kernel is compressed into the boot image, which contains the ramdisk and system kernel as well. It is not possible to directly "flash" portions of the boot image; any image flashed to /boot will completely overwrite the contents of the /boot partition.
It is important to note that due to the compression used for the recovery kernel, there is no custom recovery that can replace the factory recovery unless the entire boot image is replaced - i.e., LineageOS. TWRP does not support the compression necessary.
Remember that adb commands only work in recovery or system. You have to use fastboot commands in bootloader or fastbootd, and you must have the correct driver installed to interface with your device in bootloader/fastbootd mode.
If you're able to boot into bootloader, try the correct command to unlock bootloader on the critical partitions: fastboot flashing unlock_critical
Click to expand...
Click to collapse
I did try that but I get this error:
View attachment 5880855
So I think the dm-verity issue is locking me out of the access to use that command.
Also, I meant the Google AI Security that flags it as a dm-verity. This video also explains that it places the app in the boot Kernal (which is accessible still), which is how I think you are able to work around getting TWRP on the phone.
This is where I got my info:
(watch @ 4:00)
(watch @ 6:00)
Again, there is no "Google AI Security". Dm-verity is the first thing executed by the kernel - it compares a hash of the boot image against a reference hash. See Dm-verity
This should not matter on an unlocked bootloader; the only thing the bootloader checks is for a valid boot image header.
V0latyle said:
Again, there is no "Google AI Security". Dm-verity is the first thing executed by the kernel - it compares a hash of the boot image against a reference hash. See Dm-verity
This should not matter on an unlocked bootloader; the only thing the bootloader checks is for a valid boot image header.
Click to expand...
Click to collapse
It might be misinformation then on the video. I don't know but I guess it's not relevant either way.
Valid boot image header?
Any ideas why I am getting the error:
No adb devices/emulators found?
The phone isn't even showing when I use Diskpart on CMD to search for Disks.
I can't use an ADB command if it can't communcate with the phone. I ws going to try to use the command:
adb connect [USB port name]. Only fastboot works.
I saw someone connect that way when it was not showing. other than that I don't know how else to get my CPU to recognize my phone. Any ideas?
Pernilex said:
It might be misinformation then on the video. I don't know but I guess it's not relevant either way.
Valid boot image header?
Click to expand...
Click to collapse
Yeah, the bootloader needs a properly formatted header in order to load the boot image.
Pernilex said:
Any ideas why I am getting the error:
No adb devices/emulators found?
Click to expand...
Click to collapse
It depends. What command are you trying to use, and what mode is your device in when you're trying to use it? This error means that ADB is not able to detect a device that is either in recovery mode or Android system. If you try to use ADB commands in bootloader/fastboot mode, you may get this error too.
Pernilex said:
The phone isn't even showing when I use Diskpart on CMD to search for Disks.
Click to expand...
Click to collapse
Why would it? Diskpart only shows currently mounted partitions, so this would only work if the PC detects the phone as attached storage.
Pernilex said:
I can't use an ADB command if it can't communcate with the phone. I ws going to try to use the command:
adb connect [USB port name]. Only fastboot works.
Click to expand...
Click to collapse
Of all the ADB commands I'm aware of, "connect" is not one of them. Any connected ADB device will show up in adb devices
Pernilex said:
I saw someone connect that way when it was not showing. other than that I don't know how else to get my CPU to recognize my phone. Any ideas?
Click to expand...
Click to collapse
Try fastboot devices with the phone in bootloader mode, if nothing shows up you probably have a driver issue.
fastboot devices recognizes my phone.
adb devices also recognized my phone and so did device manager before I soft-bricked the phone.
So definitely not a driver issue.
ADB devices only recognized my phone when I selected USB file transfer while my phone was on the home screen and I could actually boot into it.
Before I bricked it, my phone's drivers were only recognized on the device drivers or under adb devices when the phone was in file sharing mode. My phone was never visible in adb devices while in bootloader/fastboot mode, so I assume this is what you are getting at.
I had forgotten that this was how I entered ADB device manager before I bricked it.
I'm assuming I have to turn file transfer on again somehow while stuck on bootloop without access to the User Interface.
Then once file transfer via USB Debugging is active, I can use the ADB command to disable dm-verity and get out of the loop.
Then I can double unlock the bootloader the way I was supposed to the first time and unlock internal storage access, not just the bootloader itself.
Then I will have access to the storage partitions so the phone will flash_all correctly and not try to flash the system image onto the phone without a partition and kick me out of the script.
Question is, how do I turn on file sharing with only access to fastboot? My phone is locked again right now (I re-locked it trying to follow a bootloop troubleshoot guide). It is now showing the same error as the fastboot critical_unlock command and saying I cannot do that.
So obviously remove dm-verity needs to come first after I enter file sharing mode. Then I can follow the proper double unlock steps.
Is there a fastboot command to re-enable USB debugging?
For example (ignore validity of commands this is just an example of steps):
1. fastboot enable USB debugging
2. fastboot boot USB file sharing / fastboot switch to ADB
3. fastboot disable dm-verity (bypass bootloop)
4. fastboot oem unlock bootloader
5. fastboot flashing unlock_critical (parttion access)
6. Fastboot flash_all (Razer 2 Stock ROM)
PS: I thought anything plugged into a USB port, HDMI port or a second hard drive port would be recognized by DIskpart. I did not know it was only for storage. I learned how to access it when I was teaching myself how to put windows ISO on a flash drive to reset my PC offline. That being said, if the CPU had access to my Razer's storage, wouldn't it show up like a flash drive would if it was hooked up to USB?
Were you able to get the issue fixed? I am currently having the same issue
Related
My phone is stuck on a loop after I tried fixing it. I tried installing Viper 6.2 on my m7 and it didn't work with an error of 7 or something and since I was coming from a different Rom I chose to wipe the data and start over. So now I have no Rom on my phone, no problem. I rebooted and tried to get into recovery again but then something weird happened where it would show the CW recovery logo and than skip to the Google logo like it was trying to boot up (no letters at top of screen). I tried installing a different recovery image but same thing it would show Teamwin logo and than cycle to the Google logo without letters at the top like it was trying to boot up and will go in a loop until I turn it off or go into the white bootloader menu. Also tried a factory reset from the white menu which did nothing. Please Help!
aznspdrmn said:
My phone is stuck on a loop after I tried fixing it. I tried installing Viper 6.2 on my m7 and it didn't work with an error of 7 or something and since I was coming from a different Rom I chose to wipe the data and start over. So now I have no Rom on my phone, no problem. I rebooted and tried to get into recovery again but then something weird happened where it would show the CW recovery logo and than skip to the Google logo like it was trying to boot up (no letters at top of screen). I tried installing a different recovery image but same thing it would show Teamwin logo and than cycle to the Google logo without letters at the top like it was trying to boot up and will go in a loop until I turn it off or go into the white bootloader menu. Also tried a factory reset from the white menu which did nothing. Please Help!
Click to expand...
Click to collapse
Try this procedure from alray:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
majmoz said:
Try this procedure from alray:
Click to expand...
Click to collapse
Yeah but the problem is I can't get to the recovery image anymore. the command says device not found and when trying to get to the recovery image it doesn't work.
aznspdrmn said:
Yeah but the problem is I can't get to the recovery image anymore. the command says device not found and when trying to get to the recovery image it doesn't work.
Click to expand...
Click to collapse
After you re-install the adb & fastboot disconnect your phone from the computer. Then reboot the computer and open the command window. Type: adb kill-server then when it is finished type: adb start-server. Now connect your phone to the PC. Type: adb devices
majmoz said:
After you re-install the adb & fastboot disconnect your phone from the computer. Then reboot the computer and open the command window. Type: adb kill-server then when it is finished type: adb start-server. Now connect your phone to the PC. Type: adb devices
Click to expand...
Click to collapse
ok when I do that it does nothing. The only menu I can get to on my phone is the bootloader one. If I choose recovery it'll get stuck in a loop and if I choose factory reset from the bootloader menu it'll get stuck in a loop. I think I need a way to factory reset the phone to any rom to get out of the loop. Right now I think the phone has a full recovery image on it but not a rom and that is somehow messing it up?
aznspdrmn said:
ok when I do that it does nothing. The only menu I can get to on my phone is the bootloader one. If I choose recovery it'll get stuck in a loop and if I choose factory reset from the bootloader menu it'll get stuck in a loop. I think I need a way to factory reset the phone to any rom to get out of the loop. Right now I think the phone has a full recovery image on it but not a rom and that is somehow messing it up?
Click to expand...
Click to collapse
If in setting USB Debugging is not enabled and there is an OS ADB will not work. It will work in Recovery.
If you have the stock firmware, you could flash it (if you are s-on, then you will need to relock your bootloader)
Then you would need to unlock your bootloader and flash a new recovery
ADB Push or sideload you rom while in recovery
Or
Flash a new recovery
ADB push or sideload your rom while in recovery
majmoz said:
If in setting USB Debugging is not enabled and there is an OS ADB will not work. It will work in Recovery.
If you have the stock firmware, you could flash it (if you are s-on, then you will need to relock your bootloader)
Then you would need to unlock your bootloader and flash a new recovery
ADB Push or sideload you rom while in recovery
Or
Flash a new recovery
ADB push or sideload your rom while in recovery
Click to expand...
Click to collapse
I've tried flashing a new recovery even changing the versions and types of recovery images. It still loops
Link to video of loop https://www.youtube.com/watch?v=efoXC-w45TA&list=UUXhWO2R4Ll4NrhM7M91T2sw
Fixed the issue by installing a RUU zip and then installing a custom rom.
aznspdrmn said:
I've tried flashing a new recovery even changing the versions and types of recovery images. It still loops
Link to video of loop https://www.youtube.com/watch?v=efoXC-w45TA&list=UUXhWO2R4Ll4NrhM7M91T2sw
Click to expand...
Click to collapse
It looks like your have an OS 3.09.401.1. I found a stock, non-rooted odex version.zip. This may wipe all of your personal data off of the phone. If fastboot is working, you should be able to flash it in FASTBOOT USB.
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_rom.zip
fastboot flash zip name_of_rom.zip
fastboot reboot
You have to run the flash command twice, the first time prepares the firmware/rom to accept the changes.
Trying to flash twrp recovery...getting error "target reported max download..."
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!
DoritoKing said:
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!
Click to expand...
Click to collapse
1) how are you trying to install TWRP?
2) You are using the most recent version from our official TWRP maintainer?
January 12, 2017
twrp-3.0.3-0-Mod_01-quark.img
https://www.androidfilehost.com/?fid=745425885120699982
3) And you are showing known file extensions in Windows? Do you know what that means?
{
"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"
}
If you have a jpg or pdf, and you see a file name -- do you also ALWAYS, ALWAYS see the extension like jpg or pdf? Default in Windows -- for idiotic reasons -- is to "hide known file extensions".
Make sure that box is UNchecked in your Windows settings. Because otherwise you are re-naming TWRP as TWRP.img(.img). You do NOT have to type the .img part, it's ALREADY an .img file.
That may or may not be your issue, but it messed up a lot of people in the past. ADB couldn't find TWRP.img because they had unknowingly called it TWRP.IMG.img -- because they couldn't see the file extension and thought they needed to add it to the file name.
1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!
Just tried with the changes....still getting same error messages.
DoritoKing said:
1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!
Click to expand...
Click to collapse
When you unchecked the extension box, what is now the visible name of your TWRP file? Does it say TWRP.img.img or just TWRP.img? Besides unchecking the extension box, you also need to make sure you are typing the actual name of the file. IF you had typed "TWRP.img"(.img) before, you now need to re-name it just "TWRP".img.
If you confirm that's not the issue, then we'll get @bhb27 involved over in the Quark TWRP thread.
I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great
DoritoKing said:
I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great
Click to expand...
Click to collapse
OK, just as a test, do this. Forget the name TWRP. That's just a convenience. Call it something else. Rename it box or chair. I'm not joking. Then, in your PC, what file name do you see? IF you renamed it "box", you should see box.img. You do NOT type .img. It's just the extension that should already be there!
then flash: fastboot flash recovery box.img
I'm suggesting this because somehow, somewhere it seems your file name is messed up?
Also you have done all this too? Permissions and stuff?
Enable USB debugging on your device:
Open Settings on your device.
Go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and you’ll see Developer options there, open it.
Tick the USB Debugging checkbox.
Connect your device to the PC. And type the following into the command window we opened to boot your device into bootloader/fastboot mode:
adb reboot bootloader
└ If you get a permission dialogue on your device to “Allow USB debugging”, tap OK.
Click to expand...
Click to collapse
Maybe revoke those permissions and re-enable them?
Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...
DoritoKing said:
Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...
Click to expand...
Click to collapse
I was just suggesting you revoke the USB permissions and re-enable them in Developer Settings, just to make sure. That's the only thing I'm aware of you need to do on the phone side... If anyone knows something different, feel free to correct me!
@bhb27 is our TWRP maintainer for our official TWRP. So, I'm mentioning him here so he'll see this issue. Maybe he'll have some ideas?
Also, you you can post this issue over in the Quark TWRP thread. You can put a link to this thread in your post, so people can see what all we've tried.
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://forum.xda-developers.com/mo...recovery-twrp-2-8-7-0-touch-recovery-t3180308
I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img
bhb27 said:
I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img
Click to expand...
Click to collapse
Here are the screenshots...if this isn't what you were looking for, just let me know.
DoritoKing said:
Here are the screenshots...if this isn't what you were looking for, just let me know.
Click to expand...
Click to collapse
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:
bhb27 said:
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:
Click to expand...
Click to collapse
Didn't recognize that command...here is the screenshot
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
DoritoKing said:
Didn't recognize that command...here is the screenshot
Click to expand...
Click to collapse
did you download the file I share?
TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.
TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
Right. His screenshot is showing other extensions, like .exe, .txt, .dll -- so his TWRP extension should be .img. It's missing.
What I cautioned him about was double naming the extension -- TWRP.img.img, which can accidentally be done if you have your Windows settings to hide known file extensions. Since his file extensions are no longer hidden, his TWRP file should say TWRP.img.
But naming it TWRP is just a convenience instead of using the regular file name like "twrp-3.0.3-0-Mod_01-quark.img". It's easier to type TWRP.img in the Windows command box than that long official file name. You could easily also re-name it "chair.img" or "box.img" as long as you were re-naming the correct file. I even suggested he do that because he seemed hung up over the TWRP name.
At this point, he probably needs to also re-download the TWRP file and re-name it. Now that he can see file extensions, it should automatically have the .img extension.
Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?
DoritoKing said:
Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?
Click to expand...
Click to collapse
I'm going to hazard a guess here that you also flashed SuperSu in TWRP and you are running the new Marshmallow update. (Yeah, confirmed, I just checked your first post. You took Marshmallow update.) In which case, it sounds like you flashed the wrong version of SuperSu. You have to flash an older version for initial root or your phone will stick at the bootloader warning screen. This has been discussed in all the Marshmallow threads.
What version SuperSu are you using? If on stock Marshmallow or stock-based Marshmallow ROM, the one required is BETA-SuperSU-v2.62-3-20151211162651). You can boot into TWRP, plug your phone into a PC and drag it over like a flash drive. It will show up in the root folder. Flash it, wipe all caches, reboot.
I've attached it to this post.
AFTER initial root, and after you successfully boot, then you can update to newest version of SuperSu. You just need it for initial root and to successfully boot the first time.
PREDICTION: Your next question will be how to get rid of the unlocked bootloader screen. Because you will see it every time you reboot your phone. When you do, here's your answer. But first, you need to flash the correct SuperSu to get past the bootloader screen.
DoritoKing said:
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.
Click to expand...
Click to collapse
Congratulations on installing TWRP.
I can't work out what's going on.
My phone lost it's root a few days ago - I only noticed when Magisk said it had a new one. So here's the lowdown:
My TWRP is out of date.
Magisk is out of date.
I've downloaded both the magisk.zip file and an img file of the latest TWRP.
I put them on the deskop, in the adb folder (in C drive) and on the phone under "downloads".
Boot into recovery, but when I navigate to install a zip file, it can only see the system files, no "downloads" folder or pictures or anything. I can't seem to change that.
Use Powershell to try and sideload the TWRP zip and it says "waiting for device" - that seems good. However, when i then boot into fastboot mode, Powershell tells me "error: cannotload twrp... .img"
So I try and look at Magisk, but I can only download the zip (of which I've done and can't flash it via recovery), or patch boot file, of which I can't navigate to as I'm currently not rooted so it can't find the boot file anyway.
What do I type into Powershell to flash the latest Magisk (I guess I can then update TWRP after using the in-
built updater?)?
When in TWRP, I click on the three lines on the right, which say:
Could not muont /data and unable to find crypto footer.
Failed to mount '/data' (no such process)
Unable to recreate /data/media folder,.
Updating partition details
Failed to mount '/data' (no such process)
... done
Unable to mount storage
Failed to mount '/data' (no such process)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (no such process)
Click to expand...
Click to collapse
What can be causing all of this?
Probably rip UFS chip, if
Code:
fastboot format userdata
won't help, then you should send your phone for repair
Hmm.
So the only fix is to format all the data?
What data gets deleted?
I don't really want to do that if I can help it but I guess it's the only way to fix it.
Strange how it's just done it by itself.
anotherxdauser said:
Hmm.
So the only fix is to format all the data?
What data gets deleted?
I don't really want to do that if I can help it but I guess it's the only way to fix it.
Strange how it's just done it by itself.
Click to expand...
Click to collapse
Is the system bootable? If yes, then you can make a backup, if not, then you can consider your data gone.
"format userdata" removes everything you have stored on the phone
Yeah, I can boot to my Resurrection Remix rom and see everything, all my files, it's fine.
I can connect to a PC and move files to and fro the device.
It's just TWRP doesn't seem to see the storage. When looking, it just says 0Mb :S
Does Userdata mean the apps and stuff as well?
I saw a video of someone formatting the userdata to ex2, then back to ex4 but if it means I'd have to reinstall RR then it's a lot of work for something that may happen again in the near future.
I have Titanium Backup but of course, it needs root, of which I can't gain :/
Sounds a lot like a failed decrypt of an encrypted userdata partition, this is common in this phone with TWRP and custom ROMs.
Skickat från min ONEPLUS A3003 via Tapatalk
pitrus- said:
Sounds a lot like a failed decrypt of an encrypted userdata partition, this is common in this phone with TWRP and custom ROMs.
Click to expand...
Click to collapse
Is there non-destructive way to fix?
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Which TWRP version do you have exactly?
Sent from my ONEPLUS A3003 using Tapatalk
przemcio510 said:
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
Yeah, try this first. Problably you have a twrp lower than 3.2.0? I think below that it cannot decrypt Oreo encrypted Partitions.
Second thing is. Probably you have to format Data (not Userdata) anyway. I think you probably tried to upgrade Magisk because you lost root. But Magisk hat a bug in 17.0. That corrupted the permission Database. I had the same problem and was not able to get root again until formatted data. You will loose every app and its setting when formatting it. But everything under sdcard/ will still be there. So the download folder should be fine and everything. So when you make a titanium backup of your most valuable apps. You can restore them after renewing your phone.
TLDR:
1. Make Titanium Backup if you have it and want to have your apps back as before.
2. Try przemcio510 suggestion to get new TWRP. (most important)
3. backup your partitions and copy them to your pc
4. backup everything importantto you on your "SDCard" Volume (Where Download is and everything)
5. format DATA, Cache, Dalvik/ART Cache, System
4. Reflash Full OxygenOS 5.0.5
(optional) 5. Flash Rom of your flavor (with/without Gapps)
(optional) 6. Flash magisk
7. boot up your device
przemcio510 said:
Oh, ok, I thought that the system is broken too. That's ok then, your memory chip is fine.
Can you boot an up-to-date TWRP from fastboot and try to access data?
Try with
Code:
fastboot boot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
Did this. ADB said it was "waiting for device" so I rebooted to fastboot but then the ADB window shows some options (see quote below), nothing to show it's done anything.
I put the img file on the sim card on the phone and in the directory of the adb.
Code:
PS C:\WINDOWS\system32> fastboot twrp-3.2.3-0-oneplus3.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\WINDOWS\system32>
RASTAVIPER said:
Which TWRP version do you have exactly?
Click to expand...
Click to collapse
3.1.1-0
S4RGE said:
TLDR:
1. Make Titanium Backup if you have it and want to have your apps back as before.
2. Try przemcio510 suggestion to get new TWRP. (most important)
3. backup your partitions and copy them to your pc
4. backup everything importantto you on your "SDCard" Volume (Where Download is and everything)
5. format DATA, Cache, Dalvik/ART Cache, System
4. Reflash Full OxygenOS 5.0.5
(optional) 5. Flash Rom of your flavor (with/without Gapps)
(optional) 6. Flash magisk
7. boot up your device
Click to expand...
Click to collapse
My Titanium Backup needs root to work :/
It might have been when I upgraded RR Rom to the Oreo release, but it's only been the past week when I mysteriously lost root access.
anotherxdauser said:
Did this. ADB said it was "waiting for device" so I rebooted to fastboot but then the ADB window shows some options
Click to expand...
Click to collapse
To be clear, I think you mean fastboot whenever "ADB" is mentioned above. adb and fastboot are related, but 2 different things, with different usages and requirements. So it's best to refer to them in correct and distinct terms.
adb: Needs debugging enabled. Will work only in OS or custom recovery. Will not work in bootloader (even in fastboot mode) - maybe this is why you have "waiting for device"?
fastboot: Does not need debugging enabled. Only works in bootloader-fastboot mode.
fastboot is what you want for booting/flashing TWRP. Not adb (at least for the commands/methods suggested here).
anotherxdauser said:
PS C:\WINDOWS\system32> fastboot twrp-3.2.3-0-oneplus3.img
Click to expand...
Click to collapse
When command prompt shows you the list of command, this almost always means your command syntax is incorrect.
In your case, you used typed "fastboot" and a file name, without telling it what to do with that file name. The suggested command was "fastboot boot filename" (no quotes) or another usage option is "fastboot flash filename".
A little confusing I know, "fastboot" in itself is not a full command/action. I has to be "fastboot boot". Think of fastboot as a "thing" instead of an action. Thus, you still need to tell fastboot to perform an action ("boot").
anotherxdauser said:
...
3.1.1-0
My Titanium Backup needs root to work :/
It might have been when I upgraded RR Rom to the Oreo release, but it's only been the past week when I mysteriously lost root access.
Click to expand...
Click to collapse
Ah right I forgot.
As redpoint73 mentioned you have to be in fastboot mode.
When you start up your phone and the unlock Warning ist triggered. Push the volume up or down button and go to fastboot.
When you are in there the fastboot command should work.
As redpoint73 pointed out it is very important that you type "fastboot boot (ImagePath)".
To make it easier for you, you should copy the image where fastboot is.
Then you have only to enter
fastboot boot twrp-3.2.3-0-oneplus3.img
This should do the trick. If you still need help. Don't hesitate to ask.
redpoint73 said:
To be clear, I think you mean fastboot whenever "ADB" is mentioned above. adb and fastboot are related, but 2 different things, with different usages and requirements. So it's best to refer to them in correct and distinct terms.
In your case, you used typed "fastboot" and a file name, without telling it what to do with that file name. The suggested command was "fastboot boot filename" (no quotes) or another usage option is "fastboot flash filename".
Click to expand...
Click to collapse
Sorry my explanation isn't that great.
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
At any rate, tried "fastboot boot twrp-3.2.3-0-oneplus3.img" and the command prompt window shows "waiting for device". My device is on, at the homescreen, doing nothing. The command prompt window stays like that until I boot into fastboot mode, where it then just shows the large list of commands quoted above.
HOWEVER, a development!
When in fastboot mode and using the "fastboot boot twrp-3.2.3-0-oneplus3.img" command, the window now says "cannot load 'twrp-3.2.3-0-oneplus3.img': No such file or directory". So I tried typing the exact file path (C:\adb\twrp... img), which has now allowed me to boot into the updated TWRP.
Does this mean it's just booted into it, but not updated to it?
I'm able to see the contents of my sdcard now. So flashed the latest 17.1 magisk zip and... success! I'm now on the latest magisk and have been able to flash the latest TWRP to recovery.
Just to say, I really appreciate the help with this.
I know I could factory reset but it's helping me learn more.
anotherxdauser said:
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
Click to expand...
Click to collapse
You confuse some terms. adb and fastboot are programs, command prompt is the interpreter of the commands you give to these programs.
And yes, the fastboot is that mode.
anotherxdauser said:
At any rate, tried "fastboot boot twrp-3.2.3-0-oneplus3.img" and the command prompt window shows "waiting for device". My device is on, at the homescreen, doing nothing. The command prompt window stays like that until I boot into fastboot mode, where it then just shows the large list of commands quoted above.
Click to expand...
Click to collapse
Fastboot mode is meant to be used while phone is booted into fastboot mode
anotherxdauser said:
When in fastboot mode and using the "fastboot boot twrp-3.2.3-0-oneplus3.img" command, the window now says "cannot load 'twrp-3.2.3-0-oneplus3.img': No such file or directory". So I tried typing the exact file path (C:\adb\twrp... img), which has now allowed me to boot into the updated TWRP.
Click to expand...
Click to collapse
"no such file" means that you could have not copied the img file to the same folder as the adb binary (this is not the case when adb and fastboot binaries are installed with %PATH% variable added, then you can use these commands all over the filesystem).
anotherxdauser said:
Does this mean it's just booted into it, but not updated to it?
Click to expand...
Click to collapse
Fastboot boot command, which I have provided earlier is used to boot temporarily, one time an image you tell it to.
anotherxdauser said:
Just to say, I really appreciate the help with this.
Click to expand...
Click to collapse
Just kindly informing that there is a button on the lower-right hand corner for this
anotherxdauser said:
Whenever I've mentioned adb it's the dos/command prompt window.
Fastboot is that small menu where it shows whether the device bootloader is locked or not isn't it?
Click to expand...
Click to collapse
Both adb and fastboot are command prompt functions. They are both "bridge" tools used to communicate from computer to the phone.
The phone menu screen you are referring to is bootloader. Fastboot is one of the choices on that (bootloader) menu. It puts the phone in fastboot mode, which is specifically intended for fastboot commands (only mode fastboot command will work). The response will always be "waiting for device" if you try fastboot commands, and not in fastboot mode.
If the command is "fastboot . . . " you are issuing fastboot commands (not adb).
If the command is "adb . . . " you are issuing adb commands.
Again, they are both related, but different. Different requirements and usages for adb versus fastboot. It is important to understand the distinction, so you don't waste more time trying command in the wrong mode (which will never work).
{
"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"
}
System Image: https://drive.google.com/file/d/1cAcgP55upO6UuX-gecPIXA_xnO0IXvUO/view?usp=sharing
Flash System Image:
- Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
- Connect your Razer Phone to your computer over USB.
- Start the Phone in Download Mode with one of the following methods:
- Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
- Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
- If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
- Open a terminal on your computer and navigate to the unzipped system image directory.
- Execute the flash_all script. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
- Once the script finishes, your Phone will reboot.
- You should now lock the bootloader for security.
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
LSS4181 said:
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
Click to expand...
Click to collapse
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
JDBarlow said:
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
Click to expand...
Click to collapse
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
LSS4181 said:
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
Click to expand...
Click to collapse
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
JDBarlow said:
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
Click to expand...
Click to collapse
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
LSS4181 said:
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
Click to expand...
Click to collapse
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
JDBarlow said:
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
Click to expand...
Click to collapse
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
LSS4181 said:
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
Click to expand...
Click to collapse
/HavocOS/Ten/20200402-vanilla/Havoc-OS-v3.3-20200402-arm64-ab-vanilla-nosu.img.xz
If anyone can get havoc 3.3 to work on Verizon without the sim card issue please let me know. No gsi rom will work on Verizon. Its frustrating. Thanks.
Finally got the MR3 update extracted
I worked all night extracting/converting the stock img and got beat by minutes posting Lol... anyway I also have the stock ota for global variant of MR3 if anyone needs it. You can easily patch the boot img with magisk and fastboot flash boot_a with the patched boot img and you have root again on MR3 Update. Works flawless
i Take a copy Thank You
Flashed some stuffs from MR3: modem (both), bluetooth (both), dsp (both), vendor (both), boot (inactive B slot only), system (inactive B slot only). These seem to work.
However, when flashing system and vendor I saw it mentioned something about "invalid sparse file format at header magic", but the flashed stuffs (at least vendor) looks fine.
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Havoc 3.3 GSI works fine here (the SELinux fix may still be needed for it to boot). However, for some reasons (either due to recent Magisk canary update, or something else), I lost access to VoLTE and that after updating to the new GSI version, all my app's permissions were lost and I need to reassign them (maybe it's time I back things up and start over again, as the permission reset issue can indeed happen when dirty-flashing newer GSI versions).
LSS4181 said:
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Click to expand...
Click to collapse
Running Manjaro Linux here too and experience the same behaviour.
Peace.
Can you dirty flash the mentioned images? Don't really feel like reinstalling all my apps and data.
is there a new root method
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Those usb drivers didn't work for me. What did work however was the samsung usb drivers so I downloaded them and installed, however that wasn't enough. While in fastboot mode under device manager, I can't recall how I installed it but I forced the driver either from android device in list or added new legacy hardware and installed samsung android adb interface. After that when I typed fastboot devices in console from tools folder it reported back for me. I hope this helps.
Click to expand...
Click to collapse
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
Click to expand...
Click to collapse
I u forgot something....
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Xinfuzemodz said:
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
Click to expand...
Click to collapse
Are you serious? The link of the OP is the link to MR3. If you click the flash_all.bat file it will wipe your phone and you get a fresh copy of MR3 installed so yes it can be installed on other builds
miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!
Hello,
I unlocked my Mi8 and successfully installed Lineage on it.
After trying to install Magisk, my phone only boots into fastboot (and mi recovery, but that's not very helpful).
fastboot boot twrp.img results in error :
FAILED (remote: Failed to load/authenticate boot image: 00000050)
I tried MIFLASH by
1) downloading, dezipping and starting newest miflash (2020.3.14.0)
2) installing drivers
3) downloading and dezipping MIUI-fastboot-ROM
4) entering path* into miflash, refresh and flash (already tried all options "clean all" to "clean all and lock")
*) path to the folder that includes among others flash_all.bat
all this results in error:
not catch checkpoint (\$fastboot -s .*lock), flash not done
Nothing changed with the phone, still the same error.
While wanting to review the logs, I clicked in miflash on log/flash log. The log did not say anything helpful, but the error code of fastboot boot twrp.img changed to command write failed (Unknown error). Nothing else changed.
UPDATE: changed back to previous error (remote: Failed to load/authenticate boot image: 00000050)
If you have any idea or need any more information, please tell me!
I need that phone and cannot afford to terminally brink it!!
I did not find much online, did no one else had this problem??
THANK YOU!
PS: Using lenovo-laptop with quite vanilla win10 (and not so vanilla kubuntu dualboot, but miflash only supports windows)
MIFLASH-log says:
Code:
[14:37:14]:lsusb path:"C:\Users\<>\Downloads\MiFlash20200314\MiFlash20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:GetScriptDevices
[14:37:15]:FlashingDevice.flashDeviceList.Remove ab6ee6a0
[14:37:15]:add device ab6ee6a0 index 1
[14:37:15]:Thread start,thread id 5,thread name ab6ee6a0
[14:37:15]:start process id 2524 name cmd
[14:37:15]:Thread stopped, thread id 5, thread name ab6ee6a0
UPDATE:
what would the world be without mysteries. Though I cannot really accept them in the IT sector, I cannot really explain, why "everything" works now.
The error of miflash still exists, but fastboot works.
I tried booting and flashing the lineage boot.img instead of twrp.img as well as miflash about every five minutes. I do not think it was the latter, though.
I am still curious on that matter, but having everything working is more important.
Thank you anyway.
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub.
There is no need to use miflash to flash the fastboot miui rom - you can do it from command line in both windows and linux. Once you decompress the fastboot tar.gz, you have .bat and .sh files in the folder - miflash runs those exact files. Just install adb and fastboot on kubuntu and run your choice of script (flash_all, flash_all_lock, etc.) this has the added benefit of not needing odd drivers in windows (last time i used miflash it complained about some .net stuff that i had to manually install).
Since normally you would install twrp i have to wonder if by any chance mi-recovery is not checking the boot image before flashing it ... not sure, or maybe it had something to do with the FBE of lineage since there was no recovery in place to decrypt the partitions, if i remember correctly, the boot image needs to be signed with the verity key. The log snippet you provided doesn't tell anything as it has no error messages or anything.
Either way, not sure how what you brutforced to get it working but glad it solved itself, however, if you still have mi-recovery instead of a custom one, i would suggest you backup the device, flash MIUI without locking the bootloader, installing twrp (not just booting it) and reinstalling lineage from there. (all this can be done from your kubuntu install so you avoid driver and other windows shenanigans)
to install adb and fastboot it's just a question of sudo apt install adb fastboot
either tar -xvzf the archive of the fastboot image or just extract it from the file manager
open a terminal in the extracted folder (where the bat and sh files are)
put the phone in fastboot mode, connect via usb and do a "fastboot devices" just to make sure the device shows up
./flash_all.sh (this does the exact same thing as the clean option in miflash - just open the script and take a look through it)
Once the flash is done and the phone reboots, skip through all the setup steps just so miui loads up then reboot to fastboot
get twrp from their website, open terminal where it is downloaded and "fastboot flash recovery <name_of_file>.img"
once the command finishes do a "fastboot boot <name_of_file>.img" and once you are in twrp, go yo wipe, do a factory reset, back, advanced wipe and select the caches, back, format data, type yes, back to the main menu of twrp and reboot recovery, this should boot you back into twrp but this time the one that is flashed on the device.
from here on install rom of choice and magisk as usual (use the install option in twrp tho, don't unpack the zip)
Had the phone for 2 years and i flashed different roms on it almost weekly since the wait time to unlock the bootloader expired and never had an issue with this workflow and it saves you from having to use windows. Even for unlocking the bootloader, in case you ever lock it back up, you can use https://xiaomitool.com/V2/download (worked like a charm on linux)
sorfat said:
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub....
Click to expand...
Click to collapse
Thank you for your detailed reply!
Of cause, in order to install lineage, I used TWRP. But I somehow did not install it, but used fastboot boot twrp.img in order to manually temporary boot twrp every time I need it. It was not intentionally at first (did do
"fastboot flash recovery <name_of_file>.img"
Click to expand...
Click to collapse
) but I learned to like the mi recovery for it's wiping and being able to use with the keys (not touch, since I managed to disable touch once before that). Mi recovery does not allow flashing at all, so no worries there^^
I have read the ryzen thread before posting, that's why I included my hardware. Not sure, if Lenovo has ryzen, mine does not.
Why I did not think of just running the script in kubuntu instead of hassling with windows, I do not know. Guess it does have something to do with the wood in front of all the trees.
I have the phone for about one and a half week and flashed it at least once a day :laugh:
But I hope to neither lock it again (twice is sweaty enough) nor have to flash it every week.
Thank you very much, if I ever lock myself out again or get another phone to set up, I will defintely reread this post!
btw: is there no way in xda to close a thread?