Yesterday, I changed my shattered screen and I followed Le55on's tutorial. It worked for the rest of the day, and today, after class, I took it out and tried to unlock it, but it wouldn't respond. I rebooted it and tried everything, but it didn't work. Then I tried three fingers, and my input was recognized. But then I gave up and decided to wait until I got home. Then, when I took my phone out from my pocket at home, it worked perfectly. So far, the screen is still responsive. Could this just be a little problem that righted itself, or will I need to open it up? Thank you!
You could try apps from the play store that help calibration of the touch screen and touches as in amount of touches and see if that helps. Hopefully its just the new screen bedding in and should be OK.
Sent from my Nexus 4 using XDA Premium 4 mobile app
androidlosernoob said:
Yesterday, I changed my shattered screen and I followed Le55on's tutorial. It worked for the rest of the day, and today, after class, I took it out and tried to unlock it, but it wouldn't respond. I rebooted it and tried everything, but it didn't work. Then I tried three fingers, and my input was recognized. But then I gave up and decided to wait until I got home. Then, when I took my phone out from my pocket at home, it worked perfectly. So far, the screen is still responsive. Could this just be a little problem that righted itself, or will I need to open it up? Thank you!
Click to expand...
Click to collapse
bladebuddy said:
You could try apps from the play store that help calibration of the touch screen and touches as in amount of touches and see if that helps. Hopefully its just the new screen bedding in and should be OK.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=ru.tpyxa.android.multitouch
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
https://play.google.com/store/apps/details?id=ru.tpyxa.android.multitouch
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
bladebuddy said:
You could try apps from the play store that help calibration of the touch screen and touches as in amount of touches and see if that helps. Hopefully its just the new screen bedding in and should be OK.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did a calibration test, and it worked. Everything was fine. Just now, it stopped working again. I rebooted it twice and then it worked perfectly. Is this a software issue? What should I do?
androidlosernoob said:
I did a calibration test, and it worked. Everything was fine. Just now, it stopped working again. I rebooted it twice and then it worked perfectly. Is this a software issue? What should I do?
Click to expand...
Click to collapse
My guess would be to flash another rom and that might give you your answer. It might be as simple as the screen and digitizer separating from each other.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
My guess would be to flash another rom and that might give you your answer. It might be as simple as the screen and digitizer separating from each other.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Okay! So, just to go over the process again because I'm a complete amateur, Nandroid backup, Wipe, Flash new rom, flash new kernel, done.
You can flash the kernel afterwards, but you have the correct order.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
You can flash the kernel afterwards, but you have the correct order.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Okay, I'll make sure to report back!
Berrydroidcafe said:
You can flash the kernel afterwards, but you have the correct order.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Well, here I am being a stupid person. After 2 hours of painstakingly configurations of drivers, I can't flash PA. I wiped system, dalvik, factory reset, everything. Then when I flash PA 4.0 Beta, it fails. I don't know why this happens...
androidlosernoob said:
Well, here I am being a stupid person. After 2 hours of painstakingly configurations of drivers, I can't flash PA. I wiped system, dalvik, factory reset, everything. Then when I flash PA 4.0 Beta, it fails. I don't know why this happens...
Click to expand...
Click to collapse
What recovery are you using? How are you flashing it? (adb/toolkit)
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
What recovery are you using? How are you flashing it? (adb/toolkit)
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
So I ended up finding out that you have to upgrade the OS 4.2.2> 4.3>4.4>4.4.2 and now I have that done, and I've flashed CM 11 and it's working flawlessly. There's been no screen unresponsiveness so far and everything seems fine. Except now, I've flashed Matr1x 12.5 GPUOC and my color is getting distorted. Did I get the wrong file?
androidlosernoob said:
So I ended up finding out that you have to upgrade the OS 4.2.2> 4.3>4.4>4.4.2 and now I have that done, and I've flashed CM 11 and it's working flawlessly. There's been no screen unresponsiveness so far and everything seems fine. Except now, I've flashed Matr1x 12.5 GPUOC and my color is getting distorted. Did I get the wrong file?
Click to expand...
Click to collapse
I'm trying to figure out why you went through all of that when you could have flashed CM11 and been done with it.
I would say that the kernel is the problem. I would wipe everything, meaning a factory reset via the recovery and just flash CM11.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
I'm trying to figure out why you went through all of that when you could have flashed CM11 and been done with it.
I would say that the kernel is the problem. I would wipe everything, meaning a factory reset via the recovery and just flash CM11.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Wait what?! You don't have to?! I was on 4.2.2 originally, and I wiped CM10.2 before I flashed PA. It kept on failing, and I tried everything I could, but it wouldn't work. So I ended up updating the device step by step in order to get PA4. It ended up flashing correctly but my backup was gone, and now I need to start up from scratch. So Wipe>Flash CM11>Flash GAPPS> then Flash Matr1x?
androidlosernoob said:
Wait what?! You don't have to?! I was on 4.2.2 originally, and I wiped CM10.2 before I flashed PA. It kept on failing, and I tried everything I could, but it wouldn't work. So I ended up updating the device step by step in order to get PA4. It ended up flashing correctly but my backup was gone, and now I need to start up from scratch. So Wipe>Flash CM11>Flash GAPPS> then Flash Matr1x?
Click to expand...
Click to collapse
Yes, but don't flash the kernel until you get CM11 flashed.
1. Wipe
2. Flash CM11
3. Boot phone to make sure everything is good.
4. Flash gapps
5. Boot phone again and check things out.
6. Flash kernel.
If there are problems, it would be the kernel.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Yes, but don't flash the kernel until you get CM11 flashed.
1. Wipe
2. Flash CM11
3. Boot phone to make sure everything is good.
4. Flash gapps
5. Boot phone again and check things out.
6. Flash kernel.
If there are problems, it would be the kernel.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I've done exactly that, but it's still the same problem.
androidlosernoob said:
I've done exactly that, but it's still the same problem.
Click to expand...
Click to collapse
The only other suggestion would be to try another rom and the problem is still there, it might be a hardware issue.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
The only other suggestion would be to try another rom and the problem is still there, it might be a hardware issue.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
So I've tried out Hells Core and everything is working well so far! Thank you so much for all your help!
androidlosernoob said:
So I've tried out Hells Core and everything is working well so far! Thank you so much for all your help!
Click to expand...
Click to collapse
No problem. Hope everything works for you from now on.
Sent from my Nexus 7 2013 using Tapatalk
Related
I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?
Go back to recovery, factory reset, wipe caches and reflash
Sent from my Nexus 7 using xda app-developers app
Try long pressing the power button to turn it off and try booting again. Sometimes it hangs on boot after flashing. Especially with certain kernels.
Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.
SpazticWonder said:
I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?
Click to expand...
Click to collapse
chivo559 said:
Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.
Click to expand...
Click to collapse
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Apocalypse487 said:
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!
chivo559 said:
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!
Click to expand...
Click to collapse
So you fixed it? I updated the bootloader before updating PA to any newer versions. I haven't had bootloops. I followed the DROIDMODDERX video on YouTube when I was on 4.1.1. In the tool kit thread it tells you how to update.
Sent from my SAMSUNG-SGH-I747 using xda premium
Reboot error related to paths?
I flashed my N7 a few weeks back (using goomanager) with 4.2 JB which worked fine. I then put on gapps and got an endless loop of error messages about trying to configure them. At this point I rebooted to recovery and put back on rooted stock 4.1.1.
I thought I would try PA again this week and the ROM flashes OK, but when I reboot the N7 "hangs" at the boot screen and goes no further. The same thing happens if I try SmoothROM. I can go back to rooted stock OK though.
I notice the paths have been updated as per 4.2 but otherwise things appear the same as before.
Any idea why PA now won't boot?
Thanks
mik
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
MERKJONES said:
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
Click to expand...
Click to collapse
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
simms22 said:
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
Click to expand...
Click to collapse
I tried clearing the data from the phone app. I can reboot and clear dalvik again. I also flashed http://forum.xda-developers.com/showthread.php?t=2127498 and it's still acting up.
are you using any mods or themes?
simms22 said:
are you using any mods or themes?
Click to expand...
Click to collapse
Nope.
MERKJONES said:
Nope.
Click to expand...
Click to collapse
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
simms22 said:
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
Click to expand...
Click to collapse
I did a clean install and manually installed all of my apps again. I managed to fix it by dirty flashing the 4.2 version of AOKP. However; my phone still has that random reboot issue. The thing that's odd is, when it comes back online it loses it's settings. So I'll have to setup Google Wallet and Google Voice again. My keyboard goes back to the default AOSP one.
I think I might just RMA this phone and start over. I do love it, and the negatives don't outweigh the positives.
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
molesarecoming said:
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
Click to expand...
Click to collapse
Um... I had the problem on stock 4.2 as well, factory from Google themselves. It rebooted at random for no reason. I have wiped everything... multiple times. It's still doing it.
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
MERKJONES said:
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
Click to expand...
Click to collapse
i just used the stock 4.2.1 ROM and kernel. I am using the backup I made for my phone when i first rooted my phone. I don't a copy of the that. try using WUG rooting kit. u should be able to load it in that way. good luck. i missing flashing custom ROM, but I need my phone call to work. and by the way my last custom ROM was AOKP.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can always follow efrants guide to go fully back to stock.
Sent from my Nexus 4 using xda premium
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
tokuzumi said:
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No. And even on stock 4.2 I'm now having the sound disappearing problem. Where it'll just stop for no reason.
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
MERKJONES said:
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
Click to expand...
Click to collapse
Everything is good now. Just flash new AOPK mr1 build 3 with newly doiwnload gapp. So far so good. Make sure you download the gapp from 12/12/2012
Sent from my Nexus 7 using xda app-developers app
So I've been looking and I haven't found an answer to this problem
I have a 16 gig nexus 7 and I like to tinker with it. I rooted it quite quickly just after getting it, and I have loaded custom roms, ect. The problem arose when I saw Ubuntu for the Nexus 7! I just HAD to try it out! So I did, and it wasn't so great :/ I went back to Android and a couple days later I realized that somehow my Nexus 7 thinks it's 6 gigs instead of 16. I was wondering if it was something that went wrong with the partitions when I installed Ubuntu on it, and if there was any way I could possibly fix it.
Thanks for all the help
Have you tried flashing a stock image back on the device?
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Have you tried flashing a stock image back on the device?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I believe I have. A little unsure though. I downloaded the stock 4.2 and flashed that onto it. Was that right or do I have to find the stock image that came with it out of the box (so 4.1.2 or close)?
Factory reset will fix the issue without installing the ROM I believe.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
Factory reset will fix the issue without installing the ROM I believe.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Well I've tried it before... No harm in trying it again after I do a backup. Will update how this goes.
EDIT I just did a factory reset and no dice. It still believes it is 6 gigs.
RimSide said:
Well I've tried it before... No harm in trying it again after I do a backup. Will update how this goes.
EDIT I just did a factory reset and no dice. It still believes it is 6 gigs.
Click to expand...
Click to collapse
What i believe has happened is that your partition module has become corrupted.
So, you tried flashing stock, and tried factory reset?
Does it show up on your computer as 6 GB when you connect it?
I had the same thing happen. I just used wugs toolkit to flash back to stock, then rerooted from there. That is the easiest way I know of to fix. Becides download times it only takes like 15 minutes to flash to stock, then unlock and root and you are back on your way.
Ok i was updating my rooted nexus 7 (2012) of the air to 4.4 kitkat. It downloaded and installed but when it was time for it to boot it just got stuck at the 4.4 booting screen (the circles) so i looked on the forums and it said to format everything (cache, system, sd) via clockworkmod so i did. When i tried to reboot it just got stuck at the Google loading screen.
1st Forum i will use this heaps more if the community can help me out
Pippindog said:
Ok i was updating my rooted nexus 7 (2012) of the air to 4.4 kitkat. It downloaded and installed but when it was time for it to boot it just got stuck at the 4.4 booting screen (the circles) so i looked on the forums and it said to format everything (cache, system, sd) via clockworkmod so i did. When i tried to reboot it just got stuck at the Google loading screen.
1st Forum i will use this heaps more if the community can help me out
Click to expand...
Click to collapse
try to wait longer, for me it also took a lot of time
thanks
_crue_ said:
try to wait longer, for me it also took a lot of time
Click to expand...
Click to collapse
that was a quick reply.
Darn i should have waited but now im stuck at this google screen how long does it normally take ??
Pippindog said:
that was a quick reply.
Darn i should have waited but now im stuck at this google screen how long does it normally take ??
Click to expand...
Click to collapse
first boot after flashing for me it took ~5-10 minutes, i don't remember. I tired to wait and go to get a lunch )))
-__-
_crue_ said:
first boot after flashing for me it took ~5-10 minutes, i don't remember. I tired to wait and go to get a lunch )))
Click to expand...
Click to collapse
I have turned it on and still its not booting after at least 20minutes the photo in the attachment is what its stuck at
Pippindog said:
I have turned it on and still its not booting after at least 20minutes the photo in the attachment is what its stuck at
Click to expand...
Click to collapse
Try reflashing it again.
All working just had reinstall some recovery thingy if anyone has this problem I will post a link to the solution
Sent from my Nexus 7 using XDA Premium HD app
Pippindog said:
All working just had reinstall some recovery thingy if anyone has this problem I will post a link to the solution
Click to expand...
Click to collapse
Much appreciated if you would.
Son's N7 is stuck at boot logo.
Downloaded this
http://forum.xda-developers.com/showthread.php?p=42407269
Then someone showed me how to use it.
Hope this helped
Sent from my Nexus 7 using XDA Premium HD app
NoSubstitute said:
Much appreciated if you would.
Son's N7 is stuck at boot logo.
Click to expand...
Click to collapse
What did you do before it got stuck? And which recovery are u using? bootloader etc
Sent from my Nexus 4 using XDA Premium 4 mobile app
JayDream said:
What did you do before it got stuck? And which recovery are u using? bootloader etc
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
TWRP and I forgot that I shouldn't let it "fix" broken root.
I just used the basic guide on how to flash a factory image of 4.3 in smaller pieces with fastboot, skipping userdata (so I could keep mine), and then sideloaded the two KRT OTA followed by flashing SuperSU 1.75. I did all that in one go, on my second Nexus 7, before booting it the first time.
NoSubstitute said:
TWRP and I forgot that I shouldn't let it "fix" broken root.
I just used the basic guide on how to flash a factory image of 4.3 in smaller pieces with fastboot, skipping userdata (so I could keep mine), and then sideloaded the two KRT OTA followed by flashing SuperSU 1.75. I did all that in one go, on my second Nexus 7, before booting it the first time.
Click to expand...
Click to collapse
1st Make sure you are on the latest twrp. 2nd it would be easier just to flash a stock ROM in recovery instead of flashing the factory images.. Is there a particular need for using the factory images or do u just want a working ROM?
Sent from my Nexus 4 using XDA Premium 4 mobile app
JayDream said:
1st Make sure you are on the latest twrp. 2nd it would be easier just to flash a stock ROM in recovery instead of flashing the factory images.. Is there a particular need for using the factory images or do u just want a working ROM?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't want to lose any data at the time.
As the title says my nexus 4 just started rebooting out of no where, while one the phone, in an app, doesnt really seem to have a pateren.. I believe it started when she got the 4.4 update and now has 4.4.2. anyone els experience this issue? I think im going to try a factory reset to see if that helps. any input would be appreciated.
Ajxx16 said:
As the title says my nexus 4 just started rebooting out of no where, while one the phone, in an app, doesnt really seem to have a pateren.. I believe it started when she got the 4.4 update and now has 4.4.2. anyone els experience this issue? I think im going to try a factory reset to see if that helps. any input would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If so and you have a custom recovery, I would do the factory reset via the recovery, that way you should still have your apps. If not, then you will lose everything and have to start from scratch.
Could be due to one of two things or a combination of things. One is a hardware issue, which I hope isn't the case. I would check the apps first before resetting, then do the reset. If it continues, try re-flashing the stock image. If after that and you're still having problems, going to 4.4, or 4.3 since it started with 4.4.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Are you rooted? If so and you have a custom recovery, I would do the factory reset via the recovery, that way you should still have your apps. If not, then you will lose everything and have to start from scratch.
Could be due to one of two things or a combination of things. One is a hardware issue, which I hope isn't the case. I would check the apps first before resetting, then do the reset. If it continues, try re-flashing the stock image. If after that and you're still having problems, going to 4.4, or 4.3 since it started with 4.4.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Its bone stock, ill have to take a look at her apps just to check whats up there but i doubt thats a culprit. I may be wrong but if I flash stock ota update it wont delete the user data and storage correct?
Ajxx16 said:
Its bone stock, ill have to take a look at her apps just to check whats up there but i doubt thats a culprit. I may be wrong but if I flash stock ota update it wont delete the user data and storage correct?
Click to expand...
Click to collapse
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)[/QUOTE
And unlocking the BL wipes it as well correct?
Click to expand...
Click to collapse
Ajxx16 said:
Berrydroidcafe said:
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)[/QUOTE
And unlocking the BL wipes it as well correct?
Click to expand...
Click to collapse
Yep!
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse