• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Nexus 7 2013 (Android 6) stuck in start up animation

in my desperation to get it worked, couple of week ago i disassemble and cleaned all the connectors, i assembled back.. but forget to connect one of the cable....

my bad

i will prepare something to eat ill be back in 40 minutes
 
ok
as i mentioned before...
and now that the device has its USB port back to live.... is there any way i could access to the files that ARE in the memory?
 
Last edited:
i got the tablet drivers installed and the tablet ready to communicate with the laptop

but before reflasfhing... id like to give it a last try and see if i one of you could help me to get access to the files in order to get only couple of them
 
Unfortunately, fastboot does not give you access to the file system. You'd have to be able to boot into Android to get files using adb. Some recoveries offer an adb mode, but i don't think you can actually get to the files, that usually simply for sideloading updates.

Now, it could be possible to save some of your files in the user partition if when you flash the firmware you skip the userdata.img so, if you are going to follow the instructions, what you do NOT want to do is
Code: 
fastboot erase userdata
and
Code: 
fastboot flash userdata userdata.img

That could get you a bootable device and let you access files like photos and media. You will lose SMS and MMS messages as well as email because those are stored in a user database in the system partition.
 
ok

could you then help me to see what can i recover and then to continue with what we were doing?

that in fact, what you was helping me was to installer the OS in a way that i could perform full backup just like James Byrne proposed in his first post... is that what was you helping me to do?
 
What exactly are you hoping to recover? Because we are dealing with a non-booting system, this is all in the realm of "it might work, but..." There are no guarantees.

I read back through James' posts and i didn't see and magical backup solution. I think what he was getting at was installing a custom recovery partition like TWRP the would allow you to make a nandroid backup. What this is is a complete image of your device at the time the backup is made which you can then copy to an external storage device (sd card or PC) to keep it safe. If your tablet would then flake out like it is now, you could simply restore the nandroid and it would put your tablet back to it's functioning state. Of course, any files, data or apps added or changed since the backup was made would be lost.

That should be an option going forward, but I don't think it's viable now. Even if you could get TWRP installed, i don't see how it will help to backup a corrupt system.

Honestly, nandroids are better for developers who are constantly flashing different ROM's to their devices for testing. There are better ways to safeguard your data. But, again this is all going forward. The best we could hope for at this point is anything stored to the userdata partition.
 
You're a saint, Luna :).

Since the tablet was/is not rooted--and I'm pretty sure the OP didn't have the bootloader unlocked--in order to boot or flash a custom recovery that would allow you to use adb to perform file recovery, the OP would first have to unlock the device (bootloader), which would auto-wipe whatever data is on there.

Catch-22, I'm afraid....so data recovery is not really possible with a locked bootloader and a stock recovery (unless Android is booting, which it is not in this case).
 
lunatic59 said:
What exactly are you hoping to recover? Because we are dealing with a non-booting system, this is all in the realm of "it might work, but..." There are no guarantees.
Click to expand...

i am aware there is no guarantee in regarding recovering the data, hopefully since i was aware the nexus 7 2013 is SO unreliable, i didn't let the nexus handle too much important info.... so its not live or dead data BUT that i would like to give it a try IF it is within the possibilities.... i am more decide to re flash the system to get it working again to put it on sale asap...

Honestly
there are two folders i really WOULD like to get access to it, one is the rerware folder (where "mybackup pro" saves the backups [some user data; since its not a phone, i dont care for any address, contacts , call history sms nor mms... but some calendars events] ) AND a folder named nnplus_backup (which is the natural notes backup folder)...
just that..

BUT
now that you explained more clear to me what James sugested

lunatic59 said:
I read back through James' posts and i didn't see and magical backup solution. I think what he was getting at was installing a custom recovery partition like TWRP the would allow you to make a nandroid backup. What this is is a complete image of your device at the time the backup is made which you can then copy to an external storage device (sd card or PC) to keep it safe. If your tablet would then flake out like it is now, you could simply restore the nandroid and it would put your tablet back to it's functioning state. Of course, any files, data or apps added or changed since the backup was made would be lost.
Click to expand...

what i understand, it is more oriented to make a full system image but when it is necessary to do a restore, only the system image is restored with no user data am i right?
whats the purpose then?
and something else that catch my attention

it is only for pulling out the image WHEN the system is working fine and then to restore when it is screwed
but..BUT... will the TWRP stuff get me access to a corrupt system in order to pull out my files?
i mean... lets imagine i have a perfect working tabet, and i install the TWRP stuff, just like James suggest.. and then my tablet becomes unbootable like now... will i have any kind of access to my files?

if the TWRP stuff will not allow me that in future... then lets forget about that and continue with what you was helping me

lunatic59 said:
Honestly, nandroids are better for developers who are constantly flashing different ROM's to their devices for testing. There are better ways to safeguard your data. But, again this is all going forward. The best we could hope for at this point is anything stored to the userdata partition.
Click to expand...

thats what i think too
 
scary alien said:
You're a saint, Luna :).

Since the tablet was/is not rooted--and I'm pretty sure the OP didn't have the bootloader unlocked--in order to boot or flash a custom recovery that would allow you to use adb to perform file recovery, the OP would first have to unlock the device (bootloader), which would auto-wipe whatever data is on there.

Catch-22, I'm afraid....so data recovery is not really possible with a locked bootloader and a stock recovery (unless Android is booting, which it is not in this case).
Click to expand...

hi!

what is OP?
 
OP = "Original Poster" ... it's you.

I'm afraid @scary alien is correct. With a locked bootloader, there's not much hope for any data recovery at this point. The best we can hope for is to restore your tablet to a working condition.
 
Also, for the record, I own a 2012 (1st gen) Nexus 7 and have purchased three 2nd gen/2013 Nexus 7 tablets (for wife, daughter, and son) and all work flawlessly.

It's unfortunate @Kharl, that you're having issues with your particular device, but my experience w/the Nexus 7 line has been nothing but positive.

Cheers and best of luck--you're in extremely capable hands with our very good friend @lunatic59 :).
 
You might go HERE and download the latest OTA image for your device.
This page contains OTA binary image files that allow you to manually update your Nexus devices. This has the same effect of flashing the corresponding factory images, but without the need of wiping the device.
Click to expand...

This just requires adb and will work even with a locked bootloader.
The instructions are in the link but it would basically just require you to put the phone into recovery mode. Then within recovery put the device in adb sideload mode and issue a command to apply the update.

It may or may not work but it might be worth a try if you have adb working and a locked bootloader.
 
lunatic59 said:
@Brian706 , @Kharl said at the time he'd just updated to the latest release. Will an OTA update over itself? I thought there was some sort of version checking with an OTA.

I'm not sure myself, but at this point anything is worth a try. :)
Click to expand...

Honestly, i have no idea. I haven't had anyone try these yet as most of the time factory images are used.

It's my (limited) understanding that these are different than the standard ota zips that actually arrive over the air that people save and sideload. These are a full package and a sort of equivalent/alternative to a factory image. Based on the information I have, I would assume that it will overwrite the same as reflashing a factory image would.

Here is the original article I had read about it: http://www.androidpolice.com/2016/0...s-for-nexus-devices-alongside-factory-images/
 
@Brian706 and @lunatic59, I believe these OTAs are "block-based" OTAs that do indeed act as factory images and not OTAs that patch your files--i.e., they write/overwrite the blocks of your partitions and therefore "fix" issues folks have with bootloops (where a single mucked-up file in your /system partition could indeed cause that behavior).

I've not downloaded one to double-check this (at work at the moment), but I'll download and examine one tonight when I get home.
 
Last edited:
scary alien said:
Also, for the record, I own a 2012 (1st gen) Nexus 7 and have purchased three 2nd gen/2013 Nexus 7 tablets (for wife, daughter, and son) and all work flawlessly.

It's unfortunate @Kharl, that you're having issues with your particular device, but my experience w/the Nexus 7 line has been nothing but positive.

Cheers and best of luck--you're in extremely capable hands with our very good friend @lunatic59 :).
Click to expand...

Thank you a lot for the wishes!

i have to admit, i really loved that tablet.. it IS powerful (really powerful) beautiful screen, incredible elegant (i love the mixture of industrial/sleek/executive design..) beautiful photos and good audio quality... but the reliability of the system...

i dont know if i should say you one of the lucky one or ME one of the unlucky one... but there are half of dozen pages talking about the reliability of this model and in my own experience....

when i bought this tablet i got it with a lot that included 30 chinese ones (7 and 10 inches model) , 2 hisense sero pro, 3 asus transformer pad tf300 and 5 asus m172, 5 nexus 7 2013

the chinese ones (30):
4=broken usb port (incredible bad soldering and docking design, IT WAS designed to be broken in short time
2=broken audio port
1= bad battery
although terrible bad screen, terrible sound, but rock solid android OS (most of them kitkat)
failure with respect the amount i sold = 23.3%

the hisesnse (2)
1=overheat and then shut down
very well designed circuit board, speakers, mic, battery, gps anthena, bt anthena, wifi anthena all of them with connectors instead direct soldering (i found it weird but very convenient)
failure with respect the amount i sold = 50%

asus transformerpad (3)
beautiful device (althought it is too big for me but i offered as an high quality alternative to the 10 inches chinese ones)
beautiful sound
failure with respect the amount i sold = 0%

the asus m172 (5)
1=the screen flickers (loose screen cable, easily solved)
1=bootloop
failure with respect the amount i sold = 40%

nexus 7 2013
1=went into bootloop (twice, the user, system wiped and solved)
1=went into deffective touch
2=went into bootloop and deffective touch (one of those; mine)
failure with respect the amount i sold = 80%

id like to give it a last try but with kit kat, since when my tablet had kitkat it was the only moment i enjoyed stability...
the only reason why i am not sure aout going back to kitkat is.. the OTG support... which android 6 handles incredible well, a truly plug and play like a regular computer
 
Last edited:
Brian706 said:
You might go HERE and download the latest OTA image for your device.


This just requires adb and will work even with a locked bootloader.
The instructions are in the link but it would basically just require you to put the phone into recovery mode. Then within recovery put the device in adb sideload mode and issue a command to apply the update.

It may or may not work but it might be worth a try if you have adb working and a locked bootloader.
Click to expand...

Thank you Brian!
i already downloaded it and also the kitkat (just in case i decide to go for the kitkat)
 
lunatic59 said:
@Brian706 , @Kharl said at the time he'd just updated to the latest release. Will an OTA update over itself? I thought there was some sort of version checking with an OTA.

I'm not sure myself, but at this point anything is worth a try. :)
Click to expand...

Brian706 said:
Honestly, i have no idea. I haven't had anyone try these yet as most of the time factory images are used.

It's my (limited) understanding that these are different than the standard ota zips that actually arrive over the air that people save and sideload. These are a full package and a sort of equivalent/alternative to a factory image. Based on the information I have, I would assume that it will overwrite the same as reflashing a factory image would.

Here is the original article I had read about it: http://www.androidpolice.com/2016/0...s-for-nexus-devices-alongside-factory-images/
Click to expand...

scary alien said:
@Brian706 and @lunatic59, I believe these OTAs are "block-based" OTAs that do indeed act as factory images and not OTAs that patch your files--i.e., they write/overwrite the blocks of your partitions and therefore "fix" issues folks have with bootloops (where a single mucked-up file in your /system partition could indeed cause that behavior).

I've not downloaded one to double-check this (at work at the moment), but I'll download and examine one tonight when I get home.
Click to expand...

what you guys say (what i understand in my limited experience playing with them [other than just using it..])

is that you suspect that, the version available to download is different than the one our devices receive to update?

and also.. comparing the webpages for downloading OS images you gave me

one is the one that James gave me
it is titled:
OTA Images for Nexus Devices

And the other is the one that Brian gave me
which is titled:
Factory Images for Nexus Devices

which is the difference? which one is more stable?


 
It is the same version that you are already using. Two different methods, same outcome.

Factory images are flashed with fastboot and require an unlocked bootloader.

The ota images are sideloaded with adb and do not require a locked bootloader.

Both will put you on the latest stock firmware.
 
As far as I can see it, you've got two options.

First, use Wug's toolkit and use the soft bricked option as I explained before. That would be my first choice. It's all GUI and if it fails, it won't make things worse.

If that doesn't work, then we'll try the ADB sideload.
 
Just a quick follow-up to my earlier post...here is the updater-script file for the 2013 wifi Nexus 7 OTA (mob30j):

(!less_than_int(1461018176, getprop("ro.build.date.utc"))) || abort("Can't install this package (Mon Apr 18 22:22:56 UTC 2016) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "flo" || abort("This package is for \"flo\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: google/razor/flo:6.0.1/MOB30J/2775141:user/release-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "30,0,32770,32825,32827,33307,65535,65536,65538,66018,98303,98304,98306,98361,98363,98843,131071,131072,131074,131554,162726,163840,163842,163897,163899,164379,196607,196608,196610,197090,215039") == "abb60169fc4a41b53023f9868c381910b2537fc9" then
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "32,32770,32825,32827,33307,65535,65536,65538,66018,98303,98304,98306,98361,98363,98843,131071,131072,131074,131554,162726,163238,163328,163840,163842,163897,163899,164379,196607,196608,196610,197090,215039,215040") == "00982d341164911bd1d15ef2f99df20f3a653d15" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing bootloader...");
package_extract_file("bootloader-flag.txt", "/dev/block/platform/msm_sdcc.1/by-name/misc");
package_extract_file("bootloader.sbl2.img", "/dev/block/platform/msm_sdcc.1/by-name/sbl2");
package_extract_file("bootloader.sbl3.img", "/dev/block/platform/msm_sdcc.1/by-name/sbl3");
package_extract_file("bootloader.tz.img", "/dev/block/platform/msm_sdcc.1/by-name/tz");
package_extract_file("bootloader.rpm.img", "/dev/block/platform/msm_sdcc.1/by-name/rpm");
package_extract_file("bootloader.aboot.img", "/dev/block/platform/msm_sdcc.1/by-name/aboot");
package_extract_file("bootloader-flag-clear.txt", "/dev/block/platform/msm_sdcc.1/by-name/misc");
package_extract_file("bootloader.sbl2.img", "/dev/block/platform/msm_sdcc.1/by-name/sbl2b");
package_extract_file("bootloader.sbl3.img", "/dev/block/platform/msm_sdcc.1/by-name/sbl3b");
package_extract_file("bootloader.tz.img", "/dev/block/platform/msm_sdcc.1/by-name/tzb");
package_extract_file("bootloader.rpm.img", "/dev/block/platform/msm_sdcc.1/by-name/rpmb");
package_extract_file("bootloader.aboot.img", "/dev/block/platform/msm_sdcc.1/by-name/abootb");
ui_print("Writing DDR...");
package_extract_file("DDR.bin", "/dev/block/platform/msm_sdcc.1/by-name/DDR");
set_progress(1.000000);
Click to expand...

As you can see, this is indeed a block OTA update! :) [notice the absence of tons of "patch"-related edify commands]

Good stuff, Google! :)
 
I have to agree, Luna you are a Saint. I've learned a lot too. I flash my Nexus every couple days. I've never worried about data to much and every time I try to restore a Nandroid it ends in a bootloop.:( If @Kharl is connected to Google, the app data and possibly any media could be backed up and restored through the restore option in Setup Wizard.


There's so much informatiom in this thread. How's anyone ever going to pick best answer?:D
 
You must log in or register to reply here.
Back
Top Bottom