Hi My 2012 nexus 7 16gb wifi updated to 4.3 and since September 11th it will not factory reset, remote reset, sideload updates or unlock bootloader.
Every boot the same app update, even if I updated them all in previous boot minutes earlier, the nexus randomly reboots It's self too.
If I delete the data it returns on reboot, nothing I can do gets a different outcome, I'm not keen on returning it as is as all my data and accounts can be accessed in current state, even credit card through google play!
I waited for 4.4 to be released in the hope the update might cure this, but I cannot update it, please advise on how I might fix this or completely wipe my nexus?
Thanks
Use wugfresh's toolkit to redo your install. It will restore it to a factory state. The only problem people seem to have is getting the drivers installed properly, so it may take you a little while. Just be patient and follow the instructions and/or go to the thread for help.
http://forum.xda-developers.com/showthread.php?p=28616745
Sent from my Nexus 7
mssam said:
Use wugfresh's toolkit to redo your install. It will restore it to a factory state. The only problem people seem to have is getting the drivers installed properly, so it may take you a little while. Just be patient and follow the instructions and/or go to the thread for help.
http://forum.xda-developers.com/showthread.php?p=28616745
Sent from my Nexus 7
Click to expand...
Click to collapse
Hi have tried every option on the toolkit, adb and fastboot drivers are working ok, but it reboots as part of the install and goes back to previous state!
also tried http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and got this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What options did you select? Did you try Flash Stock +Unroot >Current: Soft-Bricked/Bootloop? I actuary have a n7 2012 that I need to redo to factory state, so I'm going to do that with wugfresh's toolkit and see where we differ...
Sent from my Nexus 7
mssam said:
What options did you select? Did you try Flash Stock +Unroot >Current: Soft-Bricked/Bootloop? I actuary have a n7 2012 that I need to redo to factory state, so I'm going to do that with wugfresh's toolkit and see where we differ...
Sent from my Nexus 7
Click to expand...
Click to collapse
Hi, I have tried every option, even the advanced options, part of the process is booting and as soon as the nexus reboots its back to original state, same with factory reset :crying:
That is strange. If you did fastboot erase user data and that didn't wipe everything idk. What about mskip's toolkit? I remember a while back wugs kit didn't work for me, but mskips did. Did you try his toolkit?
Sent from my Nexus 7
mssam said:
That is strange. If you did fastboot erase user data and that didn't wipe everything idk. What about mskip's toolkit? I remember a while back wugs kit didn't work for me, but mskips did. Did you try his toolkit?
Sent from my Nexus 7
Click to expand...
Click to collapse
Hi, yes I tried version 5.0 with no joy!
This is what happens when I try to adb sideload image-nakasi-krt16o.zip
Signature verification failure
So when I'm there I do a factory wipe, all successful till I reboot and everything is as it was previously!
scumgrinder said:
This is what happens when I try to adb sideload image-nakasi-krt16o.zip
Signature verification failure
So when I'm there I do a factory wipe, all successful till I reboot and everything is as it was previously!
Click to expand...
Click to collapse
I just flashed the 4.4 update on the nexus 7 2012 using wugstoolkit. At first when I downloaded the factory image and tried to flash it, it wouldn't wipe the tablet like you said and flash the update. Then I started playing with the locks. I think I chose to relock it, unlock, then flash stock + unroot and it worked. If you haven't figured it out, that's what it seemed to take for it to work for me...
mssam said:
I just flashed the 4.4 update on the nexus 7 2012 using wugstoolkit. At first when I downloaded the factory image and tried to flash it, it wouldn't wipe the tablet like you said and flash the update. Then I started playing with the locks. I think I chose to relock it, unlock, then flash stock + unroot and it worked. If you haven't figured it out, that's what it seemed to take for it to work for me...
Click to expand...
Click to collapse
It won't unlock! The 4.4 ota update downloaded, but it to led to 'no command' then reset to original state as always.
scumgrinder said:
It won't unlock! The 4.4 ota update downloaded, but it to led to 'no command' then reset to original state as always.
Click to expand...
Click to collapse
I followed those instructions from laptopmag and the worked to the tee. You shouldn't have needed to sideload anything. You had it unlocked at first, so what do you mean "it won't unlock?" You can see it in your screenie below, and I can also see that the fastboot commands were working so there wasn't a driver problem. What did you do after you did the fastboot oem unlock command in the screenie below? Did you fastboot the bootloader, then the factory image.zip? It looks like everything was working for you as it should, so what happen? I've done the laptopmag instructions two times and every thing is working fine for me; the tablet was erased both times as well. I'm curious at what point in the laptopmag instructions are you experiencing the problem?
scumgrinder said:
Hi have tried every option on the toolkit, adb and fastboot drivers are working ok, but it reboots as part of the install and goes back to previous state!
also tried http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and got this
Click to expand...
Click to collapse
mssam said:
I followed those instructions from laptopmag and the worked to the tee. You shouldn't have needed to sideload anything. You had it unlocked at first, so what do you mean "it won't unlock?" You can see it in your screenie below, and I can also see that the fastboot commands were working so there wasn't a driver problem. What did you do after you did the fastboot oem unlock command in the screenie below? Did you fastboot the bootloader, then the factory image.zip? It looks like everything was working for you as it should, so what happen? I've done the laptopmag instructions two times and every thing is working fine for me; the tablet was erased both times as well. I'm curious at what point in the laptopmag instructions are you experiencing the problem?
Click to expand...
Click to collapse
It all appears to unlock, but lock state staus is always Locked
same as factory reset works fine, till it reboots to its default state!
I'm convinced its a hardware issue
I have EXACTLY the SAME problem
It really is an impossible problem. NOTHING will fix it!
I too am convinced it is a hardware problem.
I have given up & bought a 2013 version.
Let us know if you succeed....
scumgrinder said:
It all appears to unlock, but lock state staus is always Locked
same as factory reset works fine, till it reboots to its default state!
I'm convinced its a hardware issue
Click to expand...
Click to collapse
Never got this fixed, still in a drawer, anyone got any ideas?
The same thing happened to my 2012 as well.
Related
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kroenen66 said:
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
Click to expand...
Click to collapse
Yes it would appear you have a developer Rom and I doubt it would be useful to anyone. Basically you have two options:
1) Send it back to Google for a replacement. (Could end up waiting a number of weeks)
2) Flash the Factory Image for the Nexus 10 which can be found at:
https://developers.google.com/android/nexus/images#mantaray
This will load the final release of JB which should be already on your device and you could be up and running in 15 mins.
dr9722 said:
Yes it would appear you have a developer Rom and I doubt it would be useful to anyone. Basically you have two options:
1) Send it back to Google for a replacement. (Could end up waiting a number of weeks)
2) Flash the Factory Image for the Nexus 10 which can be found at:
https://developers.google.com/android/nexus/images#mantaray
This will load the final release of JB which should be already on your device and you could be up and running in 15 mins.
Click to expand...
Click to collapse
If I flash the factory image .... I have restrictions? in comparison .....to take it back to Google for a replacement???
What is the better option?
When the flash is just as good .... how / with what do I flash it?
Kroenen66 said:
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
Click to expand...
Click to collapse
Kroenen66 said:
If I flash the factory image .... I have restrictions? in comparison .....to take it back to Google for a replacement???
What is the better option?
When the flash is just as good .... how / with what do I flash it?
Click to expand...
Click to collapse
if you flash the factory image you will then be the same as everyone else, no restrictions whatsoever.
Follow this guide:
http://androidtobe.blogspot.co.uk/2011/12/galaxy-nexus-installing-ics-402-from.html
That is for the Galaxy Nexus however the same commands still apply. Just ensure you download the correct Factory Image and change the file name where appropriate.
dr9722 said:
if you flash the factory image you will then be the same as everyone else, no restrictions whatsoever.
Follow this guide:
http://androidtobe.blogspot.co.uk/2011/12/galaxy-nexus-installing-ics-402-from.html
That is for the Galaxy Nexus however the same commands still apply. Just ensure you download the correct Factory Image and change the file name where appropriate.
Click to expand...
Click to collapse
The Factory Image is no Problem:
https://developers.google.com/android/nexus/images
If I make an error in an entry, I can restart the process again or is my Nexus 10 dead/Bricked/paperweight?
Isn't there any solution to "reset" to normal state without going to unlock process and flashing all partitions manually ?
what is the normal way to get back to org. Image when "normal Nexus 10" devices are out of order ?
We urgently need root and CWM on this tablet ...8)
fogbav said:
Isn't there any solution to "reset" to normal state without going to unlock process and flashing all partitions manually ?
what is the normal way to get back to org. Image when "normal Nexus 10" devices are out of order ?
We urgently need root and CWM on this tablet ...8)
Click to expand...
Click to collapse
The normal way is to restore the device using the correct nexus factory image for your device then executing the flash all script included with the factory image. This script will flash all the necessary partitions for you and reset your device to factory stock. This method doesn't require unlocking the bootloader and doesn't require root.
Sent from my SCH-I535 using xda premium
shimp208 said:
The normal way is to restore the device using the correct nexus factory image for your device then executing the flash all script included with the factory image. This script will flash all the necessary partitions for you and reset your device to factory stock. This method doesn't require unlocking the bootloader and doesn't require root.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So - can you give us the link to the "right" image - and write 2-3 lines how to flash ? Volume up/down Power to stock recovery etc. Copy image to where ... etc ... this would be wonderful ... thank you so much ...
Nexus 10 Factory Image:
https://developers.google.com/android/nexus/images#mantarayjop40c
You also need to set up the Android SDK, especially adb and fastboot.
Reboot to bootloader:
adb reboot-bootloader
When in fastboot mode, you can start flashing the factory images.
flash-all.bat does all the work for you.
But make sure, adb AND fastboot is working inside CMD!
Thank you very much ... we will give it a try ... even if i don't know how many user get a developer version of the Nexus 10 ... this order was normaly done ... and we were some kind of surprised when the tab was started ...8)
Oh Google .. something went realy wrong this time ... 8)
Interesting that you're the second person to have this debug ROM installed and both of you are in Germany.
Me too, same here, living in Germany.
So yeah. As the title says I had a rooted VS980 on 4.4.2 with some bloat removed and I accidently hit the wrong button when prompted for the upgrade, I was in a hurry. yes, I'm a moron, and yes, I know this is probably wasting someone's valuable time and I thoroughly apologize for my n00bishness
having said that, I have tried to go through various tuts but none of them seem to be working. yes, it's likely that I am simply doing it wrong, but whatever the case I am stuck with my phone in a bootloop always returning to the TWRP recovery. I believe that means it is soft bricked so I'm hoping this can be fixed fairly easily with the right direction and some patience for my ignorance. I can't seem to get it into download mode with turning it off, holding the volume+ button and plugging it in, it just goes to twrp. :'(
my hope is to get a rooted lollipop. if that is not possible then I would be fine with going back to stock or possibly even a custom rom if it's not too awfully complicated. honestly, I'm at a point where I'm beginning to accept that I probably shouldn't be screwing around with it too much and will likely bite the bullet and just keep my phone stock since there are really only a few minor irritants that make me want to root it.
any help is very much appreciated.
anybody? pretty please? any ideas at all?
Deviouz1 said:
anybody? pretty please? any ideas at all?
Click to expand...
Click to collapse
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
a.perkins89 said:
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
Click to expand...
Click to collapse
actually, it doesn't look to be the same problem. i dont have download mode, but i do have recovery. it boots to twrp like a champ. what i think i really need is how to get the flash file VS98011A_01.zip on my phone via ADB Sideload, specifically when i cant get the drivers to work.
i've tried the following drivers:
LG_VZW_United_WHQL_v2.14.1.exe
LG_VZW_United_WHQL_v2.20.0.exe
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1_3.10.1.0
I may very well be mistaken about what needs to happen, i'm no expert, obviously, but from everything ive read any of those should have worked. i think if i can get the right flash on the phone i should be able to flash it via twrp no?
I"ll help
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Jaqueezzzy said:
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
awesome,thanks you, i'll try that!
Deviouz1 said:
awesome,thanks you, i'll try that!
Click to expand...
Click to collapse
Just so you know it talks about flashing a ROM, but just use the zip you need insted, because it's the same principal.
Step 9 Fails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i just happened to have a brand new data cable, tried again with same result so its not media related unless there is an issue with the plug itself, but it's charging and the Device manager shows the correct name ie VS980, it just has a yellow bang on it and i cant find a driver that changes that.
read some more and found others with the same issue apparently which led me to here: http://forum.xda-developers.com/showthread.php?t=2715408
which is where i found the "download mode restore" file you mentioned(i didnt see it in the thread you provided), but without the ability to get adb usb command to work i dont see how i can use it.
any ideas?
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
siggey said:
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
awesome, ty sir. i happened to have one of those laying around from when i cracked my screen on my old one and couldnt interact with the screen. took a while to find it buried but i have it and i have successfully been able to access a thumb drive. i think that might be all i need.
will report back though regardless.
ok, now i'm rrrrrEEAALLYY freakin confused...
successfully flashed (via the install section of twrp with usb otg thumbdrive mounted.)
xdabbeb_vs98028a_bootstack.zip
and
xdabbeb_vs982.5_1.1.0.zip
from
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
but when i reboot, it goes directly to twrp still.
wat? :'(
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
WOO-FREAKIN-HOOOO!!!
at the setup wizard now.
Deviouz1 said:
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
Click to expand...
Click to collapse
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
thecadman99 said:
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
Click to expand...
Click to collapse
sweet, i'm glad someone else found it useful.
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
thecadman99 said:
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
Click to expand...
Click to collapse
Is your baseband recognized by chance?
Deviouz1 said:
Is your baseband recognized by chance?
Click to expand...
Click to collapse
Nope... its UNKNOWN
And I have not download mode
And I have not cdc serial showing up when connected
And TWRP and Root are gone
I'm starting a new thread for help- I've been working on this for 2 days lol.
Thanks for the reply!
Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!
Tgab100 said:
Hey all,
So i recently flashed back to stock and since my mobile radio has just stopped. Does anyone have this same problem, or can anyone help me fix this problem? Thanks!
Click to expand...
Click to collapse
You'll need to elaborate on how exactly you flashed back to stock.
Heisenberg said:
You'll need to elaborate on how exactly you flashed back to stock.
Click to expand...
Click to collapse
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.
Tgab100 said:
I flashed back to stock using the Nexus Root Toolkit by Wugfresh. I just flashed CM 13.0 to see if the problem was a hardware malfunction, but the mobile radio worked while running cyanogenmod. I am not downloading the factory image and I am going to attempt to flash it manually. Any ideas of comments? I really have not clue as to why the radio isn't working other than that it might be caused by flashing through the Nexus Root Toolkit.
Click to expand...
Click to collapse
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Yeah, probably due to the toolkit. This is why I recommend people not use the damn things. Flash the factory images and you should be fine, I have instructions in my guide if you need them.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.
Tgab100 said:
So i was thinking that the system I'm running right now with the broken radio is corrupt so when i flash the factory image, is there a way I can erase everything? I want to make sure I'm flashing the image clean.
Click to expand...
Click to collapse
If you flash the factory images they overwrite what's already there.
Heisenberg said:
This is why I recommend people not use the damn things.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heisenberg said:
If you flash the factory images they overwrite what's already there.
Click to expand...
Click to collapse
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.
Same here with SkipSoft Toolkit, after unlock, root, busybox, wifi noproblem, but no LTE/3G on my phone, i try to relock bootloader and back to Factory image now.
Sigh!?!
Tgab100 said:
So I flashed the factory images using your method provided and I am still having the same issue Let me describe a little more in detail what exactly is going on. So obviously mobile data isn't working, including LTE 4G, 3G, and 2G, but I get calls and texts no problem. When I look at my status bar, LTE is not showing up, but if I pull down the quick toggles the phone says I have LTE connection but no data is coming in or going out. LTE also loses connection when I turn off "Enhanced 4G LTE Mode" (I'm on T-Mobile). Additionally, when I create a mobile hotspot, data works but only on 3G speeds. I honestly don't know what I'm doing wrong. Maybe i'm flashing the wrong factory image? I flashed MDB08M.
Click to expand...
Click to collapse
I honestly don't know what's going on there, it might be worth trying the L build instead of M.
Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.
badboy47 said:
Can you download latest nexus 6p android m image and flash each file manually? It's going to wipe everything but will return everything to stock. Let me know if you need help with flashing stock files via adb.
Click to expand...
Click to collapse
I seem to have touched that issue I was on the L build and went to M build using toolkit but noticed my apns got screwy so I corrected them and I'm on pure nexus and a-ok now!
I'm having a similar but different issue, I bought a used 6p... Good ESN.... A 64 GB to upgrade from my current 32 GB 6p. Everything works (including mobile data and texts) except for phone calls, it won't call out and goes strait to voicemail when calling in.
I had unlocked the bootloader and installed chroma, but still no phone calls, so I flashed back to stock and relocked the bootloader. Still nothing. I read this thread suggesting that I shouldn't use the automated tool kits, so I backed up and manually flashed it back to the latest stock image via fastboot. But same issue.... Back to no phone calls in or out, everything else working though.
Any suggestions?
Justin
For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?
kboya said:
For those of you experiencing this, are your still able to see your imei number through settings>about phone>imei info?
Click to expand...
Click to collapse
For me, yes. I can see my imei from the normal "about phone" settings menu.
Justin
Delete and readd your APN for your carrier.
Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.
+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk
Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.
sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download
hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning
I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.
So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
October Security Update just released today.
Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
CAPTCHA:
After clean fastboot flashing of this version with flash_all_except_data -> rebooting phone forces to stock recovery and requests factory reset.
Seems like after installing OTA possible behaviours are: either the same request for reset, or bootloop.
Reflashed back V11.0.14.0.QDIMIXM in order to make data backup
Aerobatic said:
Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
Click to expand...
Click to collapse
nice! thanks for this!
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Yes, the update seems buggy.
Even my phone was not able to start after the update.
Tried multiple times. Eventually had to factory reset it ?
xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse
update works fine for me with no issues at all.
xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM
So this is yet another botched update to skip, got it.
Thank you, brave ones who are willing to update first.
I'm just too afraid to update this device nowadays.
I had to reset device after last update this is really worst device support I had
For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop
updated successfully. there are no visible improvements
gromez said:
For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop
Click to expand...
Click to collapse
Try to switch to inactive slot.
How is your experience with stock rom and october patch?
HTCDevil said:
How is your experience with stock rom and october patch?
Click to expand...
Click to collapse
for me, it's snappy and stable.
Same problem here, unacceptable
Failed install here too, had to do a full reset
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
PereVidi_77 said:
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM
Click to expand...
Click to collapse
I tried unsuccessfully to reboot, Everytime showed this message, finally I accepted to erase the phone and let download the backup, I lost some downloaded stuff I may download again later.
It's an Shane this happening to Android one devices, suddenly we got from special to second class citizens
I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one
oferwald said:
I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one
Click to expand...
Click to collapse
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2
maxou88 said:
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2
Click to expand...
Click to collapse
Hi,
All I did was go into fastboot using the power and volume shortcut, and than I connected the device to my laptop and issued the command:
fastboot reboot recovery
(naturally using the SDK Platform tools)
After that, the phone started working again. Although there is no reasonable reason it should have worked. I was surprised enough so that I decided to take the effort to create an account here and share this for others. But again, maybe it was pure luck, YMMV.
Will be crossing my fingers for you.
I've tried to update and got the "Can't load Android system. Your data may be corrupt" messege. Tried again a few times, until the phone reverted back to the previous version and said it couldn't install the update. No October update for me. =(