[Q] Did I KILL My Nexus 7 2012? - Nexus 7 Q&A, Help & Troubleshooting
Hi Guys,
I was hoping to upgrade to Paranoid Android today but didn't get so far.
I went into Clockwork Recovery and did a Factory Reset. I then proceeded to wipe the Dalvik Cache and other Cache. Then after that I set it to format the SD Card.
I noticed that while in recovery I couldn't get my SD card to mount in Windows 7. I booted up the Nexus 7 toolkit and chose a sideloading option for the Paranoid Android zips while the Nexus 7 was in CM Mod. I was staring at a frozen screen so I held the power button and down volume for ten seconds.
After a while it got to the point where the Nexus 7 would not boot. It would not show me the Google logo and when plugged in the Battery Recharging graphic did not come on.
After a while I somehow got it to boot up again. I went back into Recovery Mode and tried the sideloading again. I was still looking at a frozen screen so I did the ten second power button reset.
Now it's bricked. There's no Google logo, no option to go into Bootloader or Recovery. There is no graphic indicating that the Nexus 7 is recharging.
It's been hours. I even went so far to open up the back cover, unplug the battery, and then plug it back in. There's nothing.
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
I thought out of everything I did that unplugging and replugging the battery would have reset the system and allowed me back into Recovery Mode.
Not so....
So, I have to ask: Did I kill my Nexus 7?
Is there any way to bring this thing back? I figure I will leave it charging in a 2A Charger overnight. I need some feedback though because I did some research and have seen that a lot of people are had this problem.
ev1lchris said:
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
Click to expand...
Click to collapse
Did you mean ADB drivers? I can't find anything on ADX. I would try uninstalling and reinstalling the drivers and toolkit as a quick step, I'd also consider other toolkits as a possible solution.
I think he meant APX. APX=done. Only solution: take out phone and call ASUS for an RMA number.
I refuse to believe my Nexus 7 is done.
ev1lchris said:
I refuse to believe my Nexus 7 is done.
Click to expand...
Click to collapse
If you haven't already, do a search on APX mode/drivers. You should find that the only way to recover once in APX is if you have made a copy of a file prior to bricking. That file contains a device-specific number that is required to perform the recovery. Additionally, even with that number the process is quite daunting. Good luck should you soldier on.
PS- You should also know that while in APX mode your device is "on" & the battery is discharging to a non-rechargeable state.
Yup, had the same thing happened to my N7 today after it crashed and could not recover to save it. Plugged it on my laptop and it recognized it as an apx device something. I already called asus for rma and I'll be shipping out mine on monday.
There is hope.
Sent from my ZTE V970 using xda app-developers app
First thing I'm going to do once I get my N7 back, make an nvflash blob http://forum.xda-developers.com/showthread.php?t=2455927
I don't think I ever got the chance to flash anything new onto my Nexus 7. I just did a factory reset and formatted the SD card.
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
ev1lchris said:
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
Click to expand...
Click to collapse
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Lucky! curious also on how you manage to get out of apx mode!
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
OffcerClancy said:
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Click to expand...
Click to collapse
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
ev1lchris said:
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
Click to expand...
Click to collapse
I think there's a bit of misunderstanding here about APX mode...
To put it simply... APX doesn't necessarily signify hardbrick.
APX is required for nvFlash operations, such as nvFlashing a new bootloader, should the original become erased/corrupted. Indeed, if that where to happen, the Nexus 7 would automatically default to APX mode... and await for somebody to perform such an nvFlash operation.
Currently the only way of performing nvFlash operations on the Nexus 7 is if the user had run the flatline procedure BEFORE damage had occurred to the bootloader. This procedure generates what are called 'wheelie blobs' on a per-device basis, and are unique to each Nexus 7... ie., they are not transferable. They are required to resurrect a dead Nexus 7 with a corrupted, damaged or erased bootloader.
However, you can electively get into APX mode, even with a functional bootloader. Indeed, the latter part of the flatline procedure requires it. How to do this is detailed here.
So, just because your Nexus 7 is in APX mode doesn't necessarily mean it's hardbricked or the bootloader is damaged/corrupted or erased... though, more often than not, that is exactly what it does mean.
Providing you haven't knowingly done anything that might affect the bootloader, pressing and holding the POWER BUTTON for a good 30 seconds or more, might just be sufficient to kick-start a seemingly dead Nexus 7 out of APX mode. I can't guarantee it will work of course... but it's got to be worth a shot.
And it seems to have worked for @ev1lchris.
Rgrds,
Ged.
Sound like by dumb luck he stumbled in and fell assbackwards out of APX mode.
I brick my N7 when flashing 4.3 vía fastboot, ASUS replace the motherboard and its all good now
Enviado desde mi HTC One mediante Tapatalk
After months of use it is non responsive and in APX mode again. However, I have to highly suspect that the battery is playing a role here.
I have a rubber band constantly pressing the power button.
Let you guys know what happens.
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
ChiquiNL said:
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
Click to expand...
Click to collapse
If you're still under warranty and you have tried all you can to revive the thing then yes you should call Asus and do a RMA.
Here's an update on my situation...
I installed a battery I bought off of eBay and.... nothing. Still dead.
I'm charging it and I'm going to continue to have the rubber band wrapped around the power button but I think it's pretty much dead.
Such an awesome tablet that I used and depended on every day.
I bought a refurb N7 2013 but I really would have liked to save my N7 and continued using it.
Related
Wifi - Unable to start
Took over my partners Nexus One, a few months back and all was ok and even after I set it up for me. Then the wifi just died, as in it will not even start up. So I waited to for the update to 2.2 FRF83 but that didn't help. So I tried out CyanoganMod newest build. The nexus is now running nice and fast and looks very good with the colours on the track ball, but still no wifi. The only thing I get is "unable to start wifi" So I'm now running : 2.1-update 32.36.00.28H-4.06.00.12_7 CyanoganMod-5.0.8-N1
bump. when I try update the radio.img I get this ... fastboot flash recovery radio.img sending 'recovery' (24832 KB)... OKAY writing 'recovery'... FAILED (remote: image error! (BootMagic check fail)) 3G etc works just fine, but can't even start the wifi, just keep getting "unable to start wifi" Anyone got an idea?
[Q] Cant Flash Recovery or Restore Bootloader
Hi guys, I cant for the life of me get my comp to send anything to the phone's bootloader. It just gets stuck on command prompt. Its really frustrating. My drivers are good and everything is in order. Its a new RMA device that I'm trying to root and send the recovery over fastboot but all it does it gets stuck at "sending." Nothing for a long time. I said eff it and tried restoring with a tar file and still nothing!! WTF LARRY?! Would a factory reset and bootloader relock maybe help it? Bootloader is unlocked but just cant seem to get a CWM sent to bootloader or restore it. Please let me know what you guys think. Much preesh.
Try a different USB port on your computer. Preferably one connected directly to your motherboard. Sent from my Nexus 4
thanks but still nothing.its just stuck on "sending recovery.img." this is ridiculous. when i had the phone connected via mtp i was also having a hard time transferring anything over a MB.
this is what im also getting after unplugging the cable when it's stuck" sending 'recovery' (7808 KB)... FAILED (data transfer failure (Too many links)) finished. total time: 312.632s
OMG. God Damn USB cable was the problem here. i dont know how USB cables have their on/off days...makes no sense to me.wtf..
[Q] Oem unlock freezes, unseen error
Hello, so i got a asus nexus 7 wifi model, never seen it working. Recovery says booting failed. The one thing that works is fastboot. So i decided to reflash everything. But when i run fastboot oem unlock after about 6mins i get FAILED (remote: () as i understand no error. I tried 3 drivers, official, naked and from asus nexus toolkit everytime same result. I tried few different pc's diferent usb ports. So maybe someone had a same problem and knows what to try next. Bootloader version 4.13 full log: ... (bootloader) erasing userdata... (bootloader) erasing userdata done (bootloader) erasing cache... (bootloader) erasing cache done (bootloader) unlocking... FAILED (remote: () finished. total time: 391.390s Thx in advance
xz33r0x said: Hello, so i got a asus nexus 7 wifi model, never seen it working. Click to expand... Click to collapse I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool. You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.
bftb0 said: I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool. You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7. Click to expand... Click to collapse I didn't pay for it at all yeah have read about apx. Just was wandering is there any other options, or the nand is dead like a brick
[Q] URGENT, bricked and need help
I have tried absolutely everything i can think of to restore my razr m. I'm using a macbook pro. I've tried using RSD lite in crossover, and in parallels, both windows 7, and windows xp. No matter what, my device is never recognized in fastboot mode and never pops up in RSD lite. I can use fastboot from the sdk directly in OSX. the device is recognized, but thats basically useless since the bootloader is locked, and I cant flash the system partition. Yes, I have installed the moto USB drivers, multiple times. I don't have access to any other computer and I'm in desperate need of help. please give me any suggestions you have
Get to a windows computer man. The motorola usb drivers need to talk directly to the hardware, not through another layer like parallels or other emulation software.
NRGZ28 said: Get to a windows computer man. The motorola usb drivers need to talk directly to the hardware, not through another layer like parallels or other emulation software. Click to expand... Click to collapse i literally can't until at least this weekend :/ im trying to flash the files using fastboot, but I get this error when attempting to flash system.img.ext4 sending 'system' (835010 KB)... (bootloader) Data size exceeds download buffer FAILED (remote failure) finished. total time: 0.107s any work arounds for this?
ahhhzombies said: i literally can't until at least this weekend :/ im trying to flash the files using fastboot, but I get this error when attempting to flash system.img.ext4 sending 'system' (835010 KB)... (bootloader) Data size exceeds download buffer FAILED (remote failure) finished. total time: 0.107s any work arounds for this? Click to expand... Click to collapse No man.. no workaround as long as the bootloader is locked. Otherwise we wouldn't need safestrap.
NRGZ28 said: No man.. no workaround as long as the bootloader is locked. Otherwise we wouldn't need safestrap. Click to expand... Click to collapse my buddy brought over his windows laptop, flashed without a hitch thanks for the help, and I'm installing your rom right now BTW
Hehe.. there ya go. See ? It pays to have a Windows laptop around
NRGZ28 said: Hehe.. there ya go. See ? It pays to have a Windows laptop around Click to expand... Click to collapse does it have to be a windows computer? just wondering because I only have a mac, and linux installed in my pc lol
looks like you need the new fastboot; try the linux one from this zip: http://forum.xda-developers.com/showpost.php?p=37155367&postcount=190
[Q] Bricked Nexus 7 3G - Can't Get to Bootloader - Anyone Able to Help?
Hi all, I think I just toasted my Nexus 7 3G while trying to upgrade the radio/bootloader, but before I toss it in the trash I wanted to see if many someone had any ideas I have yet to try. Thanks in advanced to anyone who can help me! The Problem: Nexus 7 wont boot and is stuck on the Google logo with the unlocked bootloader icon. Cant boot to boot loader using Power + Volume Down. When I do Power + Both Volume Up and Down the screen goes black after showing the Google logo and my PC detects the device but cant find drivers and dont get anything out of fastboot commands. Power + Volume up does nothing. Because the unlocked bootloader icon I doubt I could get away with sending it back. What I did: I was running CM10.1 with Bootloader unlocked I installed the following 4.3 ROM - http://forum.xda-developers.com/showthread.php?t=2381991 Rebooted <-- Everything was fine but running on older Radio/Bootloader I started following the following instructions to upgrade radio + bootloader - http://forum.xda-developers.com/showthread.php?t=2175086 I used TWRP to install the Recovery zip Rebooted to bootloader Fastboot Flashed bootloader <<Forgot to Flash Recovery>> Rebooted <-- everything was working Rebooted to bootloader Fastboot Flashed Radio Rebooted << TWRP launched instead of stock recovery Rebooted to bootloader Fastboot Flashed bootloader Fastboot Flashed recovery << Did not reflash recovery zip first >> Rebooted <-- seemed ok Rebooted to bootloader Fastboot Flashed radio Rebooted <<No Recovery Showed Up>> Stuck with Google logo with unlocked bootloader icon and cant get back into bootloader
Hi Mazeri, I having the same issue as I explained in the original thread. I was flash the bootloader recovery and radio. Recovery and Bootloader flashes seemed to be ok but the radio flash run ok but when the n7 rebooted got stuck in the google logo. I have tried all kind of key combinations with no success. Here is the transcript of my flash commands: Code: ~/Downloads ⮀ fastboot flash bootloader bootloader-tilapia-4.23.img sending 'bootloader' (2100 KB)... OKAY [ 0.258s] writing 'bootloader'... OKAY [ 4.140s] finished. total time: 4.399s ~/Downloads ⮀ fastboot flash recovery Recovery_Stock_Tilapia_4.3.img sending 'recovery' (10240 KB)... OKAY [ 1.223s] writing 'recovery'... OKAY [ 2.453s] finished. total time: 3.676s ~/Downloads ⮀ fastboot reboot rebooting... finished. total time: 0.020s ~/Downloads ⮀ fastboot devices 015d2XXXXXX0d fastboot ~/Downloads ⮀ fastboot flash radio radio-tilapia-1231_0.18.0_0409.img sending 'radio' (16384 KB)... OKAY [ 1.943s] writing 'radio'... OKAY [ 4.760s] finished. total time: 6.702s ~/Downloads ⮀ fastboot reboot rebooting... finished. total time: 0.020s ~/Downloads ⮀ fastboot devices ~/Downloads ⮀ fastboot devices How do you detect the device in your pc? What command are you running? Im on a mac os x. If I do a fastboot reboot recovery, I get a 'waiting for device' message but there is no information for any combination of key presses. If you are on a PC, have you tried any toolkit? I've read in a couple of thread that Wug's toolkit have worked to unbrick some devices with issues with the bootloader.
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Mazeri said: All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device. Click to expand... Click to collapse Also, I tried with the Nexus 7 tool kit and it failed to detect ADB. Fastboot also does not see the device.
Wug Toolkit also does not seem to work as it requires ADB or Fastboot to be working. If I could get the device driver to kick in that might work... but something we did while flashs is making the device show up without details such as no device name and no mfg info... so Windows just shuts it down and calls it unknown.
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix I just flash the radio and my N7 stuck at Google logo....
amakaru said: I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix I just flash the radio and my N7 stuck at Google logo.... Click to expand... Click to collapse Maybe we should check what do ourt n7's have in common... It's strange that the flash worked for other n7 but not for ours. Maybe that radio file is intended for certain devices (?). Mine is a EU Nexus7 3G bought in early January this year. I guest is in warranty yet but because of the unlock icon in the start screen, the warranty is void But I think this is not a problem related with the bootloader since the google logo appears and the unlock icon (so the n7 bootloader detects that it is unlock). The flashing worked with the bootloader but it crashed when the radio was flashed for the three of us, so it is something related with the baseband. The OS installed should not be related since the bootloader and radio baseband are independent from the OS (Maybe you can get a soft brick, stuck in the colored X logo but bootloader should work). I'm going to try to work finding a solution... but personally Im not feeling very optimistic
Now when I use three button (hold down power & vol + & vol - ) my computer show in device manager : "Android devices/ASUS Transformer APX Interfaces"
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic. It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
I have a US Nexus 7 3G, got it right when they went on sale. ameinild said: Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic. It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry. Click to expand... Click to collapse Bummer news :'( but I was expecting as much. If we don't find a fix, can we replace the main board to fix or is this problem beyond that point? Don't think selling a bricked device is worth it unless we have 0 options.
adb/fastboot commands Another one bites the dust. I should have followed the thread more closely. One of the steps (noticed this after the fact) is to "fastboot reboot", unfortunately this does not reboot the bootloader. I should've noticed this yesterday after the initial fastboot reboot when I flashed the recovery image. Anywho, I believe the last step after flashing the radio should be "fastboot reboot-bootloader" not "fastboot reboot"? Maybe someone with more adb/fastboot experience could verify? Thanks.
bootloop after radio update!!! my nexus 3g is from poland!!! please, help!!!
Still no update guys, and no luck also Right now I am thinking we will need to replace the main board, but I want to get that confirmed before buying a replacement.
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
my radiobands for device is for Poland Region i hate myself the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
sambistt said: my radiobands for device is for Poland Region i hate myself the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip. Click to expand... Click to collapse There isn't a place to know the parameters or whatever we need? What can we change physically (motherboard, or any specific chip) to solve this problem? If we return it to Asus or Google can it be repeaired? How much does it cost? Assuming the warranty is void because of the unlock icon.. ---------- Post added at 01:25 PM ---------- Previous post was at 12:31 PM ---------- eternal70 said: I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine Click to expand... Click to collapse That was not the reason. I didnt upgrade to 4.3 before flashing the bootloader and the radio and I got the same result. The bootloader is not connected to the OS, but the OS is connected to the bootloader. I mean that it doesnt matter the OS in order the bootloader to run. But maybe it is possible to have the n7 soft bricked if the bootloader installed is not compatible with your OS. Softbricked is when you are stuck in the OS logo (in case of the stock version is the colored X). This is very easy to fix, just runt in fastboot mode and flash the new OS and that's all. Everyone has experienced this situation eventually. Our n7 are hard bricked. This mean that the bootloader or the radio (or both) are corrupted or bad flashed. In our case is the radio band (since we can see the google logo that is the bootloader). The weird thing is that while the bootloader is running (we can see the google logo and the unlock icon), we can't enter in the fastboot mode. Since we cant put the n7 in fastboot mode then we cannot flash anything (not os, not radio, not bootloader). For now, the only way to flash bootloader and radio chip of the n7 is via APX. the problem is the APX configuration to flash the nvidia chips has not been released (as far as I understand, correct me if im wrong), so there is no way to know how to do it. The only hope is changing this chips physically. Because everything is integrated, that means to change the motherboard, my guess (you can find tutorials in iFixit). What's the downside? The motherboard is basically the N7 so if you change it you change everything (the storage, the 3G, etc). You can check for motherboards in ebay easily just with search: Nexus 7 Motherboards. Range price varies from 20$ for 8GB to 140$ for 3G . Another question is if we can put a 8GB or 16 GB motherboards in our 3G N7, but I think so... it would not be a problem. Everything I said a personal opinions and I can be wrong, so correct me if I'm wrong. I have to say, I still have a very very very little hope that could be a fix for this, since we can see the google logo. But I'm thinking in ordering a 8G motherboard just in case
i`m thinking to give my n7 3g to my brother for parts and never buy tablet anymore, only ultrabooks.
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit. The device got back to life again and then took the 4.3 OTA. Sent from my Galaxy Nexus using xda app-developers app
There isn't a place to know the parameters or whatever we need? Click to expand... Click to collapse no and never`ll be easyflash only for transformer pad i think to easy buy new nexus 7 2 gen or never buy tablet anymore 347 $ in trash the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet ---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ---------- DomieMic65 said: My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit. The device got back to life again and then took the 4.3 OTA. Sent from my Galaxy Nexus using xda app-developers app Click to expand... Click to collapse really? your brother flashed radio module?
sambistt said: no and never`ll be easyflash only for transformer pad i think to easy buy new nexus 7 2 gen or never buy tablet anymore 347 $ in trash the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet ---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ---------- really? your brother flashed radio module? Click to expand... Click to collapse I don't know. Sorry. I just mentioned this in case it may give you a clue. I will ask and report. Sent from my Galaxy Nexus using xda app-developers app