Related
I've been working on this for the past week. Every exploit I've tried just hangs after a while. I've gotten much further manually. I've got unbuntu and been working using various manual methods. The thing I've noticed is that there is no system folder in root. There is a system partition in which app and bin folders exist. Later today I'm going to have time to try some more. If it weren't for these silly rules id reply to somebody elses post, but I guess reading in forums for 3 years as a registered user doesn't count. Never a need to post as I've always found something using a search. And now I've got a phones that's been out for a week and there's no info out on it so I guess I get to develop myself. Not a hard thing...just time consuming and I've got better things to do, but these pink apps gotta go and I need wired or wireless tehter again. Hopefully I have succcess later today and can post how I accomplished it.
I'll be waiting anxiously. please post updates in this thread with your progress!
Any progress on this? I have been attempting but no luck.
update on progress
jb0ne said:
I'll be waiting anxiously. please post updates in this thread with your progress!
Click to expand...
Click to collapse
ok so here's what i've learned so far from trying every method that i can find...
when you boot the phone into the pink screen (volume up and volume down plus power) there is a partition containing 1 folder with 5 files. That folder is called image and the file inside are amss.mbn, boot.img, cust.img, emmcboot.mbn, and recovery.img
The Ascend G300 is a similar phone to the G312 and there is a filed called superrecovery which changes the recovery to set ADB with root priveliges and installs SU in system. If we use the recovery from that batch file made by PauloBrien and push it to the device while in pink screen mode and then reboot into recovery the phone won't power on. You can return to the pink screen and change back to the original recovery, but you can not boot the device into recovery nor regularly. Now this gave me an idea as i'm typing. what if i change it and issue the command in ADB as ADB works during the pink screen. I'm going to try that now.
But this can't be done when in bootloader, only in pinkscreen which makes me think it's fastboot USB mode, but fastboot commands dont work uless you are in the bootloader with the huawei logo which you can only get into by issuing the reboot-bootloader command through adb. once you enter bootloader mode via ADB reboot command then you are able to issue some fastboot commands.
ok so that didn't work...basically when the files in the imge folder are changed the device won't boot into anything but the pink screen mode.
the original recovery file size is 6340KB and the one from PauloBrien is smaller at 5074KB. I'm wondering if file size has something to do with why it won't boot, however, i'm not familiar with what's inside of these files. So...as i reasearch how to build our own clockworkmod recovery i'm wondering if there's a way to change the ADB command inside from not root to root. if it's a on off selecton i'm not sure how i'd affect file size. this is where we get into the realm of knowledge that i don't possess.
so if anybody can offer up some knowledge from where i stand now... please do so.
on a side note, when running exploits, (gingerbreak, zergrush, doomsomething, psneuter, etc)...they all hang.
in linux when trying to drop a file into /system/bin the terminal read out says something about failing to cycle power, not certain what this means.
as i learn a bit more, i'll go ahead and add more...
I am hopeful to hear back from you with a successful root method for this device. I myself just purchased this phone for myself and would really love to see more development on it. Seems like a solid phone with a low entry price. Look forward to seeing what you come up with.
I'm also waiting anxiously for someone to figure this out. I just got this phone and while I really like it, there is just so much packed on this thing that I want to get rid of before I can really enjoy the phone.
I'll be watching this thread as well hopefully OP or someone else will figure out the trick to rooting this phone, like others I have used the usual methods but no luck. I've counted no less than 13 programs I'd uninstall right off the bat.
For what its worth the phone seems to not be considered part of the Ascend models of phones although they are quite similar our model is called the Unite U8680 and the Unite Q U8730 (the slider version). I've sent a email to Huawei lets see if they respond at all.
It's pretty much useless but this is all I can find on the G312 on the Huawei website:
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=4086&tb=0
I'll be watching this thread as well. According to a post on another forum regarding a different Huawei model, dialling *#*# 2846579 #*#* and making some changes in the log file settings suddenly made their phones rootable for some reason. However while the same # gets you into the service mode on this phone, the log file changes made no difference.
I wonder, though, there are quite a few other options in that service mode. Maybe something in there that could be useful.
Edit: There's one menu that looks interesting, the USB one. You can change it to all sorts of modes including "Manufacture mode" whatever that is. Afraid to try it, don't want to brick my wife''s new phone
I've been playing with this menu as well and some of the USB modes do seem interesting. I was hoping this would let me find the product ID for the phone cause I found a link on the Huawei homepage to register to get an unlock code for the boot loader on this phone. If anyone is interested here is a link to the page and sadly the method they say to find the product ID doesn't work on our phone.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
huawei says the product ID is an 8 digit number. I've been trying to dump the log files so i can scan them for some kind of 8 digit number. i've also tried all the different USB modes as well as a few other changes in the project menu that we're able to access. These haven't given me any success in changing the ownership of the folders needed to gain root access. i've not had any time to tear apart the recovery image to figure out what it's doing. but all in due time somebody will figure this out. still haven't been able to get fastboot to work properly either. am running through the usb modes on that now.
Yes please help i cannot figure out out either
builder.clockworkmod.com
so i've been working on building a recovery image for this devices using koush's site and have been able to build it, but the device won't boot into recovery yet. not sure how to fix this, gonna mess around and keep on trying. i can get it to boot back up and can get it to respond to adb commands when in the mode that just shows the android 4g logo. but i can't get into recovery. not through adb and not through using the power and volume buttons.
still working on it... any body else have anything yet?
No info on rooting this phone but Huawei just posted on their website the open source gingerbread kernel for the G312 U8680 here is a link to it:
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3MzU=
It's been rooted!
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
jb0ne said:
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
Click to expand...
Click to collapse
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
jamonthis said:
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
Click to expand...
Click to collapse
If you figure it out and find anything out I would love to know about it. Where should I watch for an update in case someone does get that sorted out?
Recovery mode
There is an accessible recovery mode, at least on my querty version of the phone. You have to completely pull the battery first. Put the battery back in, hold Volume up, and then hit power. I held the power button for a couple seconds, and volume up for maybe 6-8 seconds, then started hitting volume up repeatedly. The key is to pull the battery each time you try, I think. It looks like powering off from the phone's power menu just puts it in a suspend sort of mode. (Compare boot times when rebooting, and when pulling battery)
Apparently the bootloader is locked, so not sure how useful it is yet.
For anyone with a T-Mobile MyTouch Q (Huawei U8730), I created a wiki page for it, and we should post in the New Device Forum Requests thread so we have a specific place to post info.
I just purchased a U8730 today and will definitely be figuring out how to root it at some point.
For anyone that cares here's a link in case you haven't registered at the other site.
http://j.gs/1U5q
I'm hoping we can get some development going for this phone. I just picked one up for my daughter a month ago and it's giving her memory filled messages already. It'd be great if we can get it permanently rooted and remove bloat to start... then possibly move onto Cyanogen... considering she had the horrible Comet (also by Huawei) previously and it had development for CM7. I may be taking a leap from my contract soon, but can't go to Straight Talk with her phone unless it's unlocked
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).
Read here :
http://www.androidauthority.com/android-wear-update-interactive-watch-faces-635676/
download here :
https://android.googleapis.com/pack...signed-anthias-LCA43-from-LDZ21T.18fa3a21.zip
Step to update
1. Set up ADB (numerous tutorials on the internet)
2. Connect your watch via the charging block to a USB port on your computer
3. In the Settings menu on the watch, go into "About"
4. Go down to where it says "Build Number" and tap on it a bunch of times until the toast message says "You are now a developer!"
5. Swipe back one menu and head into the new menu that showed up below About, called "Developer Options."
6. Enable "ADB Debugging." At this point your computer should recognize the watch and take a few seconds to install the proper drivers
**6a.** Unlock your phone, and check the box that says "always allow from this computer" and accept the authorization by clicking "OK"
7. Open up a command prompt on your adb folder and type "adb reboot recovery"
8. Once you get the Android with the red triangle, swipe down to bring up the menu, and swipe down again to select "Apply update over ADB"
9. Swipe **left or right** and orange text should pop up that says "Now send the update via ADB"
10. Back on the computer, type "adb sideload C:\whatever\path\to\otafile.zip" (replace that with the actual path)
11. It will take about 5-7 minutes to update, once it's done the menu with the Android and red triangle should pop back up.
12. Make sure "reboot" (the first option) is selected (you may have to swipe down to bring up the menu again) and swipe **left or right** to select it and reboot the watch.
Voila, after rebooting, you should be on build LCA43.
I got mine OTA last week. It seems more stable, has added functionality and has restored my battery life to 36-48 hours (it went down to 24-30 hours with the previous upgrade). A big improvement.
Willber G said:
I got mine OTA last week. It seems more stable, has added functionality and has restored my battery life to 36-48 hours (it went down to 24-30 hours with the previous upgrade). A big improvement.
Click to expand...
Click to collapse
I've only been running it for a little over a day, but I agree, it seems smoother and more responsive to me.
I have to give this a shot , since I got my watch back from RMA I only get about 12 hrs of battery life.
Followed the instructions to a "T" and am told it doesn't see the device, even though it rebooted it into recovery. I did install the drives and so on.
Oh well, I'm getting great battery with the Text Watch face.
dirtybudha said:
Followed the instructions to a "T" and am told it doesn't see the device, even though it rebooted it into recovery. I did install the drives and so on.
Click to expand...
Click to collapse
Mine did that the first try, because it doesn't load the needed driver until after you start the update function on the watch. So the first time through, doing the "adb sideload ______" failed saying it couldn't find the device. I just issued the command again, and by that time the driver had loaded, and it worked.
Hhmmmmm, perhaps i need to wait a few minutes for my computer to load everything. I tried using the command a few times.
Glad to hear I'm not crazy. I mean i can root a phone and I'm pretty sure i can do this.
Update: Nooooooope, recovery times out. Huh, not sure what could be wrong. I'm on Windows 10, but that shouldn't be the issue.
Oh well.
BOOM, shalakalaka
dirtybudha said:
Update: Nooooooope, recovery times out. Huh, not sure what could be wrong. I'm on Windows 10, but that shouldn't be the issue.
Oh well.
Click to expand...
Click to collapse
How new (or old) is your adb? The one I used is dated 12-9-2014. I know I had problems with an older one the last time I did one of these updates manually.
Hello to Dallas, BTW. I lived in Plano and then Murphy for 13 years. Our youngest two kids were born there. Been back in our hometown in IL for 10 years now, though.
Here's the one I got, the version number seems to be the newer one.
http://forum.xda-developers.com/showthread.php?t=2588979
Hey! I'm over in Far North Dallas, near Addison. Looking to move to the Plano/Richardson area in the fall. I'm actually from Austin.
CSX321 said:
How new (or old) is your adb? The one I used is dated 12-9-2014. I know I had problems with an older one the last time I did one of these updates manually.
Hello to Dallas, BTW. I lived in Plano and then Murphy for 13 years. Our youngest two kids were born there. Been back in our hometown in IL for 10 years now, though.
Click to expand...
Click to collapse
Download and install PDA net. Its drivers work with CSC Fastboot mode on the Zenwatch.
I just wait for the OTA updates - am I missing something?
Sometimes we like to install before the OTA hits.
Update: OTA came through.
Update 2: AAAND I lay the touch screen ability. Oy.
Willber G said:
I just wait for the OTA updates - am I missing something?
Click to expand...
Click to collapse
BOOM, shalakalaka
I'm on the June security patch and I haven't been able to update anything OTA even though I have an AT&T SIM. Is there someway to force the Software Update check to work properly by using a pm command in the shell? Do I need to sideload the firmware to get it update to OREO and if so, what is the command and where can I find the full file. Any help would be useful.
please go here: https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/XT1789-04/
download the at&t rom for your device.
unzip into platformtools.
and run these commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
let me know if this helps you get back on track with being able to update from AT&T
i have used this in a bat script to install the AT&T rom on the tmobile hardware, then i was able to go back to stock once more and install updates.
Do these commands work on a locked bootloader which AT&T has? Does someone have a good understanding of how the following packages work regarding ota updates?
com.motorola.ccc.devicemanagement
com.motorola.ccc.checkin
com.motorola.ccc.mainplm
com.motorola.ccc.ota
com.motorola.ccc.notification
I was wondering if i could clear out the cache of one of them or disable then re-eanable one or more of them would that possibly fix my ota problems?
I am having the same issue, the phone is stuck on the June patch and no matter what I do I can't get any updates, nor will adb sideload or install update from zip in recovery work.
edit:
got it working, if you are still stuck on June security patch just download the AT&T update from the 2nd post above, put the phone into bootloader mode, and unzip the attached bat file in the folder then run it (ensure you have the Motorola drivers installed). as soon as I rebooted and set up I checked for updates and it started downloading the new 8.0.
DISCLAIMER: for AT&T Z2 Force models.... will wipe data.... this worked for me may not work for you... use at your own risk.... it's you not me.... this is your choice.
i did the same, now i have november update but i didnt get the oreo update afterwards.
Install the stock rom
Is there any way to flash the downloaded stock rom from post 2? No further OTA update
What do you mean will wipe data
Mrgabi said:
What do you mean will wipe data
Click to expand...
Click to collapse
It will wipe everything from your phone like a factory reset so make sure you have a backup of whatever you need to reinstall.
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next.
Thanks,
Click to expand...
Click to collapse
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
kingstu said:
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
Click to expand...
Click to collapse
OK well, I bought it on Swappa it was new (resale) so the box was opened but everything else wasn't and still had the plastic on it. So I contacted Motorola on their support forums and they said to just wait a little while and see if it'll update but too they also said they'd have someone take a look into it as they have my IMEI number so I guess will see what they say.
Thanks for the reply
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hello, Just checked and it says my warranty expires Sep 2018. So hopefully it shouldn't cost. Now though if I do return it I am assuming they'll just want the device nothing else and will they send me back a new device as this device is new no scratches or nothing and don't want to get back a device that has any marks or scuffs etc. Also, the first thing I did before even turning the device on was put on a tempered glass screen protector so I am assuming I'd take that off before I sent the device back to them. Either way, I hope I can get the issue fixed without having to return it but at least I know it's under warranty, Assuming that when it says Sep 2018 that once Sep 1st hits that the warranty will be expired?
Thanks again
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hey, I dropped my device off with FedEx on Sunday and Motorola said they received it yesterday, anyways just wondering how long your turnaround time. I have my Moto E4 that I can use so it's not the worst if I have to wait. Hopefully, it won't be too long especially if they're just going to send me a new device that should have Android oreo and updated security patches on it.
Thanks again for your advice.
Seems like it runs through script fine until the end
Script seems to run fine until the end. Phone wont boot and flashes at logo screen and then goes to bootloader logs saying your device didn't start up successfully. Need help. Can anyone help with this? I think the problem might be with the userdata not automatically formatting at the end. Nevermind, Everything all good after 3 or 4 tries. I still can't update to the latest build after flashing, which is OCXS27.109-47-11 according to what I looked @ att website. It says I have the latest version which is OCXS27.109-47-7. Anyone have the latest build to flash?
i had the same issue
I've used Lenovo Smart Moto Assistant and managed to get the last update
I have the same issue with T mobile. the phone says there is a new update, it downloads and tries to install but fails. I am on the May 2018 security patch, OCXS27.1.3. Android File Host and other sites don't list any new firmware. I have tried the Lenovo Smart Moto Assistant and it also doesn't recognize the new update. Any suggestions?
Oreo Update
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
Click to expand...
Click to collapse
westec2 said:
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
Click to expand...
Click to collapse
Hello.
I don't know if i did not understand correctly, but when I have the phone recognized to do the update, i turn it off, and since the PC stops recognizing it is connected, the lenovo smart assistant goes back to the sync page.
How could you achieve that? Do you have another setting on your PC or lenovo assistant software?
Do you turn it off before clicking proceed?
Do you turn it off while the "all information could be wiped" is on screen?
Do you turn it off when the "loading bar" starts?
Could you be more specific? I would like to update my phone.
Thank you.
ETA: I don't see a way to delete this topic so I'm just updating it. I didn't want to risk waiting another day to not have an answer since I'd already posted other places over the weekend with no response and we need it working for tomorrow morning, so I just went ahead and flashed the factory image from here:
https://developers.google.com/android/images
Everything is in order now! Tips for anyone else doing this, don't skip the step of adding the platform tools to the path environment variables. I did the first time and the flash script wasn't able to find some files because of it and aborted. Everything pushed to the tablet and installed fine after I added the tools folder to system variables.
**********************************************************
This is the only place where I see detailed answers so I registered to ask this.
Status locked/not rooted, just however I bought it when it released plus whatever OTA updates before I stopped using it. Dead in a drawer for maybe two years, I got it powering on again by disconnecting/reconnecting the battery then charging on my PC overnight via USB, but it kept booting to a black screen, no logo, no splash.
I went into recovery mode and did the wipe data/factory reset. I can now get to the welcome setup screen but there are two problems:
1) Errors immediately pop up blocking the screen, making it hard to choose anything because as soon as I hit ok to make an error go away, another pops up. It bounces between "android.process.acore/gapps/media has stopped" with "calendar has stopped/email has stopped" sometimes appearing too but it's mainly the first ones.
2) If I'm fast enough after dismissing an error, I can click next from the language screen to the wifi connection screen. SKIP is greyed out. I can select my wifi but when the password prompt comes up, no keyboard appears after clicking the field to enter one. It's just the blinking cursor.
Keep in mind the errors are still popping up too so I don't know if they're blocking things. I sometimes used a bluetooth keyboard with it, so I grabbed that and tried typing with it just in case and no luck.
Attempts​
I found a fix to try sideloading a factory image via the apply update via adb option in recovery mode, but the google site said it's safer to try sideloading a whole image OTA, so I tried that instead using the zip file there for Nexus 7 2013 wifi (I have 1st Gen but don't see that anywhere so this may be the issue too). After it hit 100% it was aborted for some reason I can't remember now.
But I do remember when I looked up whatever it said, most responses were that sideloading a whole image OTA won't work on devices that haven't been "unlocked" or something.
I found another response to someone with my problem, not having a keyboard after resetting, which said to sideload a keyboard app through adb. I found some gboard apk listed as the version for the Nexus 7 but when I did the adb thing, it aborted because of something to do with e-signature not being verified.
Question​
I can figure out trying to copy over a factory image but since I suspect the main issue now is the Nexus not having wifi access to complete setup then update/install what it needs to stop those errors, I consider that a last resort. So my question for now is for further help on getting a keyboard app or another way so I can type. If I still can't get things working after that, then I'll ask about the factory image.
Thanks!