So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. I did it, then had trouble rooting it. I decided to just say screw it and then restore my Nandroid backup (which I made like a good boy). Then I got a failed message on the restore. Booted back up to a fresh boot. Brand new "please select your language" .. Wtf? So then I went back to TWRP wiped everything tried to restore again. Now... Fail. So now I can't boot up because I wiped my ROM and I'm freaking stuck all over this 4.3 update. Really?
So now I will try to wait until WUGS toolkit gets updated and see if I can use it to flash a stock 4.3 image to the device then root it. I don't know if i can even use that toolkit if I don't have a ROM on the device. Anyone had experience with such a cluster and have advice? Any thoughts on why the nandroid didn't restore?
:banghead:
Sent from my Nexus 7 using xda app-developers app
Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish
EddyOS said:
Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish
Click to expand...
Click to collapse
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app
Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta
italia0101 said:
Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?
Federico_96 said:
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?
Click to expand...
Click to collapse
Yep anything you want. Doesn't matter, I was on pa and matrix
Sent from my Nexus 4 using Tapatalk 4 Beta
Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app
jcnbama said:
So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. ...
Click to expand...
Click to collapse
I could tell this was going downhill after reading this first sentence. Why would you install a custom recovery in order to flash an OTA? I don't mean to offend you but you have a lot of reading to do before you continue flashing anything.
I was in the same boat and confused as hell back in my Nexus One/Galaxy Nexus days. What I've discovered after a lot of trial and error as well as A LOT of reading, is that once you become extremely familiar with using ADB and Fastboot commands you realize how unbelievably simple this stuff really is. Even soft bricks are just small hiccups that won't stress you out anymore.
Learn how to properly use ADB/Fastboot commands through terminal (in OSX) or command prompt (n Windows) and you will realize that the toolkits are silly and do exactly the same thing.
Again, I mean this in the least offensive way possible. This is coming from someone who thought he bricked his Nexus 7 and let it sit in a drawer for 5 months before finally understanding ADB/Fastboot, pulling it out of the drawer and having it back up and running within 10 minutes...
jcnbama said:
Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This is completely OK. Follow THIS guide (just one of many) to learn how to setup your computer for ADB/Fastboot. Then follow THIS guide to learn how to flash back to completely stock. No current ROM is required on your phone to do any of this.
I swear this is a nightmare. I don't have TBU or anything. I literally have to start over. I am always VERY careful to read and make back ups that's why I use TWRP it's why I make Nandroids and this just sucks. Ugh. I have to piss and moan I don't know where to start lol. Thanks for letting me vent..
Sent from my Nexus 7 using xda app-developers app
jcnbama said:
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.
simms22 said:
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.
Click to expand...
Click to collapse
Well I do understand that point. It's a good one. I honestly don't know how to use ADB like I should. But at the same time it's a lot easier and if used properly can prevent mistakes. And good Devs make good money in donations so everyone is happy.. Lol :beer:
Sent from my Nexus 7 using xda app-developers app
Related
I have rooted and unlocked the bootloader of my N7 and installed cm10. Now I want to go back and reflash the Stock ROM. Can someone outline me the exact steps?
I've used the Nexus 7 Toolkit and selected option 9 to flash the Stock ROM but it didnt work..
binarydrummer said:
I have rooted and unlocked the bootloader of my N7 and installed cm10. Now I want to go back and reflash the Stock ROM. Can someone outline me the exact steps?
I've used the Nexus 7 Toolkit and selected option 9 to flash the Stock ROM but it didnt work..
Click to expand...
Click to collapse
Use the Toolkit, option 9
http://forum.xda-developers.com/showthread.php?p=29637670
Sent from my Nexus 7 using Tapatalk 2
heyodee said:
Use the Toolkit, option 9
http://forum.xda-developers.com/showthread.php?p=29637670
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I just used Nexus Root Toolkit instead and it worked. I selected the option: "flash stock and unroot". So I am guessing that I went back to stock JB 4.1.1 and the only thing needed is to root using the same tool?
I'm in a similar situation, but I rooted/unlocked manually on a MAC.
Flashed to a ROM but would prefer to flash back to the original one.
pmgreen said:
I'm in a similar situation, but I rooted/unlocked manually on a MAC.
Flashed to a ROM but would prefer to flash back to the original one.
Click to expand...
Click to collapse
+1
Guys. Take 5 minutes and learn some basic fast boot and adb commands. Then this kind of stuff will seem trivial.... Stop acting helpless and learn something here
Sent from my Galaxy Nexus
Pirateghost said:
Guys. Take 5 minutes and learn some basic fast boot and adb commands. Then this kind of stuff will seem trivial.... Stop acting helpless and learn something here
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Your point is right, but the delivery is wrong. All of us were noobs at some point and asked questions that seemed trivial to the more experienced HUMANS in the community.
True, we should all look around the forums and read, but, that's not the way to answer to people looking to incur into the flashng, dev, modding community.
Just saying, no offense meant.
Okey so yesterday I couldn't wait anymore and wanted to update my Nexus 7 to 4.2 but couldn't.
After restarting it did initiate the update but right after it gave me a red triangle with a (!)
And now I can't see any updates anymore. I yet I'm on 4.1.2 still
Dang it..
Sent from my Nexus 7
Download the 4.2 factory images from google and flash via fastboot.
Consider yourself lucky and stay with 4.1.2
I have the same problem as well. When I first tried to get the update, the Android had a red ! And failed the update. Now, it says no update available....
I'm not sure if I should wait until a more stable version is out, however.
Sent from my Nexus 7 using xda app-developers app
Meh rootbrain is right. Jag ive been reading upp on 4.2 and i better stay on 4.1.2
Sent from my Nexus 7
It's all subjective. Some like it, while others don't. Neither opinion is the end all, be all gospel truth.
Sent from my Nexus 7 using Tapatalk 2
rootbrain said:
Consider yourself lucky and stay with 4.1.2
Click to expand...
Click to collapse
Aren't there enough 4.2 bashing threads that you feel the need to take this one off-topic?
The OP asked for help not for your opinion.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x
Any help would be appreciated...I want to have the latest update, not be stuck...
Sent from my Nexus 7 using xda app-developers app
yanksrock1000 said:
Any help would be appreciated...I want to have the latest update, not be stuck...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Have you modified, frozen, or deleted any of the stock system files? The update checks for approximately 200 files and if any aren't stock, will fail. Your best bet, as someone else said, is going to be to fastboot flashing the stock image. Be forewarned that you'd be essentially starting from scratch as it would wipe your tablet, but I'd personally find that preferable since you'd be circumventing some of the issues that are irking the most vocal of 4.2's critics.
Sent from my Nexus 7 using Tapatalk 2
I actually just purchased the tablet, and out of the box the first thing I tried to do was update, and it failed.
I'm not very knowlegable about flashing the factory image myself, but I've heard about updating using a "toolkit"? Is this easier?
Sent from my Nexus 7 using xda app-developers app
yanksrock1000 said:
I actually just purchased the tablet, and out of the box the first thing I tried to do was update, and it failed.
I'm not very knowlegable about flashing the factory image myself, but I've heard about updating using a "toolkit"? Is this easier?
Click to expand...
Click to collapse
Yup, easier. But using a command line and the android SDK/fastboot isn't all that hard... maybe your issue is just the universes way of saying you should go learn a new trick. :cyclops:
However I doubt the universe will waste any energy punishing you if you choose to go the easy route. Plus, you can always read the thorough directions for both routes and make an educated decision before you get your hands even the least bit dirty.
using Fastboot: http://forum.xda-developers.com/showthread.php?t=1907796
Wugs Windows toolkit: http://forum.xda-developers.com/showthread.php?t=1766475
najaboy said:
Have you modified, frozen, or deleted any of the stock system files? The update checks for approximately 200 files and if any aren't stock, will fail. Your best bet, as someone else said, is going to be to fastboot flashing the stock image.
Click to expand...
Click to collapse
i have the same issue, but i dont want to fastboot it, what should i do? i havent rooted or anything yet. i have a 32gb no 3g version...
PenguinDroid said:
i have the same issue, but i dont want to fastboot it, what should i do? i havent rooted or anything yet. i have a 32gb no 3g version...
Click to expand...
Click to collapse
Why not, it's a safe operation.
If you're completely stock, and update fails, either try again (and again, and again), or send it to repair (slowest). Or fastboot (fastest).
issak42 said:
Why not, it's a safe operation.
If you're completely stock, and update fails, either try again (and again, and again), or send it to repair (slowest). Or fastboot (fastest).
Click to expand...
Click to collapse
well, in that case, id rather root it and flash a custom rom, and thats probably what i am gonna end up doing... ill see, thanks for the answer
Hello, my girlfriends new Nexus 7 for some reason wont update to 4.2, its stuck on 4.1.2. So whats the best way to root it on 4.1.2? And afterwards, its possible to flash 4.2 on it, correct? Ive rooted a couple of different phones and customized them, but I want to make 100% sure I dont screw up her second love lol. Thanks for the help!:cyclops:
What is 4.3?
Sent from my Nexus 7 using xda app-developers app
dparrothead1 said:
What is 4.3?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sorry, meant 4.2 LOL
Try Wug's Nexus Root Toolkit. It does a great job and walks you through each step.
thats the one I was looking at! I wasnt sure if I should use that one, or the other Toolkit, but the other one seemed a little more confusing. Thanks!
Wugfresh worked great for me this weekend.
The only unexpected headache was having to deal with device driver issues since I was rooting the n7 on a laptop that I used to root my Galaxy tab a year ago. There were 6-7 Samsung drivers that I had to remove and then reboot the laptop.
Still an easy process but the driver situation made the process take longer than expected (maybe an hour total).
Still, a lot faster and more newb friendly than rooting in 2009
Sent from my HTC Sensation using XDA Premium App
Toolkits are fail. Learn to use adb and fastboot. That way you can be sure of exactly what your doing to your phone and fix it if necessary. It may sound daunting at first but in the long run it's much better.
Sent from my Nexus 4 using Tapatalk 2
zidane1341 said:
Hello, my girlfriends new Nexus 7 for some reason wont update to 4.2, its stuck on 4.1.2. So whats the best way to root it on 4.1.2? And afterwards, its possible to flash 4.2 on it, correct? Ive rooted a couple of different phones and customized them, but I want to make 100% sure I dont screw up her second love lol. Thanks for the help!:cyclops:
Click to expand...
Click to collapse
dr.m0x said:
Toolkits are fail. Learn to use adb and fastboot. That way you can be sure of exactly what your doing to your phone and fix it if necessary. It may sound daunting at first but in the long run it's much better.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Completely agree with this...
-----------
Hi, zidane1341...
Rooting is really simple.
(You will need an unlocked bootloader for this).
Get a custom recovery .img for your device...
Either CWM - http://www.clockworkmod.com/rommanager
...or TWRP - http://www.teamw.in/project/twrp2/103
...it matters little which.
-----------
fastboot flash it.
-----------
Get Chainfires SU .zip package here http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Flash it using the custom recovery you've just fastboot flashed...
Reboot... and you're rooted.
-----------
Having said all that though, I don't see how root will facilitate an upgrade of your girlfriends N7 from 4.1.2 to 4.2...
For that you will need the factory stock image for your device, available here http://developers.google.com/android/nexus/images.
There is a thread here http://forum.xda-developers.com/showthread.php?t=1907796, that details how to flash factory stock images.
-----------
On a final note... it's kind of puzzling why your girlfriends N7 isn't being automatically upgraded to 4.2.
When I flash back to stock, (as I do, from time to time), I use JOP40C (4.2) and as soon as I get a WiFi connection, I get 'nagged' about upgrading to JOP40D (4.2.1), which I always allow. And it does so without problems.
If your girlfriends N7 is running (even at the slightest level) a modified version of JellyBean, then the automated update procedure from Google's servers will fail.
Rgrds,
Ged.
Well I know from personal experience, after I rooted my optimus I could upgrade to a newer version of android, I can just flash 4.2 after rooting correct? I called Asus and they said to send it in, but they didn't know what was wrong. My girlfriend is pretty mad about that, so I was thinking I could bypass that by doing it myself.
You guys have prob seen a thread like this a million times, but I am getting my nexus 4 soon and I wasn't sure if i should root it or not. I have rooted before (droid x2, galaxy nexus, nexus 7) so I am fairly familiar with how the process works. I will not loose my updates from Google if I root and stay on stock ROM? That's what I would plan on doing anyways if I did. Thanks for the help!
Sent from my Nexus 7 using xda app-developers app
Just Google some of the benefits of having root.. if any of those sound appealing to you then... root it. If not, don't. Buuuut since you've already been rooted with several devices, you should already know if you should root or not. But thanks for making a new thread for this personal decision that you've made 3 times before
Sent from my X909 using Tapatalk 2
In his defense this is a different devices I rooted and flashed rooms on my gs3 and gs2 but have not rooted or anything to this device but the key is yet right now haven't found a huge reason to do so this rom works perfectly for me and I get a days use out of it
Sent from my Nexus 4 using xda premium
I just couldn't stand it no more and rooted after 1 month. Also flashed clockworkmod.
Went to Nightly Mako.
I love the device but feel the new Clockwork mod's blobs folder, unable to access backups so easy, and the dam memory size...
I hesitate and hope Nightlies are flawless. Frankly its awesome. So are is the Stock ROM.
I just prefer CM10.1
ROOT!!
If I were to flash nexus 4 PA would I need to wipe system as well as do a factory reset in recovery? The directions just say factory reset.
Sent from my Nexus 7 using xda app-developers app
You had better gain root... Gaining root denotes a gain not a loss. Unlocking the bootloader means your unbacked data would be lost. So back up data and root and enjoy. And yes you may wipe system I recommend it.
Sent from my rooted Stock Nexus 4 using xda premium
Hi,
http://forum.xda-developers.com/showthread.php?t=2180999&highlight=root+or+not+root
http://forum.xda-developers.com/showthread.php?t=2194992&highlight=root+or+not+root
And: http://lmgtfy.com/?q=root+or+not+root,+why?
Original thread, what`s next: Wich rom should i choose?, please tell me all about while i wait for your answers because i`am too lazy to look for myself
gee2012 said:
Original thread, what`s next: Wich rom should i choose?, please tell me all about while i wait for your answers because i`am too lazy to look for myself
Click to expand...
Click to collapse
Hi,
LOL... That's what I thought, like all these kind of threads...
Locked soon... ?
viking37 said:
Hi,
LOL... That's what I thought, like all these kind of threads...
Locked soon... ?
Click to expand...
Click to collapse
Yes.
Hello everybody.
A few days back I managed to brick my Nexus 4 after using it for 1 day!!!! I realize that this all is a very moronic situation and there isn't a fix for my brick because a used a *Toolkit*. Well, I'm already receiving my replacement and it will be here in an hour.
I know how everyone here feels about Google paying for our mistakes but I'm so lucky they're so kind. The advice that I need is on how to NEVER be in this same position. If I were to have set up fastboot instead of a toolkit would all of this have been avoidable? Btw, CM 10.1 is how I bricked my phone....I never have had any luck with that rom.
Thanks everyone for your advice.
Almost all errors are caused by, you guessed it, users. I am skeptical when people claim the toolkit bricked their phone. Also, if cm 10.1 has been troublesome for you, why keep using it? Its the very definition of insanity: keep doing the same thing over and over and expecting different result.
Sent from my Nexus 4 using xda premium
Sooooo, in your professional opinion....would my brick have been less severe if I used fastboot?
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
blitzzz3434 said:
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
Click to expand...
Click to collapse
Well what happened was when I tried to flash it the first time I got a boot loop. So I restored from a backup. Then I redownloaded and when I was in my custom recovery I did a factory reset, a cache wipe and a factory wipe. Then I installed CM.
No after like 3 minutes of booting, I got to my homescreen. I think what happened was I wanted to get off CM because it wasn't working right so I tried to boot into recovery so I held down power and volume keys. I got a yellow light then a red light and now bootloader. After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
My excuse for all of this stupidity is that it was 6am and I hadn't slept yet. Nothing good happens for me without sleep lol. btw, thats as accurate as I remember.
Alpha-Wat3rloo said:
After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
Click to expand...
Click to collapse
What is smirkit? The only hits I could find on it were for the Kindle Fire. It sounds to me like you flashed a bootloader for another device, that would certainly give you a hard brick.
Sent from my Nexus 4
As I suspected, user error.
Sent from my Nexus 4 using xda premium
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Thank you you've actually helped Mr to figure out why it happened. It was super late/early. Serves me right flashing anything without proper rest.
Sent from my Nexus 4 using xda app-developers app
If you had flashed the wrong bootloader or kernel (one meant for a different device) via fastboot then you would still have a hard brick.
Using fastboot instead of a toolkit does mean you have more control over what your are doing, but you still need to make sure you are still flashing the right things.
Sent from my Nexus 4
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your original post made it sound like you used one of the toolkits made specifically for the Nexus 4 and that is what had bricked your phone. It wasn't till half way down the thread you mention you used a tookit for another device. Toolkits are not free from user error even when you use the correct one as you still have to download the correct files and place them in the correct folders. There have been a lot of newbies bricking phones because they have downloaded the incorrect files and then blame it on the developers and or phone for being defective. So this is why people are skeptical when they read these threads.
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that`s what happens when your SMARTphone is Smarter than you.....