Related
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"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"
}
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse
westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.
Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.
despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !
Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it
wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk
despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143
Problem statement: I have been looking to make a full backup of my phone, so that I have it in case device breaks or gets lost. I am aware there are app backup tools, but they all rely on application cooperating; some apps won't - for example Authenticator app will refuse to backup, and migrating to new device would be tedious, especially if it's lost. I would like to be able to do a one-time non-persistent root, which allows me to use titanium backup.
I understand there is a bootloader-based root now possible, which is useful, as it persists. But it will erase data before applying. Which makes sense, as that's protecting user data from being lifted from device by third party. But it defeats the purpose
I wonder if there's some sort of an exploit that could get me rooted temporarily, and then it goes away on reboot.
galets said:
Problem statement: I have been looking to make a full backup of my phone, so that I have it in case device breaks or gets lost. I am aware there are app backup tools, but they all rely on application cooperating; some apps won't - for example Authenticator app will refuse to backup, and migrating to new device would be tedious, especially if it's lost. I would like to be able to do a one-time non-persistent root, which allows me to use titanium backup.
I understand there is a bootloader-based root now possible, which is useful, as it persists. But it will erase data before applying. Which makes sense, as that's protecting user data from being lifted from device by third party. But it defeats the purpose
I wonder if there's some sort of an exploit that could get me rooted temporarily, and then it goes away on reboot.
Click to expand...
Click to collapse
LG Bridge can make a backup.
ChazzMatt said:
LG Bridge can make a backup.
Click to expand...
Click to collapse
Is that a full backup, similar to titanium, or is it a regular adb backup?
Can't Qfil do it? That's not unlock based, it's firehose based(and typically used in the process of unlocking).
Eric janaika said:
Can't Qfil do it? That's not unlock based, it's firehose based(and typically used in the process of unlocking).
Click to expand...
Click to collapse
Can you explain in a little bit more details, how are you proposing to use qfil, what problem will it solve?
galets said:
Is that a full backup, similar to titanium, or is it a regular adb backup?
Click to expand...
Click to collapse
More like Titanium.
You install LG Bridge on your PC, connect your phone and back up.
galets said:
Can you explain in a little bit more details, how are you proposing to use qfil, what problem will it solve?
Click to expand...
Click to collapse
I was under the impression it can read partitions as well as write. Is that not the case?
Eric janaika said:
I was under the impression it can read partitions as well as write. Is that not the case?
Click to expand...
Click to collapse
So, you saying it is capable of reading data partition from a _locked_ device? I was always assuming it's impossible by design
Update: you might be right... Per https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207 it seems like it might be possible. I'll go ahead and try it out. Thanks!
ChazzMatt said:
More like Titanium.
You install LG Bridge on your PC, connect your phone and back up.
Click to expand...
Click to collapse
Do you know if LG Bridge is similar in functionality to LG Mobile Switch? I just made a backup using Mobile Switch and used 7z to extract data. It backed up authenticator apk, but none of it's data. In other words, it's pretty much same as adb backup in functionality
galets said:
Do you know if LG Bridge is similar in functionality to LG Mobile Switch? I just made a backup using Mobile Switch and used 7z to extract data. It backed up authenticator apk, but none of it's data. In other words, it's pretty much same as adb backup in functionality
Click to expand...
Click to collapse
Two different pieces of software with totally different purposes.
https://www.androidcentral.com/how-use-lg-bridge-your-lg-phone
UPDATE:
* @ChazzMatt LG Bridge on windows PC flat out refused to back up. "Your phone is not supported for backing up with LG Bridge"
* @Eric janaikat QFIL connected to device in download mode (restart then Vol Up), but "Partition Manager" is grayed out. I'm not sure if that's correct mode to use. Perhaps, it is because device is not boot-unlocked. Unlocking will cause reset, which defeats the purpose. Or, perhaps I'm just not putting device in correct mode.
* Update2: Also put the phone into "Qualcomm HS-USB QDLoader 9008" mode, and tried to use qfil. Partition manager is still grayed out.
Did you follow the guide you linked? Seems like they show you how to backup the partitions in the guide. Did you select the firehose programmer? Did you remember to put it in UFS mode?
Eric janaika said:
Did you follow the guide you linked? Seems like they show you how to backup the partitions in the guide. Did you select the firehose programmer? Did you remember to put it in UFS mode?
Click to expand...
Click to collapse
I think we might be getting somewhere here, but I'm not sure. I got a programmer selected, and now I can see partition manager enabled. But it still won't open (see screenshot). It seems that the instructions had reference to "rawprogram0.xml", but I can't see where can I find one...
Eric janaika said:
Did you follow the guide you linked? Seems like they show you how to backup the partitions in the guide. Did you select the firehose programmer? Did you remember to put it in UFS mode?
Click to expand...
Click to collapse
okay... I did finally pull the `userdata` from device. Now what? I can't decrypt it. I think the android is using hardware key derivation, which makes it impossible to mount userdata outside the phone it was generated on. That means I can't copy it to another device either. Am I incorrect?
That might be so. I haven't had to try myself, but I imagine Qfil doesn't decrypt it. You just need a backup so you can restore to the same phone after unlocking right? The key shouldn't change should it?
If you want a general purpose backup, make one after you root it.
ChazzMatt said:
Two different pieces of software with totally different purposes.
The LG Bridge software creates a backup of .lbf file format, which seems to be proprietary to LG and can not be read from the computer the backup is stored upon.
Click to expand...
Click to collapse
Eric janaika said:
That might be so. I haven't had to try myself, but I imagine Qfil doesn't decrypt it. You just need a backup so you can restore to the same phone after unlocking right? The key shouldn't change should it?
Click to expand...
Click to collapse
I think there's hardware module which stores part of key derivation information. If you reset phone, it's gone. Since you indicated you never did it yourself, I don't believe I want to try it either, since my goal is to make reliable backup BEFORE my phone is destroyed
Eric janaika said:
If you want a general purpose backup, make one after you root it.
Click to expand...
Click to collapse
We are going in circles here. That was exactly the purpose if my post - I want to get root, so I can backup. I can't root it via unlocking bootloader, since it will erase the very data I'm looking to backup
RKHenderson said:
The LG Bridge software creates a backup of .lbf file format, which seems to be proprietary to LG and can not be read from the computer the backup is stored upon.
Click to expand...
Click to collapse
Have you been able to even use LG Bridge to backup v35? Specifically, LM-V350ULM. My attempts were met with "Your phone is not supported for backing up with LG Bridge". If you were, did it successfully restore apps which resist being backed up, such as google authenticator?
galets said:
Have you been able to even use LG Bridge to backup v35? Specifically, LM-V350ULM. My attempts were met with "Your phone is not supported for backing up with LG Bridge". If you were, did it successfully restore apps which resist being backed up, such as google authenticator?
Click to expand...
Click to collapse
I was able to backup but mine is LM-V350AWM. I used the LG Bridge to backup, meaning the usb cable not the wifi bit (I think they call that LG Air Drive). It made a backup that I can load on the phone and it keeps my steam auth.
Only problem is that the file on my computer is not a format I can read (.lbf). I would really like to get this backup to read to see what exactly it did store but after making the backup it seems I am stuck.
UPDATE: rooting device seems to be too much of a nuisance. What I did instead is modify google authenticator to allow backing up database using one-way encryption (e.g.: can't read it back if device is hacked). If anybody is interested, I can publish source code after bringing it into a publishable state.
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
I'm looking for a solution that would allow me to either unlock my phone without data loss, or make a backup of the phone's internal storage on an sd card/pc before hard resetting.
The device is not rooted and I don't have custom recovery installed. USB Debugging is on, but my laptop is not authorized.
With Adb, the device is detected but unauthorized. It seems to be detected normally in fastboot mode. I was able to get my laptop to detect it in recovery mode by clicking on "Connect with MIAssistant" while it was plugged in, but only in sideload mode. I also somehow managed to get into safe mode, but I used the stock screen lock, so unless there's something else that can be done in that mode, it doesn't seem useful in this situation.
I tried the actual MIAssistant software but it tells me to update my device before connecting. From what I found, this is because it doesn't even work with phones running Android 6.0 Marshmallow or above, so that seems to be a dead-end, unfortunately. Downloaded from here, updated to version 3.2.1.3111. If there's a newer version that could support my device, even an untranslated one, I would love to know, but I couldn't find a working one.
I had some ideas that could potentially solve my problem, but couldn't find a way to actually execute them, so here they are in case someone out there who knows more than me could help me with one of them.
1, Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
2, Is there a way to make a backup of the internal storage of my phone in fastboot/sideload mode?
3, Is there a way to get adb to detect this device normally in recovery mode, instead of in sideload mode?
4, Is there a way to get my device into mtp/ptp mode instead of charging mode when connected to a PC without USB Debugging so I can copy my files?
5, Here's a thread I found that seems promising, although it's old. Could I somehow use this, or a similar method on Redmi Note 8? The Recovery Mode is much more limiting on this device, unfortunately, so I can't exactly follow this tutorial. Are there alternatives that can be done in adb fastboot/sideload mode, perhaps?
6, If I am forced to hard reset, is there any software out there that could recover at least some of the deleted data afterwards, or is everything lost in case of a reset?
I am open to new ideas not listed above, as well. I am not a very advanced user so I probably missed some things.
Thank you so much for any answer in advance!
zoey_96 said:
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
Click to expand...
Click to collapse
do you have the default recovery ? or a custom one ?
zoey_96 said:
Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
Click to expand...
Click to collapse
No
loopypalm said:
do you have the default recovery ? or a custom one ?
Click to expand...
Click to collapse
Default, which doesn't have many options on Xiaomi. :/
loopypalm said:
No
Click to expand...
Click to collapse
Sad to hear that. Are there any alternative options that could solve my problem? I'd really rather not factory reset.
zoey_96 said:
Default, which doesn't have many options on Xiaomi. :/
Click to expand...
Click to collapse
if you had twrp or similar your problem would be solved ...
zoey_96 said:
Are there any alternative options that could solve my problem?
Click to expand...
Click to collapse
not as far as i know, ask in ADB thread if you find any
Updated with extra info in case anyone else has any ideas.
Even if you can copy your files to PC, they are problably unusable because of encryption.
That is why you need that pattern
For security this is exactly what you want, if your phone is lost or stolen.
Elinx said:
Even if you can copy your files to PC, they are problably unusable because of encryption.
That is why you need that pattern
For security this is exactly what you want, if your phone is lost or stolen.
Click to expand...
Click to collapse
Do you mean that the reason it doesn't accept the correct pattern anymore is for security? I would have thought it would still accept the correct one, at least after several tries of the same thing. Being completely locked out even when you know the correct password is a little strange to me.
zoey_96 said:
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
I'm looking for a solution that would allow me to either unlock my phone without data loss, or make a backup of the phone's internal storage on an sd card/pc before hard resetting.
The device is not rooted and I don't have custom recovery installed. USB Debugging is on, but my laptop is not authorized.
With Adb, the device is detected but unauthorized. It seems to be detected normally in fastboot mode. I was able to get my laptop to detect it in recovery mode by clicking on "Connect with MIAssistant" while it was plugged in, but only in sideload mode. I also somehow managed to get into safe mode, but I used the stock screen lock, so unless there's something else that can be done in that mode, it doesn't seem useful in this situation.
I tried the actual MIAssistant software but it tells me to update my device before connecting. From what I found, this is because it doesn't even work with phones running Android 6.0 Marshmallow or above, so that seems to be a dead-end, unfortunately. Downloaded from here, updated to version 3.2.1.3111. If there's a newer version that could support my device, even an untranslated one, I would love to know, but I couldn't find a working one.
I had some ideas that could potentially solve my problem, but couldn't find a way to actually execute them, so here they are in case someone out there who knows more than me could help me with one of them.
1, Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
2, Is there a way to make a backup of the internal storage of my phone in fastboot/sideload mode?
3, Is there a way to get adb to detect this device normally in recovery mode, instead of in sideload mode?
4, Is there a way to get my device into mtp/ptp mode instead of charging mode when connected to a PC without USB Debugging so I can copy my files?
5, Here's a thread I found that seems promising, although it's old. Could I somehow use this, or a similar method on Redmi Note 8? The Recovery Mode is much more limiting on this device, unfortunately, so I can't exactly follow this tutorial. Are there alternatives that can be done in adb fastboot/sideload mode, perhaps?
6, If I am forced to hard reset, is there any software out there that could recover at least some of the deleted data afterwards, or is everything lost in case of a reset?
I am open to new ideas not listed above, as well. I am not a very advanced user so I probably missed some things.
Thank you so much for any answer in advance!
Click to expand...
Click to collapse
Howdy bro (I also have a Xiaomi Redmi Note 8).
I've been almost two intense weeks reading and watching the XDA forum, trying somehow and I did not find the way to unlock it .... Besides that I have the Bootloader disabled it makes me more difficult, because for that I need to format my phone and is what I do not want .... Already today is my last day of searching and I think I will have to leave my memories behind and Format my cell phone.
I leave you a thread of a user that explains well the process of why you can not:
A Comprehensive Guide to getting Past the Android Pattern Lock Screen
So, here's the situation I’m in. Also I am 99% sure I got something wrong so please tell me. I’m past the pattern lock screen so ADB won’t directly work to unlock the lock screen. If I was at a pattern lock screen, I could use ADB to unlock the...
forum.xda-developers.com
and several more of the many threads that I searched, maybe it will help someone:
[Xiaomi] How to unlock phone after forgetting the password.
Hello, today it happened that I forgot a password to my phone. I've tried to restore it by logging in into my xiaomi account and my google account. Unfortunately it only offers to wipe my data, which I want to avoid at all costs. I have Poco F2...
forum.xda-developers.com
[Android][Guide]Hacking And Bypassing Android Password/Pattern/Face/PI
- DISCLAIMER - This Is For Educational Purposes Only You Shall Not Use This On Other People Phones Without Permission Under Any Circumstances I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices Files And Tutorials Are...
forum.xda-developers.com
[Android][Guide]Hacking And Bypassing Android Password/Pattern/Face/PI
- DISCLAIMER - This Is For Educational Purposes Only You Shall Not Use This On Other People Phones Without Permission Under Any Circumstances I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices Files And Tutorials Are...
forum.xda-developers.com
[GUIDE] Unlock bootloader without losing user data.
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data. 0 - Read the whole guide before proceeding and proceed at your...
forum.xda-developers.com
[GUIDE] Redmi K20 Pro - Unlock & Root Information, Links, Tools and Instructions
Like many, I was overwhelmed with information when trying to unlock, flash, and root my phone. After many failures, I decided to compile the good information all in one place. I hope this helps. If it does, please consider buying me a beer...
forum.xda-developers.com
Recovery without data loss
Hi Community, you are my last salvation. I am owner of Pixel 4a 5g since half a year and now it cannot boot anymore. I see only the google-"G" and the loading bar nothing else. I can start the Boatloader but before i do a factory reset i need to...
forum.xda-developers.com
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.
I need help with my pixel (taimen), and I don't know what to do. In attempt of resizing partitions with help of parted, I somehow deleted all the partitions (even though it showed they were recreated successfully), and now the phone won't even boot to fastboot. Is there any way how to repair it? I've had it for long time and I don't feel like loosing it today.
There are a couple of other threads where a user posted firebase files that could be used with existing firmware. Those files and a copy of MiFlash on the PC may be able to restore the device, but only if it shows up as a Qualcomm USB loader in Windows. The only other alternatives are to pay Google to fix the problem or sell the unit for parts.