yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Homurato:
A very old thread i know, but maybe i'll get some answers from people who faced the same problem who knows :D

so i decided to update my nexus 7 2012 to 5.1.1 and after that got bricked and whenever i start the tablet i get stuck on the fastboot screen (at least it works)

no recovery, nothing else works, when i hook it normally with pc i get APX mode, but the good news is that i can start it in fastboot mode

tried to factory reset it with NRT toolkit on bootloop mode with no success tried flashing other bootloaders and stuff with no success

using ADB shell i can format it i can push the bootloader but when it is writing i get a FileWritingFailed error and that happens when flashing recoverys, system or anything else

any help is really appreciated, i'm on an unlocked bootloader with fastboot mode, those are my only options

View attachment 3308336

View attachment 3308337
[Nexus 7 Original Development] mccabet:
Not sure what the actual problems you are having are, I would recommend going to the beginning of this thread and attempt the procedure to back-up the tablet before you corrupt it beyond repair ( is it possible?? )

When you create the backup files, you should get some evidence as to the problem, such as corrupt partitions, etc. Backup all partitions you can read. If it fails, try again.

Good Luck!
[Nexus 7 Original Development] Partitionator:
I think the emmc is dead (went to read only because of to much badblocks) but you can try to Boot a recovery without flashing it with fastboot boot recovery.img
[Nexus 7 Original Development] Homurato:
yeah i'm not sure neither, but since i cannot, access neither the OS nor the recovery

making backup isn't doable

Well that helped a little i guess ! booting the recovery was successful via ADB but i can't mount nor format anything, so i booted the flatlinerecovery to try and backup my blob.bin

couldn't complete the first step to install the nvflash bootloader, but backing up the blob.bin succeeded, i think, now well i don't really know what to do
[Nexus 7 Original Development] mccabet:
If you successfully was able to create a blob.bin, then you should have access to nvflash.

Go back to the first post and follow the link to how to create your blob.bin. In the instructions it shows how to use the blob.bin to enable nvflash access. It also tells you how to backup important files and partitions. MAKE SURE TO DO THE NEXUS 7 COMMANDS, I goofed initially.

Try to create those backups first. Then I would start backing up all the partitions, labeling which one they are. You can also dump the partition table to a text file to make sure it is correct. Once you have all you can backup saved, the you can try recovering the partitions.

The partition text file will have the partitions that are available by number and name.

to enable nvflash access, reboot into APX mode and Enter the command:

wheelie --blob blob.bin

Save partitions by using command :

nvflash --resume --read PartitionNumberToRead NameToSaveTo.img

substitute the number of the partition and the filename to save to.

If a backup of a partition is to fail, try again.. I had to do it more than once on a couple of the larger partitions.
[Nexus 7 Original Development] Homurato:
Hello and thanks, that was very helpful and there might be some hope after all for the tablet, the thing i'm not sure about

is the flashing bootloader that didn't work, as i said there was step 1 flashing the flatline BL and step 2 backing up the blob, step 1 didn't pass

as the bootloader couldn't be written, so i tried to backup the blob anyway and it worked, does that mean something ?
[Nexus 7 Original Development] mccabet:
Don't get your hopes up too high, you can still have a flash problem

To make sure, you loaded the recovery and attempted to install the bootloader in the recovery step 1 and that failed? But step 2, create the blob, did work.

Only thing I can say is to try the blob using wheelie. wheelie --blob blob.bin

What do you get? If you get an 04 error, your blob maybe bad.

If it appears to work with out errors, try the backup commands and see if they work.

If you run nvflash with no parameters, you will get a command list. Try reading the partition table, nvflash --resume --getpartitiontable part.txt

good luck
[Nexus 7 Original Development] Homurato:
indeed i'm getting a 04 error, incorrect blob, guess that's the end of the road then,

when i boot the recovery i get many mount errors, also i can't mount nor format anything
[Nexus 7 Original Development] Partitionator:
You could let it run from a USB-OTG Device. dd your mmcblk0 to a USB-Pendrive an modify initrd that it uses sda instead of mmcblk0.

But you would need your PC for every boot (to upload the Kerneles, because you can't flash it) and you need to leave the Pendrive attached all the time.
[Nexus 7 Original Development] Homurato:
Thank you sir that's pretty much interesting, is there a guide or a tutorial on the matter ? because it doesn't seem as easy as usual
[Nexus 7 Original Development] Partitionator:
As far as I know nobody ever tryed this before so there are no tutorials. But I can help you if you want.

EDIT: You need a fast(!) USB-Stick (it will be erased and at least the size of your emmc) and a USB-OTG-cable

Then you have to boot boot TWRP via fastboot. Navigate under Advanced to Terminal Command and select /dev/block. Then enter ls to see all block devices. After that attach your USB-Stick and type ls again. Now search for the new device (is should be sda (in the following commands I assume its sda)

Than clone the emmc to the USB-drive it with

dd if=mmcblk0 of=sda

This will take some time.

I will try to make the new boot.img.

Maybe it would be a good Idea if a Mod moves this to a new Thread...

EDIT2:
[Nexus 7 Original Development] Partitionator:
Is your device grouper or tilapia?
[Nexus 7 Original Development] Homurato:
Hello and thanks for the help, as this is pretty interesting as a solution maybe then i can write to internal memory from the stick when booted

im grouper 32gb with unlocked bootloader
[Nexus 7 Original Development] Partitionator:
I don´t think so. You can see your Problem as a Hardware failure...

OK I have the 16GB grouper. I already unpacked the ramdisk and moddet it, now I just have to repack it.
[Nexus 7 Original Development] ichigo_kurosaki:
i bricked my nexus 7 grouper 2 days ago. i dunno how it happened but before it did, my tab had been acting weird for days. i encounter freezes and screen unresponsiveness and the only way to get out of it was to do the force reboot. so long story short, i was able to boot back into my custom rom (was on multirom twrp and running optipop as primary rom and slimkat as secondary) but then it happened..i got stuck at the google screen and could no longer boot. no more multirom selection screen..i tried booting into bootloader/fastboot..it was ok..but when i tried to boot into twrp it gets stuck on the TWRP blue intro screen. now my tab is just like this:

https://www.youtube.com/watch?v=m0hv6AJNKK0

So now upon research i was able to find stuff about NVFlash and the Flatline recovery..i did the steps on the site..i managed to flash the flatline recovery..but i can just go as far as step 6 i think..that step that tells you to boot into recovery and go to advanced>wheelie and do whatever it says there. but that's it. i'm stuck there. that next procedure taling about..this to be specific: "After the flash process has completed you will need to reboot your device into recovery. It is important that you reboot completely rather than directly enter recovery. If you don't there is a risk that the process can fail.

Once your device has booted into recovery, select the "Wheelie" menuitem in the "Advanced" item, accepting the warning if you wish to continue. At this stage you will need to select "Step 1: Flash AndroidRoot BL" which will flash the AndroidRoot custom bootloader.

The device will power off. Power the device back on and allow it to boot normally into Android. Once the device has fully booted please reboot the device back into recovery mode."..where the hell do i find the step 1 in that wheelie thing? :'( that's my point. i have the nvfllash tool, the naked drivers. and here is the screenshot of my xtracted nflash zip..i can't find any wheelie bat/executable thingy anywhere.:( can you guys please help me with an easy to understand procedures? will be greatly appreciated.:)
[Nexus 7 Original Development] Partitionator:
The wheelie thing is in the recovery.

But there musst also bee a wheelie binary to youse your generated blobs
[Nexus 7 Original Development] ichigo_kurosaki:
Yes i have accessed that. What i did was flash the flatline recovery, then booted to it, went to advanced > wheelie > accepted that blah blah then message

attempting to mount data...

That's all..i didn't run the nvflash bat and even if i run it i duno how to use it..what should i do next..i can only go as far as that in the instructions..that part that says go to wheelie step 1 "flash bootloader, i have seen a screenshot of it (i googled) but on how to acces it is ?? for me. Lol..please do help..

EDIT: wheelie binary/executable.is what i'm missing here i believe. No link to download that.:(
[Nexus 7 Original Development] ichigo_kurosaki:
Blob files compatibility?

hi..me again..:D

on my continued research to revive my dying grouper, it then came to me to look in the Q&A section for our dear grouper..i found the thread for hard brick (though i belive my brick state is not a hard brick as i am not in APX and can still access fastboot/bootloader) now..i found someone sharing his blob file from his 16GB grouper here. now my question is can i use blob from 16GB grouper on a 32GB one? maybe this will be the shortcut for me finally reviving my beloved grouper.:D just a though..:) expert opinions and answers will be most welcome.:) for those who are looking for blobs check that thread.:D
[Nexus 7 Original Development] AndDiSa:
If you can still access bootloader, why do you want to use flatline?

1. Flatline works only if you have prepared the blobs of *your* device before it became a brick, blobs from other devices will not be accepted.

2. If you can access to bootloader, fastboot flash a system image from google and everything should be fine again unless you have hardware problems
[Nexus 7 Original Development] ichigo_kurosaki:
Thanks for the reply.:)

thank you for the reply mate.:) hmm you think so that i don't need flatline? my bootloader is bad.:( for an accurate description/picture of the state of brick my device is in (i don't think this is not a hard brick as i don't have apx mode. here
[Nexus 7 Original Development] AndDiSa:
If your Nexus is behaving like shown in the video, I suppose your boot partition (*not* the bootloader) is corrupt / erased and due to that the device is not booting.

Try to get familiar with fastboot, have a look here and download the factory image for your Nexus device (Nexus 7 WiFi (2012) -> nakasi). Flash that image and you should be recovered from the *brick*.
[Nexus 7 Original Development] ichigo_kurosaki:
already tried.:(

yes, i have already tried flashing factory image..all partitions flash successfully except bootloader with unknown error something..used the NRT for flashing it. tried various versions of factory images for nakasi..lollipop 5.1.1, kitat, JB..nothing works..sorry for the questions..:(
[Nexus 7 Original Development] AndDiSa:
What is your version of the bootloader? There are / were factory images with a wrong bootloader inside which cannot be flashed (you might want to look here). Try to find a factory image which supports your bootloader version, i.e. if you are still on version 3.41 try to flash the JZO54K-factory image, if you are on 4.1.3 try to flash the JOP40D-factory image, and so forth.

If running the flash-all.bat / flash-all.sh does not wotk, try to flash the partionions singulary, i.e. extract the partition image files from the factory image file and run the following commands:

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash data data.img
[Nexus 7 Original Development] ichigo_kurosaki:
i'm on the 4.23 bootloader. tried flashing everything manually after learning to setup the SDK (been using the NRT for a while now) still nothing..erased what needs to be erased (except bootloader ofcourse) manually via fastboot..flashed everything accorfing to sequene in the instruction..all goes well until well..bootloader flashing..which always fails.

To be specific i am confused by these (see screenshot attactments (note, these screenshots are borrowed from transformer nvflash..:D

you see, i can get here

and here:

and finally here:

but when i click to accept whatever it says, i don't get here (wheelie menu):

instead, the flatline-grouper recovery just displays

flatline CWM Recovery v1.0RC1

E:can't mount /cache/recovery/command

E:can't mount /cache/recovery/log

E:can't open /cache/recovery/log

E:can't mount /cache/recovery/last_log

E:can't open /cache/recovery/last_log

so llike what i said earlier maybe i'm msissing something here..the whelie binary something..
[Nexus 7 Original Development] AndDiSa:
As far as I know the flatline-grouper-recovery is working only on 4.13 bootloader, not on 4.23. Probably that's the reason why you are getting the errors in the recovery.
[Nexus 7 Original Development] ichigo_kurosaki:
Thank you..that's my last bet.:) would you mind giving me a link to a working 4.13 bootloader? Tia.:)
[Nexus 7 Original Development] AndDiSa:
If you look at the list of factory images, all those not marked red are file, I.e. they include a functional and flashable bootloader. The same is valid for the latest factory images, e.g. lollipop 5.1.1.

You can extract it from there and try to flash using fastboot.
[Nexus 7 Original Development] ichigo_kurosaki:
marked red? what do you mean? can you please provide a screenshot? :fingers-crossed:
[Nexus 7 Original Development] Partitionator:
As far I know 4.4 contains ja valid bootloader
[Nexus 7 Original Development] AndDiSa:
Have a look at post #183, there is a link to the list of factory images and their status ...
[Nexus 7 Original Development] secret.animal:
I believe my nexus 7 2012 wifi (grouper) tablet has hit the end. Tried going back to stock after lock ups and freezes on the system. Where I had to hold the power button from 20 seconds or more for it to reboot.

Tried going back to stock and NRT it starts to lockup on the bootloader 4.23 which I have had forever. I try to put a recovery stock or otherwise on through fastboot and the system locks up before rebooting from modified boot to install. I can put temp on there and flash a img of boot.img, but a recovery img fails everytime.

If I tell it to flash system.img from a Stock file it says it completes but I really don't think it does.

Any idea, what I might be able to do??
[Nexus 7 Original Development] secret.animal:
More research tells me after getting lucky to flash a recovery. That the motherboard memory is blown. No storage. Going to have to replace it.
[Nexus 7 Original Development] deechte:
Hi, I've been the lucky guy to have bricked my Nexus 7 (grouper). Now I've replaced the motherboard and try to make the necessary backups to prevent this from happening again.

So far I've been able to use the AndroidRoot.mobi guide (thank you guys!) to backup the blob files (8 in total, they correspond in size with the screenshot earlier in this thread). My question is if I'm save now to unbrick my Nexus when I brick it in the future?

I'm confused, cause the AndroidRoot.mobi guide says, after being done with the 8 blob files:

Is this bricksafe.img needed to restore the blogs or for any other purpose when the device is bricked? Or isn't it? And "Support being withheld" by whom then? AndroidRoot.mobi, or Asus/Google? The latter I don't care, warranty has ended any way.

Subsequently the guide says:

Same question: do I really need them when my device is bricked, or is it for another - less fatal - purpose?

And my last point of confusion: can I just let the AndroidRoot.mobi recovery and custom bootloader like it is when ending the AndroidRoot.mobi guide? I see many people trying to get the original 4.23 bootloader on it afterwards. Should I do that too, or is that only when you're still under warranty and want to be able to return the device to asus/google.

The reason I'm not simply just pulling those files is that I only have a Windows 8.1 and a Windows 10 PC, and a Windows 7 PC without admin rights. So I have no PC with working APX drivers.
[Nexus 7 Original Development] kasserx:
mr i need help from you can you compress all files nexus 7 as rar or zip then uploade it on mediafire because my nexus 7 fully bricked after remove mmcblck0 on ubuntu desktop

all partition as bootloader ,boot,system,userdata are wiped now my device just boot with blackscreen with APX mode

iwant all your files please just to boot only bootloader
[Nexus 7 Original Development] AndDiSa:
[MENTION=565661]kasserx[/MENTION] I told you already that somebody else's files will not help you. You need files created specifically for your single device. If you did not create it before unfortunately you are lost ...
[Nexus 7 Original Development] kasserx:
i dont not how can create it so

I need the basic files

for example:

blob.bin

bootloader.bin

bct.bct

bricksafe.img

recovery.bct

bootloader.ebt

factory-config.img

mda.img

eks.img

rely i dont know how can find them or create them

to re-survive my nexus7 bcuz i like my device

i want your help:

my uid: 0x166160e2a600e00

sbk v1.1 0x7D0EF701 0x1EFD0400 0x4006E702 0xD8F00403
[Nexus 7 Original Development] AndDiSa:
You cannot create the files because your device is bricked ...
[Nexus 7 Original Development] DutchMan_1990:
[MENTION=2188693]AndDiSa[/MENTION] As it's doesn't work with 4.23 bootloader, the how can I get back to 4.13.
[Nexus 7 Original Development] AndDiSa:
Fastboot flashing a 4.13 bootloader, then flashing the flatline image and preparing the blobs. After you've done that you can revert to a 4.23 bootloader and restore your ROM.

But keep in mind: flashing the bootloader is the most risky part! If (for what ever reason) the bootloader flash failed you might have a real brick. *do not reboot* unless you are sure the bootloader flash succeeded.
[Nexus 7 (2013) Q&A] adamhlj:
Does anyone know how to enable LTE only on the device? Since there isn't a dialer pad app, I can't type in *#*#INFO#*#* to manually select the LTE Only mode.
[Nexus 7 (2013) Q&A] kpetrie77:
Stock launcher you can install an app that has a shortcut. Battery Monitor Widget is an example.View attachment 2289853View attachment 2289854View attachment 2289855

Otherwise, use launcher that supports activities shortcuts. Below is Nova, others are similar.

View attachment 2289858View attachment 2289859View attachment 2289861View attachment 2289862
[General Questions and Answers] rome1983:
Hey, New to this here and in need of help with my Xperia S Lt26.

I bought it off eBay earlier this year not realising it was rooted, once I got the phone I performed a factory reset and removed apps like moxier and superSU (which I now think was a mistake).

Anyway with the new update out my android system says computer required and when I connect to Sony update on computer it says I can't do it, I have also tried to update via WiFi with no luck as my girlfriend was able to do her update this way.

How can I get my phone back to its stock factory settings and avoid this happening again?

I want my phone back to how it should be, like it was never rooted, then I can update it the correct way.

I have never rooted or flashed a phone before, so step by step would be great, thanks
[General Questions and Answers] rome1983:
just want to add I tried to reinstall superSU and do the remove root on my phone but once I opened the app it came up that no binary was found
[General Questions and Answers] rome1983:
somebody surely must have an answer
[MDA II, XDA II, 2060 General] burbuja:
Hi to all.

Does anyone know where can I download some Himalaya PDF manuals (quick start, user guide, etc...) in spanish ?

Thanks a lot.
[MDA II, XDA II, 2060 General] paketecuento:
esta dificil. tendras que verlo en ingles...

esta el el ftp de esta pagina.

it's ditificult to find. you'll have to read it in english...

it's on xda ftp.
[MDA II, XDA II, 2060 General] pancho:
Send me your email and i will send you my manuals in Spanish...
[AT&T HTC One (M7)] jomak123:
Hi Everyone, I am new to Android, iPhone user who hated Apple, glad to be on the HTC one. However, I loaded myself GE 4.3 and don't like it for the fact I can't use Zoe and they way GE is laid out. How can I load the stock HTC build back?
[AT&T HTC One (M7)] rdub504:
Did you create a nandroid backup?

---------- Post added at 03:45 PM ---------- Previous post was at 03:33 PM ----------

If not,that may not be possible through the device.I know there was a AT&T leak of the 4.3.3 jellybean Rom with sense 5 some developers are using now,so the benefits of 4.3.3 are are there,without having to revert back to 4.1.2 or 4.2.2. I have always been a fan of arhd by mike_1986, and some say cleanrom is good also. One of the first things you will learn is nandroid backups are key in situations like the one you have now,it allows you to revert to the Rom used prior to the flash of the one you decided to try. I would familiarise myself with it before you go any further.
[AT&T HTC One (M7)] jomak123:
I thought I had a nandroid backup, but I am new to Android so the file structure of the location would be?

I was looking for the AT&T sense leak to try that build over the GE. Hopefully I can find it.
[AT&T HTC One (M7)] xcrazydx:
It's in the HTC one android development section.

http://xdaforums.com/showthread.php?t=2440315
[AT&T HTC One (M7)] rdub504:
This is a quick tutorial on how to create a nandroid.

https://www.youtube.com/watch?v=inLWqtN0J24&feature=youtube_gdata_player

Also Your nandroid would be applied in recovery,just like when flashing a new Rom,except you select the option for backup instead of a downloaded Rom.
[AT&T HTC One (M7)] Nick281051:
Honestly I don't think you understand the concept of the difference between roms. An at&t sense build is something that's completely separate and you don't just flash one on Top of the other. Once you flash a rom it completely erases what was on there before. Hope this helps
[AT&T HTC One (M7)] chenchen399:
Don't flash the leaked build that some people have posted, since the official update is coming in a matter of several days (I hope). You can search for the stock RUU file on this forum. You can also go to the HTC website, and find your device under the support section. Find the downloads and updates section, and download the most recent update for your HTC One. This is a .exe file that will completely wipe your device and restore it to stock so be sure to back everything up!
[Sony Xperia S, Acro S, Ion] KWOKSFUNG:
I used to listen music with the minimum volume (just above mute), using the stock headphone and it was ok

I havent been listening to music for weeks. But when I listen to music again today, seems the minimum volume is much louder than before!!

Is it becoz I have upgraded to the .96 firmware??

anyone found this problem??

or just problem of my personal health??

any way to get the volume between mute and the min??

please help i dont wanna get deaf

thx
[Sony Xperia S, Acro S, Ion] Mr. Khan:
What rom you use?

Try stock rom or flash rom again..
[Sony Xperia S, Acro S, Ion] KWOKSFUNG:
trinity rom

wont flash stock rom back now

This rom is much better in any other way