Related
Hey all,
Just nuked my phone set up so I could install the latest doomkernel (first time wanted to try it out) on my GSM play running latest SE software, but it refuses to flash the boot.img file to the device.
I unlocked (after a re-lock a while ago) the boot loader and can access fastboot (blue LED on phone, "fastboot.exe -i 0x0fce getvar version" brings a version 0.3)
fastboot.exe flash boot boot.img ---> stuck on "< waiting for device >" message
I tried with the latest flashtool and I got this from the log:
Code:
05/046/2012 00:46:31 - INFO - Device connected in fastboot mode
05/046/2012 00:46:42 - INFO - Selected kernel (boot.img or kernel.sin): C:\boot.img
05/046/2012 00:46:42 - INFO - Flashing selected kernel
05/046/2012 00:46:43 - INFO - FASTBOOT Output:
sending 'boot' (7330 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
I then rooted the phone using zergrush and it's rooted properly, but I can't for the life of me figure out why I can't push the kernel, since I know the fastboot process is working because I used it to unlock the boot loader
Code:
C:\Users\Access\Downloads>fastboot.exe -i 0x0fce oem unlock 0x
< waiting for device >
... INFOUnlock phone requested
INFOErasing block 0x00000d00
INFOErasing block 0x00000e00
INFOErasing block 0x00000f00
Is there something I'm missing or will I never be able to have a custom kernel?
Any ideas and suggestions appreciated thanks
I have the exact same problem with my Arc S, can`t figure out why is getting stuck on "< waiting for device >"
Try fastboot -i 0x0fce flash boot boot.img
Michealtbh said:
Try fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
Thx alot man, it worked like a charm !
Code:
C:\Android>fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android>fastboot -i 0x0fce flash boot boot.img
sending 'boot' (7922 KB)... INFOUSB download speed was 9187kB/s
OKAY [ 0.892s]
writing 'boot'... INFODownload buffer format: boot IMG
INFOFlash of partition 'boot' requested
INFOS1 partID 0x00000003, block 0x00000280-0x000002e3
INFOErase operation complete, 0 bad blocks encountered
INFOFlashing...
INFOFlash operation complete
OKAY [ 1.532s]
finished. total time: 2.424s
Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows
Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:
All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!
So I was flashing my device to the December update on my unlocked bootloader Pixel 3. Everything seemed to work fine and it loaded after the flash. Went through the startup options and reset the phone. Now I can only turn it on by holding down power and Volume Down to load in Fastboot Mode. When I do it gives me "Device state: error!" (error is in red).
When I open command prompt and type fastboot flashing unlock it tells me:
FAILED (remote: 'Error getting device locked state No Response') after 9 seconds.
Any advice on how to get this back up and running? I've done some google searches but haven't found this error message. Thanks in advance!!
First thing to try is flash factory image with flash-all, and then start over. You could try and remove -w from flash-all script to try first, so it doesn't wipe the phone.
Getting to bootloader is always a good sign at least.
I am having the same problem. Except when i go to flash the recovery or even the boot image i keep getting error not allowed. I too can only boot to the bootloader.
I've tried this.
Sending 'bootloader_b' (8489 KB) OKAY [ 0.437s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.809s
rebooting into bootloader OKAY [ 0.062s]
Finished. Total time: 0.062s
< waiting for any device >
Sending 'radio_b' (71148 KB) OKAY [ 2.598s]
Writing 'radio_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 11.955s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.058s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: values given
Serial Number........: values given
--------------------------------------------
Checking product OKAY [ 0.052s]
Checking version-bootloader OKAY [ 0.054s]
Checking version-baseband OKAY [ 0.059s]
extracting boot.img (64 MB) to disk... took 0.627s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.062s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 5.967s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2158 MB) to disk... took 71.632s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 12.458s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.004s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 12.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_b' (65536 KB) OKAY [ 2.457s]
Writing 'boot_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 185.977s
Press any key to exit...
boostedduece said:
First thing to try is flash factory image with flash-all, and then start over. You could try and remove -w from flash-all script to try first, so it doesn't wipe the phone.
Getting to bootloader is always a good sign at least.
Click to expand...
Click to collapse
Ofuroski said:
So I was flashing my device to the December update on my unlocked bootloader Pixel 3. Everything seemed to work fine and it loaded after the flash. Went through the startup options and reset the phone. Now I can only turn it on by holding down power and Volume Down to load in Fastboot Mode. When I do it gives me "Device state: error!" (error is in red).
When I open command prompt and type fastboot flashing unlock it tells me:
FAILED (remote: 'Error getting device locked state No Response') after 9 seconds.
Any advice on how to get this back up and running? I've done some google searches but haven't found this error message. Thanks in advance!!
Click to expand...
Click to collapse
When you load fastboot mode what is the 'device state'?
what version of SDK Platform-tools is on your computer?
It should be r28.0.1
Did you open the Command Prompt in the Platform-tools folder?
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + December 2018 Security Patch
Make sure you all have the latest sdk platform tools, r28. Looking at your posts here it looks like that is the problem. And to op, once the bootloader is unlocked it'll stay that way unless you specifically lock it so there's no need to try again. But, once you're in the bootloader use the command fastboot devices. Does it return a serial number or just hang like when you tried to unlock again. If it just hangs there's either a problem with your fastboot drivers or try different cables and USB ports.
Sent from my [device_name] using XDA-Developers Legacy app
Yes, I'm in the powershell in the folder and have the latest SDK. As stated, when I boot up into Fastboot mode, it gives device state as "error!" in red lettering like it's unable to determine if it's locked or not. It does not say locked or unlocked.
Homeboy76 said:
When you load fastboot mode what is the 'device state'?
what version of SDK Platform-tools is on your computer?
It should be r28.0.1
Did you open the Command Prompt in the Platform-tools folder?
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + December 2018 Security Patch
Click to expand...
Click to collapse
When I type adb devices it says list of devices and is blank. However if I type commands such as flash-all it will recognize the device and attempt to flash (although it fails as seen above) since it gets hung up on not being able to determine the locked state. When doing this, it does show a serial number. Any other ideas?
jd1639 said:
Make sure you all have the latest sdk platform tools, r28. Looking at your posts here it looks like that is the problem. And to op, once the bootloader is unlocked it'll stay that way unless you specifically lock it so there's no need to try again. But, once you're in the bootloader use the command fastboot devices. Does it return a serial number or just hang like when you tried to unlock again. If it just hangs there's either a problem with your fastboot drivers or try different cables and USB ports.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ofuroski said:
When I type adb devices it says list of devices and is blank. However if I type commands such as flash-all it will recognize the device and attempt to flash (although it fails as seen above) since it gets hung up on not being able to determine the locked state. When doing this, it does show a serial number. Any other ideas?
Click to expand...
Click to collapse
If you're booted into the bootloader adb doesn't work. It's only for when you're in system or recovery. Fastboot is what you need when booted into the bootloader. I'm sure, based on the flash-all working, that if you type fastboot devices when booted into the bootloader you'll get yet serial number returned.
Have you tried to flash only the bootloader image to both slots?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
If you're booted into the bootloader adb doesn't work. It's only for when you're in system or recovery. Fastboot is what you need when booted into the bootloader. I'm sure, based on the flash-all working, that if you type fastboot devices when booted into the bootloader you'll get yet serial number returned.
Have you tried to flash only the bootloader image to both slots?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, you are 100% correct. When I type fastboot devices the serial does appear. However, this still does not help me with the "device state: error!" message. The only thing I've flashed was the December update, so I'm not sure what you mean by flashing only the bootloader image to both slots.
Ofuroski said:
Yes, you are 100% correct. When I type fastboot devices the serial does appear. However, this still does not help me with the "device state: error!" message. The only thing I've flashed was the December update, so I'm not sure what you mean by flashing only the bootloader image to both slots.
Click to expand...
Click to collapse
If you extract the factory image you'll find a bootloader-blueline- image file. You would use
fastboot flash bootloader --slot all bootloader.img (where bootloader is the full name of the file)
Edit, sorry you have the XL so it would be bootloader-crosshatch-
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
If you extract the factory image you'll find a bootloader-blueline- image file. You would use
fastboot flash bootloader --slot all bootloader.img (where bootloader is the full name of the file)
Edit, sorry you have the XL so it would be bootloader-crosshatch-
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Right. I tried that now and it gives me the same.
Sending 'bootloader_a' (8489 KB) OKAY
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
Finished.
Ofuroski said:
Right. I tried that now and it gives me the same.
Sending 'bootloader_a' (8489 KB) OKAY
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
Finished.
Click to expand...
Click to collapse
Then something is probably wrong with your device. But try one last thing, booted into the bootloader try
fastboot flashing unlock_critical
This shouldn't make any difference but who knows. It'll wipe the device too so plan for that.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Then something is probably wrong with your device. But try one last thing, booted into the bootloader try
fastboot flashing unlock_critical
This shouldn't make any difference but who knows. It'll wipe the device too so plan for that.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Wiping doesn't matter since I already wiped when flashing the December update right before the error occurred, but I think that command was for Pixel 2? It tells me
FAILED (remote: 'invalid argument unlock_critical') when I try that command.
I'm trying to figure out why the phone gives no response when trying to determine the locked state. Seems odd that I haven't seen this error message brought up anywhere on these forums before.
Ofuroski said:
Wiping doesn't matter since I already wiped when flashing the December update right before the error occurred, but I think that command was for Pixel 2? It tells me
FAILED (remote: 'invalid argument unlock_critical') when I try that command.
I'm trying to figure out why the phone gives no response when trying to determine the locked state. Seems odd that I haven't seen this error message brought up anywhere on these forums before.
Click to expand...
Click to collapse
I'm betting your eMMC is bad since nothing seems to be able to determine the lock state. When you boot to the bootloader the device state should say locked or unlocked and yours says error. So it's not being read correctly or at all. I haven't seen this problem either with this device but there's always a first. You should be able to RMA the device and that's where I would go from here.
Sent from my [device_name] using XDA-Developers Legacy app
Ofuroski said:
Wiping doesn't matter since I already wiped when flashing the December update right before the error occurred, but I think that command was for Pixel 2? It tells me
FAILED (remote: 'invalid argument unlock_critical') when I try that command. I'm trying to figure out why the phone gives no response when trying to determine the locked state. Seems odd that I haven't seen this error message brought up anywhere on these forums before.
Click to expand...
Click to collapse
Yes, unlock_critical was only needed for the Pixel 2. Run "fastboot getvar all" and post the result. At least the first 30 lines or so. Sounds like you ran factory reset from within system and that is when the trouble started, but how about when you run it (FDR) from recovery mode? ADB commands will only work in recovery mode.
v12xke said:
Yes, unlock_critical was only needed for the Pixel 2. Run "fastboot getvar all" and post the result. At least the first 30 lines or so. Sounds like you ran factory reset from within system and that is when the trouble started, but how about when you run it (FDR) from recovery mode? ADB commands will only work in recovery mode.
Click to expand...
Click to collapse
Thanks for your help and info. Here's what getvar posts.
(bootloader) product:crosshatch
(bootloader) serialno:85HY008F7
(bootloader) variant:MSM USF
(bootloader) max-download-size:0x10000000
(bootloader) slot-suffixes:_a,_b
(bootloader) version-bootloader:b1c1-0.1-5034669
(bootloader) version-baseband:g845-00023-180917-B-5014671
(bootloader) secure-boot:NONE
(bootloader) secure:no
(bootloader) hw-revision:EVT1.1
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) unlocked:error
(bootloader) nos-production:error
(bootloader) off-mode-charge:1
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) battery-voltage:3790
(bootloader) battery-soc-ok:yes
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd:0x2000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc:0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore:0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp:0x80000
Ofuroski said:
Thanks for your help and info. Here's what getvar posts....
Click to expand...
Click to collapse
The notable ones I see are different from mine. Everything else is the same except for the differences between blueline and crosshatch. I'm not a dev and don't know exactly what they mean but there is something wrong with secure-boot. Since you were stock there should be little risk in running the flashing command and try lock and then unlock the bootloader. Generally the rule is once the bl is unlocked you never go back for any reason, but you are dead in the water right now anyway. Hopefully you are in good shape warranty-wise in case you can't recover.
(bootloader) secure-bootRODUCTION
(bootloader) secure:yes
(bootloader) unlocked:yes
(bootloader) nos-production:yes
I have exactly same issue on Pixel5.
Did you find any solution?
Not sure if this helps anyone else, I had my Pixel 3 XL just break.
Bootloader failed to verify/load image. Going into rescue mode didnt work. Fastboot was giving the same No response error
Fastboot command (flash:bootloader_b) failed: 'error getting device locked state No Response'
I tried to flash the bootloader
(env) ➜ platform-tools fastboot flash bootloader bootloader-crosshatch-b1c1-0.3-7065185.img
Sending 'bootloader_b' (8517 KB) OKAY [ 0.310s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state No Response')
and i tried to unlock the bootloader
(env) ➜ platform-tools fastboot flashing unlock
FAILED (remote: 'Error getting device locked state No Response')
fastboot: error: Command failed
So i figured this thing was bricked so i started play around with every command to see if anything would work
(env) ➜ platform-tools fastboot update ~/Downloads/crosshatch-rq2a.210405.006/image-crosshatch-rq2a.210405.006.zip
--------------------------------------------
Bootloader Version...: b1c1-0.3-7241706
Baseband Version.....: g845-00173-210331-B-7249945
Serial Number........: 8BLY10DMG
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.058s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'b1c1-0.3-7241706'.
Update requires 'b1c1-0.3-7065185'.
fastboot: error: requirements not met!
(env) ➜ platform-tools fastboot flashing unlock
FAILED (remote: 'Error getting device locked state No Response')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem fastboot oem
FAILED (remote: 'Invalid oem command fastboot')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem ddrtest
FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem
fastboot: usage: empty oem command
(env) ➜ platform-tools fastboot oem citadel state
FAILED (remote: 'failed to get citadel state No Response')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem citadel reset
OKAY [ 0.190s]
Finished. Total time: 0.190s
(env) ➜ platform-tools fastboot oem citadel state
(bootloader) Citadel state:
(bootloader) Version : 1
(bootloader) Bootloader state: 0
(bootloader) Production state: 1
(bootloader) Number of locks : 4
(bootloader) Lock[0]: 1
(bootloader) Lock[1]: 1
(bootloader) Lock[2]: 1
(bootloader) Lock[3]: 0
OKAY [ 0.151s]
Finished. Total time: 0.151s
(env) ➜ platform-tools fastboot flashing unlock
FAILED (remote: 'flashing unlock is not allowed')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem citadel reset-locks
FAILED (remote: 'failed to reset citadel AVB locks Device Error')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem citadel reset-locks
(env) ➜ platform-tools fastboot reboot
Rebooting OKAY [ 0.080s]
Finished. Total time: 0.080s
I finally got a different screen after
fastboot oem citadel reset
fastboot oem citadel state
fastboot oem citadel reset-locks
fastboot reboot
This gave me an android with a No connection error message and fastboot was no longer showing the device. I then hit power+up vol until it rebooted, hit power+down vol until it rebooted.. and it booted into Android!
hope something here helps someone else, I have no idea what i actually did but
Hi!
I recently unlocked the bootloader of my Motorola G7 Plus. I did everything right and every time I restart shows a warning about the smartphone being unlocked, and I do have the drivers of the phone updated, the adb & fastboot drivers updated and I have tried 4 different cables and 3 USB ports.
So I want to flash Lineage OS but it is showing me some errors when I try to flash the recovery.img lineage.
*It was starting to download to boot but never ended, and I mean 5 hours (25 mb), only showing (sending.....) and FAILED (remote failure)
*So i tried the methods Lineage recommends fastboot boot__a/boot_a/boot_b/boot__b. RecoveryImageName.img
None of them worked
I gave up the idea of trying by Lineage, so I tried with TWRP, didn't install as well. Sometimes just showing (sending....) and stayed there for hours, FAILED (remote failure), but with me trying new commands to fix it started to appear errors about not knowing partitions file sizes, not detecting any partitions and maximum file reached for that partition.
I did try a whole bunch of commands, ways, tutorials but couldn't figure it out.
The phone is perfectly fine, I can´t just flash it
This is my last bit of my code trying
C:\Users\0\Pictures\platform-tools>mfastboot flash recovery recovery.img
(bootloader) max-sparse: not found
sending 'recovery' (23065 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\0\Pictures\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\0\Pictures\platform-tools>adb reboot bootloader
C:\Users\0\Pictures\platform-tools>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (23065 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Users\0\Pictures\platform-tools>mfastboot flash recovery "recovery.img"
(bootloader) max-sparse: not found
sending 'recovery' (23065 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.002s
C:\Users\0\Pictures\platform-tools>fastboot --set-active=_a
Slot _a does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>fastboot --set-active=__a
Slot __a does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>fastboot --set-active='a'
Slot 'a' does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active="a"
(bootloader) slot: not found
fastboot: error: Device does not support slots
C:\Users\0\Pictures\platform-tools>fastboot --set-active="b"
Setting current slot to 'b' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>fastboot --set-active='b'
Slot 'b' does not exist. supported slots are:
a
b
C:\Users\0\Pictures\platform-tools>fastboot --set-active=b
Setting current slot to 'b' FAILED (remote: '')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>mfastboot --set-active=_a
mfastboot: unrecognised option `--set-active=_a'
C:\Users\0\Pictures\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\Users\0\Pictures\platform-tools>mfastboot --set-active=a
mfastboot: unrecognised option `--set-active=a'
Hi there,
flashing twrp is different for different phones
for instance, when i flashed the recovery twrp for my coolpad note 3 lite, i have to press the power key and volume up key but it didn't flash successfully.After six to seven attempts i realised i have to hold down the keys until the whole flashing is completed but the guys in the youtube did it differently and it worked.
maybe why don't you try something of that sort???
Maybe some information and assistance in your device forum Section:
Moto G7 Plus
The Moto G7 Plus is a 6.2" phone with a 1080 x 2270p display. The Snapdragon 636 is paired with 4GB of RAM and 64GB of storage. The main camera is 16MP and the selfie camera is 5MP. The battery has a 3000mAh capacity.
forum.xda-developers.com
You have good skill. You need to find proper steps. Some steps may different for different mobile. Look within forum
-.-
HY anyone testet the DIVESTOS on Xperia XA2?????
https://divestos.org/index.php?page=home
My Mobile Data dont work.....
Does it detect your SIM card? If so adjust your APN.
If not flash the correct firmware for your device.
SkewedZeppelin said:
Does it detect your SIM card? If so adjust your APN.
If not flash the correct firmware for your device.
Click to expand...
Click to collapse
Hello Sir
simcard not detectet.....
can you post a link from correct firmware and flashing instruction .........
Thanks
Any ideas where to ask for support for h4113. Flashing divestOS seems only for h3113, since i get a the following error:
fastboot update divested-19.1-20221210-dos-pioneer-fastboot.zip
--------------------------------------------
Bootloader Version...: 1310-0301_X_Boot_SDM630_LA3.0_P_38
Baseband Version.....: 1311-2918_50.2.A.3.77
Serial Number........: XXX000XXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'H4113'.
Update requires 'sdm660'.
fastboot: error: requirements not met!
Guttergorm said:
Any ideas where to ask for support for h4113. Flashing divestOS seems only for h3113, since i get a the following error:
fastboot update divested-19.1-20221210-dos-pioneer-fastboot.zip
--------------------------------------------
Bootloader Version...: 1310-0301_X_Boot_SDM630_LA3.0_P_38
Baseband Version.....: 1311-2918_50.2.A.3.77
Serial Number........: XXX000XXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'H4113'.
Update requires 'sdm660'.
fastboot: error: requirements not met!
Click to expand...
Click to collapse
this is an issue with packaging for unified builds, just extract the fastboot.zip and `fastboot flash` each file to the appropriately named partition, then continue on the steps documented.
alternateively you may be able to just `fastboot update --force ...`
new Build is up........flashed zip with twrp......all ok works fine
Hello Everybody
I have exactly the same issue:
Bootloader Version...: 1310-0301_X_Boot_SDM630_LA3.0_P_38
Baseband Version.....: 1311-2845_50.2.A.3.77
Serial Number........: CQ30017WZR
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'H3113'.
Update requires 'sdm660'.
fastboot: error: requirements not met!
1/ I tried to with fastboot update --force divested-19.1-20230507-dos-pioneer-fastboot.zip
but I have the same result.
2/I also tryed to flash twrp recovery with this command:
fastboot flash recovery twrp-3.7.0_9-0-pioneer.img
And the result was:
Sending 'recovery' (32464 KB) OKAY [ 1.114s]
Writing 'recovery' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
3/I also tryed to flash one by one files with for exemple:
fastboot flash android-info.txt
and result was:
unknown partition 'android-info.txt'
fastboot: error: cannot determine image filename for 'android-info.txt'
Can you help me please?
Thanks
Ok I reach to install it via the command:
fastboot flash boot twrp-3.7.0_9-0-pioneer.img
after wipe data and sideload the .zip file via
adb sideload divested-19.1-20230507-dos-pioneer.zip
So I didnt use adb sideload copy-partitions-device.zip
DO you think it would be a security problem?
silver-fox-81 said:
So I didnt use adb sideload copy-partitions-device.zip
DO you think it would be a security problem?
Click to expand...
Click to collapse
It is probably fine