After installing pixel experience rom on my RN 4 I wanted to go back to MIUI as several apps such as BHIM, Google Pay could not be used on a device with unlocked bootloader. While doing so I somehow bricked my device as I locked the bootloader by mistake. Now it only goes it fastboot mode with [power+ vol down]. A regular power button press brings mi logo but shuts down.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.069s
I had TWRP installed on the device earlier and now I am just unable to get anything installed. Is there anyway to get my device back to life?
Please help.
Have you tried Flash official rom dev below 8 version via flash tool to unlock it again?
harige said:
After installing pixel experience rom on my RN 4 I wanted to go back to MIUI as several apps such as BHIM, Google Pay could not be used on a device with unlocked bootloader. While doing so I somehow bricked my device as I locked the bootloader by mistake. Now it only goes it fastboot mode with [power+ vol down]. A regular power button press brings mi logo but shuts down.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.069s
I had TWRP installed on the device earlier and now I am just unable to get anything installed. Is there anyway to get my device back to life?
Please help.
Click to expand...
Click to collapse
Don't Panic
Just Download Mi Flash Tool and Download Redmi note 4x rom in that connect to pc your mobile in bootloader mode and then click on Lock and Flash Rom
Your phone will be fine
See this if you don't understand
https://m.youtube.com/watch?v=o0AFJlbJXac
tekno125 said:
Have you tried Flash official rom dev below 8 version via flash tool to unlock it again?
Click to expand...
Click to collapse
Yes, I have been flashing offcial ROMs only have tried MIUI 10 and 9 on both Stable and Beta. But the problem is the flashing completes in 1 second and it says Success. But it isn't. Please note that the last time when the phone was working it didn't have MIUI but was on PixelExperience custom ROM ( Android P). Also the TWRP was installed. After which I ended up locking the bootloader.
notoriouslion said:
Don't Panic
Just Download Mi Flash Tool and Download Redmi note 4x rom in that connect to pc your mobile in bootloader mode and then click on Lock and Flash Rom
Your phone will be fine
See this if you don't understand
https://m.youtube.com/watch?v=o0AFJlbJXac
Click to expand...
Click to collapse
Thank you.
I have tried that several times but doesn't help. Flashing completes in 1 sec. See attached.
Tried MIUI 10 and 9 on both Stable and Beta each time flashing still completes in 1 second and it says Success. But it isn't. Please note that the last time when the phone was working it didn't have MIUI but was on PixelExperience custom ROM ( Android P). Also the TWRP was installed. After which I ended up locking the bootloader.
See image here - https://i.postimg.cc/fLf88bnq/Untitled.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
harige said:
Thank you.
I have tried that several times but doesn't help. Flashing completes in 1 sec. See attached.
Tried MIUI 10 and 9 on both Stable and Beta each time flashing still completes in 1 second and it says Success. But it isn't. Please note that the last time when the phone was working it didn't have MIUI but was on PixelExperience custom ROM ( Android P). Also the TWRP was installed. After which I ended up locking the bootloader.
See image here - https://i.postimg.cc/fLf88bnq/Untitled.png
Click to expand...
Click to collapse
Select option Clean all and lock then flash rom
notoriouslion said:
Select option Clean all and lock then flash rom
Click to expand...
Click to collapse
I have tried all 3 options also, just that didnt want to attach multiple screenshots. No luck.
Do you have any other suggestion?
Thank you
harige said:
I have tried all 3 options also, just that didnt want to attach multiple screenshots. No luck.
Do you have any other suggestion?
Thank you
Click to expand...
Click to collapse
That is the last option as you've locked your bootloader
Strange that miflash tool isn't working for you try searching YouTube videos on flashing stock rom with locked bootloader
I encountered same problem as well months ago
notoriouslion said:
That is the last option as you've locked your bootloader
Strange that miflash tool isn't working for you try searching YouTube videos on flashing stock rom with locked bootloader
I encountered same problem as well months ago
Click to expand...
Click to collapse
Took it to another authorised service centre today, explained the exact problem. In one hour they fixed it and didn't even charge me for that, now I I'm replying using my lovely RN4. The tech said he was able to unlock the bootloader and flash MIUI 10. My problem is solved.??
Related
[SORTED OUT]
By fastboot gives the following error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and rsd lite
Does anyone know how to fix this error?
Looks like you forgot unblock your bootloader.
When I try to unlock the bootloader of this error
Can you solve this error with some command? Because the phone does not turn on.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.017s]
finished. total time: 0.019s
rodrigofvl said:
When I try to unlock the bootloader of this error
Can you solve this error with some command? Because the phone does not turn on.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.017s]
finished. total time: 0.019s
Click to expand...
Click to collapse
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Defaultnickname said:
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Click to expand...
Click to collapse
this flashing_locked
Can you boot into recovery? Try factory reset through recovery. If there a bootloop, flash recovery, via
Fastboot flash recovery.img
Should work with locked bt and stock recovery.
Defaultnickname said:
Can you boot into recovery? Try factory reset through recovery. If there a bootloop, flash recovery, via
Fastboot flash recovery.img
Should work with locked bt and stock recovery.
Click to expand...
Click to collapse
rodrigofvl said:
Click to expand...
Click to collapse
Look at this thread:
https://forum.xda-developers.com/2015-moto-g/help/updated-moto-3-2015-stuck-bootloop-to-t3485191
did not work
SOLUTION FOR THE PROBLEM
Failure to install rom Moto Z XT1650-05 Sheridan Chinese.
https://forum.xda-developers.com/mo...-xt1650-05-t3695286/post74498676#post74498676
As I did not get able to install another rom or recover the one that was installed because of the blocked bootloader and the OEM lock and without TWRP, I was able to install by the recovery in update by the ADB and installed a modified rom to AOSP and the cellphone called, more by account of some bugs I used the fastboot boot twrp.img thread and I ran the TWRP without installing and changed to the lineageOS and installed GApps. I do not intend to use this rom for much longer until I figure out how to unlock OEM by the developer menu I'm going to stick with it I hope it helps someone. Thank you to everyone who helped me.
Tutorials that help:
https://forum.xda-developers.com/moto-z/how-to/official-moto-z-receiving-7-1-1-update-t3620742/page4
https://forum.xda-developers.com/moto-z/development/recovery-twrp-3-0-3-n1-moto-z-t3547672
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
https://forum.xda-developers.com/moto-z/development/rom-aokp-rom-moto-z-oms-substratum-t3550077
phone doesn't turn on with power button
Defaultnickname said:
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Click to expand...
Click to collapse
phone doesn't turn on with power button so we can't show it but if it plugs to usb 2 port windows detect as "motorolla ADB interface" in cmd command ,we can detect it as fastboot devices, but we can't do anything because moto z with that condition, it doesn't have any Partitions
is there a problem with no solution ? :angel:
rodrigofvl said:
SOLUTION FOR THE PROBLEM
Failure to install rom Moto Z XT1650-05 Sheridan Chinese.
https://forum.xda-developers.com/mo...-xt1650-05-t3695286/post74498676#post74498676
As I did not get able to install another rom or recover the one that was installed because of the blocked bootloader and the OEM lock and without TWRP, I was able to install by the recovery in update by the ADB and installed a modified rom to AOSP and the cellphone called, more by account of some bugs I used the fastboot boot twrp.img thread and I ran the TWRP without installing and changed to the lineageOS and installed GApps. I do not intend to use this rom for much longer until I figure out how to unlock OEM by the developer menu I'm going to stick with it I hope it helps someone. Thank you to everyone who helped me.
Tutorials that help:
https://forum.xda-developers.com/moto-z/how-to/official-moto-z-receiving-7-1-1-update-t3620742/page4
https://forum.xda-developers.com/moto-z/development/recovery-twrp-3-0-3-n1-moto-z-t3547672
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
https://forum.xda-developers.com/moto-z/development/rom-aokp-rom-moto-z-oms-substratum-t3550077
Click to expand...
Click to collapse
my recovery not working.... its damaged. Do you have any solutions?
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
i was trying to unlock my phone bootloader and installing twrp
after succesful installing twrp, i wipe my phone
then reboot
but after that my phone only boot into fastboot,
powerup using only powerup button just boot into fastboot
i can't go to recovery any button i try to press while boot always bump into fastboot
My pc recognize my phone,
i tried to flash recovery again to twrp
and try to "fastboot boot twrp.img"
the fastboot just stuck on booting text
i trying to wait for 30 minutes but it still didn't boot
can anyone help me with the problem?
fastboot oem device-info
----------------------------------------------------------------------------
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Bootloader version: PE1830-0x01-20190900173600
(bootloader) Verity mode: true
----------------------------------------------------------------------------
Hey bro just flash the stock fastboot ROM
I am having the same problem with my Zenfone Max M2.
Try to install stock ROM/firmware from ASUS's official website.
I'll let you know if my phone got fixed.
-Tanishk Shrivastava
Techgaming432 said:
Hey bro just flash the stock fastboot ROM
Click to expand...
Click to collapse
I fix it with QFIL Tool
Help Me!!
My phone is in this situation now!! I cannot use my phone for almost 2 weeks now! Please help me with full guide... really appreciate it:crying:
theteebox said:
My phone is in this situation now!! I cannot use my phone for almost 2 weeks now! Please help me with full guide... really appreciate it:crying:
Click to expand...
Click to collapse
1.Download this stock rom from here: https://drive.google.com/uc?id=1Io74E60ClyNxX6a7s1ad7CjG0tRK4g01&export=download
2. Extract it
3. Enter fastboot on phone and connect phone to PC
4. Go to the downloaded rom which you have extracted and double click on a file named flashall_AFT
The flashing will start after this.
Hope you fix your phone.
Note: This rom is for ZB632KL please check model no before flashing.
Appreciate it but not helping much
1. That wasn't my phone model. Mine is (was) Asus Zenfone Max M2 / X01AD / ZB633KL
2. To do that fastboot thing, I have some other issue with connecting that phone. Maybe the driver was not right. Or i have ruine my fastboot file, because Im pretty sure it was not because of cable (change and buy almost about 7 cables from many types :victory:
theteebox said:
1. That wasn't my phone model. Mine is (was) Asus Zenfone Max M2 / X01AD / ZB633KL
2. To do that fastboot thing, I have some other issue with connecting that phone. Maybe the driver was not right. Or i have ruine my fastboot file, because Im pretty sure it was not because of cable (change and buy almost about 7 cables from many types :victory:
Click to expand...
Click to collapse
Check this one:
https://drive.google.com/file/d/1OntNio5IirYcbYD7TO4kHnbLGrbbHjxf/view
You are my hero. I wish i could stand in front of you and yelling "you're the man"!!
Well... typing this reply of using my reborn phone for the 1st time since forever ?? You saved my life once. I save my money this time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
theteebox said:
Well... typing this reply of using my reborn phone for the 1st time since forever You saved my life once. I save my money this time
Click to expand...
Click to collapse
Congrats man in reviving your phone.
Cheers?
Hello friends, I have this problem on my cell phone, would you be able to help me, I tried to access the links to try to fix it, but it was no longer available!
I've already looked it up in several places, but so far I've only found your post that worked. Help me please!
GTtron816 said:
1.Download this stock rom from here: https://drive.google.com/uc?id=1Io74E60ClyNxX6a7s1ad7CjG0tRK4g01&export=download
2. Extract it
3. Enter fastboot on phone and connect phone to PC
4. Go to the downloaded rom which you have extracted and double click on a file named flashall_AFT
The flashing will start after this.
Hope you fix your phone.
Note: This rom is for ZB632KL please check model no before flashing.
Click to expand...
Click to collapse
My cell phone is this ZB632KL model, it only lasted a month, and I couldn't use it anymore.
Thank you very much in advance!
Hello all together,
i´ve got an Xiaomi Redmi 4 Prime (3G/32GB) FullHD Smartphone which i was very happy the last 3 years. It worked smooth and i had a great experience. Every evening when i go to bed, i shut down the phone and reboot it in the morning. So i did one week before. But on next morning phone does not boot any more. It was stuck on MI Logo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I could not do ANYTHING.
Could not even remove battery because it is not removable. All i could do is to wait until fully charged battery did go down to 0%.
So i tried rebooting many time without success. Looking at the internet i found some users reporting same problem, but most did have problems after an update or flashing or something. My Phone is Stock, i ordered it from china and never flashed anything. I did have Google Play Store and good working OS (Android 6.0 and MIUI 8). In the phone itself i often tried to look for updates but all time it told me i am up to date. i didn´t care about having an old OS. It was working and ok for me.
Ok so i did do alot of searches in google and found some instructions like how to boot into recovery mode or how to boot into fastboot mode.
As a software developer, i already had Android Studio on my machine and i did try to use the platform-tools from the SDK (adb.exe and fastboot.exe)
After some drivers update i can tell if iam in recovery mode, adb is listing my device
so when i type "adb devices" i get
List of devices attached
e0991c307d03 sideload
Click to expand...
Click to collapse
i did try a "adb pull /sdcard" but i get error: connection failed: closed
so i tried with fastboot
i found some information like booting twrp like a live cd with fastboot boot twrp.img (i did download a twrp version from the internet)
but i had no success and got that message
downloading boot.img OKAY [0.119s]
booting FAILED (Status read failed(Too many links))
Finished. Total time:
Click to expand...
Click to collapse
i tried fastboot erase cache, this seem to be worked, but my phone does not boot
fastboot oem device-info is giving me this info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY...
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) battery-soc-ok:yes
(bootloader) variant: QRD eMMC
(bootloader) secure: yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
Click to expand...
Click to collapse
So now WHAT I WANT!!!
I want to boot my phone to like it was WITHOUT loosing ANY DATA.
or at LEAST, recover the FILES from the internal 32GB storage.
I have WhatsApp Conversation and Media Files from near 4 years which i don´t want to miss.
I´ll be thankfully for every help i get from you. Please, before that trouble i have now, i never used adb, fastboot, twrp or anything like that before.
But why does it not boot any more, i just powered it off
Maybe the internal storage is near full, that is the only reason i could think. so erasing some files might help
For this guy who can help me to reboot my phone without loosing any data in it i will even donate some bucks via paypal to you.:fingers-crossed:
did you try to just press the Power down for 10-15 seconds to force the Redmi 4 to reboot back into Android manually?
Hi, pressing and holding the power button for more than 10 seconds simply does reboot the phone, but it is still locked on the boot screen (MI Logo)
I did now try and read many things.
I am successfully able to enter fastboot mode, but i see no fastboot command to access (and recover) any files from the internal storage.
i WAS able that the devices was listed unter adb devices in sideload mode?? but unfortunatelly in sideload mode, the adb pull command seems not to work?
there seems to be other adb modes besides adb sideload mode??
3. Mode i can enter is in download mode, i had to install some qualcomm drivers and the QPST. It contains a lot of tools and it seems to offer also a backup software, but i does not seem to work. also i found a EFS Explorer which also does not seem to work.
IT MUST be possible to at LEAST READ and BACKUP any files from the internal storage. I don´t care if the phone will remain dead, but at least i want to access and read the internal files. It can not be possible that so many members do not have any solution, even if i offer some money on a successful solution
Hi, I have a Moto One (deen retail) XT1941-3, and I had unlocked the bootloader, but now I want to lock it again, I followed instructions I saw on the internet, rooted it, installed the stock rom, etc. But when I go to the settings, in OEM unlock it appears: The bootloader is already unlocked. and also it is disabled and greyed out. I saw here on the XDA forum that I needed to root, but I already did!! Can someone help me!?
FilipeET said:
Hi, I have a Moto One (deen retail) XT1941-3, and I had unlocked the bootloader, but now I want to lock it again, I followed instructions I saw on the internet, rooted it, installed the stock rom, etc. But when I go to the settings, in OEM unlock it appears: The bootloader is already unlocked. and also it is disabled and greyed out. I saw here on the XDA forum that I needed to root, but I already did!! Can someone help me!?
Click to expand...
Click to collapse
Hi, be careful! Never lock the bootloader if you have a custom rom or root installed! Otherwise, you will block the phone and it will no longer be possible to start it. You have to install stock rom and type
Code:
fastboot oem lock
command. Good luck
Jan Skokan said:
Hi, be careful! Never lock the bootloader if you have a custom rom or root installed! Otherwise, you will block the phone and it will no longer be possible to start it. You have to install stock rom and type
Code:
fastboot oem lock
command. Good luck
Click to expand...
Click to collapse
Thanks, I didn't know I couldn't have root, but I already have the stock rom installed and I removed the root, but it still gives this error. Unfortunately, I couldn't find anything here on the forum about this.
Look:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
FilipeET said:
Thanks, I didn't know I couldn't have root, but I already have the stock rom installed and I removed the root, but it still gives this error. Unfortunately, I couldn't find anything here on the forum about this.
Look:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
The error tells you that you have to enable "oem unlock" in the developer settings, otherwise it won't work.
Jan Skokan said:
The error tells you that you have to enable "oem unlock" in the developer settings, otherwise it won't work.
Click to expand...
Click to collapse
Do this and try again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I Can't, It's greyed out :
Try this command
Code:
fastboot flashing lock
FilipeET said:
I Can't, It's greyed out :View attachment 5923601
Click to expand...
Click to collapse
Look
Jan Skokan said:
Look
View attachment 5923621
Click to expand...
Click to collapse
Thank you, would you know how long I need to wait to block it again? Because I unlocked the bootloader in January, I tried to block it but it didn't work, so this week I tried again, it didn't work, I already reinstalled the stock rom about 6 times but it never worked and every time I waited more than 7 days but it never worked , I'm starting to think my device is having issues.
When I run "fastboot flashing lock" it gives the same error, but says "(bootloader) This creates a recovery to unlock if Android fails to boot."
I don't have much experience with A/B devices, I started in January, before that I had a samsung so I used odin and it also only had A slot, which was much easier.
Did I do something wrong?
FilipeET said:
Thank you, would you know how long I need to wait to block it again? Because I unlocked the bootloader in January, I tried to block it but it didn't work, so this week I tried again, it didn't work, I already reinstalled the stock rom about 6 times but it never worked and every time I waited more than 7 days but it never worked , I'm starting to think my device is having issues.
When I run "fastboot flashing lock" it gives the same error, but says "(bootloader) This creates a recovery to unlock if Android fails to boot."
I don't have much experience with A/B devices, I started in January, before that I had a samsung so I used odin and it also only had A slot, which was much easier.
Did I do something wrong?
Click to expand...
Click to collapse
Have you been waiting since January? So I really don't know what to do with it.. And why do you want to lock the bootloader?
I also have an unlocked bootloader on my Motorola + I have a custom rom installed and I have root and I don't want to go back to the stock rom
Jan Skokan said:
I also have an unlocked bootloader on my Motorola + I have a custom rom installed and I have root and I don't want to go back to the stock rom
Click to expand...
Click to collapse
Actually I just wanted to remove the unlocked bootloader warning image...
but i was also happy with my android 10 but now that you mentioned not blocking i thought i would not try to block it again!
But, do you know why slot B does not work?
because it is also another reason, I always wanted to install something in slot B but it gives an error.
FilipeET said:
Actually I just wanted to remove the unlocked bootloader warning image...
but i was also happy with my android 10 but now that you mentioned not blocking i thought i would not try to block it again!
But, do you know why slot B does not work?
because it is also another reason, I always wanted to install something in slot B but it gives an error.
Click to expand...
Click to collapse
I'm sorry, but I don't know.
Jan Skokan said:
I'm sorry, but I don't know.
Click to expand...
Click to collapse
No problems. Thank you for help!!