Xiaomi Redmi 4 Prime does not boot anymore. Stuck on MI Logo. Please help recover - Android Q&A, Help & Troubleshooting

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

Related

Failure to install rom Moto Z XT1650-05 Sheridan Chinese.

[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?

LG H901 (TMobile) How to unbrick?

My phone got bricked once back in May when I was messing with rooting it (I managed to fix it) I can't remember how, but right now my phone is just dead all over again (now boot looping and giving me a green screen every few reboots) and I wasn't even trying to do anything wrong with him, just regular usage.
{
"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 attempted to get into Download mode, my computer won't recognize the phone was ever plugged in.
Then tried with fastboot, it gets recognized, however there's nothing I can do there since everything gives me this error:
FAILED (remote: unknown command)
finished. total time: 1.047s
I also tried with this QPST Tool that I can't get the phone connected to, and LGUP (doesn't recognize the phone) and also LGFlashtool (doesn't recognize the phone) Lastly tried with LG Bridge which didn't recognize the phone either.
It is like the phone somehow just blew up every piece of system information it had and now it's paperweight
If anyone remotely knows what can I do to fix this phone (I really like it and can't afford a new one for now) please let me know, I'll be checking this page daily.
PS: My Windows is W10 Pro B15063.rs2_release.170317-1834
(I gave this info just in case the Windows has something to do with the phone not being recognized in the computer)
PS #2: Obviously the phone has no warranty from the first time I tried to root it, so please skip the Take it to your carrier, please
My phone details using command fastboot -i 0x1bbb getvar all
PS E:\New folder> fastboot -i 0x1bbb getvar all
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd1b300000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x10bc00000
(bootloader) serialno:LGH901xxxxxxxx
(bootloader) kernel:lk
(bootloader) product:MSM8992_PPLUS_TMO_US
(bootloader) unlocked:yes
all:
finished. total time: 0.178s
These sound like similar symptoms of the dreaded bootloop issue that the G4 and v10 were prone to. Some people reported this issue happening slowly (phone kept rebooting until it stopped turning on) while others experienced their phone becoming a paperweight all at once. If this is the case there's no fix for it because the processor has separated from the motherboard. So it's either buy another motherboard or buy a new phone.
I'm not sure if this actually true but some people said that getting a good USB cable and using a different computer with Windows 8.1/7, possibly a regular USB 2.0 port gave them success. Again I don't know if this true but if you have access to these it might be worth a shot. The reason I say this is because T-Mobile rendered fastboot commands useless in a lot of the newer ROMs (especially the Nougat update) so even if fastboot recognizes the phone I'm not sure it can do anything helpful. Getting your phone recognized by LGUP or LG Bridge is best. Be warned that even if you can recover your phone it still may be a ticking timebomb after you fix it if it is the infinite bootloop issue.
Take it to anyone with an octopus box and he will fix it.
Recognized in computer but still nothing on screen
chin'ah.girl said:
These sound like similar symptoms of the dreaded bootloop issue that the G4 and v10 were prone to. Some people reported this issue happening slowly (phone kept rebooting until it stopped turning on) while others experienced their phone becoming a paperweight all at once. If this is the case there's no fix for it because the processor has separated from the motherboard. So it's either buy another motherboard or buy a new phone.
I'm not sure if this actually true but some people said that getting a good USB cable and using a different computer with Windows 8.1/7, possibly a regular USB 2.0 port gave them success. Again I don't know if this true but if you have access to these it might be worth a shot. The reason I say this is because T-Mobile rendered fastboot commands useless in a lot of the newer ROMs (especially the Nougat update) so even if fastboot recognizes the phone I'm not sure it can do anything helpful. Getting your phone recognized by LGUP or LG Bridge is best. Be warned that even if you can recover your phone it still may be a ticking timebomb after you fix it if it is the infinite bootloop issue.
Click to expand...
Click to collapse
For a while my phone wasn't doing anything and now I just used another cord in another USB port and it is recognized in the device manager as
ALCATEL HS-USB QDLoader 9008(COM9)
where do I go from here?
gameplayerdo2 said:
For a while my phone wasn't doing anything and now I just used another cord in another USB port and it is recognized in the device manager as
ALCATEL HS-USB QDLoader 9008(COM9)
where do I go from here?
Click to expand...
Click to collapse
Your device is hard-bricked. You will have to flash it with firmware dump files using qfil. Also make sure of what version your board is, there is a regular H901 and a "hybrid" H901 with a F600L board. You can check yours by looking at the sticker underneath the battery. Please be aware you may have to use firmware dump files that were from the same firmware version as the one your device was bricked with so the files contained in these guides may or may not be outdated. If this is the case you will have to find a user that has the same firmware version that your phone had to make the file dump for you, but I could be (and hopefully am) wrong about this.
Here is the guide for a hybrid version.
Here is a guide for standard H901.
Good luck!

Unable to unbrick RN4

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.??

Only boot into Fastboot

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!

Errors while trying to unlock bootloader on moto g6 plus

I'm trying to root my motorola g6 plus but when I run the command
fastboot oem get_unlock_data
I get this response:
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
I do notice here that up on top of the response it says that it doesn't recognise 'get_unlock_datas' which is certainly not what i typed, i typed 'get_unlock_data'
Okay so I took a break from writing this and tried to type the command in manually instead of having it copied from motorola's website, only this time it worked. However, the next time I tried writing it manually I got the same message just that instead of it saying 'get_unlock_datas' it said, 'get_unlock_da'.
I guessed that my machine was having trouble understanding what I was typing and sometimes thought I typed 'da' or 'datas' instead of 'data'.
So I did what I thought would fix it and typed the command in until it worked, and it did.
I did however run into a couple more errors like this one:
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) s: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.003s
On maybe my 10th try of copy pasting the code I finally succeeded, I would like to know why I don't get my desired response when typing 'fastboot oem get_unlock_data'. Keep in mind I am very new to rooting.
(Don't mind my bad grammar I figured you'd still be able to understand what i'm writing and this isn't an exam.)
iwanttoroot said:
I'm trying to root my motorola g6 plus but when I run the command
fastboot oem get_unlock_data
I get this response:
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
I do notice here that up on top of the response it says that it doesn't recognise 'get_unlock_datas' which is certainly not what i typed, i typed 'get_unlock_data'
Okay so I took a break from writing this and tried to type the command in manually instead of having it copied from motorola's website, only this time it worked. However, the next time I tried writing it manually I got the same message just that instead of it saying 'get_unlock_datas' it said, 'get_unlock_da'.
I guessed that my machine was having trouble understanding what I was typing and sometimes thought I typed 'da' or 'datas' instead of 'data'.
So I did what I thought would fix it and typed the command in until it worked, and it did.
I did however run into a couple more errors like this one:
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) s: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.003s
On maybe my 10th try of copy pasting the code I finally succeeded, I would like to know why I don't get my desired response when typing 'fastboot oem get_unlock_data'. Keep in mind I am very new to rooting.
(Don't mind my bad grammar I figured you'd still be able to understand what i'm writing and this isn't an exam.)
Click to expand...
Click to collapse
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
WoKoschekk said:
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
Click to expand...
Click to collapse
Do you mean one of those USB extender things like this?
{
"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"
}
iwanttoroot said:
Do you mean one of those USB extender things like this? View attachment 5724301
Click to expand...
Click to collapse
yes, that's exactly what I mean.
WoKoschekk said:
yes, that's exactly what I mean.
Click to expand...
Click to collapse
Okay thanks I'll try
WoKoschekk said:
yes, that's exactly what I mean.
Click to expand...
Click to collapse
I have now successfully rooted my motorola g6 after 2 years of struggles, thank you.
WoKoschekk said:
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
Click to expand...
Click to collapse
You, sir... are a genius! thank so much!
But i also have a problem. When i go to the fastboot on cellphone it gets a black screen.. i still could send the commands to unlock the boatloader, but now i cant get to install the twrp or magisk.. i dont know if its a outdated fastboot os something. Can u guys help me?
alexestanislau said:
But i also have a problem. When i go to the fastboot on cellphone it gets a black screen.. i still could send the commands to unlock the boatloader, but now i cant get to install the twrp or magisk.. i dont know if its a outdated fastboot os something. Can u guys help me?
Click to expand...
Click to collapse
Fastboot mode is only a UI for some bootloader commands. The known screen with the green Robot is only a .png file stored in your logo.bin. Did you modify your logo.bin (boot logo)?
WoKoschekk said:
Fastboot mode is only a UI for some bootloader commands. The known screen with the green Robot is only a .png file stored in your logo.bin. Did you modify your logo.bin (boot logo)?
Click to expand...
Click to collapse
Actually the cellphone wasnt mine until yesterday.. I dont know if they changed anything previously.. but there is no menu at all, just black screen

Categories

Resources