Database Develop

[Q] helps moto x hardbrick

helps moto x hardbrick not that it makes nanny someone q solved and me of an idea it does not ignite in fasboot please: Rolleyes:: Rolleyes:

posedys said:
helps moto x hardbrick not that it makes nanny someone q solved and me of an idea it does not ignite in fasboot please: Rolleyes:: Rolleyes:
Click to expand...
Click to collapse
I can see English isn't your first language, but I really can't make any sense of your post. Are you using Google Translate?
Does it power on at all? Are you able to get into the bootloader? If so, RSDLite.

posedys said:
helps moto x hardbrick not that it makes nanny someone q solved and me of an idea it does not ignite in fasboot please: Rolleyes:: Rolleyes:
Click to expand...
Click to collapse
From what I can gather, you're trying to get your phone to start up in fastboot mode, but it is failing. I assume you are not very strong in English and you're either using a translator to post, or posting with a fairly limited number of English words that you know, so I will try to be as plain as possible.
Do you have your computer drivers installed properly to detect your phone through adb (Android Debug Bridge)? If so, try running the command
Code:
adb reboot bootloader
to get it to boot up into fastboot mode.
If you cannot get that to work, do the following: turn your phone off. Then press the power button and volume down button at the exact same time. Hold both of them for about 10 seconds, then release. Your phone should boot into fastboot mode.
I'll try to help as much as I can, but cannot guarantee that I will be able to help you.

no fastboot
Johmama said:
From what I can gather, you're trying to get your phone to start up in fastboot mode, but it is failing. I assume you are not very strong in English and you're either using a translator to post, or posting with a fairly limited number of English words that you know, so I will try to be as plain as possible.
Do you have your computer drivers installed properly to detect your phone through adb (Android Debug Bridge)? If so, try running the command
Code:
adb reboot bootloader
to get it to boot up into fastboot mode.
If you cannot get that to work, do the following: turn your phone off. Then press the power button and volume down button at the exact same time. Hold both of them for about 10 seconds, then release. Your phone should boot into fastboot mode.
I'll try to help as much as I can, but cannot guarantee that I will be able to help you.
Click to expand...
Click to collapse
If I use a translator xq I speak Spanish .... not it does not ignite does not enter way fastboot and precionado the buttons but nothing as is you say to me but I do not achieve some solution enters to the way fastboot d another way of doing the take-off

oh man the translator you are using is horrible.

posedys said:
If I use a translator xq I speak Spanish .... not it does not ignite does not enter way fastboot and precionado the buttons but nothing as is you say to me but I do not achieve some solution enters to the way fastboot d another way of doing the take-off
Click to expand...
Click to collapse
will your phone turn on at all? in any way. or is it just blacked out. The only people that i have seen hard brick their device did so this way:
they downgraded their firmware to 4.2.2 or something. then they took the OTA for 4.4 before activating the device. this then bricked their phone and they had to return it. but the two people i saw have that problem were able to return it for a brand new phone no problem.

posedys said:
If I use a translator xq I speak Spanish .... not it does not ignite does not enter way fastboot and precionado the buttons but nothing as is you say to me but I do not achieve some solution enters to the way fastboot d another way of doing the take-off
Click to expand...
Click to collapse
Okay, so neither of those methods worked? What happened when you used the second method where you hold down the power button and volume down button together? Does it light up at all or vibrate or anything? That should work in most cases. Make sure your phone is off, and make sure to press them both at the same time, hold them both down for about 10 seconds, then release them both.
Can you get your phone to start up in any other mode? As in, normal mode or recovery mode? Is there any way to get any sounds or any lights from your phone?

posedys said:
helps moto x hardbrick not that it makes nanny someone q solved and me of an idea it does not ignite in fasboot please: Rolleyes:: Rolleyes:
Click to expand...
Click to collapse
If u received OTA after a downgrade......then your phone is fkn dead. And it can't be fixed
R.I.P.

omias said:
If u received OTA after a downgrade......then your phone is fkn dead. And it can't be fixed
R.I.P.
Click to expand...
Click to collapse
I am certain you can accept an OTA update if you have downgraded from 4.4 to 4.2.2. As far as I am aware the only people who have had problems didn't downgrade all files, or upgraded without upgrading all files.(they commented out certain portions of the xml so rsdlite didn't flash them)
posedys -
Does your battery have enough power, it may need to charge before you can access bootloader mode.
Can you tell us how the problem started?

Steve-x said:
I am certain you can accept an OTA update if you have downgraded from 4.4 to 4.2.2. As far as I am aware the only people who have had problems didn't downgrade all files, or upgraded without upgrading all files.(they commented out certain portions of the xml so rsdlite didn't flash them)
posedys -
Does your battery have enough power, it may need to charge before you can access bootloader mode.
Can you tell us how the problem started?
Click to expand...
Click to collapse
i know for a fact people have hardbricked from taking the OTA after fully downgrading without removing xml files. But they didn't upgrade with rsd lite or manual flashing. they just clicked the take the ota button when it popped up on the screen before they activated the device. the phone rebooted to take the ota, got held up when trying to do what it was doing. rebooted. then went black screen and didn't turn on at all no matter how many different buttons they pressed. I know of this happening to two people in the forums. It may have happened to more but those are the only i have seen.

jayboyyyy said:
i know for a fact people have hardbricked from taking the OTA after fully downgrading without removing xml files. But they didn't upgrade with rsd lite or manual flashing. they just clicked the take the ota button when it popped up on the screen before they activated the device. the phone rebooted to take the ota, got held up when trying to do what it was doing. rebooted. then went black screen and didn't turn on at all no matter how many different buttons they pressed. I know of this happening to two people in the forums. It may have happened to more but those are the only i have seen.
Click to expand...
Click to collapse
Fair enough, I have done it myself without any problem on several XT1058s. Sounds more like there is a flaw in the update process and it may just be taking an OTA that is killing it, nothing to do with the downgrade process.
Did it happen on CDMA based devices perhaps, for the GSM versions of the Moto X (XT1053, XT1058) there is no "activating" the phone.

Steve-x said:
Fair enough, I have done it myself without any problem on several XT1058s. Sounds more like there is a flaw in the update process and it may just be taking an OTA that is killing it, nothing to do with the downgrade process.
Did it happen on CDMA based devices perhaps, for the GSM versions of the Moto X (XT1053, XT1058) there is no "activating" the phone.
Click to expand...
Click to collapse
i only know that one of the individuals lived in south america somewhere. I can't remember the model. But by activating i meant like activating it on the network i guess. When you first get your phone and it activates on the network (perhaps that is what they meant when they said that). The way they described it, they downgraded booted the phone but didn't activate it on the network or something like that, then the take the ota option appeared, they took it,then got bricked. Ill see if i can find the first person i saw with the issue and post the link.
edit: i stand corrected. it was a long time ago i saw all those posts. I knew that they just normally took the ota but apparently didn't remember the part where they removed the gpt.bin from the xml file. Not sure i actually ever read that part until now. But ya you were/are right. Why would anyone remove that anyway lol. Thats why rsdlite is the savior and devil. Make things too easy and people get the feeling they know what they are doing apparently. If they just learned how to fastboot instead they wouldn't make that error. Oh well.

help
jayboyyyy said:
i only know that one of the individuals lived in south america somewhere. I can't remember the model. But by activating i meant like activating it on the network i guess. When you first get your phone and it activates on the network (perhaps that is what they meant when they said that). The way they described it, they downgraded booted the phone but didn't activate it on the network or something like that, then the take the ota option appeared, they took it,then got bricked. Ill see if i can find the first person i saw with the issue and post the link.
edit: i stand corrected. it was a long time ago i saw all those posts. I knew that they just normally took the ota but apparently didn't remember the part where they removed the gpt.bin from the xml file. Not sure i actually ever read that part until now. But ya you were/are right. Why would anyone remove that anyway lol. Thats why rsdlite is the savior and devil. Make things too easy and people get the feeling they know what they are doing apparently. If they just learned how to fastboot instead they wouldn't make that error. Oh well.
Click to expand...
Click to collapse
Q if the truth is not as revicirlo that i would love to because is dead dead not long ago reaction to nothing hopefully any solution can be and would welcome your assistance please

posedys said:
Q if the truth is not as revicirlo that i would love to because is dead dead not long ago reaction to nothing hopefully any solution can be and would welcome your assistance please
Click to expand...
Click to collapse
sorry man. either your spanish is a different version then most translators understand or your translator you use sucks. It is really hard to grasp what you are saying. If you can get the phone to fastboot then just run rsdlite from there. If you can't figure that out, get a friend that speaks some english to come translate for you because its virtually impossible to help you based on the english words you are producing in your posts.

posedys said:
Q if the truth is not as revicirlo that i would love to because is dead dead not long ago reaction to nothing hopefully any solution can be and would welcome your assistance please
Click to expand...
Click to collapse
Dude, if you want me to translate what you're trying to say, just PM me the message and I'll post it here. My English might not be the best but I'm sure I can do it better than your translator.
(si quieres que traduzca lo que intentas decir, sólo mandame un mensaje privado con lo que quieres decir y lo pongo aquí. Mi ingles no será el mejor pero seguro que puedo hacer algo mejor que tu traductor.)

He upgraded to Brazilian kitkat 4.4. Then he downgraded to movistar (it's a carrier) 4.2.2 but he received an ota upgrade so he took it. The upgrade downloaded and then the phone tried to reboot but it didn't boot.
He says he didn't know he had to install the 4.2.2 rom with the camera upgrade so now his moto x is hardbricked. He tried to fix it manually but couldn't enter to fastboot mode.
Also he says he's afraid battery might run low. (I think that might not be a problem because I guess even if the phone is bricked it will charge but I'm not sure)

perri.etb said:
He upgraded to Brazilian kitkat 4.4. Then he downgraded to movistar (it's a carrier) 4.2.2 but he received an ota upgrade so he took it. The upgrade downloaded and then the phone tried to reboot but it didn't boot.
He says he didn't know he had to install the 4.2.2 rom with the camera upgrade so now his moto x is hardbricked. He tried to fix it manually but couldn't enter to fastboot mode.
Also he says he's afraid battery might run low. (I think that might not be a problem because I guess even if the phone is bricked it will charge but I'm not sure)
Click to expand...
Click to collapse
Hardbrick (no fastboot - no battery charging)
R.I.P.

I'd like to know how he managed to install a 4.2.2 pre OTA file unless he only flashed some of the files. If you try to flash a 4.2.2 pre OTA update to a phone which has previously been updated it should fail, unless he edited the xml file and removed certain files. If that is the case then the phone is dead.

Yap its hard bricked, gpt.bin file will fail if you try to flash from 4.4 to pre camera ota, he probably edited the XML file incorrectly and it flashed the bootloader files
Sent on my Moto X

con relacion al ultimo mensaje es traducemelo xfa
perri.etb said:
Dude, if you want me to translate what you're trying to say, just PM me the message and I'll post it here. My English might not be the best but I'm sure I can do it better than your translator.
(si quieres que traduzca lo que intentas decir, sólo mandame un mensaje privado con lo que quieres decir y lo pongo aquí. Mi ingles no será el mejor pero seguro que puedo hacer algo mejor que tu traductor.)
Click to expand...
Click to collapse
no no no amigos no e edite nada estando en kit kat brazil retail lo hice con un escrib con el fasboot desde la ventana d comando descomprimi toda la rom original de 4.2.2 movistar peru luego le di a shift habrir ventana de comando y le di a instalar pero no edite nada luego de haber instalado arranco en 4.2.2 movistar peru luego me salio un aviso por ota para actializar le di q si descargo actualizo al reiniciar y salio el logo de androide q estaba instalando y cuando termino no arranco y se estanco no encendio mas e probado todas las combinaciones existentes de los botones pero nada aun no consegui hacerlo encender

[Need help] after updating to android 6.0 computer doens't recognize mobile and mbugs

Hello community. I own a xt1069 (moto g 2gen) and there was no problem with my mobile until i update it to the android 6.0.
The notifications doesn't make sound and i can't hear them in the notification config screen. The dialer doesn't work the speakerphone feature, but it doesn't work only in this native app (dialer), beacause while i make a call with other apps it works fine. And the biggest problem it's that after i updated it, any of my computers can open the mobile. I just get a usb device not recognize error, i'm going to put here: (as my pc it's in pt-br i'm going to translate literaly and the error message might be different on english windows versions):
"Windows interrompeu este dispositivo porque encontrou problemas. (Código 43)
Falha em uma solicitação de descritor de dispositivo USB. "
English:
"The windows interrupt this device due to some problems (code 43)
Failure in a usb device description solicitation"
And that's the biggest problem because if i can't access my mobile through my pc i can't downgrade it.
I'm really worried and all help is welcome
ah, and i've already tried to open the usb debugging option in the developer options and also change the usb connection type. (mtp/ptp) but it just charges the phone and gives the error. =/
Kind regards
Thank you all 0/

mitchu said:
Hello community. I own a xt1069 (moto g 2gen) and there was no problem with my mobile until i update it to the android 6.0.
The notifications doesn't make sound and i can't hear them in the notification config screen. The dialer doesn't work the speakerphone feature, but it doesn't work only in this native app (dialer), beacause while i make a call with other apps it works fine. And the biggest problem it's that after i updated it, any of my computers can open the mobile. I just get a usb device not recognize error, i'm going to put here: (as my pc it's in pt-br i'm going to translate literaly and the error message might be different on english windows versions):
"Windows interrompeu este dispositivo porque encontrou problemas. (Código 43)
Falha em uma solicitação de descritor de dispositivo USB. "
English:
"The windows interrupt this device due to some problems (code 43)
Failure in a usb device description solicitation"
And that's the biggest problem because if i can't access my mobile through my pc i can't downgrade it.
I'm really worried and all help is welcome
ah, and i've already tried to open the usb debugging option in the developer options and also change the usb connection type. (mtp/ptp) but it just charges the phone and gives the error. =/
Kind regards
Thank you all 0/
Click to expand...
Click to collapse
Try doing a factory reset as this can sometimes resolve many issues.

stonedpsycho said:
Try doing a factory reset as this can sometimes resolve many issues.
Click to expand...
Click to collapse
i've already tried twice. but today i send it to motorola's warranty store and now i'm going to wait, anyway, thanks for you answer.

Ayuda con el dispositivo Huawei P9 L09

Buenas y saludos desde Costa Rica...
Mi caso, intente actualizar mi dispositivo huawei p9 L09 del EMUI 4.1. y android 6.0 a la version del emui 5.0 y android 7.0. libere el bootloader y todo normal. el problema surge que no me percate que la room no tenia entrada de texto por letras solo por voz. A la hora de hacer el hard reset me pide la confirmacion de la cuenta y por consecuencia el ingreso de texto por voz no admite ni simbolos ni poner contraseñas. Existe alguna forma de volver al android anterior o volver a instalar otra room 7.0 con la funcion de entrada por texto? gracias de antemano

Please use English when posting, XDA is an English language forum. Thanks.?

trettet said:
Please use English when posting, XDA is an English language forum. Thanks.
Click to expand...
Click to collapse
I use google translate. sorry :crying:
Good and greetings from Costa Rica ...
In my case, try upgrading my huawei p9 L09 device from EMUI 4.1. And android 6.0 to the version of emui 5.0 and android 7.0. Free the bootloader and all normal. The problem arises that I do not realize that the new room did not have text input by letters only by voice. At the time of doing the hard reset it asks me for the confirmation of the account and consequently the entry of text by voice does not admit neither symbols nor put passwords. Is there any way to go back to the previous android or reinstall another 7.0 room with the text entry function?

KevinCTR said:
I use google translate. sorry :crying:
Good and greetings from Costa Rica ...
In my case, try upgrading my huawei p9 L09 device from EMUI 4.1. And android 6.0 to the version of emui 5.0 and android 7.0. Free the bootloader and all normal. The problem arises that I do not realize that the new room did not have text input by letters only by voice. At the time of doing the hard reset it asks me for the confirmation of the account and consequently the entry of text by voice does not admit neither symbols nor put passwords. Is there any way to go back to the previous android or reinstall another 7.0 room with the text entry function?
Click to expand...
Click to collapse
if you have a bluetooth keyboard then connect that to your phone and then you can input text via the physical bluetooth keyboard

Or plug in usb keyboard.
Sent from my EVA-L09 using Tapatalk

aceclift said:
if you have a bluetooth keyboard then connect that to your phone and then you can input text via the physical bluetooth keyboard
Click to expand...
Click to collapse
At this time the phone does not go beyond the verification part of account, you could not activate the bluetooth of the same. Connecting the keyboard via OTG will recognize it? There will be no other way :crying:

icaka20011 said:
Or plug in usb keyboard.
Sent from my EVA-L09 using Tapatalk
Click to expand...
Click to collapse
The problem is that I can not access the start as it is with a factory formatting and asks me the initial: language, region, wifi connection, and at the time of putting the account does not allow it by voice input

KevinCTR said:
At this time the phone does not go beyond the verification part of account, you could not activate the bluetooth of the same. Connecting the keyboard via OTG will recognize it? There will be no other way :crying:
Click to expand...
Click to collapse
Yes, connecting a keyboard via OTG would also work same as the bluetooth method
KevinCTR said:
The problem is that I can not access the start as it is with a factory formatting and asks me the initial: language, region, wifi connection, and at the time of putting the account does not allow it by voice input
Click to expand...
Click to collapse
You've mis-understood what this person has told you. Plugging in a USB keyboard is the exact same as connecting a keyboard via OTG. He just didn't use the term "OTG (On The Go) ".

aceclift said:
Yes, connecting a keyboard via OTG would also work same as the bluetooth method
You've mis-understood what this person has told you. Plugging in a USB keyboard is the exact same as connecting a keyboard via OTG. He just didn't use the term "OTG (On The Go) ".
Click to expand...
Click to collapse
I explained how my phone is at this moment:
- The ROM "L09 B383 (update.app)" was installed and the ROM complement the "update_data_full_hw_eu.zip" ... In this part the phone did not give any installation error in both files
-At the time of connecting it to the pc the ADB does not allow to install the TWRP the file "twrp-3.1.0-1-eva.img"
-In the moment of connecting the phone to the PC in fastboot mode to verify that it is unlocked or try to unlock again (here the phone screen indicates "phone: unlock" and "FRP: lock")
- the ADB reads the device correctly, if it puts the serial that indicates that it is in fastboot mode but indicates this error when installing the twrp mentioned with this command "fastboot flash recovery twrp-3.1.0-1.eva.img "The ADB mentions this error:" FALIED (remote: Comand not allowed) "
- I continue without installing the twrp and the phone starts normal requesting the language, region, wifi connection, and when it asks for the verification of the account of google returned to the problem of that it does not have entrance of text by letters.
** I will try to buy an OTG converter that works
** with this converter should without error read a keyboard either USB or bluettoth right?
** I would appreciate it if you explain to me if I have been wrong in some way

Huawei G7 Unbricking/Restoring stock ROM

Hey Guys...... After spending nights of unsuccessful searching for solutions to how to put my Huawei G7-L03 back to Kitkat, Android 4.4.4, stock rom, I decided to do it my self and it worked after reading through tons of material...... It should also work for similar Huawei G7x models...
If anyone is having a problem with aftermarket roms or phone is bricked and would like to restore their phone back to the original form, then follow along....
Note:- I take no responsibility if anyones phone explodes or it transforms into an alien robot.....
However, you should be fyne...
1.
https://forum.xda-developers.com/gx8/how-to/methods-to-install-stock-rom-g8-t3370013
Go to the above link and scroll down to the section, "Install using fastboot." You are going to use this method and forget about other methods mentioned there.
2. Now under that method, for the stock rom download option, I used Huawei's website to download the rom for my model and carrier....You should go to your own respective country's Huawei's website to download the stock rom......Should not be that hard......Just search for your model.......Here's the link to my model if you wanna take a risk and flash it with yours.......it might work or it might not.... http://consumer.huawei.com/ca/support/mobile-phones/g7-ca-sup.htm
Again scroll down and you will see it....
3. Huawei update extractor link is provided there...
4. For the Fastboot crapp.... Download this software.... https://forum.xda-developers.com/showthread.php?t=2703972
and when you open and it asks you to update it...just keep clicking no many times and it will shut up......and then you can move on to do your thang.....
That's it....if you followed all of it correctly......you should have factory phone back in your hand.......
Cheers!!

Firmware Huawei mya l03
Hola sabes tengo un Huawei mya l03
Y se me ha brikeado
Necesito alguna ROM o algún firmware de fabrica para poder restaurarlo
Me puedes ayudar?

my phone is brick help
my phone has full brick and I can not relive it
everything happened when I got an update via OTA and as I had TWRP I decided to put the recovery stock I decided to flash with flashify and when I restart the phone I did not boot and I can not enter fastboot mode or recovery sorry my bad english
i am from in mexico

hello, I have the same problem. Did you solve the problem?

G9 plus stuck on logo screen. Can photos +videos be recovered after factory reset?

Dear forum,
G9 plus has been fine from release. Until now, where at some point in the night the phone ended up in first M logo screen and stuck. (was it a failed OTA update?)
Initially I have been presented with the TRY AGAIN or FACTORY RESET as options. I have tried TRY AGAIN many times. I haven't tried FACTORY RESET as it says it will delete user data, and having not backed up photos in recent times I want to avoid if possible (although looking through I haven't found an alternative that will get the phone back.)
I have tried the power button and volume down, and then the power button and volume up, but none of the options available in those modes do anything to resolve......a reset there is also going to delete. (Is this the same factory reset, just in a text only interface?) When I do the graphics test the phone goes through an update to the graphics has and error and then installs graphics again which does through; but that does resolve anything either, I'm not sure what that is installing, but it doesn't nudge the thing back to life unfortunately.
Also, the USB port on the phone will not register with the computer, as the PC now won't recognise the device......so I can't use any ways of looking at the phone that use PC and the USB lead (unless I'm doing something wrong) Is that the driver of the USB on the phone not engaging because the system doesn't load up?
I have looked at posts and found very scant reference to recovery software, with much scepticism on whether they work. I was wondering whether anyone has had success with these types of software and are there other options using techniques found on this forum that would be more reliable (if I were to learn them).
Some software says that they phone doesn't have to be rooted, some say that they do. Is the requirement to root better because it would produce better results? Or would there be no difference / likelihood? I take it the rooting would have to be done after a reset? And would that risk deleting more data areas on the memory and then decrease the likelihood of getting photos undeleted.
Are local phone repair shops going to have set ups that will produce safe and better results? Do they use these recovery softwares?
I would appreciate any advice.....and getting my phone back asap ! And by miracle get photos and videos back.
BTW, I haven't yet done the factory reset, I take it if I select it on either the TRY AGAIN screen or the other low format list then it would reliably bring the phone back to as bought? Or are there problems where this is not a guarantee?
Kind regards
Steve

PS> I don't have an SD card installed. All data, including photos are on the internal phone memory.
PPS. Of the recovery softwares, has anyone had success with them on internal memory, any that you would recommend?

The error that shows is No bootable A/B slot error.
Searching people describe using Android SDK Platform tools and the replacing boot.img file...........Will this method work if currently I can't get the USB to see the phone on the PC, ie will the tools be able to communicate with the phone?
Is there any method that can do this kind of thing via a SD card. I have no way of identifying whether an SD card would be seen.
Regards
Steve

Well, got a replacement USB board for the phone and swapped out in case of hardware fault on the data part of the usb socket.............(full usb failure has happened to most of my past phones)
Still the same:
Unknown USB device (Device Descriptor Request Failed)
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Tried the drivers from motorola. Following other hints online, none appear to resolve.
Anyone ?

SRober said:
Dear forum,
G9 plus has been fine from release. Until now, where at some point in the night the phone ended up in first M logo screen and stuck. (was it a failed OTA update?)
Initially I have been presented with the TRY AGAIN or FACTORY RESET as options. I have tried TRY AGAIN many times. I haven't tried FACTORY RESET as it says it will delete user data, and having not backed up photos in recent times I want to avoid if possible (although looking through I haven't found an alternative that will get the phone back.)
I have tried the power button and volume down, and then the power button and volume up, but none of the options available in those modes do anything to resolve......a reset there is also going to delete. (Is this the same factory reset, just in a text only interface?) When I do the graphics test the phone goes through an update to the graphics has and error and then installs graphics again which does through; but that does resolve anything either, I'm not sure what that is installing, but it doesn't nudge the thing back to life unfortunately.
Also, the USB port on the phone will not register with the computer, as the PC now won't recognise the device......so I can't use any ways of looking at the phone that use PC and the USB lead (unless I'm doing something wrong) Is that the driver of the USB on the phone not engaging because the system doesn't load up?
I have looked at posts and found very scant reference to recovery software, with much scepticism on whether they work. I was wondering whether anyone has had success with these types of software and are there other options using techniques found on this forum that would be more reliable (if I were to learn them).
Algunos programas dicen que el teléfono no tiene que estar rooteado, otros dicen que sí. ¿Es el requisito de rootear mejor porque produciría mejores resultados? ¿O no habría diferencia/probabilidad? ¿Supongo que el enraizamiento tendría que hacerse después de un reinicio? Y eso correría el riesgo de eliminar más áreas de datos en la memoria y luego disminuiría la probabilidad de recuperar las fotos.
¿Los talleres locales de reparación de teléfonos tendrán configuraciones que producirán mejores resultados y más seguros? ¿Utilizan estos softwares de recuperación?
Agradecería cualquier consejo... ¡y recuperar mi teléfono lo antes posible! Y de milagro recuperar fotos y videos.
Por cierto, todavía no he realizado el restablecimiento de fábrica, lo tomo si lo selecciono en la pantalla INTENTAR DE NUEVO o en la otra lista de formato bajo, ¿entonces devolvería el teléfono de manera confiable a como lo compré? ¿O hay problemas en los que esto no es una garantía?
Atentamente
Steve
Click to expand...
Click to collapse
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com

jhenao12 said:
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Click to expand...
Click to collapse
For info,
That requires a usb to connect......... got access to forum, which didn't come up with any answer other than try a hard reset (which I'd already done) Also found user complaining about being left on Android 11...........anyway last update appears to have wrecked my phone or hardware has broken down with no answer other than in the end being told to send for repair.......so no chance of getting any lost photos :-(