Posting on behalf of my daughter and if the topic has been covered I apologize and would welcome a link ... anyway here goes, no idea how the tablet got to it's current state but when switched on it will simply go through normal boot up up to the colored blocks then it goes blank and starts again. From what my daughter says she was having some issues with it in the morning and gave up trying to sort it and did a factory reset ... this appears to have gone belly up or at least done more than she expected ending in the current state. She did try and do the same again "many times"
To me it does not look to good but I have limited knowledge of Android so may be reading to much into what I see, any suggestions / assistance to get the system back to normal would be appreciated. The tablet is stock and was running latest version of Kit Kat
Thanks in advance
Was the tablet rooted? Have you ever used adb (android debugging bridge)? Try and get into recovery mode or fastboot mode from off you press power and vol up or down you will see either android on his back (fastboot) or recovery mode
Sent from my C5303 using xda app-developers app
Captain Sweatpants said:
Was the tablet rooted? Have you ever used adb (android debugging bridge)? Try and get into recovery mode or fastboot mode from off you press power and vol up or down you will see either android on his back (fastboot) or recovery mode
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
No not rooted was stock with Kitkat 4.4.2 running ...never used ADB but having read a few posts on here have been getting to know it, got into fastboot using SDK Manager and am trying to work through what I should do next to get the thing back up, recovery mode using the method you mention did nothing looked to me as my daughter may have wiped all data by accident ..well usable data that is as the tablet must have something on it as it was looping non stop .....
OK well in fastboot type the command "fastboot OEM unlock" that will bring up a screen on the tablet warning you about the terrible woes of unlocking your bootloader go ahead and if that succeeds then you will see an unlocked padlock on the Google screen you bootloader is now unlocked if this process fails or hangs at the unlocking stage then you have a corrupted nand partition (bad) the internal memory of the tablet has become corrupted this is the source of your problems and a new motherboard is in order. If it succeeded then we are on to the next step download wugfresh nexus root toolkit use the unroot back to stock option be sure to tick soft bricked and this will automatically flash a new factory image onto the tablet
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:
OK well in fastboot type the command "fastboot OEM unlock" that will bring up a screen on the tablet warning you about the terrible woes of unlocking your bootloader go ahead and if that succeeds then you will see an unlocked padlock on the Google screen you bootloader is now unlocked if this process fails or hangs at the unlocking stage then you have a corrupted nand partition (bad) the internal memory of the tablet has become corrupted this is the source of your problems and a new motherboard is in order. If it succeeded then we are on to the next step download wugfresh nexus root toolkit use the unroot back to stock option be sure to tick soft bricked and this will automatically flash a new factory image onto the tablet
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
Thanks Captain Sweatpants
Things seem to have taken a turn for the worse though managed to do the OEM unlock, all seemd ok never got to the stage using the download you mention, had to pack in what I was doing as I was going to work shut the tablet down which seemed ok now it won't stir one bit tried all the buton combinations nothing ..... I am guessing it's bricked :crying:
Any ideas ?????
It's possible you have a flat battery plug in the charger and hold power button for two mins use a watch it really does take that long if that doesn't work take the back off and disconnect the battery use a multi meter to check the voltage. Its a two cell 3.7v battery there are two pairs of red and black wires they should both give about 3.6/7v anything below 3.5 means its dead
Sent from my C5303 using xda app-developers app
Captain Sweatpants said:
It's possible you have a flat battery plug in the charger and hold power button for two mins use a watch it really does take that long if that doesn't work take the back off and disconnect the battery use a multi meter to check the voltage. Its a two cell 3.7v battery there are two pairs of red and black wires they should both give about 3.6/7v anything below 3.5 means its dead
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
Captain Sweatpants Thanks Again since last post I have got a bit more info as to how the tablet has got to the state it is, as I said I had stopped the loop and was able to get to fastboot and unlock the tablet but left it after that as due for work, it appears my son did a bit of fiddling about and that ended up with my current state ... from what a friend has said on taking a look at it it is now basically a very expensive coaster, the bootloader has gone and the tablet can only be seen on a pc using an APX driver (think that's what he called it) basically will see what the cost of a new motherboard would be and weigh that against a new one ..... :fingers-crossed: Anyway thanks for your help it was worth a try Cheers:good:
Presario29 said:
Captain Sweatpants Thanks Again since last post I have got a bit more info as to how the tablet has got to the state it is, as I said I had stopped the loop and was able to get to fastboot and unlock the tablet but left it after that as due for work, it appears my son did a bit of fiddling about and that ended up with my current state ... from what a friend has said on taking a look at it it is now basically a very expensive coaster, the bootloader has gone and the tablet can only be seen on a pc using an APX driver (think that's what he called it) basically will see what the cost of a new motherboard would be and weigh that against a new one ..... :fingers-crossed: Anyway thanks for your help it was worth a try Cheers:good:
Click to expand...
Click to collapse
OK once you have a shredded bootloader that's the end of the line. Unlocking the bootloader allows you to execute commands an reflash the tablet unfortunately it also opens up the possibility of hard bricking it if you do something wrong. Its recoverable but only if you have previously backed up the bootloader. No one has ever recovered a nexus bootloader without a backup and very few have ever done it with one.
On the bright side a new motherboard for a n7 is not expensive about £30 in the UK not sure about other countries. And is very easy to fit
Sent from my C5303 using xda app-developers app
Related
I'm ready to spike this thing into the pavement and redeem my squaretrade warranty.
I was tinkering with the recently released 3.41 bootloader and I was getting the bootloop issues, though I could alwasy fastboot back to 3.34 and be fine.
So just now I was following the advice of another user:
http://forum.xda-developers.com/showpost.php?p=32771308&postcount=133
After which I tried flashing the 3.41 bootloader and would get a FAILURE in the fastboot dialog. So I tried erasing/flashing recovery (TWPR 2.3) and bootloader (3.34) and each time got another FAILURE dialog on each erase and flash.
Now when attempting to boot, the screen is *completely* unresponsive. Even went as far as cracking it open and re-plugging in the battery. Nothing.
When plugging in a USB cable though on Windows 7, you get the familiar USB connection alert sounds. Although when plugging in USB devices, you should get the low-to-high sound (do-di), and unplugging you should get the high to low (di-do).
Well, you get the di-do sound when unplugging (keep in mind, screen is off), but when plugging IN, you get 3 low tones (do-do-do)... screen still off.
All the time the screen being completely blank. Did I actually kill this thing? Are there any steps to take to bring it back to stock, or at leats get the screen running. I am afraid at some point recovery or bootloader was erased and somehow not re-flashed... though I have done so numerous times in the past.
Any similar experiences or suggestions?
Did you adb erase bootloader? If so then you are truley bricked until the nvflash is available for this device. I believe that is what its called.
Travisdroidx2 said:
Did you adb erase bootloader?
Click to expand...
Click to collapse
Can't boot tablet, whether it be bootloader, recovery, or android. No matter what combination of power/volume I try, the screen remains blank. The only "responsiveness" I get is when plugging/unplugging USB cables in my pc, but even then I get the odd do-do-do as though the device drivers were unable to property install.
Sent from my Galaxy Nexus using Tapatalk 2
Did you ever run that command though? I see you said you tried to delete recovery and bootloader.
Everything leading up to this point was run in the bootloader via fastboot (fastboot erase recovery / fastboot erase bootloader / fastboot flash bootloader xxx.img / fastboot flash recovery xxx.img). I followed the steps I linked in the OP. Everything was running fine prior to booting to the bootloader to tinker with 3.41.
Now that I read what I've done, I am guessing I fried the bootloader. :\
Sent from my Galaxy Nexus using Tapatalk 2
Adb erase bootloader is where you went wrong. Sorry that sucks.
Anyway to get this thing running again short of dropping and replacing?
Sent from my Galaxy Nexus using Tapatalk 2
kbluhm said:
Anyway to get this thing running again short of dropping and replacing?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not at this point in time.
Oof.. Of all things to accidentally erase.. The bootloader.. I'm sorry man, that's a hard lesson to learn. The erase option for me has giant blinking neon light on it that says "STAY AWAY".. In over two years of owning Android devices I've never once actually used that command option and have absolutely no plans to ever use it.
Hahaha, hard lesson to learn, I agree. This sucks, looks like my beloved Nexus 7 may be meeting with an untimely demise.
Sent from my Galaxy Nexus using Tapatalk 2
kbluhm said:
I'm ready to spike this thing into the pavement and redeem my squaretrade warranty.
I was tinkering with the recently released 3.41 bootloader and I was getting the bootloop issues, though I could alwasy fastboot back to 3.34 and be fine.
So just now I was following the advice of another user:
http://forum.xda-developers.com/showpost.php?p=32771308&postcount=133
After which I tried flashing the 3.41 bootloader and would get a FAILURE in the fastboot dialog. So I tried erasing/flashing recovery (TWPR 2.3) and bootloader (3.34) and each time got another FAILURE dialog on each erase and flash.
Now when attempting to boot, the screen is *completely* unresponsive. Even went as far as cracking it open and re-plugging in the battery. Nothing.
When plugging in a USB cable though on Windows 7, you get the familiar USB connection alert sounds. Although when plugging in USB devices, you should get the low-to-high sound (do-di), and unplugging you should get the high to low (di-do).
Well, you get the di-do sound when unplugging (keep in mind, screen is off), but when plugging IN, you get 3 low tones (do-do-do)... screen still off.
All the time the screen being completely blank. Did I actually kill this thing? Are there any steps to take to bring it back to stock, or at leats get the screen running. I am afraid at some point recovery or bootloader was erased and somehow not re-flashed... though I have done so numerous times in the past.
Any similar experiences or suggestions?
Click to expand...
Click to collapse
Hey,
Did Squaretrade fix your device? I just want to know if there warranty is still valid if you unlock or brick your tablet
Hey Guys,
I've been on android since the G1. I've troubleshooted all problems I've had since flashing cyanogenmod when he was first on xda. With this Nexus 7, however, I've kept it completely stock.
I've had it for a month and it's been great. Yesterday I downloaded a homeland torrent and watched it. Put it down, came back two hours later and it was on a black screen (it was charged when I left at least to 50% after d/l and watching the video). I pressed the power button and it wouldn't start. I finally held it down for about 30 seconds and then it went to the "Google" screen all in white letters. It stayed there. I tried holding power for 10, 20, 30, 40, 50, 60 seconds and it would just reboot to the google screen. I finally tried to enter fastboot, i was able to, and got excited at being at a functional screen that I went into "recovery" and then the google screen just popped back up. Now I can't even get into fastboot.
I've tried the nexus toolkits but they both need either abd in android or the fastboot screen. I can't get into them. I finally called google play devices support and they said they will email me within two days to replace my nexus 7. However, I'd like to get my stored images, music, videos, etc off of there at the very least (although, I'd much rather fix it and keep it).
Can you guys suggest anything?
tl;dr : Stuck on google screen, can't enter fastboot. Is there anything I can do to make it boot? Option 2: how can I at least take my (emulated /virtual) sd card data out of it?
THANKS!
You are rebooting each time you try fastboot, correct?
Sent from my Nexus 7 using Tapatalk HD
Correct. It goes black for about three seconds then back to Google screen indefinitely
Sent from my HTC VLE_U using xda app-developers app
Bump?
Wow, I see criticism every time someone mentions they're "Bricked." Now that someone finally is bricked--or at least it seems like--no one is saying anything...
What happens if you hold all 3 keys for ~30-40 seconds, it should, at that point, reboot to the bootloader.
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
mihahn said:
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Thanks guys!
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, holding all three, holding power and volume up, holding power and volume down doesn't work. I've tried holding power until it restarts and then doing power and volume down, up, and both. Nada.
I appreciate your input guys. I'll just return the product to google... hopefully they don't fix it without a full wipe and get ahold of my files! Yeek!
AW: [Q] Stuck on Google Screen- Cannot enter fastboot
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
But I guess the best is to replace it
Sent from my SK17i running Android 4.1.2
mihahn said:
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
Click to expand...
Click to collapse
He said he was 100% stock.
The stock recovery doesn't start up the adbd daemon. That's typical for stock recoveries.
Proves the point that even if you stay with stock on the N7, you should unlock the bootloader as soon as you get the device. Then the option of soft-booting a different recovery (fastboot boot recovery.img) would be available for rescue situations - even if the ROM stays completely stock and unrooted.
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
When your device is on and showing Google
Press and hold the Power key till the screen goes black
Once black, press and hold the volume down key
This will take you to fastboot
Press volume key up twice then power key to select
Device should now be in recovery mode
If you wiped the OS, use Wugs Toolkit to recover from soft brick in advanced options
If you want to push files to your device and try to recover, use MSKIP's Toolkit
Hope this helps....good luck
Sent from my Nexus 7 using XDA Premium HD app
dwny said:
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
Click to expand...
Click to collapse
Nope, not unlocked, rooted or have a custom recovery.
Recently I have had a major issue with my nexus 7. About 2 weeks ago, it died (ran out of battery) while I was using it. When I attempted to turn it on after charging it, I would get the screen that says google, with unlocked lock icon. The tablet would be frozen at this screen. I left it running until it died again. I was running the latest stable release of cyanogenmod 10 with clockworkmod recovery with no problems before when this happened.
By now I had realized that the nexus may have been bricked. I did some googling and found that this is an issue other users have been having when their battery died on android 4.2.2. I attempted to restore the nexus. At this time I was able to access bootloader on the device by holding down all of the buttons at the same time. I think I selected the recovery option. However, I decided not to restore the nexus, and wait until a time where I would be able to turn all of my attention to the problem, and powered the device off, it may have been in recovery mode at that time but I do not remember.
But now, I can't access the bootloader! When I reboot the device by holding down power, I see the google screen for about 4 seconds, then I get a black screen (I can tell the device is still on because the screen is an illuminated black screen). Black screen remains there indefinitely. Any button combo (voldown+power, volup+power, all 3, volup+voldown (this one doesn't do anything), hard reset combo, etc) doesn't do anything except reboot the device and give me the same behavior.
I connected it to my pc (running windows 8) and used the nexus root toolkit by wugfresh to install some drivers. I could install the first driver the toolkit told me to but not the second because the device wouldn't reboot into bootloader. In device manager I see "Galaxy Nexus ADB Driver", hardware ids are USB\VID_18D1&PID_D001&REV_9999 and USB\Vid_18D1&PID_D001, so that tells me custom recovery. Running "adb devices" tells me the device is in recovery mode, but I just see a black screen. Doing adb reboot bootloader or fastboot reboot bootloader hangs and gives waiting for device respectively. Similarly wug's toolkit hangs when trying to reboot the device into bootloader.
I've opened up the back and done a literal battery pull many times. Battery connector is in place after this. I also accidentally broke off one of those tiny copper tabs next to the battery, but that's not relevant to this problem and I believe is minor, broke that after I got this problem. After I do battery pull and plug back in, I either:
a) get a battery lightning icon in the center of the screen, which begins to fill up after a few moments. Rebooting device gets me back into google then black screen mentioned above
b) get a screen with static/snow on it. There is also a hissing/humming noise coming from the back of it. Rebooting gets me to google screen again. This screen also can appear rarely with no discernable pattern to when it appears.
c) same google screen followed by illuminated black screen.
I've left the device charged in, unplugged it, let battery die, and tried many combos of buttons, but can't get anything except the three screens stated above.
I know the saying "Nexus devices are almost impossible to brick" but if I can't access the bootloader and just get black screen then I don't know if I can fix this.
I've posted a thread similar to this one before, so if your username is bftb0 then you've seen this problem already. I'm trying to repost with more information to see if any other ideas are there. Other thread is http://forum.xda-developers.com/showthread.php?p=39522179#post39522179.
So these are my theories to what the problem is:
-corrupted bootloader
-bug/corrupted clockworkmod recovery
-bad battery/power/overheating
-corrupted memory
So how can I solve this?
I know there is NVFlash but there isn't a version for nexus 7. Almost all of the things I've found involve using bootloader. Any suggestions for things I haven't tried yet?
I have obtained an RMA from Asus but I don't want to send the device in because the bootloader is unlocked, so they would probably not cover this under warranty.
Does anybody know of a way to erase evidence of having a bootloader? Or a way to convince Asus to fix the device even with bootloader unlock? What's the price of the repair if not covered under warranty? I'm a poorish student with not much money, so I hope it's not that much and that's why I'm reluctant to pay for repairs.
Also I haven't done anything stupid like fastboot erase bootloader, in fact I hadn't connected the device to pc in a week.
I think this might be a bug with android 4.2. I love android and nexus, but if this is google's fault then I might be done with Android.
Thanks so much.
if it's still bricked i would be interested in buying it for the screen (even screen only,and you keep everything else) cause mine broke today!
komakos96 said:
if it's still bricked i would be interested in buying it for the screen (even screen only,and you keep everything else) cause mine broke today!
Click to expand...
Click to collapse
Perhaps. I'll try to see if I can RMA it under warranty, probably wouldn't be covered though. I'll consider it.
Anyone else, have ideas for how to fix?
Had that problem before:
I had fixed it by opening the nexus 7 and unplugging the battery,
then I hooked it up to the charger(its screen turned on to a black one with the hissing speaker) and used the power button hard reset it,
The nexus 7 reset and gave me a really glitchy/teary black screen.
Then I unplugged it and replugged the battery and put the whole thing back together (mines tape-fixed BTW) and turned it on
Sent from my Nexus 7 using xda app-developers app
STLset said:
Had that problem before:
I had fixed it by opening the nexus 7 and unplugging the battery,
then I hooked it up to the charger(its screen turned on to a black one with the hissing speaker) and used the power button hard reset it,
The nexus 7 reset and gave me a really glitchy/teary black screen.
Then I unplugged it and replugged the battery and put the whole thing back together (mines tape-fixed BTW) and turned it on
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Still no luck... It just gave me the black screen as before. Thanks though
Hi, can you access bootloader mode???
If you not your Nexus has its /boot partition broken or formatted. That is a "Super brick" is irreversible.
Good luck!
Regards.
Sent from my Nexus 7 using xda app-developers app
/boot is kernel. It has nothing to do with his problem. He can't access bootloader.
Flowed from my HTC branded muffin...
No chance to get a free repair out of Asus right? Know of any way to get them/trick them to repair it for free?
If no, what's the price they'll charge?
Hi stereo8.
/boot is not just the kernel, is the boot loader too, and if he can't boot on boot loader mode we have the problem.
Regards.
Sent from my Nexus 7 using xda app-developers app
MlucianoEze said:
Hi stereo8.
/boot is not just the kernel, is the boot loader too, and if he can't boot on boot loader mode we have the problem.
Regards.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Excuse me, but stereo8 is right. You should probably read a bit more about the internal structure / partitions of the Nexus7.
Sent from my Nexus 7 using xda app-developers app
Update:
I think my device may just be stuck in recovery. I think I may have accidentally hit the recover button when I was able to access the bootloader. I was running clockworkmod recovery 10. Perhaps it has been corrupted.
How do I get out of the recovery using adb?
Why do you have 2 threads open for this ?
Sent from my Galaxy Nexus
patil215 said:
Update:
I think my device may just be stuck in recovery. I think I may have accidentally hit the recover button when I was able to access the bootloader. I was running clockworkmod recovery 10. Perhaps it has been corrupted.
How do I get out of the recovery using adb?
Click to expand...
Click to collapse
Connect to the usb to pc and use the adb command" adb reboot bootloader "
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
heavy_metal_man said:
Connect to the usb to pc and use the adb command" adb reboot bootloader "
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
I've already posted that I've tried that. The device just powers off and doesn't power on again. Turning it on with any combination of buttons puts me back in the google screen then black screen.
patil215 said:
I've already posted that I've tried that. The device just powers off and doesn't power on again. Turning it on with any combination of buttons puts me back in the google screen then black screen.
Click to expand...
Click to collapse
Ok, while the device is registered as "recovery" open a cmd and cd to your adb set up.
Try using the commands
Adb shell
#wipe data
This should wipe all user data from the tablet, maybe even the sdcard/internal memory as well. I am looking to see if you can use and to flash a bootloader for you, but it would carry heavy risks.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Hi guys yesterday my nexus freeze in gmail.. so i turn it down by pressing and hold te power button
then the tablet freeze in the Google LOGO
after taht i try to ge into Recovery mode,, it freeze aswell then i just reboot it on bootloader adn i leave it thre for about 1 hour charging
the i try to go to boot loader to fhasl stok rom..
but..!! it wont work.. never turns on..
and it shows in my pc as APX mode
no more than that y tri to start it in bootloader but i just cant with every method i find in internet even i try to charge it by pogo pins and nothing happends
i try to do soetring with nvflash but it said
Unknow devices found and do nothing
pls help me ,!!
radeon9550 said:
Hi guys yesterday my nexus freeze in gmail.. so i turn it down by pressing and hold te power button
then the tablet freeze in the Google LOGO
after taht i try to ge into Recovery mode,, it freeze aswell then i just reboot it on bootloader adn i leave it thre for about 1 hour charging
the i try to go to boot loader to fhasl stok rom..
but..!! it wont work.. never turns on..
and it shows in my pc as APX mode
no more than that y tri to start it in bootloader but i just cant with every method i find in internet even i try to charge it by pogo pins and nothing happends
i try to do soetring with nvflash but it said
Unknow devices found and do nothing
pls help me ,!!
Click to expand...
Click to collapse
Ok as far as I have herd there is no way to rescue a bricked nexus 7 using NVflash if there are no Backed-up Blob files on it. If you just ended up in apx mode without doing anything to its bootloader then it is probably out of charge or needs to have a particular button combo to sort it out
if on the other hand you corrupted the bootloader and after that the device is in a sleep of death then you have hardbricked your nexus 7 'apparently'
good luck
No Custom Bootloader
Hill well i never done something to the bootlaoder no Multibot no Custom bootloader ( factory only )
i try a lot of key combination but nothing happend :/
but my questin is i got a second n7 same specs how can i pull the blob files and,
can i use this files to unbrink the other
if i can pls explainme that
i love my tablet i dont wanna see her die
thnaks..
don't give up
radeon9550 said:
Hill well i never done something to the bootlaoder no Multibot no Custom bootloader ( factory only )
i try a lot of key combination but nothing happend :/
but my questin is i got a second n7 same specs how can i pull the blob files and,
can i use this files to unbrink the other
if i can pls explainme that
i love my tablet i dont wanna see her die
thnaks..
Click to expand...
Click to collapse
Ok if you want to know about how to set up a link between the NVflash tool (on your computer) and your new n7 just use the following proceedure here www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
As far as your old n7 is concerned if it is definitely hard-bricked and you have not made a backup using NVflash before the brick then there is no known way to save it with only a computer and n7 connected via USB however there is a slim chance your old n7 might just be in a state where it can't access the bootloader because of some power shortage or incorrect button states so do keep trying the key combos and recharging etc because there are a lot of stories of people who escaped using this random strategy. Normally to get into apx mode one would press all three buttons at once so to get out you could do the same so it is worth a try
BTW I have one more trick up my sleeve, if you download WugFresh's toolkit for the n7 (make sure its 2012 edition) then you could try pressing the 'reboot bootloader' option in the advance options menu in the lower left.
good luck
Gloftking said:
Ok if you want to know about how to set up a link between the NVflash tool (on your computer) and your new n7 just use the following proceedure here www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
As far as your old n7 is concerned if it is definitely hard-bricked and you have not made a backup using NVflash before the brick then there is no known way to save it with only a computer and n7 connected via USB however there is a slim chance your old n7 might just be in a state where it can't access the bootloader because of some power shortage or incorrect button states so do keep trying the key combos and recharging etc because there are a lot of stories of people who escaped using this random strategy. Normally to get into apx mode one would press all three buttons at once so to get out you could do the same so it is worth a try
BTW I have one more trick up my sleeve, if you download WugFresh's toolkit for the n7 (make sure its 2012 edition) then you could try pressing the 'reboot bootloader' option in the advance options menu in the lower left.
good luck
Click to expand...
Click to collapse
Same deal here - and frickin ASUS wanted $165 JUST for the motherboard part. So I said no to the RMA and they sent it back.
NOW my question is - can I order a motherboard and just swap it out? Does that work? http://www.ebay.com/itm/Asus-Nexus-...2GB-ASUS-Google-ME370T-Ship-Fast/121330719361
bshiznit said:
Same deal here - and frickin ASUS wanted $165 JUST for the motherboard part. So I said no to the RMA and they sent it back.
NOW my question is - can I order a motherboard and just swap it out? Does that work? http://www.ebay.com/itm/Asus-Nexus-...2GB-ASUS-Google-ME370T-Ship-Fast/121330719361
Click to expand...
Click to collapse
Haven't done it myself, but understand it does work. https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943
PrizmaticSmoke said:
Haven't done it myself, but understand it does work. https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943
Click to expand...
Click to collapse
Thanks! Ordered it and will be attempting
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
possibly?
Did you just update and it got stuck at the booting up????
opeller said:
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
Click to expand...
Click to collapse
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
ChainFires Son said:
Did you just update and it got stuck at the booting up????
Click to expand...
Click to collapse
No, it did not occur after an update.
theminikiller said:
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
Click to expand...
Click to collapse
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
You can download factory images from here https://developers.google.com/android/nexus/images
opeller said:
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Click to expand...
Click to collapse
First we should check if you can boot into the bootloader at all. First turn the device off. Then hold down both the volume buttons and then press and hold the power key. Keep holding all the buttons until you see some different colored text. If that happens we should be able to install a factory image, if it still gets stuck on the Google logo I unfortunately don't have any more ideas.
Tried pressing both volume keys and power button. Google logo show for a second, then black for 2 second, thank flashing red notification light every 1/2 second until I let go of the buttons.
When I release the buttons, the phone goes back to charging battery screen.
I see people suggesting that the red light flashing means a battery problem, but the device keeps trying to boot up while it is not plugged to the charger, unlike what happened to them
Any Ideas why this is happening or what the red light means in this case?
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
harishmenace said:
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
Click to expand...
Click to collapse
Oh it was just volume down, not both. Heh, sorry.
Use the Nexus Root Toolkit (NRT), it's the easiest way to unlock, root, flash and manage your SuperUser needs!
http://www.wugfresh.com/nrt/
Not sure, but maybe?
You can try using the nexus root kit & unlock your bootloader and see if a factory reset can work. If it does you can always relock it again ☺..Flashing a factory image can work too also ...
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
I'm you can't get into the bootloader then I am unfortunately not aware of any way to help you. If you can't even get into the bootloader I think it is a high probability that it is a hardware problem.
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
opeller said:
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
Click to expand...
Click to collapse
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
Bus 001 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode),
Click to expand...
Click to collapse
on windows (XP/Vista/7)
Qualcomm something QDL Mode or something like this on "device manager"
Click to expand...
Click to collapse
there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
x1123 said:
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
on windows (XP/Vista/7) there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
Click to expand...
Click to collapse
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
opeller said:
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
Click to expand...
Click to collapse
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
That sounds like the battery is completely empty. Put the device on charger over a night and try then to boot into the bootloader.
Once I had these symptoms (red light flashing) on my N4, it was enough to charge the battery for one hour. Then it booted properly. It's worth trying.
x1123 said:
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
Click to expand...
Click to collapse
How do I do that?