i was flashing a rom via ruu then when the error that says flush immediately popped up i typed fastboot oem rebootRUU but it said waiting for device so i disconnected the phone and rebooted into fastboot but i might have rebooted into android i can't remember, now fastboot doesnt work. anyone help ? thanks.
also on the bootloader it says OS-3.62.1700.1 (3.10.502.2) in red letters. its relocked bootloader s-off cid1111111 i wanted to go to stock cause its on gpe 4.4.2 and its still there.
Everything suggests so but would like to get confirmation before I finish my fight.
Phone was reacting weird, apps were closing itself upon opening. I copied important stuff from phone but one folder wouldn't delete. After reboot I get stuck on logo and nothing. Once phone loaded next logo and then error that encryption was interrupted so factory reset is necessary. After reboot keeps hanging on logo. Wouldn't flash any firmware, errors from Sahara. Failed to mount cache, wiping data does nothing. I got into fastboot and unlocked bootloader and even managed to flash a firmware but after reboot same thing, stuck on logo. Further inspection and
fastboot oem device-info
Device unlocked: false
fastboot oem unlock
fastboot oem device-info
Device unlocked: true
fastboot reboot bootloader
fastboot oem device-info
Device unlocked: false
flashing boot.img gives error : FAILED remote: partition table doesn't exist
similar situation to described here : https://forum.xda-developers.com/go...tboot-oem-unlock-goes-to-lock-reboot-t2903581
so looks like nothing can be done but please confirm because if there is something I am open for ideas
Hello recently an automatic firmware update happened on my phone , after the update has finished my phone is now stucked on the EMUI after booting up. My phone has bootloader unlocked
update:
i flashed the stock rom using adb & fastboot
i flashed these
ramdisk.img
kernel.img
recovery-ramdis.img
system.img
wiped / format the data and the cache partition
Was all succcess but now im getting stucked on the ""your device has been unlocked and can't be trusted" screen
pls send help
upppppppp pla help
im still getting stucked please help
up i need help please
bumpy uppp
up please help
then try to go to erecovery by pressing volume up while the your device has been unlocked and can't be trusted
i can help if u like remotly
Did you find a solution
anonpurged09 said:
update:
i flashed the stock rom using adb & fastboot
i flashed these
ramdisk.img
kernel.img
recovery-ramdis.img
system.img
wiped / format the data and the cache partition
Was all succcess but now im getting stucked on the ""your device has been unlocked and can't be trusted" screen
pls send help
Click to expand...
Click to collapse
install minimal adb and fastboot tool (for quickness) on window's computer
Put your phone back into fastboot mode (insert usb with mobile switched off whilst holding the volume up button and plugged into your laptop)
Check your bootloader's status with this command fastboot oem device-info And then go back and lock your bootloader again using the fastboot oem lock command then restart your phone in recovery mode and factory reset it .....you may have to put your phone's serial number at the end off fastboot oem lock ************* you can get it using the fastboot devices command,just copy and paste serial " at end of your command then use the fastboot oem device-info command again to check that you have been successful.....Failing that you might have to re-flash and try a fresh download of firmware stock rom from a different source as it might be corrupted
Good luck.
Hello,
I had mate 10 lite with an unlocked bootloader. The phone hung up on the information "Your device has been unlocked and ..." but Fastboot worked fine, then I installed TWRP and some custom ROM and everything worked fine, but (one more thing) I wanted to have the stock ROM, so then block the phone with adb " fastboot oem relock xxxxxxxxx ”and now the phone is bricked, hang on the huawei logo and nothing else. There are no Fastboot (USB and vol- not working), please help
in this case if no any fastboot or recovery u can restore only by test point, thats mean u need open phone
Hello I have a xiaomi mi mix 3 5g that I never removed the bootloader on, as it had the stock EU firmware on. It has recently been updated to to MIUI12. however the battery went low and went all weird and now constantly reboots.
I can get to fastboot by holding down the power and volume down, I have also tried a wipe device by holding down the power and up. From what I have read I i cant re-install fastboot firmware without and unlocked bootloader. (can someone confirm that this is correct) as its not clear.
***I have now confirmed this I have tried to install firmware using xiaomi flash tool and fails with the following
"Error: erasing boot Failed remote erase is not allowed in locked state. so this confirms it.
Also I cant unlock the bootloader as it wont boot. Does any body have any idea of what I can do with this phone? any help would be apprciated
thanks
The error I get when trying the mi unlock tool
Couldn't Unlock
Please add your account in MIUI;s Settings > Developer options > Mi Unlock Status
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
jwoegerbauer said:
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
Click to expand...
Click to collapse
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
sivhead said:
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
Click to expand...
Click to collapse
How to flash firmware to any Xiaomi smartphone is described here.
jwoegerbauer said:
How to flash firmware to any Xiaomi smartphone is described ["]here[/url].
Click to expand...
Click to collapse
I have already tried that method When I flash using the flash tool I get the error "Error: erasing boot Failed remote erase is not allowed in locked state" My bootloader is not unlocked is this method supposed to be work with a locked bootloader. Bit of chicken and egg situation. I cant unlock the bootloader as I cant boot the device and I cant reflash software as I don't have an unlocked bootloader.
AFAIK you always are allowed to flash an original firmware image without unlocking the phone's bootloader.
If you can access the device by means of ADB try to flash the Stock ROM via ADB:
Code:
adb devices
adb reboot sideload
adb sideload <LOCATION_OF_STOCK_ROM_ZIP_FILE_HERE>
C:\adb>adb devices
List of devices attached
f625af1 sideload
C:\adb>adb sideload miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip
loading: 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip'
* cannot read 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip' *
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
jwoegerbauer said:
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
Click to expand...
Click to collapse
tried that same error cannot read rom.zip
sivhead said:
tried that same error cannot read rom.zip
Click to expand...
Click to collapse
C:\adb>adb sideload c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip
loading: 'c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip'* failed to read command: No error
I also thought its worth mentioning that I have never registered the device with mi connect
Also enable usb debugging is not enabled.
aqnd THe bootloader is locked .
Man I wish I would have unlocked the bootloader when I got it and put a custom rom on. then I wouldnt be in this situation. how ironic that I wanted to keep it stock
so I am at a loose end