[Q] Bricked by Nexus (and I'm not a techie) - Nexus 4 Q&A, Help & Troubleshooting

Hi everybody.
Okay I'm not a techie. I managed to root my nexus 4 running android 5.0.1 with kingo root. I wanted the OTA 5.1 UPDATE, so unrooted, tried the OTA and it failed.
I've installed minimal adb and fastboot but after various goes I'm no further on. Is my phone ruined?
Under system recovery I'm now showing LMY470. If I try and reboot I just get the google display.
PLEASE - can anybody help (I go on holiday on Sunday and really need my phone!)
Hope somebody can help
Rob

Just flash the factory image with fastboot.
Download the factory image, extract it. In there is a flash-all batch file
Boot into the bootloader and connect your device to the pc
Double click on the flash-all
Note, this will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app

robigouk said:
Hi everybody.
Okay I'm not a techie. I managed to root my nexus 4 running android 5.0.1 with kingo root. I wanted the OTA 5.1 UPDATE, so unrooted, tried the OTA and it failed.
I've installed minimal adb and fastboot but after various goes I'm no further on. Is my phone ruined?
Under system recovery I'm now showing LMY470. If I try and reboot I just get the google display.
PLEASE - can anybody help (I go on holiday on Sunday and really need my phone!)
Hope somebody can help
Rob
Click to expand...
Click to collapse
Your phone is not ruined.... You may need to have to flash the image again. You might want to try using the "Nexus Root Toolkit"
Just search for it It will walk you through the whole process. You might also search for the SkipSoft Android Tool Kit.
I hope that helps Let us know how you get on

Blacksmith5 said:
Your phone is not ruined.... You may need to have to flash the image again. You might want to try using the "Nexus Root Toolkit"
Just search for it It will walk you through the whole process. You might also search for the SkipSoft Android Tool Kit.
I hope that helps Let us know how you get on
Click to expand...
Click to collapse
All done. manged to put no the original 4.3 and then let it do all the OTA stuff. dont' think I'll be rooting again, put me off!

robigouk said:
All done. manged to put no the original 4.3 and then let it do all the OTA stuff. dont' think I'll be rooting again, put me off!
Click to expand...
Click to collapse
When you say you "unrooted", how did you do so? I have found with 5.+ that in order for the OTA to not fail when you have been rooted, requires that you flash the stock images for the current version, as opposed to Factory Resetting, and then you will be able to install the OTA update without it failing. Has to do with out the updater checks the entire partition and not pieces, which is a new method. If one byte of data is out of place on System partition, it OTA fails.

Related

Rooted, stock, how to install OTA update? Is there an idiots guide?

Hello,
I'm completely new to Android. I've been working on computer chips for 15+ years though (IC layout). I'm currently working on the follow up to Tegra 3.
I wanted to use SwitchMe on my N7 so I rooted it with msabra's one click root tool(CWM). Now I am getting constant reminders about the 4.1.1 system OTA update.
I really have no desire or time to play with mods right now.
I've searched on how to do it, but would one of you mind explaining the steps in detail? Also, if I unroot to install the update will I lose all of my user data, apps, etc?
Thanks!
Chris
ChrisAttebery said:
Hello,
I'm completely new to Android. I've been working on computer chips for 15+ years though (IC layout). I'm currently working on the follow up to Tegra 3.
I wanted to use SwitchMe on my N7 so I rooted it with msabra's one click root tool(CWM). Now I am getting constant reminders about the 4.1.1 system OTA update.
I really have no desire or time to play with mods right now.
I've searched on how to do it, but would one of you mind explaining the steps in detail? Also, if I unroot to install the update will I lose all of my user data, apps, etc?
Thanks!
Chris
Click to expand...
Click to collapse
You can just unroot, install the update, and reroot. I would use Wug's toolkit. You could also install voodoo OTA rootkeeper I believe, and backup your root, temp unroot and install the OTA update, and then restore the root that you backed up.
Unless you lock the bootloader and unlock the bootloader, the device shouldn't wipe the data partition on it's own.
Thanks for the help. Unfortunately the toolkit keeps crashing at the unroot step.
http://forum.xda-developers.com/showthread.php?t=1465661
ChrisAttebery said:
Thanks for the help. Unfortunately the toolkit keeps crashing at the unroot step.
Click to expand...
Click to collapse
Try toolkit release by mskip..hope it help and for the wug toolkit make sure reboot your pc and please connect and disconnect the usb cable. Be sure that there is one android adb driver is install. Check at your device manager. If you use winXP, kindly upgrade to win7 pro or later for better stability. Hope it help .
I was able to run backups with Wug's kit, but it gave me an error every time I tried to unroot. I don't think I rebooted my PC after I installed it, so I'll try that out tonight.
I also downloaded mskip's kit, but haven't tried it out yet.
I'm on W7 64.
Thanks!
yosh76 said:
Try toolkit release by mskip..hope it help and for the wug toolkit make sure reboot your pc and please connect and disconnect the usb cable. Be sure that there is one android adb driver is install. Check at your device manager. If you use winXP, kindly upgrade to win7 pro or later for better stability. Hope it help .
Click to expand...
Click to collapse

[Q] 4.1.2 update enquiry after unlocked, rooted. kernel changed

Hi,
I am new to this forum and android stuff.
Please forgive me if I asked noob question.
I tried to search but got no complete answer.
My condition:
Nexus 7
build number JRO03S
used Nexus root toolkit 1.5.3
to unlock and root
used TWRP to install poitee kernel for usb dac.
Then:
The 4.1.2 updates notification show up
I pressed yes ... accidentally.
Now:
The build number becomes JRO03S
but the Android version is still 4.1.1
Question:
a. How to update to 4.1.2?
b. How to update without wiping any data and apps?
c. Do I have to reinstall the pointee kernel?
d. Will flashing rom ( updating to newer version ) wipe all things?
Sorry for so many questions,
For my situation it is a mixed up that I can't find similar condition on the internet yet.
Please kindly help and advise.
Much Thanks!
Btw,
I done below, no success:
1. quickboot
2. TWRP recovery
3. install nakasi-JZO54K-from-JRO03S.zip (from /sdcard)
4. error --> "Status 7" shown.
Cannot update.
Please Please help....
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
Understood and Thanks a lot!!!:good:
that means all in all,
I still have to go through
the route of "Backup all --> Flash Stock & unroot --> Root --> Restore all".
However, considering the latest update seems don't have anything important or useful to me
So I just wait for the next more important update.
and save the drudgery next time.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
He doesn't need to lock his bootloader, and he'll still not be able to run the update the natural way as long as he's got twrp or cwm installed. He can flash the factory rom and push the update through using custom recovery though.
Visa Declined said:
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
Click to expand...
Click to collapse
Thanks for you advise,:highfive:
it is very kind of you to help.
I think may be the Status 7 error could be caused by the Custom Kernel Installed (poitee)
I better ask him in detail later on.
But mine is JRO03S,
May be it is safer to Return to Stock Rom completely and go for OTA later.
Sadly, This 4.1.2. seems got no very useful component to me,
I solely use it as a second PDA and Music Player with USB DAC.
I will have to wait for better solution then.....
pleaseabcd said:
However, considering the latest update seems don't have anything important or useful to me
Click to expand...
Click to collapse
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Visa Declined said:
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Click to expand...
Click to collapse
O'really.....em...then it is a different story..(Safer for the future...)
Perhaps, I just:
1. use Titanium Backup to back up everything --> copy the "Back up" to PC (just in case)
2. use Wugfresh Nexus Root Toolkit 1.5.4 to Flash Stock n Root
3. if can Flash to 4.1.2 stock rom directly, OK
4. if can't --> flash back to 4.1.1 stock rom (JRO03S) and then OTA
5. Finally, use Titanium backup to restore Everything.
Have to Thank You you guys again!
I know I am a newbie... but I am learning......
Hate to be limited to what I was given......while I can experiment and make mistake to grow up !:laugh:

[Q] Best first steps with a new tablet

Ultra Noob here
So I had my first android-TF700 for about 10 days. Played around with it, read around this site and realized it was a tablet for someone with experience.
So I now have an N10. Charged, not even turned on yet. What should be my next steps? I see a couple toolkits,an auto root, and ASOP-
What would you suggest a noob start with?
I know, I know, turn it on
Thanks!
Depends on what you want to accomplish with the device. If you want to try or at least gain some understanding as to the different features you might be interested in, read the first post of the different ROMs available and see if anything sounds enticing.
I personally use me for taking media with me on the go, be it news or videos, so I don't have to carry a laptop around. I'm on CM10.1 right now but cycle through every rom to see how everything works. Good luck!
Sent from my Nexus 10 using XDA Premium HD app
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
rauschkugl said:
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
Click to expand...
Click to collapse
And how do you unlock the bootloader and install root?
What do you mean a custom recovery?
Are there other ways to root the device with out wiping it? Seems like most android smartphone you can load up an exe or something to shift the su app around or something.
Thanks.. (still waiting for my N10 to arrive.. meanwhile.. still playing with my ICS Bionic)
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
rauschkugl said:
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
Click to expand...
Click to collapse
Found the threads. Look easy enough to follow. Something I'm not understanding . What does it mean to install a recovery? whats the purpose of that. I've search and (at least not yet) found a good description of what/why that it. I'm sensing that devices are different (duh!) and I didnt need to install a "recovery" on my Droid Bionic when I rooted it, but this N10 must be different.
With the custom recovery you're able to install zip files, make a backup of your Rom,... You can't do that with the recovery that comes with the nexus 10.
Recovery is like a separate system that you can boot to, if you want to mess with the main Android OS. Like rauschkugl said, you can boot to a custom recovery to flash different ROMs that are distributed in flashable ZIP files. You can also make (or if anything goes wrong, revert to) a complete backup of the device's internal memory.
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
Great questions. You are one step ahead of me on my new N10. I've not turned it on yet, really wanting to, but I dont want to do much to it, until after I unlock/root/ and learn how to make backups. Though since i've got a TBpro license, I'll probably use that. I dont want to tweak the OS. so I think I need root just to be able to run TBpro. I just want to be sure I'll still get OFA updates, and I want to learn more about if and how backup work for a multi-user N10.
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
I would suggest straight away that you perform a backup with TWRP, so that if you decide to delve deeper into ROMs and playing with your system files, you'll have a completely stock backup to rely on. Simply boot into recovery and select 'Backup', then you can rename the backup file if you want, then swipe the slider across and wait, then you're done!
When it comes to system updates, you'll most likely have to use your root toolkit to unroot the device, else the update will fail. You can however continue to update all your apps as you normally would. Hope this helped
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
EraVulgaris said:
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
Click to expand...
Click to collapse
Sounds like a great success then so are you saying that you performed the system update while you were rooted and you retained the root access?
Nope. Got the OTA system update and it knocked me off root. But I got it back easily with the toolkit.

android 4.2.2 update question

Hey guys, will the android update 4.2.2 erase everything on my nexus?I am rooted and unlocked, so if the main update thing does erase all of my data is there another way to update without loosing any of my data? I used the nexus toolkit to root, and I know there was an option to reinstall android without erasing data, but is that possible with a newer version of android..
Thanks
Micro
No it will not erase everything.
Because you are rooted, there is a chance that the OTA will not succeed, depending on how close to stock you are. (Some root apps appear to diddle a variety of things in /system, and if any of these things are targets of the OTA patching process, the OTA will fail). Also if you have a custom kernel, this particular OTA will not succeed.
If the OTA fails, no worries - it always fails during initial verification steps when it is checking to make sure that the checksums of targeted files exactly matches what it expects, before anything on your tab has been altered. So, if it fails don't freak out - everything on your tablet is the same as before the OTA started.
If it succeeds, you will loose root as a result of the setuid/setgid permissions of the "su" binary getting reset by the OTA installer script. You can either manually fix that with a "chmod" command (via adb with the custom recovery running and /system mounted) or you can simply re-flash the same SuperSU (or Superuser) root installer kit that you used when you originally rooted. The OTA also flashes a new stock recovery in place, so you will need to re-flash your custom recovery back into place after it has finished. That should be no problem so long as you know how to do so, using either fastboot directly or a toolkit.
I'm not sure you needed to start a new thread on this - scroll through a few pages here and see just how many "4.2.2. update question" threads there have been recently.
good luck.
PS If your OTA fails and you want to try patching things by hand, read through all the trouble threads in here before posting. Each time it runs, it will report the source of the error in /cache/recovery/recovery.log. As always, make a Nandroid backup before you begin.
Sorry what exactly does ota mean? And so your saying there's no way to update without loosing my data? If that's the case I'm not updating because I'm filled to the max with data
Thanks
Micro
microzee said:
Sorry what exactly does ota mean? And so your saying there's no way to update without loosing my data? If that's the case I'm not updating because I'm filled to the max with data
Thanks
Micro
Click to expand...
Click to collapse
Which part of this:
bftb0 said:
No it will not erase everything.
Click to expand...
Click to collapse
did you find confusing?
I said that it will either succeed or fail, and if it fails it will do so in a way where nothing changes. If it succeeds, it will change some things, but not the things you are referring to as "my data".
OTA = Over The Air (update)
I used rootkeeper, temp unroot then installed ota update by toching on it. But after successfully updating my tablet is still on 4.2.1. Pls help. Even after updateing application msg on boot ithas not updated.
Sent from my Nexus 7 using xda app-developers app
sukhjit_bhullar said:
I used rootkeeper, temp unroot then installed ota update by toching on it. But after successfully updating my tablet is still on 4.2.1. Pls help. Even after updateing application msg on boot ithas not updated.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I was wondering if RootKeeper would work or not.
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
Wait....I just tried usig RootKeeper to temporarily un-Root the device then upgrade to 4.2.2 and it seems to have worked without an issue. I let it run through the entire upgrade, it rebooted, I looked to see what version I was on, it shows as 4.2.2, I then used RootKeep to restore Root, it worked like it was supposed to and it looks like it kept 4.2.2 as well.
I've tested a few apps that need Root and they worked just fine.
Hi all,
I've the same Problem here. the OTA-Update fails on my Nexus 7 (rooted). The message is only the green Robot with "Error". After restarting I can see that the version is still 4.2.1 :crying:
This is not the mainpoint (I've read up to now some threads which describing this issue). My point is: I can not restart the OTA-Update. There is no message whicht tolds me, that there is an update avalible... neither in the statusbar nor in the Settings.
Additionaly I can not find the log-file, which was some times described, where the error will be explained (I think it was deleted after the second restart).
Can someone explain me, how I can restart the OTA? Is it possible with the Framework-data deletion-trick? If I use this trick, what will be deleted in the Framework? Is there a place where the file /cache/recovery/recovery.log will be backuped?
If here is the wrong place for my questions, I'll make a new thread, but I think the thread which I've chosed fits it more or less
BR
SolarPlexus said:
Can someone explain me, how I can restart the OTA? Is it possible with the Framework-data deletion-trick? If I use this trick, what will be deleted in the Framework?
Click to expand...
Click to collapse
it's the framework data deletion trick*, yes. If you find solution to the update error problem, please keep us posted, cause i have the same issue...
*settings->apps->all->google service framework->force close->clear data. After that you go to the update menu (settings->about tablet->system updates) and tap on check now.

5.1 OTA failed

I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .
1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update
sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.
There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM
neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.
Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.

Categories

Resources