I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
rjgonzalez73 said:
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
Click to expand...
Click to collapse
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
rjgonzalez73 said:
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
Click to expand...
Click to collapse
Sorry to revive this thread, but I'm having the same issue and I'm a little desperate.
I'm running a Vista, as are all the computers in my household.
My kindle got screwed up again after a restore from back up. Now it goes like this
a)shows Kindle fire (yellow) 1 second
b)shows fastboot 1 second
c)then screen goes blank, until I switch it off
As I switch it on, repeats a, b & c
The device manger keeps searching & refreshing OMAP4440 drivers every 2 second( with ding sounds)
This happens both with a factory cable as well as the standard usb.
Any one knows how to troubleshoot this?
Bump
OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
looks like your device doesn't have enough power to stay in fastboot. just leave it charging for about an hour even if it doesn't display anything. it should still be charging.
UMM!!
stunts513 said:
OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
1. I tried pluging it in ubuntu-12.04-desktop-i386 live usb, didnt detect the device. Do I have to download some thing before?
2. After a,b,c, the screen goes black but the OMAP4440 keeps refreshing in device manger it only stops when I push the power button for more than 20 seconds. I beleive the KFHD is not switching of but just goes to a black screen.
3. What is a bash script?
OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hey, the description is quite technical for me. Can you write a step by step guide, starting from once i boot up a linus live usb (12.4 ubuntu)?
stunts513 said:
OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I am literally falling asleep right now, I will write it tomorrow after I finish writing my résumé... I will warn you it will be slightly vague because I don't use the newer distributions of Ubuntu and am unfamiliar with the ui. Actually for simplicity I will upload a zip file with the fastboot binary and any files it requires, so I don't have to explain how to install stuff in Ubuntu. Hopefully the nautilus browser is the same. For the record nautilus is basically like Ubuntu version of windows explorer. As long as you can find your home folder and launch a terminal you should be able to follow my vague instructions. Anyways I will write a guide tomorrow since I am literally nodding off.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Your problem is that you are using OMAP drivers instead of fast boot or adb drivers.
Sent from my Amazon Kindle Fire HD using xda app-developers app
It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
If the device IS actually going into fastboot, then it's entirely possible to re-flash the bootloader.
In order to do this, you have to enter the command while the device is unplugged, then plug it in when you see "waiting for device". As soon as fastboot mode is detected, the command will execute and the bootloader will be flashed, but be warned....
While flashing the bootloader happens rather quickly, if for some reason only part of the bootloader is flashed, the device will likely be unrecoverable. I suggest that you make sure the md5sum of the downloaded u-boot-bin checks out, and that you aren't using an extraordinarily slow computer.
Yea at this point his kindle is going to go either way, either way though if he didn't try what he's doing or if he did and it didn't work he'd be sending it into amazon though more than likely and seeing if they'd take it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
I lost you on step 5. Which website? the md5sum that i get is (bb029673d8f186db4dff6d38f4aa28cf) <---Nevermind. I know what website you are talking about.
---------- Post added at 01:49 AM ---------- Previous post was at 01:22 AM ----------
Once I get to number 6 I get this?
[email protected]:~/Kindlefix$ ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
bash: ./fastboot: No such file or directory
And the fastboot file and kfhd7...bin file are inside the folder.
Update.. FIXED
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!
lo pudiste solucionar?
ToPViP said:
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!
Click to expand...
Click to collapse
hola soy latino pero frecuento bastante el foro, antes no opinaba puesto que no hablo ingles , alguno que hable español me podria ayudar? me pasa lo mismo que el joven que inicio el tema, veo que algo hizo para arreglarlo pero yo no entiendo , porfavor ayudenme:crying:
stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
Lol,nice guide mate. I saw the title and just thought,"How the hell does OMAP4 refresh itself?" Anyway,I think that he would be better off installing android-tools-fastboot since he's running Ubuntu.
Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.
stunts513 said:
Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.
Click to expand...
Click to collapse
help me please please
Translation: hi i am latino but quite frequent the forum, not previously thought since I do not speak English , some speak Spanish could help me ? I feel the same as the young man who started the topic , see something done to fix it but I do not understand , please help : crying :
My Spanish is horrible so I ran it through Google.
If it is doing exactly what the original poster is doing rather than showing up only as a omap4boot and not turning on then I recommend using Linux and running "fastboot -i 0x1949 erase boot" once it clears the boot partition it should kick it into fastboot until the boot partition gets re-flashed.
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
SirGoldenTaco said:
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
Click to expand...
Click to collapse
If you want to go back to Android 9, flash the latest RAW
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
SirGoldenTaco said:
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
Click to expand...
Click to collapse
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
MrKioFLow said:
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
Click to expand...
Click to collapse
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
SirGoldenTaco said:
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
Click to expand...
Click to collapse
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
MrKioFLow said:
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
Click to expand...
Click to collapse
You should be really careful about using USB hubs, for anything flashing related or if you are transferring a file without a checksum I would highly recommend going direct to a normal USB port.