Related
sorry about other thread..... titled it wrong. anyway, i tried to partition my kf but it failed.... how to you issue fastboot oem format command?
n00byn00bface said:
sorry about other thread..... titled it wrong. anyway, i tried to partition my kf but it failed.... how to you issue fastboot oem format command?
Click to expand...
Click to collapse
Type "fastboot getvar product" in a command prompt wherever your fastboot is, plug in the KF and once it's connected, type "fastboot oem format"...
EDIT: If you're coming from CWMR, you may want to make sure you don't have a troublesome emmc chip and there hasn't been permanent damage to it...
EDIT 2: Why are you posting this question over and over around?
"No Sim Card detected" (due to TWRP backup restore) fix through fastboot commands?
Yesterday I had to restore my phone to a previous ROM (stock MM) from RR 5.8.5 Nightly. This was due to my working from home and needing to generate an RSA soft token, which is set up on an app on the backup, yadda yadda... Anyway, my restore worked fine, and I was able to generate my key and work from home.
However... when I went to use my phone, I noticed that the SIM card was no longer detected. I tried restoring my RR rom, and it too would not detect my Sim card.
In my attempts to find a fix, and then my attempt to restore the stock firmware and bootloader (that seems to be the only fix), I managed to royally hose my phone by attempting to flash the Full Stock LL ROM, which failed and must have overwritten the bootloader and recovery partitions. Trying to turn the phone on resulted in a vibration, but only a black screen. I was able to unbrick the phone using various guides I scrounged up and utilizing XFSTK and IntelSOC drivers, which must be installed when Windows 10 is booted with the special option to install unsigned drivers enabled (hold shift when you click restart, then option 7). I can post what I went through when I get home to my files and stuff if anyone requests it. Asus Flash Tool refused to flash the raw firmware (wrong format my ass), so I had to manually run the fastboot options. Everything was hunky dory after this.
Every fix for the SIM card issue pointed to reverting to stock firmware, which is what I did. However, I'm thinking there must be some key partition that I flashed in fastboot that revived the SIM. I performed the below commands from this thread . Does anyone see a command that screams "I'm fixing sim card issues"?
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Click to expand...
Click to collapse
If we can get the fix for an undetected SIM card after TWRP backup down to a few (or single) fastboot command, it'd be a nice convenience for us all.
Alternatively, does anyone know of a proper way to restore TWRP backups without losing SIM card detection?
UPDATE SECTION
I had found this site while searching for a solution yesterday, and it has the following fastboot commands for fixing the sim issue:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
So in this case, the modem partition is being erased. But I don't see anything in the unbricking fastboot commands that erases the modem partition. Am I just missing it? I could see my IMEI in Sim Slot 1, so maybe it wasn't a modem partition issue.
-------------------------------------------------------------------------------------------------------------------
Found this thread (How did I miss it before?): https://forum.xda-developers.com/zenfone2/general/guide-how-to-zenfone-t3173314
The minimal boot options he listed are all in TWRP 3.1.1-0. The only thing I was missing before was config... I'm thinking that might be the key to preventing this. Next step is to determine if there's a config partition, and what happens when you do stuff to it (and ultimately how to restore the partition when you don't have a TWRP backup on hand).
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
toxinburn said:
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
Click to expand...
Click to collapse
I am gonna check one thing I had it all working another method before but after installing something thru magisk it soft bricked I think it was vanced youtube maybe also cant seem to find a way to get vipre to work sadly.
Question
Does this method bypass the screen lock password on the phone? I have this phone that is locked with a passcode, so I can't easily get it into developer mode. Sorry, I'm a total newbie to this but am trying to learn. Thanks in advance!
A tip for linux users. If you are getting "< waiting for any device >" after the "fastboot oem get_unlock_data". Ctrl-c to exit the command. Su to root and then "fastboot oem get_unlock_data".
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Hyoretsu said:
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Click to expand...
Click to collapse
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Linux-Lord said:
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
The thing is, "stopped working" literally, it doesn't have out of service, phone number, no signal, not even the "emergency calls only", heck I can't even find my IMEI in settings nor *#0606#, I think that's what's causing the problem. This SIM also came from that Custom ROM device (originally inserted there, but bought as a standalone data plan)
Linux-Lord said:
and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
If you're talking about how it showed up like that on the G7 Play it used to work just fine in there, and no, that's not the original phone, it's just a phone I used to test if my SIM was still working
Linux-Lord said:
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
Click to expand...
Click to collapse
In this phone, G7 Power, it doesn't even recognize a card is in the tray anymore (unlike the G7 Play which at least knows there's one and G5+Custom ROM, in which it works)
Linux-Lord said:
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Click to expand...
Click to collapse
Not that it's gonna help much but OI (Brazil), and if that's on Motorola support page my G7 Power is main phone already.
Is the force encrypt disable necessary? And what does it do?
So, I have successfully rooted my Moto G7 Power by using the method above, but i tried not doing the "format data" and fortunately, I have rooted my phone. For the 1st attempt, I kinda soft-bricked my device by doing the steps briefly, my phone would always bootloop back to recovery mode, but after not doing the "format data" step, it led to a success. So for anyone who are currently experiencing bootloop, flash the stock firmware to your phone and root it again by using the method above but don't do the "format data" step. (flashing the stock firmware would not re-lock the bootloader, so you can try to root your phone again easily.)
error
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
---------- Post added at 08:07 AM ---------- Previous post was at 07:49 AM ----------
gladiatorbong said:
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Click to expand...
Click to collapse
same here
brokenlocked22 said:
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
Click to expand...
Click to collapse
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Hyoretsu said:
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Click to expand...
Click to collapse
same thing as always.. no matter what lol
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
If it's same thing as always then you're still using "adb push magisk adb push Magisk-v20.1(20100).zip /tmp/". There's no "but I'm not", if it's indeed the same error as before you're messing up on the syntax. Make sure you've put Magisk inside Minimal ADB folder, rename it to magisk.zip and run "adb push magisk.zip /tmp/"
why is magisk pushed to tmp and not to internal storage . Why not just push magisk to internal sotrage and just install that way through twrp or that wont work. just wondering.
Anyone tried this on XT1955-4?
dirtyscout said:
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
IM a bit confused should I flash a fresh installed firmware first right after i unlock the boot loader?
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
[Redacted]
Excellent guide, rooted my Moto G7 from Metro PCS.
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
I LOVE IT!!! :good:
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed
more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler.
If you have a Chinese version (K40s)and you have locked the bootloader on a rom other than Chinese, it comes from that.
bvyral said:
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Click to expand...
Click to collapse
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
System23 said:
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
Click to expand...
Click to collapse
What do you mean( only look 4 another Firmware)?
NOSS8 said:
What do you mean( only look 4 another Firmware)?
Click to expand...
Click to collapse
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
System23 said:
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
Click to expand...
Click to collapse
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
System23 said:
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
Click to expand...
Click to collapse
But i got the firmware from here..i choose poco f4 global fastboot type
NOSS8 said:
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
Click to expand...
Click to collapse
Yea..the bootloader is now locked..what should i do?..and can it be done?..
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
Do you have a Poco F4 or a K40S?
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
If you need to leave Fastboot mode, just press and keep a combination of the Power button + the Volume Down for about 10 seconds.
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
hope one of the Options will Work!!
Click to expand...
Click to collapse
You cannot use Mi Flash with a locked bootloader.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
not working...error:FAILED (remote: Erase is not allowed in Lock State)
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Boot Recovery via fastboot
fastboot boot xxx/Images/recovery.img
or
Reboot Recovery
fastboot reboot recovery
or
Flash Boot/Recovery
fastboot flash boot xxx/Images/boot.img
fastboot flash recovery xxx/Images/recovery.img
fastboot reboot
when this not working you can use EDL-Mode!!!
Poco F4 test Point Reboot 9008 EDL - ROM-Provider
Poco F4 test point is typically a set of pins on the device's circuit board that can be shorted together in order to put the device into edl mod
romprovider.com
Than you can Flash it with QPST or QFiL Tool from Qualcomm!!! but i must look when i at home if the fastboot Firmware includes all needed Files!!! rawprogrammer0.xml patch0.xml firehosexxxx.mbn
System23 said:
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Click to expand...
Click to collapse
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Poco F4 (Munch) Firmware Flash File (Stock ROM) - ROM-Provider
Download Poco F4 Firmware Flash File stock ROM, here we share latest firmware for Xiaomi Poco F4 with flash tool & usb driver
www.google.de
with MiFlash in EDL-Mode and the EDL-Firmware GLO, its like this Article a working Solution!! and i dont know if fastboot reboot edl with special edl fastboot work, and I dont know if it can Start with ButtonsCombo!!! adb reboot edl is not availible wile stuck at Fastboot-Mode!! iam only give ideas to test them out, in variants they i know!! Iam Testing my variants out to find a way that works!!!
NOSS8 said:
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Click to expand...
Click to collapse
give me more Input, iam intressted to read more!!!
System23 said:
give me more Input, iam intressted to read more!!!
Click to expand...
Click to collapse
This is not the subject of the thread. (do some research).
If it is impossible to enter recovery or fastboot mode and if it is not a HW problem, the phone is in EDL Mode.
It will not appear on the PC unless you install the Qualcomm drivers and will be detected by Miflash (in Fastboot mode, no need to log in) on a com port (login mandatory), but you will not have permission to flash (requires a special account).
This permission is not needed on very old devices.
Until the OP has answered my questions, I could not provide him with a possible solution.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
thanks, after managing to unlock the phone just by moving it to local disk c, after some googling n youtubing, and i tried ur method again ,editing some flash_all bat.((
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || exit /B 1))
and run it....it works.. i sincerely thanks you..