[Q] [q] help:problem updating/fastbooting toshiba folio 100 - Folio 100 General

Hi,
l'm really need HELP desperately to update my folio 100 from factory installed 2.2.15 version to the latest jellybean. l have rooted my device using Superone-click, installed the necassery andriod SDK/adb /PdaNet drivers, tested that the device is rooted using Terminal emulator. But l cant update the recovery or install a new ROM, have tried everything l learnt from this site including install update.zip from SD card , fastboot recovery to install custom recovery,everything just won't work apart from the device being rooted. Here is the error l get after l tried to fastboot a new recovery image from my PC to my tablet : "erase recovery failed(write command failed)too many links))", but suprisingly l can fastboot reboot the tablet from my pc. :THIS IS THE ERROR FROM MY TABLET DURING FASTBOOT mode: Failed to process command getvarartition-type recovery :recovery error(0x2) .[/COL PLEASE HELP, Been at it all week,l'm primarily a windows user.

Same problem here!

Already solved. The problem was that the fastboot didn't detect my tablet. When I do fastboot devices, it replys: ? fastboot.
With adb everything is OK!
On fastboot commands erase, flash etc, nothing was working. Except reboot.
The only way was: fastboot boot recovery-cwm-CM10-A3.img [/B](Have to be on your Pc fastboot directory) and then install everything from SD card.
Note: I can't intall recovery yet, give me an error 7 or something. Everything else is fine, and the rom is realy awsome Thanks!

rastonb said:
Already solved. The problem was that the fastboot didn't detect my tablet. When I do fastboot devices, it replys: ? fastboot.
With adb everything is OK!
On fastboot commands erase, flash etc, nothing was working. Except reboot.
The only way was: fastboot boot recovery-cwm-CM10-A3.img [/B](Have to be on your Pc fastboot directory) and then install everything from SD card.
Note: I can't intall recovery yet, give me an error 7 or something. Everything else is fine, and the rom is realy awsome Thanks!
Click to expand...
Click to collapse
Same problem here but i had already recovery-cwm-6.0.1.4 and A2 on my folio. So I installed until A5 with this recovery without problems.

RE:Q] [q] help:problem updating/fastbooting toshiba folio 100
acilo said:
Same problem here but i had already recovery-cwm-6.0.1.4 and A2 on my folio. So I installed until A5 with this recovery without problems.
Click to expand...
Click to collapse
How were u able to install recovery-cwm-6.0.1.4 and A2 on your toshiba folio 100

TEEBOYZ said:
How were u able to install recovery-cwm-6.0.1.4 and A2 on your toshiba folio 100
Click to expand...
Click to collapse
I did it how it is discribed for "Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012" in this post: http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9.
My former FW was foliomod1.4.

rastonb said:
Already solved. The problem was that the fastboot didn't detect my tablet. When I do fastboot devices, it replys: ? fastboot.
With adb everything is OK!
On fastboot commands erase, flash etc, nothing was working. Except reboot.
The only way was: fastboot boot recovery-cwm-CM10-A3.img [/B](Have to be on your Pc fastboot directory) and then install everything from SD card.
Note: I can't install recovery yet, give me an error 7 or something. Everything else is fine, and the rom is realy awsome Thanks!
Click to expand...
Click to collapse
l did as you suggested, was able to fasboot into recovery, installed formatsd, cm-9.0.0-RC0-2012.03.04-betelgeuse-KANG-signed and goggle apps, wiped cache/data and reboooted, but the new image won't boot up, will like to know what steps you took,/how you were able to successfully load the image and which image did you use...THANKS

Related

assert failed: write_raw_image("/cache/boot.img", "linux")

I had TnT 0.2 installed when i got message internal storage damaged so i boot to clockwork and try to format and wipe device. then go back to FolioMod but when trying to install it installs system then it try to install boot.img i get error message:
assert failed: write_raw_image("/cache/boot.img", "linux")
E:Error in /sdcard/FolioMod.zip
(Status 7)
Installation aborted. Then i read someone else had the same issue onetime and his device had booted anyways and he had managed to fix it but it didnt say how?
I dont know these things but i was thinking maybe i could fastboot boot.img and that would work. But i really dont know these things well enough, im just used to follow guides, so i really dont know the right procedure. Or maybe theres another answer, anyways i need help. Some info my device boots in to recovery and it reads my external sdcard. Thankfull for help, i want my Folio
Hi, it was me who had the same problem.
Try "LOST or Destroyed partitions - METHOD 2 - ADB USB" on http://bb2k.org/folio100wiki/index.php/FolioMod_Issues
Loupák said:
Hi, it was me who had the same problem.
Try "LOST or Destroyed partitions - METHOD 2 - ADB USB" on http://bb2k.org/folio100wiki/index.php/FolioMod_Issues
Click to expand...
Click to collapse
Thank you for answering. but i dont see how i can connect to adb. I was thinking maybe i can flash a rom from clockwork as it installs system and if i could fastboot boot.img to get it to boot. Or if i can flash stock recovery so I could go by Method 1. But the links are broken for the partion map. Please if anybody has any ideas or knows a way. If not I was thinking of fastbooting stock recovery and send it in to toshiba and just say its broken.
Anyone? Problem not solved. If anyone could please help me or guide me in the right direction
It's simple
Put a boot.img on your android files (computer)
Launch Fastboot on command DOS
Fastboot flash linux boot.img
If this don't work
Fastboot erase cache
Fastboot erase system
Fastboot erase userdata
And try again and launch recovery on your Folio to install system/cache partition etc
Sinate said:
It's simple
Put a boot.img on your android files (computer)
Launch Fastboot on command DOS
Fastboot flash linux boot.img
If this don't work
Fastboot erase cache
Fastboot erase system
Fastboot erase userdata
And try again and launch recovery on your Folio to install system/cache partition etc
Click to expand...
Click to collapse
Thank you sounds good. Do i need a special fastboot? Because the with the one that comes with SDK i seem to have some problem. I put my Folio in fastboot, i insert mini usb, computer recognizes, i update folio driver in device manager to the one we use for ADB(Bootloader). And all goes well but when i open comman window and type fastboot devices i get:
fastboot devices
? fastboot
Then i rememberd something , when instaling fastboot for DesireHD on my other computer i had to download another fastboot from Modaco for it to work.
Gratefull for help if anyone recognizes this when setting up fastboot or knows what im doing wrong.
Come on, someone. Still not fixed. Cant get fastboot to work, i have fastboot setup for Nexus S and always had it setup for my phones but i dont get this, why doesnt it work?
PROBLEM SOLVED

How to solve Magic Value Mismatch. Solution Here!

Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilà... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method

My OPX cannot be recognized by windows 10.HELP

Hello friends,
I have an OPX and I did some mistakes with it during my attemp to update it to the latest Oxygen 3.1.3.
I had stock rooted 2.1.2 Oxygen OS with Kingroot and TWRP installed. I downloaded the zip of the ROM
for 3.1.3 from Oneplus and tried to flash it. It came up an error so I wiped system cache and data and tried again
but the same errors came up. Then I tried to flash the stock recovery .img file from TWRP to get the stock recovery
and try to flash the ROM from there. When I attempted to flash the stock recovery it asked me about the partition
I wanted to install it and I chose recovery.Installation seemed successfull and I rebooted to recovery.After that I had
no recovery and no system to boot.When I try to boot to recovery I only get the oneplus logo. When I try to boot to
system I get oneplus logo and "Powered by android" at the bottom. Fastboot mode seems ok. So I thought i could flash
everything back with adb BUT no tool or program recognizes correctly in any mode.In device manager of windows 10
the device is listed under "Kedacom Usb device" section with name "Android Bootloader Interface".
Please Help me.
zafiris said:
Hello friends,
I have an OPX and I did some mistakes with it during my attemp to update it to the latest Oxygen 3.1.3.
I had stock rooted 2.1.2 Oxygen OS with Kingroot and TWRP installed. I downloaded the zip of the ROM
for 3.1.3 from Oneplus and tried to flash it. It came up an error so I wiped system cache and data and tried again
but the same errors came up. Then I tried to flash the stock recovery .img file from TWRP to get the stock recovery
and try to flash the ROM from there. When I attempted to flash the stock recovery it asked me about the partition
I wanted to install it and I chose recovery.Installation seemed successfull and I rebooted to recovery.After that I had
no recovery and no system to boot.When I try to boot to recovery I only get the oneplus logo. When I try to boot to
system I get oneplus logo and "Powered by android" at the bottom. Fastboot mode seems ok. So I thought i could flash
everything back with adb BUT no tool or program recognizes correctly in any mode.In device manager of windows 10
the device is listed under "Kedacom Usb device" section with name "Android Bootloader Interface".
Please Help me.
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
cva_kabil said:
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
Click to expand...
Click to collapse
I have already tried to do this guide. Windows says the best drivers are already installed for this device and will not install the qualcom ones. Also the program just waits for a device to be connected to start the process of unbricking.Thanks for answering
zafiris said:
I have already tried to do this guide. Windows says the best drivers are already installed for this device and will not install the qualcom ones. Also the program just waits for a device to be connected to start the process of unbricking.Thanks for answering
Click to expand...
Click to collapse
But still u can acess fastboot right? Without any problem?
cva_kabil said:
But still u can acess fastboot right? Without any problem?
Click to expand...
Click to collapse
I think so, yes. When I enter fastboot mode there is the oneplus logo and "fastboot mode" written under it.
zafiris said:
I think so, yes. When I enter fastboot mode there is the oneplus logo and "fastboot mode" written under it.
Click to expand...
Click to collapse
Yes it is fastboot. now connect ur mobile to pc and type "fastboot devices" in adb cmd screen.. if it shows your device info,then u can flash stock recovery and make a fresh start.
cva_kabil said:
Yes it is fastboot. now connect ur mobile to pc and type "fastboot devices" in adb cmd screen.. if it shows your device info,then u can flash stock recovery and make a fresh start.
Click to expand...
Click to collapse
Yes i know. Whenever I type fastboot devices nothing happens. No device gets listed.
I had the same problem, but the Guide to Unbrick worked well.
Now, I cannot flash anything, because Fastboot doesn't recognize my phone. I'm stuck in stock.
cva_kabil said:
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
Click to expand...
Click to collapse
thank you very much this guide finally worked!! It was my mistake.I was booting first on fastboot mode and then plugging in the usb cable
whereas the guide says to keep pressing volume up and then plug it in which is was made it work!
zafiris said:
thank you very much this guide finally worked!! It was my mistake.I was booting first on fastboot mode and then plugging in the usb cable
whereas the guide says to keep pressing volume up and then plug it in which is was made it work!
Click to expand...
Click to collapse
Glad u did ?

TWRP no OS / mount problem

Hi guys
Can't install any OS (tried via ADB commands and flashing custom roms via TWRP).
Whatever I try, it just boots to TWRP.
ADB commands do work because I managed to install TWRP 3.0 and 3.1 for the Moto Z Griffin
Bootloader is unlocked
This device was working fine on Stock Noughat (installed via ADB) and AOKP (installed via TWRP).
Problems began when the camera "failed to start" and in my frustration, I wiped everything via TWRP including system, so now I have no OS.
Not sure why I can't get anything to install.
reflash stock firmware
Any idea what method I should use?
forcedv said:
Any idea what method I should use?
Click to expand...
Click to collapse
Fastboot or RDSlite. Flashing rom only won't help.
Tried this but it didn't work... Just boots to TWRP again.
What am a doing wrong?
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
forcedv said:
Tried this but it didn't work... Just boots to TWRP again.
What am a doing wrong?
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Click to expand...
Click to collapse
There's no stock recovery flash command on the list in the link. If you've got full firmware you need to execute this command as well:
Fastboot flash recovery recovery.img
Thank you so much, that fixed this problem.

DEEP TROUBLE! Please help.....

I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
maybe the bootloader got locked check otherwise erase and flash the whole rom using fastboot mi flash tool
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
asifzbaig said:
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
Click to expand...
Click to collapse
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Than it seems like yoir bootloader is locked.
Try using Xiaomi's Unlock Tool again, beware, it will wipe all of yoir internal storage as well.
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try edl mode to flash the full file and beware of anti rollback
karthik03 said:
Try edl mode to flash the full file and beware of anti rollback
Click to expand...
Click to collapse
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Doesn't try the fastboot flash recovery recovery.img, try fastboot boot recovery.img ,that can help
mjskraju said:
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
Click to expand...
Click to collapse
Use fastboot to edl it is present on xda or try shorting of pins
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Have you tried different PC? Mine works on Intel and have same error code on AMD.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
tnsmani said:
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
Click to expand...
Click to collapse
Seems like ryzen is the problem brother! I used another pc as i had no other options left

Categories

Resources