Related
So I had the latest version of Paranoid Android on my rooted nexus 10. The keyboard was messing up so i wanted to run a factory reset and go all the way back to stock 4.2.1. In the process I accidentally wiped both the Rom and stock from my nexus 10 leaving it with no OS and nothing but the boot-loader. If i try and go to recovery mode all i get is the android laying down with an exclamation mark in a red triangle in it's stomach or the word Google with and unlocked padlock underneath it.
Any advice/help would be amazing! Thanks!
Download the factory image from Google: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-0d641789.tgz
If you don't have fastboot already you need that too: http://downloadandroidrom.com/file/tools/fastboot.zip
Unzip the factory image tgz I linked to with 7zip/winrar etc
Unzip the fastboot.zip contents into the folder you just extracted
open a command prompt in the folder you just unzipped (mantaray-jop40c)
Boot your device into the bootloader by holding down BOTH volume keys and the power button
Connect your Nexus 10 to your PC
At the command prompt type
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader [wait for the device to reboot back to the bootloader]
fastboot -w update image-mantaray-jop40c.zip
This will wipe, repartition and install 4.2 straight from Google back to your device.. You will be prompted to update by Google to install the 4.2.1 update shortly after you boot up.
If you didn't have Fastboot already and had to download the zip I linked to, it's highly suggested to download and install the Android SDK so you have it and more native tools at your disposal. You can do that after the fact though and optional but highly suggested if you plan on learning your device more.
Will this work even if my device WAS Android 4.2.1 JOP40D?
Jamocobi said:
Will this work even if my device WAS Android 4.2.1 JOP40D?
Click to expand...
Click to collapse
Yep.
styckx said:
Yep.
Click to expand...
Click to collapse
Awesome thanks, I'll give it a shot once the files downloaded!
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
styckx said:
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
Click to expand...
Click to collapse
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Jamocobi said:
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Click to expand...
Click to collapse
How did you unlock and root this device in the first place?
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
With the WugFresh Nexus Root Toolkit (Sorry, Can't post a link yet)
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Jamocobi said:
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Click to expand...
Click to collapse
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
styckx said:
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
Click to expand...
Click to collapse
Sorry about that, i was hoping you'd see it in time! You're definitely right about that, i was just worried i would totally mess it up if i did it myself but i can do that anyway with a toolkit so next time ill give it a shot without one.
Okay thanks, I'll take note of that one for sure! Really appreciate the help, thought i was doomed! haha!
You're welcome man.. It's no fault of your own for using the toolkit. To new users they're attractive and promise quick results.
Side note. It's extremely, insanely, stupidly hard to permanently screw up a Nexus device by flashing. There is always a way back from `the grave'.
Take care
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
Hi, KingMGT...
You typed the command that should never be typed!
Unless you have previously created 'blobs' specific to your Nexus 7 (using the flatline procedure), your device is unrecoverably bricked.
Rgrds,
Ged.
Can you help me fix this problem? :( :([/QUOTE said:
Strip it and sell the parts on eBay apart from the motherboard im afraid its unrecoverable without blob backups
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
Captain Sweatpants said:
Strip it and sell the parts on eBay apart from the motherboard im afraid its unrecoverable without blob backups
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
Is RMA out of discussion here ?
Wild78 said:
Is RMA out of discussion here ?
Click to expand...
Click to collapse
Yes. Because he erased his bootloader.
You could buy a new motherboard and fit it you self its pretty easy and you can get them for about £40/50 but warranty is out the question.
Sent from one of my 47 iPads running android C3P0
Read read read, learn, learn more, understand, understand fully......then and only then start messing with your devices.
Sorry for your loss.
Sent from my N5 cell phone telephone....
KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
Well bro, you have my sympathy.
This command results in hard bricks.....
Now the only way is to restore a .blob backup which you should have taken through flatlines nvflash before doing the biggest mistake of your life.
You may reclaim your warranty, I think.....but your n7 is dead.
Sent from my Nexus 7 using Tapatalk
Thanks all.
I sold it and bought a new Google nexus 7 16GB Wifi.
After bought, i instant backup blob.bin hehe.
We live and learn. The first time I started messing with android I hard bricked a Samsung galaxy spica. Got really nervous about messing with my next phone
Sent from one of my 47 iPads running android C3P0
KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
I am pretty sure your nexus is a paperweight, but can I ask....what possessed you to type that?...
KingMGT said:
I very noobs when type command "fastboot erase bootloader". My Nexus 7 is brick.
Can you help me fix this problem?
Click to expand...
Click to collapse
Curious if you know which bootloader version you have? I'm on 4.23 and I have, out of morbid curiousity, typed that which should never be type... fastboot erase bootloader and it doesn't erase. Says erase failed. Bootloader and Nexus unharmed. That being said, please DO NOT try this at home! But I'm wondering under what circumstances a bootloader would allow itself to be erased? I've flashed bootloaders, which makes total sense, but erasing should never be an option.
adomol said:
Curious if you know which bootloader version you have? I'm on 4.23 and I have, out of morbid curiousity, typed that which should never be type... fastboot erase bootloader and it doesn't erase. Says erase failed. Bootloader and Nexus unharmed. That being said, please DO NOT try this at home! But I'm wondering under what circumstances a bootloader would allow itself to be erased? I've flashed bootloaders, which makes total sense, but erasing should never be an option.
Click to expand...
Click to collapse
You sir, are brave.
Sent from my N5 cell phone telephone....
adomol said:
Curious if you know which bootloader version you have? I'm on 4.23 and I have, out of morbid curiousity, typed that which should never be type... fastboot erase bootloader and it doesn't erase. Says erase failed. Bootloader and Nexus unharmed. That being said, please DO NOT try this at home! But I'm wondering under what circumstances a bootloader would allow itself to be erased? I've flashed bootloaders, which makes total sense, but erasing should never be an option.
Click to expand...
Click to collapse
Hi, adomol...
As politely as I can put this, but "Why?"... did you try this...
Generally, the command...
Code:
fastboot erase <partition_name>
...will delete/erase whatever the named partition occupies. Often, this will be for something relatively innocuous, (eg., fastboot erase boot, fastboot erase userdata, etc.) but it also WILL ERASE THE UNIQUE DEVICE SPECIFIC, CRYPTOSIGNED BOOTLOADER for your unique Nexus 7 if your attempt to erase the bootloader succeeds. And your device is then HARDBRICKED.
---------------------------------------------
I suspect the reason why your quasi-suicidal attempt to brick your Nexus 7 failed, is because your bootloader is probably locked... and fastboot commands fail if the bootloader is locked.
I strongly recommend you desist from further experimentation along these lines.
Rgrds,
Ged.
GedBlake said:
Hi, adomol...
As politely as I can put this, but "Why?"... did you try this...
Generally, the command...
Code:
fastboot erase <partition_name>
...will delete/erase whatever the named partition occupies. Often, this will be for something relatively innocuous, (eg., fastboot erase boot, fastboot erase userdata, etc.) but it also WILL ERASE THE UNIQUE DEVICE SPECIFIC, CRYPTOSIGNED BOOTLOADER for your unique Nexus 7 if your attempt to erase the bootloader succeeds. And your device is then HARDBRICKED.
---------------------------------------------
I suspect the reason why your quasi-suicidal attempt to brick your Nexus 7 failed, is because your bootloader is probably locked... and fastboot commands fail if the bootloader is locked.
I strongly recommend you desist from further experimentation along these lines.
Rgrds,
Ged.
Click to expand...
Click to collapse
I know it was reckless and could have hardbricked my device, but the thrill overtook me. I have a history of this kind of behavior. But that is beside the point.
I've used fastboot many times and executed most of the usual commands... format, erase, flash, devices, oem unlock, oem lock. All on this very device. The same one I almost euthanized. It is a Nexus 7 2012, unlocked running all-f2fs SlimKat, bootloader version 4.23 (which is the current version.) I flashed that bootloader myself a couple months back when I did a nexus factory image install through fastboot. I also used the erase command on all the usual partitions before flashing them, as I took care of each one seperately.
That being said, I executed the dreaded command on this N7. Result... erase failed
Now that result just brings up more questions, although it would make sense to have fastboot not be able to erase that part or somehow build into the bootloader somekind of failsafe. Could be that 4.23 can't be erased and older versions can?
adomol said:
I know it was reckless and could have hardbricked my device, but the thrill overtook me. I have a history of this kind of behavior. But that is beside the point.
I've used fastboot many times and executed most of the usual commands... format, erase, flash, devices, oem unlock, oem lock. All on this very device. The same one I almost euthanized. It is a Nexus 7 2012, unlocked running all-f2fs SlimKat, bootloader version 4.23 (which is the current version.) I flashed that bootloader myself a couple months back when I did a nexus factory image install through fastboot. I also used the erase command on all the usual partitions before flashing them, as I took care of each one seperately.
That being said, I executed the dreaded command on this N7. Result... erase failed
Now that result just brings up more questions, although it would make sense to have fastboot not be able to erase that part or somehow build into the bootloader somekind of failsafe. Could be that 4.23 can't be erased and older versions can?
Click to expand...
Click to collapse
Hi, adomol...
You're definitely onto something here... I must be mad, but I've just attempted to erase my bootloader. And encountered a similar error to yours.
So, with every precaution available to hand, here's what I did...
------------------------------------
...made available a known working copy of the v4.23 bootloader.img on my laptop, with the intention of immediately fastboot flashing it, in the event the bootloader erase SUCCEEDED. (Providing you DON'T reboot the device immediately after a bootloader flash failure (or erasure), there is a small window of opportunity to fastboot flash a known working bootloader... before you reboot the device.)
...made available my 'flatline' created 'blob.bin' file, and nvFlash tools...
My device...
Nexus 7 (2012), 16Gb,'grouper' model, WiFi only.
Bootloader v4.23, unlocked.
Custom recovery is TWRP 2.7.0.0
Running rooted KitKat 4.4.2, with modifications (see my sig. for details).
--------------------------------------------------------------------------
With all tools, files and everything I could think of readily available (and my heart in my stomach!!)... I ran the potential Nexus 7 command line killer...
WARNING TO ALL READERS: The following command is potentially VERY dangerous, and may BRICK your device. Do NOT use casually. The previous poster raised an interesting issue regarding the v4.23 bootloader, and what follows is my own risky experiment... which happily, did not brick MY Nexus 7. I can make no such guarantees about YOUR Nexus 7.
Code:
fastboot erase bootloader
It failed... with this error message...
Code:
erasing 'bootloader'...
FAILED <remote: Unsupport Erase bootloader Partition.>
finished. total time: 0.016s
See my attached thumbnail.
So, it DOES appear that, at least as far as the v4.23 bootloader is concerned... it's impossible to deliberately erase it... although accidentally overwriting it, I suspect might be a different matter - eg., inadvertently fastboot flashing a boot.img to the bootloader partition, for example.
Anyway... very nice find, @adomol... you've discovered something interesting as a result of your bravery or foolhardiness... and I can't decide which! Whichever quality it is, I think I share it.
--------------------------------------------------------------------------
Right... I'm off for a cigar, and a drop of whisky to calm my nerves.
Rgrds,
Ged.
GedBlake said:
Anyway... very nice find, @adomol... you've discovered something interesting as a result of your bravery or foolhardiness... and I can't decide which! Whichever quality it is, I think I share it.
--------------------------------------------------------------------------
Right... I'm off for a cigar, and a drop of whisky to calm my nerves.
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm breeding an XDA loony bin in here! It's like Jackass Nexus 7 edition. :laugh:
Thanks for posting the screenshot, though. I wish I would have been resourceful enough to do that, considering how unlikey these results were thought to have been. Good job @GedBlake!
@adomol That being the one command that will irrevocably brick a nexus you at either very brave or stupid to type that please tell me you had a blob.bin backup before trying that. Anyway that's an interesting find nonetheless.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Ok, so I figured I'd start a thread for a little community think tank.
If you have any ideas, direction, insight, experience, or anything else constructive, throw it in and maybe one of us can come up with something to crack this bootloader. Root might be nice, but to do anything worth a damn, an open bootloader is needed.
So I'll get this thread rolling...
Something I thought of...some devices need special programming cables.
How comical would it be if Amazon is selling the product needed to send the special command to the device to unlock it?
amazon.com/Factory-Fastboot-Cable-N2A-Motorola/dp/B0099E59SG
I'm going to pick one up and see what I can do with it.
Also something to throw out, anyone aware of how to gather the HW identifier for fastboot devices? Some devices also need to manually have the HW identifier passed via fastboot -i
kenmoini said:
Ok, so I figured I'd start a thread for a little community think tank.
If you have any ideas, direction, insight, experience, or anything else constructive, throw it in and maybe one of us can come up with something to crack this bootloader. Root might be nice, but to do anything worth a damn, an open bootloader is needed.
So I'll get this thread rolling...
Something I thought of...some devices need special programming cables.
How comical would it be if Amazon is selling the product needed to send the special command to the device to unlock it?
amazon.com/Factory-Fastboot-Cable-N2A-Motorola/dp/B0099E59SG
I'm going to pick one up and see what I can do with it.
Also something to throw out, anyone aware of how to gather the HW identifier for fastboot devices? Some devices also need to manually have the HW identifier passed via fastboot -i
Click to expand...
Click to collapse
That cable will not cut it. I have a few N2A fastboot cables, so don't wast your money. The identifier is out there somewhere, don't remember where I found it, but fastboot -i xxxxxxxx will not do it either. Not trying to shoot down the post, but most of the obvious stuff has been tried. It is very likely that a key must be sent before fastboot will go online via usb, but I haven't found anything that works pouring thru the source or bl/misc dumps & hex views.
GSLEON3 said:
That cable will not cut it. I have a few N2A fastboot cables, so don't wast your money. The identifier is out there somewhere, don't remember where I found it, but fastboot -i xxxxxxxx will not do it either. Not trying to shoot down the post, but most of the obvious stuff has been tried. It is very likely that a key must be sent before fastboot will go online via usb, but I haven't found anything that works pouring thru the source or bl/misc dumps & hex views.[/QUOTE
I'm no device but will this help?
if stay at fastboot you should send command ” fastboot -i 0×1949 oem idme bootmode 4000″ under fastboot command line. if it can not fix, you should reflash the system.img to the kindle fire hd.
Click to expand...
Click to collapse
Tomen8r said:
GSLEON3 said:
That cable will not cut it. I have a few N2A fastboot cables, so don't wast your money. The identifier is out there somewhere, don't remember where I found it, but fastboot -i xxxxxxxx will not do it either. Not trying to shoot down the post, but most of the obvious stuff has been tried. It is very likely that a key must be sent before fastboot will go online via usb, but I haven't found anything that works pouring thru the source or bl/misc dumps & hex views.[/QUOTE
I'm no device but will this help?
if stay at fastboot you should send command ” fastboot -i 0×1949 oem idme bootmode 4000″ under fastboot command line. if it can not fix, you should reflash the system.img to the kindle fire hd.
Click to expand...
Click to collapse
No. That is for the older model, using TI & uboot.
Click to expand...
Click to collapse
How about flashing an alternative bootloader like U-boot?
Patrick4 said:
How about flashing an alternative bootloader like U-boot?
Click to expand...
Click to collapse
We are not at the point where we can overwrite the bootloader yet. The kernel prevents the system from touching the bootloader.
JordanRulz said:
We are not at the point where we can overwrite the bootloader yet. The kernel prevents the system from touching the bootloader.
Click to expand...
Click to collapse
The kernel can not really prevent access to the bootloader. The bootloader & kernel are independent of each other. In fact, the bootloader is online before the kernel and even without a kernel, you can still access the bootloader. In fact, I have learned that at this time, no kernel can allow or bar access to the bootloader. That applies to Linux, not just Android.
Even beyond that, many functions on all devices are being moved onto parts of the chip that the kernel cannot access period. They are moving many functions & features into the trusted zone, beyond the kernels reach.
At any rate, none of that changes the fact that you have to have an unlocked bootloader to change the bootloader, or at the very least, an exploit that makes the bootloader think it is unlocked, or that temporarily unlocks it.
Would it help if I offered my HDX 8.9, with the advantage that I have a RIFF box so I could eventually restore the whole thing if needed?
I haven't been able to it teardown, I am afraid I might break something when trying it, but according to iFixit's mini teardown: ifixit.org/blog/5564/kindle-fire-hdx-8-9-mini-teardown/
It doesn't have screws to open the lid, but I can see some screws holes on the pictures and it was too stuck at the top part (right where the HDX 7 has the pink screws).
So:
- If any of you did tear it down without visible scratches or dents and can point me in the right direction I will be willing to try it (have some jtag adapters which I think should work with the socket on the Kindle).
- Is it worth it for any devs to try with my Kindle and available tools?
Thanks!
Would it be possible to pull the bootloader of the device and analyze it in hex or disassemble it ?
All Stormed out?
Guess this brainstorm dissipated? I am researching because of a Saturn that somehow lost the boot.img file. I may have to relinquish it to the brick pile.
I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped
The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.
I have erased my bootloader - fastboot erase bootloader.
I am ready to give $200 if someone can give me procedure to bring it up again.
i can share CPUID as generated by NVFlash, thats all I have.
So if someone looking for quick $200, here is your chance..
Well I don't want your money, I would suggest wugfresh myself. Has the option for a bricked device. Has saved a lot of people. And I have no idea why you did that.
raviverma said:
I have erased my bootloader - fastboot erase bootloader.
I am ready to give $200 if someone can give me procedure to bring it up again.
i can share CPUID as generated by NVFlash, thats all I have.
So if someone looking for quick $200, here is your chance..
Click to expand...
Click to collapse
You can buy a Nexus 7 for less than $200 I own one myself paid £200 in 2012 and must admit they are ****e and Google must be held accountable for releasing a device which is always in beta
treefrog20012003 said:
Well I don't want your money, I would suggest wugfresh myself. Has the option for a bricked device. Has saved a lot of people. And I have no idea why you did that.
Click to expand...
Click to collapse
i updated lollipop on nexus 10 and then while doing on nexus 7, by mistake i did
fastboot erase bootloader
fastboot reboot bootloader
without
fastboot flash bootloader bootloader.img
i have done flashing several times, but this was my bad day. I have no blobs or other data saved as i never anticipated this will happen. I tried hard so far but could not bring up with NVFlash, so finally i thought if someone can do it definitely deserves the prise money of cost of the TAB.
raviverma said:
i updated lollipop on nexus 10 and then while doing on nexus 7, by mistake i did
fastboot erase bootloader
fastboot reboot bootloader
without
fastboot flash bootloader bootloader.img
i have done flashing several times, but this was my bad day. I have no blobs or other data saved as i never anticipated this will happen. I tried hard so far but could not bring up with NVFlash, so finally i thought if someone can do it definitely deserves the prise money of cost of the TAB.
Click to expand...
Click to collapse
ok have you tried the wugfresh nexus root toolkit it does the job
Tmzdroid said:
ok have you tried the wugfresh nexus root toolkit it does the job
Click to expand...
Click to collapse
I had tried that too.. it keeps looking for ADB, when there is no ADB.
I have the root tool kit installed. Please correct me if i am doing something wrong.
As i said, there is no bootloader so no fastboot either, only APX mode as of now.
Wugfresh has an option for bricked devices, I figured that would do it
Sent from my DROID3 using XDA Free mobile app
Do you mind uploading the screenshot with the button marked, if at all you can.
I cannt find any way for - unbriking on toolkit.
Its under a sub screen, advanced options I think. I would give you a screen shot but i'm not home and won't be for hours.
Sent from my DROID3 using XDA Free mobile app
---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------
Go to YouTube and search for unbrick nexus 7, there are a lot of vids there, one should help.
Sent from my DROID3 using XDA Free mobile app
You know you can buy nexus 7 2012 model on ebay for around 100.00
you can buy a new Main board for around 35.00 ...And people on here will help you for free . Just ask.. If you did not do the pre boot-loader unbrick procedure you are totally lost .
NV-FLASH Is your only hope to revive without hardware Replacement. From the best of my knowledge anyway...
Sorry...
Thats right I dont have any per data saved.
NVFlash too wont work without blob.bin which is device specific.
I know people on xda help just for good of people but i wanted to reward since I have tried hard enough already with NVFlash.
If at all someone can bring it up deserves a good reasonable amount
Thank you and I am greatful.
After some extensive searching I'm going with your hosed. 2 options, buy a new main board or buy another one. Sorry about your situation, should you find a magical answer let us know.
New mb. There might be a way to reload the os through JTAG, which I think is how it is done at the factory, but it would cost more than just replacing it.
Yup looks like its time to say good bye to bricked Nexus7 and buy a replacement new Tab.
Thank you friends for all your help and time. Looks like its time to close the bounty as incomplete project.
I did a quick search on eBay and found a person offering JTAG services
http://www.ebay.com/usr/patrickwalls?_trksid=p2047675.l2559
Maybe you could talk to the guy.
Thank you ! I have contacted the guy you mentioned. Lets see what reply we get !
The nexus has a UART interface in the headphone jack. Not sure what UART can be but maybe can be used to comunicate at a low level with the board and flash a bootloader.
For less than $100 you can get another one on swappa.
http://swappa.com/buy/nexus-7-wifi/us
http://www.amazon.com/gp/product/B0...e=UTF8&camp=1789&creative=390957&linkCode=as2
USD$120 refurbished, fullfilled by amazon
Yes I have heard Nexus7 Serial interface through Audio Jack. I will try it. I think i have one audio serial interface cable.
All this exercise is becoming a collective hacking of Nexu7.
I did HEX Diff of two Blob.bin generated by flatline.img and found there is
- a common header and footer
- in between there is around 2MB of AES encrypted data.