Related
NOTE: THIS FOR WIFI ONLY MODEL XOOMS
For those of you who have managed to stuff up your android device like i have, and who have reached out to the community and received a set of vague comments barely outlining how to do something along the lines of fixing it from people who aren't really interested in helping you, this guide is for you. I've managed to fix my xoom by flashing a stock android 3.0 rom to it
For the sake of anyone who was in the same predicamant as me, the steps I took to fix it were:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
6) Once that is done, type fastboot reboot or hold power+volume up (reboots device). you are now done and it should boot into android. From there, you can start again and re-root or flash new firmware or whatever, just remember to regularly back up your roms so you can just restore them from clockwork recovery!
**IF ANYONE FOUND THIS HELPFUL, PLEASE SAY SO!**
Why use the stock when there images of tiamat roms on the forum here. I've screwed mine up once but figured how to get into recovery and flashed tiamat back.
Tiger62651 said:
Why use the stock when there images of tiamat roms on the forum here. I've screwed mine up once but figured how to get into recovery and flashed tiamat back.
Click to expand...
Click to collapse
Please, really? Not everyone shares your opinion on everything. Some people, myself included, prefer to run stock. (Actually, I'm running stock rooted with CWM for Nandroid backup and screenshot purposes.)
Some people may need to go back to factory for warranty or upgrade service fron Motorola as well.
Sometimes, you have to see past your own view.
I personally prefer stock, as with the upcoming android 4.0 upgrade (!) just around the corner i want to have the ability to upgrade to it as soon as it comes out.
Thanks for this post! In the event I get the itch to do some flashing, this guide will help when I'm in a pinch.
dbam987 said:
Thanks for this post! In the event I get the itch to do some flashing, this guide will help when I'm in a pinch.
Click to expand...
Click to collapse
I second you.
It works but if your a 3g/4g owner and you do this you will lose your baseband because they wont let you pass 3.2 in OTA updates, when it is required to have 3.2.2
Sorry for being noob but I have the bootloader to 1.5 i have all stock images for 3.2.2 but my xoom wont see 3g or 4g any ideas!!!
Are you talking about the method, itself, or about the stock image realated in the link ?
localizador said:
Are you talking about the method, itself, or about the stock image realated in the link ?
Click to expand...
Click to collapse
The stock images they change something in the bootloader for the 4g card to work
THANKS, just saved me from my boot loop after trying a modified update script for 4.0.3 ;-)
Saved my chops too we must buy beer for him
Thanks for this guide, I will be making use of this this week.
HD2wally said:
Saved my chops too we must buy beer for him
Click to expand...
Click to collapse
Make it a Blue Moon!!!!!
amysdadforever said:
It works but if your a 3g/4g owner and you do this you will lose your baseband because they wont let you pass 3.2 in OTA updates, when it is required to have 3.2.2
Sorry for being noob but I have the bootloader to 1.5 i have all stock images for 3.2.2 but my xoom wont see 3g or 4g any ideas!!!
Click to expand...
Click to collapse
I thought that was fixed? See -> http://www.mydroidworld.com/forums/...la-xoom-3-2-2-recovery-images.html#post106459 and/or starting around post #331 of -> http://forum.xda-developers.com/showpost.php?p=18753267&postcount=331
But what can be fix if there is no way to get to Fastboot screen? no matter how Vol up + Power or Vol dn + power ... there is only "Dual core screen" ... i guess for those that have got that screen the Xoom is totally bricked
y2k-inc said:
But what can be fix if there is no way to get to Fastboot screen? no matter how Vol up + Power or Vol dn + power ... there is only "Dual core screen" ... i guess for those that have got that screen the Xoom is totally bricked
Click to expand...
Click to collapse
Hmmmm dont know what to tell you never had my xoom just stick at the dual core screen for sure you already tried boot xoom up wait 2 sec and vol down button twice!!!
---------- Post added at 08:38 AM ---------- Previous post was at 08:36 AM ----------
KidJoe said:
I thought that was fixed? See -> http://www.mydroidworld.com/forums/...la-xoom-3-2-2-recovery-images.html#post106459 and/or starting around post #331 of -> http://forum.xda-developers.com/showpost.php?p=18753267&postcount=331
Click to expand...
Click to collapse
Yes I see the fixed and spend 3 days trying to fix this I made a section where its 10x faster to fix using a actual mz602 .sbf file heres the link to it
http://forum.xda-developers.com/showthread.php?t=1445135
---------- Post added at 08:38 AM ---------- Previous post was at 08:38 AM ----------
KidJoe said:
I thought that was fixed? See -> http://www.mydroidworld.com/forums/...la-xoom-3-2-2-recovery-images.html#post106459 and/or starting around post #331 of -> http://forum.xda-developers.com/showpost.php?p=18753267&postcount=331
Click to expand...
Click to collapse
Yes I see the fixed and spend 3 days trying to fix this I made a section where its 10x faster to fix using a actual mz602 .sbf file heres the link to it
http://forum.xda-developers.com/showthread.php?t=1445135
Thanks you this guide is great!!!!
Because the stock images come in a set with separate roms for the different sections
Its actually only 6.0 oops didn't look
If you are getting Error 7 Restore the stock system.img and it will flash
this is being uploaded i will have it up by the end of this day 1/4/2016
Update.zip file found here - Google Drive
when of course i get it fully uploaded
So if you have any questions or comments feel free to email me at [email protected] or text me at 5418870575 I do have school since I'm only 16 but will get to you asap
Me and 6th_Hokage think that the bootloaders completely locked because of the messages that the terminal gives system.img is unavailable because of this reason
Instructions
Step 1: Download the zip to your sdcard.
Step 2: Boot your phone into recovery mode by turning off your phone then holding the power and down volume button at the same time. Holdthese buttons until you see the recovery mode screen
Step 3: Navigate the menu by using the up and down volume buttons. Push the down volume button until you reach Update using sd card" It should be the last selection on the menu,
Step 4: Select this option by pressing the power button Once Step
5: Install the zip by selecting the update.zip.
Step 6: Let the install run(total time took about 15 minutes for me)
Step 7: Reboot the phone.
Your done.
I can't pull the system img I already posted what I was getting trying to pull it - bootloaders completely locked no way of bypassing it so far
Want to watch some tutorials on how to install the stock zv4 or zv5 come on by to my YouTube channel - Dominic Gresham
Ok ill say it... What the hell is this? Where did it come from?
Since Boost has already started OTA, I imagine Dominic is capturing and preparing to upload it for us.
jmacie said:
Since Boost has already started OTA, I imagine Dominic is capturing and preparing to upload it for us.
Click to expand...
Click to collapse
exactly i will also have a youtube video showing up soon enough
Well it should be 6.0.1 because that's what ZV7 is so so so... get some kind of confirmation on it 'cause I'm pretty sure there's no 6.0.0 for our CDMA devices.
kcarden said:
Ok ill say it... What the hell is this? Where did it come from?
Click to expand...
Click to collapse
boost mobile a week ago said that marshmallow 6.0 was coming out for the phone im half way uploaded it should be up vary soon maybe like another 20 minutes but i did run into some issues when capturing the system.img
here i have attached a image of the error that i get and its a weird one
DominicGresham said:
boost mobile a week ago said that marshmallow 6.0 was coming out for the phone im half way uploaded it should be up vary soon maybe like another 20 minutes but i did run into some issues when capturing the system.img
here i have attached a image of the error that i get and its a weird one
Click to expand...
Click to collapse
thanks 6th_Hokage again for the commands
br0adband said:
Well it should be 6.0.1 because that's what ZV7 is so so so... get some kind of confirmation on it 'cause I'm pretty sure there's no 6.0.0 for our CDMA devices.
Click to expand...
Click to collapse
ya it is 6.0 thats the android version
Well that ain't right, geez, guess they'll have to push another update at some point to get that .1 happening. Bleh, I'm selling my Stylo this morning anyway so I guess I'm pretty much done with them till I can find a good deal on a T-Mobile model, the 1GB of RAM just ain't workable for me.
Is this for the sprint lg stylo too thx
i instaled update.zip i put in sd card recovery and install beware they stuck in update system image long time but they instaled fine
Thanks Dominic! and also [email protected] for preparing me to be patient for the update to install. Looking forward for the root solution Dominic, Thanks again!
br0adband said:
Well that ain't right, geez, guess they'll have to push another update at some point to get that .1 happening. Bleh, I'm selling my Stylo this morning anyway so I guess I'm pretty much done with them till I can find a good deal on a T-Mobile model, the 1GB of RAM just ain't workable for me.
Click to expand...
Click to collapse
You must be new to the whole Android thing
add
jmacie said:
Thanks Dominic! and also [email protected] for preparing me to be patient for the update to install. Looking forward for the root solution Dominic, Thanks again!
Click to expand...
Click to collapse
thanks and work great is less lagging and more fast response
the one thing we now have to work on is root for 6.0 and pulling the system.img i can look into the international G3 forums to see how they did it
---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------
mike9976 said:
Is this for the sprint lg stylo too thx
Click to expand...
Click to collapse
should work an technically you should've gotten it first ._.
Where is the option to adopt sd card??
I did the update through recovery and the only thing i can't seemed to find is how to make sd card adoptable on my lg stylo??
Hey guys two quick questions, first the download seems to not be working, maybe uploading it someplace else would alleviate that. Secondly, doesn't booting into recovery force you to do a factory reset? If anyone that already flashed can clear that up I'd be grateful...
Anyone with root able to uninstall root and install update yet?
Either with simple unroot or factory reset
Blu8 said:
Hey guys two quick questions, first the download seems to not be working, maybe uploading it someplace else would alleviate that. Secondly, doesn't booting into recovery force you to do a factory reset? If anyone that already flashed can clear that up I'd be grateful...
Click to expand...
Click to collapse
Blu8, I just re-dwnld's it went a 8,5 MB/s, that's my max ( downl'd to my PC, then transferred to my SD) and it was fine. So I don't know. Some guys on the facebook stylo page just now were having problems straight dwnloading to their phone, so I don't really know.
Kolma- I used the Un-root and un-brick-xda- http://forum.xda-developers.com/android/development/official-boost-lg-g-stylo-unbrick-guide-t3215198
then I used Dominic's update.zip in his OP on the first page and it all went fine. It took a bit of time to check, extract and install, so be patient, but it went fine for me. Good Luck!
This is Edwin bro lol thanks again
Sent from my LGMS631 using Tapatalk
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Plz any developers help him
Sent from my Lenovo A6000 using Tapatalk
Find how to flash device with qfil in google
Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
Im on rr 5.7.3
- first i wipe data,dalvik,cache and system in twrp
- flash L2KK.zip
- reboot recovery and stuck at boot (lenovo powered by android)
i know i have to flash twrp for kitkat right? but i end up flashing something about partition because i wasnt giving attention. not my phone cannot go into recovery or fastboot. just a red notification light. i know this is my fault.
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
sasukay said:
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
Click to expand...
Click to collapse
nope
Irwan Fauzi said:
nope
Click to expand...
Click to collapse
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
sasukay said:
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
Click to expand...
Click to collapse
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Sloved
i have sent my device to service center.. thanks to everyone who trying to help me..
Irwan Fauzi said:
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
Click to expand...
Click to collapse
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
bvsbrk said:
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Click to expand...
Click to collapse
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
sasukay said:
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
Click to expand...
Click to collapse
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
bvsbrk said:
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
Click to expand...
Click to collapse
I can understand who you are talking about
No problem
I never considered myself above anyone so something
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
I would not suggest flashing a6000 s ROM on your new phone or you may end up like your a6000
Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
Don't you ever try to flash custom ROM that not supported for your phone
My daughter managed to change the pattern on her phone while on vacation and she can't remember what the new one is. I have gotten into the boot menu in attempts to completely reset the phone, however, there is no option for factory reset. Can somebody please tell me how to wipe this phone so she can use it again.
I'm just gonna ask for someone who knows better. I guess you'd be better off leaving the bootloader locked so you can have the warranty, so would it be possible to flash TWRP through fastboot, then delete lockscreen database stuff with it, then flash stock recovery? All without unlocking the phone?
Also could you tell us the model? Is it an A2017G, A2017, or A2017U?
If the phone hasn't got fastboot, you would have to use MiFlash to flash A2017*_FASTBOOT_UNLOCK_EDL then get TWRP and delete the files.
---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------
Also, if you do that process you could avoid resetting the phone. I'm just not sure if you can change system stuff without unlocking the bootloader. so until someone with actual knowledge shows up I'd advise you to hold on tight.
MasterDDF said:
My daughter managed to change the pattern on her phone while on vacation and she can't remember what the new one is. I have gotten into the boot menu in attempts to completely reset the phone, however, there is no option for factory reset. Can somebody please tell me how to wipe this phone so she can use it again.
Click to expand...
Click to collapse
unlock the bootloader.
Jusz go into recovery mode, shutdown the phone wait for 5 seconds than push the volume up and Power button at the same time and wait till. you are in recovery mode, than you can factory reset the phone
https://youtu.be/Rw5TMxyAGMc
nuridurdu27 said:
Jusz go into recovery mode, shutdown the phone wait for 5 seconds than push the volume up and Power button at the same time and wait till. you are in recovery mode, than you can
Click to expand...
Click to collapse
If only it was that simple. That was the first thing I did after 30 failed attempts for her figuring out her pattern. However there isn't am option to reset to factory. I've never seen a phone not have the option before
Choose an username... said:
I'm just gonna ask for someone who knows better. I guess you'd be better off leaving the bootloader locked so you can have the warranty, so would it be possible to flash TWRP through fastboot, then delete lockscreen database stuff with it, then flash stock recovery? All without unlocking the phone?
Also could you tell us the model? Is it an A2017G, A2017, or A2017U?
If the phone hasn't got fastboot, you would have to use MiFlash to flash A2017*_FASTBOOT_UNLOCK_EDL then get TWRP and delete the files.
---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------
Also, if you do that process you could avoid resetting the phone. I'm just not sure if you can change system stuff without unlocking the bootloader. so until someone with actual knowledge shows up I'd advise you to hold on tight.
Click to expand...
Click to collapse
Slightly embarrassing realizing I even had the model of phone wrong. Not listening to my wife anymore. It is an axon 7 mini. Model B2017G. If there is a moderator that would like to relocate the post that would be fine
lafester said:
unlock the bootloader.
Click to expand...
Click to collapse
Is there a walkthrough on unlocking the bootloader? I haven't messed with getting that done before.
MasterDDF said:
Model B2017G.
Click to expand...
Click to collapse
Oops... Sorry man, but there's no proven way(or probably just no way) of doing this kind of stuff on the Axon 7 mini. For some reason there are zero developers for that phone
The only other thing I can think of is to put a bunch of random patterns, then wait, then do that again until the phone decides to leave you put her Google account and password. I hope that works...
Or one other thing, but I'm almost sure this won't work: if the phone has Nougat, which I doubt, you can look over at zte support if there's a Marshmallow system zip. Download it and extract the zip that's inside the zip, then throw it inside an SD card, put it in the phone, then go to the recovery and select to flash update, select it. It should wipe everything to oblivion.
---------- Post added at 01:42 AM ---------- Previous post was at 01:28 AM ----------
MasterDDF said:
Is there a walkthrough on unlocking the bootloader? I haven't messed with getting that done before.
Click to expand...
Click to collapse
Wait - even better, there seems to be a factory reset option. Look at this:
https://forum.xda-developers.com/axon-7-mini/help/b2017g-forgot-password-factory-data-t3596774
Choose an username... said:
[/COLOR]
Wait - even better, there seems to be a factory reset option. Look at this:
https://forum.xda-developers.com/axon-7-mini/help/b2017g-forgot-password-factory-data-t3596774
Click to expand...
Click to collapse
Was worth a shot. But I don't even get a robot. Any other device I've owned I get the robot laying on the ground.
MasterDDF said:
Was worth a shot. But I don't even get a robot. Any other device I've owned I get the robot laying on the ground.
Click to expand...
Click to collapse
I don't know. If that phone hasn't got a recovery then ZTE is weirder than I thought. Try power + volume up or power + volume down, it has to do something...
Hello, MasterDDF. I'm afraid that the last maintenance update removed the factory reset option from the Android Recovery Menu, however, we've confirmed that an update will be released soon for the Axon 7 Mini device. Since you are unable to unlock the device, we're happy to repair or replace the device utilizing your warranty. If you'd like additional information or, have any questions or concerns, please feel free to contact our Support team at 1-800-617-5065 or, via our social media on Facebook ZTEUSA, and Twitter ZTE_USA.
ZTEUSA Support
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
back to bootloader and
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
pen101 said:
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
Click to expand...
Click to collapse
Hold power longer than 10 seconds (hard reboot) then volume down and it'll boot bootloader. From there flash a working boot image with working TWRP patched for the Rom you are on.
Sent from my PH-1 using Tapatalk
---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------
pen101 said:
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
Click to expand...
Click to collapse
https://www.youtube.com/channel/UCucUjVNJshybBA8JWftayVA check out my channel where I provide tutorials, reviews and files in links to complete pretty much any task for essential.
Sent from my PH-1 using Tapatalk
First and foremost,,,,
THANKS FOR THE REPLIES AND ADVISE.
Got up, drank a cup, dragged a brush across me head...booted up bootloader, hit on recovery mode and now back to square one with the latest pie flavor.
Sometimes you "over work" the problem.
As a mechanic I sometime got "stuck" and instead of getting frustrated, I simply walked away and came back to it, only to find (as with this) a simple solution.
I am expecting a tv box (PIE, 4 and 64)....should be a head scratcher.
Great forum, good peeps...MANY THANKS!