yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
I believe I've hard-bricked my Nexus 7. I'm not stranger to flashing, etc., but something must have messed up this time. I was previously running stock Android 4.3 with TWRP recovery and my tablet took the OTA update. The update of course failed because of the root and recovery, but instead of going back to Android 4.3, it wouldn't boot past the fastboot screen (bootloader screen? with the green android).

So, planning to return to all stock, I downloaded the official Android 4.4 .tgz file and extracted it to my platform-tools folder for the Android SDK. I ran "flash-all.bat" as explained in this tutorial: http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/

Something must have went wrong because the screen went black and will not turn back on. When plugged into the PC, it is recognized as only an "APK" device. Sources online indicate that this is hard-bricked, as there is no "nvflash" openly available for the Nexus 7 to restore the bootloader.

1. What happened and how can others prevent this?

I think I should have flashed each partition individually (i.e. boot, recovery, system, etc) instead of "flash-all." Any idea what happened to the bootloader? Any other ideas on how to restore the bootloader?

2. What to do now?

EDIT: Apparently my device is out of warranty. Crap.

EDIT 2: Apparently I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi)... Opps!

There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?

Thanks for your assistance in advance! This forum is great.
[Nexus 7 Q&A, Help & Troubleshooting] noradoor:
What about pressing and holding power button for more than 30 seconds?

Once it could boot and you could enter into fastboot mode, then I think you would get a chance to save it.

BTW, I did mess up when I was flashing KRT16O factory images, which was the earlier release for Kitkat.

At that time, I just used the flash-all.bat like you did. And in the second round, I still failed when following and typing the listed commands in flash-all.sh.

So I chose to use nexus toolkit after that.
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
Thanks for your reply.

I keep trying that, along with the various other combinations of power button and volume down and volume up. Nothing. The most that happens is when it's plugged into the PC, the PC makes the sound of something being connected and disconnected. I just tried unplugging the battery too. I'll let it charge over night and try again tomorrow.

When yours failed the first 2 times, you were still able to get into fastboot? You're right, if I can just get there then I'll be alright.

Thanks again.
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!

1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)

2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
[Nexus 7 Q&A, Help & Troubleshooting] noradoor:
No problem,bro. I think you can always get responses here at XDA though I didn't help you out.:p

And yes, I could still enter into Fastboot at that time.

However, I was not able to reboot my N7 using the aforementioned methods since it got stuck in Google logo.:(

Hence I removed the battery(:silly:), booted it and used the key combination to get into Fastboot. And you know the rest, used the toolkit....
[Nexus 7 Q&A, Help & Troubleshooting] xateeq:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)

I do this all the time just for fun :D

Let me give u step by step instructions.

1. Download this tool kit

http://xdaforums.com/showthread.php?t=1766475

2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)

https://developers.google.com/android/nexus/images

3. Install toolkit, Select your device and don't worry about android version because u have non rit now :P and install the proper drivers for fastboot to work.

4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.

5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).

6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.

7. Enjoy.

FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
[Nexus 7 Q&A, Help & Troubleshooting] RootTheMachine:
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
Thanks for your help, but unfortunately I can't even enter fastboot. I can only enter APX mode, which apparently is pre-fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
Thanks. I saw that thread, but of course it was too late at that point. Perhaps I'll look into buying one with a cracked screen, or sell mine for parts on ebay.
[Nexus 7 Q&A, Help & Troubleshooting] xateeq:
Plz dont tell me u flashed wrong bootloader, plz plz plz.
[Nexus 7 Q&A, Help & Troubleshooting] SteveRiley:
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!

---------- Post added at 11:40 AM ---------- Previous post was at 11:09 AM ----------

Well, now isn't this weird... I unplugged the USB cable from my PC and then plugged it into the wall charger. After waiting a while, I was able to boot the Nexus into the "wrong" bootloader. I immediately flashed the correct one, and now am running the latest factory image.

[MENTION=3550399]zamboniman87[/MENTION] -- I did find a thread on Android Central describing a situation in which someone erased their bootloader. The thread contains a tool that a couple folks claimed to help fix the problem. You might give that a try.
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
Lucky you! This gives me hope though. I'll check it out. Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
yep.... I feel dumb. haha.
[Nexus 7 Q&A, Help & Troubleshooting] psykg:
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery :(

img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0

all I can load is fastboot mode

img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0

I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
[Nexus 7 Q&A, Help & Troubleshooting] psykg:
hey it worked thanks!

at first there were problems with fastboot and drivers somehow usb 2.0 was a bit problematic but usb 1.0 was able to see device

after downloading many drivers (some from nexus tollkit some from web) , and after few restarts of device and bootloader, pc was able to recognize device and than I had to go 2 times with nexus tololkit >softbrick/bootloop

1st time failed

2nd time worked!

thank all!
[T-Mobile Samsung Galaxy Note 3] WhAtSROoT?:
ok so my phone is changing network mode, and I have to manually change it back to lte, usually its on LTE/wcdma/gsm (autoconnect), but then it drops down to 4g, but instead of staying in that network mode it drops down to wcdma/gsm (autoconnect). I took it to the store and the guy said its probably due to the servers being worked on but that's sounds like a load, I hate this because to get LTE again I have to go and manually change it back to the top setting, and I don't think this is normal since the autoconnect mode should in theory switch inbetween networks seamlessly, I have to know if this is a defect before dec 3, that's my deadline.
[T-Mobile Samsung Galaxy Note 3] flipq88:
Probably a defect, mine never switches by itself, even if I don’t get lte
[JAM, MDA Compact, S100 Software Upgrading] garethsimpsonuk:
Hi I know the big storage hack is plastered all over this forum but i still cant get it right.Some one please help me!

Ive got a magician with rom version 1.13.00 WWE radio v. 1.12.00 (i used to have 1.12.00 but i upgraded it by accident.<I woz finkin of it anyway>)

I fink Ive tried every procedure possible but always have problems but basically this is what ive done:

1.Using OS image tool ive copied my rom to pc.

2.Ive changed the 80 00 00 thingy to b8 01.

3.Ive tried to use the os image tool to write it back t ppc but it comes with a usb/communication error in programme A.Im using this way because I have only 32mb mmc card.

Any help would be much appreciated,

Thanks
[JAM, MDA Compact, S100 Software Upgrading] oltp:
wiki

Try the wiki (top right link on the page) & go to the magician section. It contains a description howto patch a shipped-rom, the one you used to upgrade to 1.13WWE, & get BS. Apperently you missed this method.

Cheers, M
[JAM, MDA Compact, S100 Software Upgrading] garethsimpsonuk:
I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.

My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!

Thanks 4 ure help,

Gareth
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Stop,

You're going in the wrong direction. The BS from shipped-rom method is about patching the provider supplied exe file. & after the patch you run it like a regular rom-upgrade. No SD or MMC involved!!! It's a rom-update via USB like the normal update.

pls read it once again @ the wiki.
[JAM, MDA Compact, S100 Software Upgrading] garethsimpsonuk:
ok thanks im trying that now.Im stuck on getting nbfdec to run.Ive extracted it to the unzipped rom folder.I open ms-dos command prompt and drag and drop the .exe on the command line to save typing the path.The program runs but then it crashes.Can anyone help me?
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Try putting everything in "C:\BS" saves a lot of typing errors including filename handling.
[JAM, MDA Compact, S100 Software Upgrading] garethsimpsonuk:
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.

Sorry for going on and on I cant get my head round it!

Thanks
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Hi Rod,

To go to C:\BS from your personal doc&settings type on the commandline:

cd \ [Enter]

now you should be in C:\

then type:

cd bs [Enter]

now you should be in C:\BS

Works for other directories too.

Cheers, M
[JAM, MDA Compact, S100 Software Upgrading] garethsimpsonuk:
Thanks, that helped me a lot.Ive done everything els now so I converted it back to nbf and then executed the maupgrade_noid.It checked device info then displayed the rom to and from screen and both were blank.I proceeded and it displayed the 'success' screen but nothing had actually happened on the ppc.Ive tried the other upgrade program and the one thats cracked on the site.

Any help would be much appreciated

Thanks
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Did you reset after the update process finished? & if so did it boot normally? & if so did you look at the internal storage folder size? Cause that's the only thing that's changed & the ext-rom has disappeared. Oh & you shouldn't see the customization start after a hard-reset...

btw rom to & from shouldn't be blank, pls run the update program without patch cause I think the editing somehow invalidated the shipped-rom. The original upgrade program should work & if so you know what's going on. If the original program fails there might be something with your device.

So start the plain shipped-rom first to find out..
[JAM, MDA Compact, S100 Software Upgrading] garethsimpsonuk:
Thankyou!Its worked!!

I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?

Thankyou very much oltp for your help.It's much appreciated.

I think this site is long overdue a donation from me.

Cheers m8
[JAM, MDA Compact, S100 Software Upgrading] oltp:
The header contains info about romtype & provider name, probably some things more I'm

not sure about. The reason for changing it is to avoid errors like the country id error. With the use of maupgradeut_noid it's less important.

One thing I'm questioning is the reason why some of us have probs with connecting to the, I believe, special O2 services. Some claim there not able to connect anymore... Can some other setting as well. I'm on T-Mobile & everything works fine.

Basically if the upgrade was succesfull, you have an enlarged storage & the rest of your device will be working as before.

Cheers, M
[JAM, MDA Compact, S100 Software Upgrading] shivam:
how much space would i have in my main memory now? i have a 64+64 system (O2 Xda Mini) now branded to T-Mobile 1.33 and now applied the new patch (BIG STORAGE) using the Wiki Information guides. However any idea how much FREE space on first reboot i should have.
[JAM, MDA Compact, S100 Software Upgrading] shivam:
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?
[JAM, MDA Compact, S100 Software Upgrading] shivam:
nevermind got it :)

Total Main Memory - (FREE MEMORY) - 43.99MB Storage / 25.54 MB Programs! woo hoo this is HOT
[JAM, MDA Compact, S100 Software Upgrading] oltp:
First boot takes much more time than next boots.

Have fun, M
[JAM, MDA Compact, S100 Software Upgrading] bartgomes:
all,

look over here.

cheers!
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Sorry to say, but it's old news. We got a thread about it for three months now I guess with that method. Problem is you always need to update first & then dump your rom again. & somehow not all dumps are accurate. The brick change with a SD is larger than with a shipped-rom.

M
[Nexus 5 Q&A, Help & Troubleshooting] stenzor:
Haven't changed anything on the phone at all today, no new apps or new settings.. About half an hour ago all my buttons stopped responding. Power button, volume rocker don't do anything. Strangely enough, holding the power button still restarts the phone, and holding the volume down button at the same time still gets me into fastboot.. so clearly it's not a hardware issue.

Also, plugging the phone in doesn't register that it's charging.. however if I restart the phone while it's plugged in it will register that it's charging, but unplugging it will still show that it's charging. I've obviously restarted the phone several times already.. any clue what this bizarre issue could be?
[Nexus 5 Q&A, Help & Troubleshooting] khuzema9:
if you have some backup , restore it , otherwise you can just flash facotry image ,
[Nexus 5 Q&A, Help & Troubleshooting] stenzor:
Yeah I was hoping to do that as a last resort.. but i'll try if nothing else works
[Nexus 5 Q&A, Help & Troubleshooting] Hecarim:
Pretty strange issue. I agree and think your best bet would be to try and restore a backup if you can. Hope everything works out for you!

Sent from my Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] stenzor:
Alright, I did a factory restore... still the same issue
[Nexus 5 Q&A, Help & Troubleshooting] stenzor:
Aaaaand literally 30 seconds after I posted that they are working again
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
I'd fastboot the factory image and if it still does it, rma it
[Nexus 5 Q&A, Help & Troubleshooting] stenzor:
They started working again after I approved the 13 app updates or whatever it does to the stock google apps after first boot
[LG Optimus L9 P760, P765, P768, P769] tawhid111:
How to fix partion problem !!!

After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:

ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...

1.install fastboot drivers

2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !

Make sure you write down your imei or serial number AND make sure battery is fully charged . then

Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides

Thats it
[LG Optimus L9 P760, P765, P768, P769] artit:
So you solve it! :good:
[LG Optimus L9 P760, P765, P768, P769] foreverman:
:/

Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
[LG Optimus L9 P760, P765, P768, P769] puntoazul:
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
[LG Optimus L9 P760, P765, P768, P769] theshamrockking:
Where can I find the lelus script?

Sent from my Note II
[LG Optimus L9 P760, P765, P768, P769] ciccillover:
Sorry for reviving such an old thread, but oh well...

Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?

My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.

Any hint?
[LG Optimus L9 P760, P765, P768, P769] puntoazul:
Then you need a Technician with a Octopus Box to repair your partition table...
[LG Optimus L9 P760, P765, P768, P769] kuma82:
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
[LG Optimus L9 P760, P765, P768, P769] ciccillover:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?

I have also tried:

fastboot boot some_recovery_image.img

It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.

Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
[LG Optimus L9 P760, P765, P768, P769] puntoazul:
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
[LG Optimus L9 P760, P765, P768, P769] ciccillover:
Thanks for your opinion. Yet, I still want to hear from others.
[LG Optimus L9 P760, P765, P768, P769] lecorbusier:
I'm running into more and more problems with the L9 as their me grows.

-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.

-ADB seems to work, but requiring the device to be still able to boot.

-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!

So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.

-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)

But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.

W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
[LG Optimus L9 P760, P765, P768, P769] er.davinder:
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
[LG Optimus L9 P760, P765, P768, P769] ciccillover:
No, I didn't. I have sold the phone for spares.

Inviato dal mio LG-D855 utilizzando Tapatalk
[LG Optimus L9 P760, P765, P768, P769] lecorbusier:
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.

I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.

And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
[Galaxy Note 3 Q&A, Help & Troubleshooting] mathrania:
How do i flash recovery, probably CWM touch on rooted note 3?

I have experience flashing it on HTC One using the fastboot flash commands, but here i didn't find a tutorial for flashing recovery.

Can anyone guide me the about it, like what are the pre requisite and process of flashing recovery.

Regards.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
Download your and flash it with odin

Look in the CWM thread, there shd be a tutorial afaik

hit 'thanks' if i helped you

SM-N9005 DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Q&A, Help & Troubleshooting] JoshuaFCB:
How can you do it on mac?

---------- Post added at 11:41 PM ---------- Previous post was at 11:26 PM ----------

Never mind I used an app from the play store