USB Debugging setting status not known
RETURN TO STOCK and/or UNBRICK your N7 3G+
Here, I have a doubt. If my device is bricked (don't know soft or hard) which means I have no way of checking USB Debugging setting status (ticked or unticked since I don't remember also), can I still use your guide to return to stock.
and here
6. Now type:
Code:
fastboot -w update image-nakasig-jdq39.zip
Here also, does removing
-w makes sure that data won't be wiped in the process?
My whole story goes like this:
My Asus Nexus 7C 2012 got 'bricked' not because I tried to either flash any custom rom/stock (Actually I never did that) or do anything stupid but because of some sets of reasons which resulted in bricked devices all around the world, and like many other users, it happened 'just' after the warranty period expired.
(what I remember is that I used an app using GPS (GPS Essentials) for tracking for the first time in the morning, then I forgot to exit the app and later in the evening, the device stopped booting for ever). I researched too much to an extent that now I'm bored. Before, I knew nothing about flashing, custom roms, stock, CWM, ADB, fastboot etc etc now I may be a bit of help to other rookies
but couldn't help troubleshooting my N7C (2012) till now.
I think I have found some step-by-step guides like this URL (unbrick.itcse dot com/unbrick-soft-bricked-nexus-7) and, believe me, many others. The thing which always stopped me finally giving at try to that was the hope of somehow be able to recover the precious data from device since it stopped booting. Deciding to go for flashing has become even harder because somewhere I read to remove -w from some command like fastboot -w update image-nakasi-jwr66v.zip to avoid wiping data and now I can't seem to find the webpage. Also, I never updated the android from its factory build i.e. 4.2 I guess and actually there used to be a notification present asking for updating the system to some higher version build as far as I remember which I never touched because I was worried it would wipe clean the app settings/data which I did not want at that time.
When I said bricked, I meant that the device doesn't get past the google loading screen. I can get to the bootloader page (where it shows the fastboot mode on line one) and when I select either recovery mode or start, it just freezes at the google screen. Also, I'm kind of sure that I never touched the USB debugging settings before the device got bricked. So if it was not factory enabled, probably it won't be now if that's any meaningful since its not booting!
Hopefully I've explained fully about the problem that I'm having. This is the kind of a problem that others also faced. So, if anyone here knows the right forum or any blogpost which explains the step-by-step procedure to deal with this issue, please share it asap.
At the bootloader prescreen, if that's what its called, It says line by line
FASTBOOT MODE
PRODUCT NAME - tilapia
VARIANT - tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.10.0_1021
SERIAL NUMBER - XXXXXXXXXXXXXXXX
SIGNING - not defined yet
LOCK STATE - LOCKED