hi devs
i flashed accidentially Chinese recovery rom on my whyred now i m unable to switch from Chinese to global version as i tried every method fastboot,recovery,qfil,mi flash and edl mode i mean every possible way but all in vain as every method ended with error and my fastboot command is locked.
so what can i do please suggest me
it's Chinese miui 11
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
aliasgertaj said:
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
Click to expand...
Click to collapse
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
SubwayChamp said:
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
Click to expand...
Click to collapse
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
aliasgertaj said:
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
Click to expand...
Click to collapse
Fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on Developer section, i.e. USB debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
subwaychamp said:
fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on developer section, i.e. Usb debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
Click to expand...
Click to collapse
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
aliasgertaj said:
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
Click to expand...
Click to collapse
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
SubwayChamp said:
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
Click to expand...
Click to collapse
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
drnightshadow said:
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
Click to expand...
Click to collapse
thanks for response bro
i did it under developer option and trusted my computer connection also and install adb fastboot devices many time changed cable and port but nothing happen. i tried fastboot files of china stable rom but it also doesn't worked
aliasgertaj said:
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
Click to expand...
Click to collapse
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
SubwayChamp said:
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
Click to expand...
Click to collapse
i m frustrated now tried all the thing tried official flash tool official build but even official build by miflash official latest tool unable to flash image
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
aliasgertaj said:
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
Click to expand...
Click to collapse
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
drnightshadow said:
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
Click to expand...
Click to collapse
ok bro i will try today with another pc and update you
aliasgertaj said:
ok bro i will try today with another pc and update you
Click to expand...
Click to collapse
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
aliasgertaj said:
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
Click to expand...
Click to collapse
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
drnightshadow said:
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
Click to expand...
Click to collapse
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
aliasgertaj said:
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
Click to expand...
Click to collapse
TWRP can't bypass encryption, when you have no access to read data (0mb) then you have to format it, to avoid that is always recommended use OrangeFox, just for future reference, if you understand that you can flash OrangeFox through TWRP for better experience.
Also you can use this tool to help you to automate some stuff https://github.com/Szaki/XiaomiADBFastbootTools
Related
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?
ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5
hello there, I'm currently using one plus 7 T, I don't know why , but after updating the last software update my device stuck in Boot loop, i can't able to turn it on, The boot reason says that : Init_user0_Failed . Unable to parse kernel log.Could you please help me to get out from this issue. As i'm outstation from the city, so i can't able to reach the service center. I need my data so i'm trusting you that you guys will sort out the issue, Thank you so much for reading this.
"fastboot set_active other" to switch slot
I'm facing the same problem. Please find a workable solution asap. I'll thank endlessly.
HueyT said:
"fastboot set_active other" to switch slot
Click to expand...
Click to collapse
How and where do I do this?
kiranlalge said:
How and where do I do this?
Click to expand...
Click to collapse
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
HueyT said:
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
Click to expand...
Click to collapse
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
kiranlalge said:
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
Click to expand...
Click to collapse
Plug phone into windows laptop with adb installed on laptop:
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Zesotar said:
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Click to expand...
Click to collapse
15 min adb fastboot drivers, OnePlus USB drivers, Qualcomm USB 9008 drivers (msmtool)
ashuetrx said:
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Click to expand...
Click to collapse
Enable "USB debugging" in Dev.Options, Boot into fastboot mode on phone, type "fastboot devices" and it should give you a code--then your phone is ready for fastboot flashing files
Tried in another computer with Windows 10. It returns: "Slot change is not allowed in Lock State"
I get the a code with the fastboot devices, so it seems the phone is ready.
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Zesotar said:
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Click to expand...
Click to collapse
how exactly did you do it with MSM tool?
cromedo7 said:
how exactly did you do it with MSM tool?
Click to expand...
Click to collapse
5 seconds with Google.
Fastboot method is much easier and without data loss.
Download
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Reboot to fastboot mode
Start minimal ADB and fastboot
Type: fastboot devices
If you see device and something like that:1S67gz everything's ok.
Now type: fastboot set_active other
Type reboot.
Done