HardwareBye Bye Nexus 7

  

Press Ctrl+Enter to quickly submit your post
Quick Reply  
 
 
  
 From:  CHYRON (DSMITHHFX)    15 Jan 2019 14:55 
 To:  ALL 15 of 19 
42289.15 
The saga continues... after reviewing the NRT rooting [attempt] log (attached ^^^) I suspected that although the SuperSU, BusyBox etc were copied to the tablet, they may not have been installed because of the failed reboot. So I booted into the "TWRP" (replacement recovery partition) and was able to install them from there. But this didn't fix the boot loop. After several attempts, I decided to revert to stock 5.1.1 ROM from TWRP recovery.

In doing this, it reformatted the cache partition (to ext4), I'm not sure if that is normally done from the stock recovery option, since that gives no verbose console indication of WTF is going on, unlike TWRP. TWRP is definitely the superior tool (allowing unhindered access to the file system, including system folders, and mounting all partitions including OTG devices), and a host of recovery options,and I'll be curious to see if that is still on board.

Anyhow, it immediately rebooted into stock Android 5.1.1 which I again have to set up. But at least the tablet is usable. Supposedly the fstrim command can be run from the TWRP console, in which case rooting would not really be needed
“If there is a concrete wall in front of you, go through it” – Donald Trump, 2004
0/0
 Reply   Quote More 

 From:  Liya (BAOZHAI)   16 Jan 2019 08:48 
 To:  ALL 16 of 19 
42289.16 
My nexus 2013 tablet has died down. It was such a wonderful tablet of that time. Very snappy and was easy to use. 

APPROVED: 16 Jan 2019 11:04 by MILKO
0/0
 Reply   Quote More 

 From:  CHYRON (DSMITHHFX)    18 Jan 2019 14:54 
 To:  ALL 17 of 19 
42289.17 
Are you sure it's dead? I thought mine is/was, but reflashing (three times) brought it back up to scratch.

Attempted rooting* with SuperSU (twice, 2nd time by accident) made it unbootable, so I reflashed stock, configured, flashed TWRP to recovery and backed it all up so (hopefully) future recovery will take a few minutes vs. a few hours.




*now reckoned to be not terribly useful for most folks
“I’m old, sedentary and slouch a lot – will standing up at my desk … um, never mind.”
0/0
 Reply   Quote More 

 From:  Dan (HERMAND)   12 Feb 2019 18:02 
 To:  CHYRON (DSMITHHFX)       18 of 19 
42289.18 In reply to 42289.1 
Heh, I've got a Nexus 10 and yeah....it's pretty much a paperweight now. Shame really, cos it really did the trick for a long time - but I tried to resurrect it a year or so ago and it would just randomly reboot.

Dan Herman
0/0
 Reply   Quote More 

 From:  CHYRON (DSMITHHFX)    12 Feb 2019 18:22 
 To:  Dan (HERMAND)      19 of 19 
42289.19 In reply to 42289.18 
My 7 is back in action. Reflashing with stock rom brought it back from the dead, and I've put in an updated "RAM cleaner" app that somewhat improves usability (still reliably slows down and randomly reboots, but a lot less frequently).

Two main ongoing (apparently related) glitches seem to be wifi and "system ui", which typically crashes about ~15-mins after starting anything using wifi. If it makes it through a system ui reset without rebooting itself, it actually runs smooth for a few hours. So usable about as much as I need it to be.

 
“The Man Who Killed Hitler And Then The Bigfoot”
0/0
 Reply   Quote More 

Reply to All    
 

1–19

Rate my interest:

Adjust text size : Smaller 10 Larger

Beehive Forum 1.5.2 |  FAQ |  Docs |  Support |  Donate! ©2002 - 2024 Project Beehive Forum

Forum Stats