• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

JellyBean 4.2.1 Out

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
If this is in response to the person who said CWM was taking up extra space.... that is for backups. If he's backing up via CWM I am pretty sure he does need CWM.

Yeah I'm dumb. I thought he was talking about CWM being needed for root. I stopped using CWM backup once I switched to Nexus because I haven't felt the need to flash custom rom. Stock images are available direct from Google and everything else is pretty much backed up to Google cloud.
 
I got a random reboot yesterday. Not nice.

However, given some of the other problems I've been having, I don't know if it's 4.2 or a defective unit. I'm gonna send it in.
 
Yeah I'm dumb. I thought he was talking about CWM being needed for root.

That's what I meant and thought. Thank you for correcting me.

I didn't use the 1-click tool. To be frank that thing was more confusing than fastboot method to me. I basically followed this video with some omissions (already had USB drivers) and modifications (used latest version of SuperSU).

So I went this way:

fastboot flash recovery clockwork.img
fastboot reboot-bootloader
fastboot boot clockwork.img

After the "blobs" nonsense, I deleted everything clockwork and reflashed recovery using TWRP.

@Dulanic: I intend to use TWRP for backups due to the phenomenon I described with regard to CWM in my previous post.
 
Back
Top