Nexus 7 2013 aka flo stuck on boot screen [stock ROM]

dkn91

Member
May 18, 2011
23
0
0
I know this has been raised so many times and trust me I have read through many of them.

Problem:
My tab jus wont start. I am able to charge it but when i try to power it on, it always stays on Google screen. :(

Things I tried:
1. boot into recovery, fails back to Google screen
- I am able to get to the bootloader screen by pressing vol down and power button. but then when i select recovery mode, it reboots and gets stuck again on Google screen

2. reinstall stock image
- got on google's website and downloaded latest NExus 2013 img aka razor-mob30x
- got all the required sdk and usb driver for windows
- booted device to bootloader screen. the Lock state was LOCKED
- connected device and used fastboot oem unlock and it did unlock the device
- used the img flash-all.bat and reinstalled the stock img. it took few mins bt it did finish install and automatically rebooted device
- my hopes were so up until, it stayed on Google screen again :crying::crying::crying::crying:

I really want to get it working again. what are my options here?
as next steps I am thinking to use twrp img and flash that and see if i can enter twrp recovery

any, literally any thoughts and ideas are welcome. I am gonna actively watch this thread and try my best to respond at the earliest
 

dkn91

Member
May 18, 2011
23
0
0
Do...
  1. get Restock2
  2. run relog.bat
  3. attach "relog-xxxxxx.zip" to your next post
:good:
Tried this today.

1. restock2.bat worked like charm. it did its magic and rebooted the device. it went all the way to android setup after it booted up but i stopped thr as per instructions
2. rebooted in bootloader and kicked off addons.bat
3. installed twrp, stock fix1 and magisk, no to kernel since i wanted stock only
4. device booted and stuck on Google boot screen again :(
5. forced booted again in bootloader and used restock2.bat again. went smooth but still boots and stays on google's boot screen.

I guess i should not have used addons.bat? attached log file
 

Attachments

k23m

Senior Member
Jan 3, 2016
869
457
93
....attached log file
and now we know what is going on...
Code:
<3>[    9.604370] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[    9.604797] elan-ktf3k 3-0010: [elan] elan_ktf3k_ts_recv_data: i2c_master_recv error?!
ELAN, the touch control chip, does not respond. No worries, it is fixable. If you have to opt for the #2 then note:
:fingers-crossed:

Interestingly, I observed that if the silver ribbon cable is completely disconnected then Android actually boots OK, see att.
 

Attachments

dkn91

Member
May 18, 2011
23
0
0
and now we know what is going on...
Code:
<3>[    9.604370] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[    9.604797] elan-ktf3k 3-0010: [elan] elan_ktf3k_ts_recv_data: i2c_master_recv error?!
ELAN, the touch control chip, does not respond. No worries, it [URL="https://forum.xda-developers.com/showpost.php?
Is that the reason why the tab wont go beyond Google screen also? Agreed, the touch screen is not working either when i get to twrp recovery.

I have done hw repair before on phone so this should be doable. will check back in when i try this out.
 

dkn91

Member
May 18, 2011
23
0
0
and now we know what is going on...
Code:
<3>[    9.604370] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[    9.604797] elan-ktf3k 3-0010: [elan] elan_ktf3k_ts_recv_data: i2c_master_recv error?!
ELAN, the touch control chip, does not respond. No worries, it is fixable.
Interestingly, I observed that if the silver ribbon cable is completely disconnected then Android actually boots OK, see att.
UPDATE:

tried Opt #1 and that didnt work.
tried Opt #2, everything was easy and simple to work with and I got the tablet boot up :highfive::highfive:
Boots up nicely now without any trouble. thank you so much for all the help.
One thing i am still seeing is no touch response.
steps I took:
I removed the silver touch ribbon. booted the tab, and it boots up nicely. no touch response
inserted the ribbon back in and booted tab again. boots up nicely, no touch response
removed the ribbon from both connectors and reconnected, boots up nicely, no touch response.
removed the ribbon from both connector and switched directions. boots up nicely, no touch response.

is this a case of bad cable? Do i need to order one? where can I find it, ebay?

Once again, I cant thank you enough with where I am with this tablet. Currently I have connected keyboard+mouse using OTG cable.