Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Reserved for updates
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium
Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)
chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium
chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250
Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium
Hey
I know this is a greatly discussed topic but I have been through countless threads and tried everything so please bear with me! Long story short, my phone is in a massive rut at the moment and nothing seems to get it out of bootloop (tried fastboot, odin etc; yes I'm not an expert at all but I'm not exactly a noob). Odin is/was my last hope and for some reason Windows XP seems to keep crashing it the minute I hit start. I read through numerous posts on the Galaxy Nexus forum and have also tried numerous other methods including trying to go back to stock via fastboot and toolkits, trying to flash .img files individually etc etc etc and I basically need all the help I can get if someone wouldn't mind? The phone does turn on to fastboot and is detected on toolkits and drivers are fine.
For those who need the info its a i9250 GSM maguro (UK version i.e. without google wallet) running JB 4.1.1. I did try to flash maguro ICS 4.0.4 and when I go into fastboot, the bootloader version has changed to PRIMELA03 whereas I'm sure JB isn't that but I may be wrong! The phone crashed 2 nights ago and ever since then it gets stuck in bootloop when switched on, the images are noisy and fuzzy as if the phone has some kind of virus and nothing flashes on it! Fastboot just crashes requiring a battery removal all the time. Odin crashes too so I cannot flash any other firmware. The phone is not rooted but the bootloader is unlocked and I have no SD card (obviously).
Sorry if I have posted in the wrong thread or done anything I shouldn't have -_- I just need help so someone PLEASE guide me in the right direction!
Thank you in advance!!
Update: I just tried to flash JB back over the bootloader version and it changed from PRIMELA03 to PRIMELC03 so the bootloader version does change however nothing else seems to flash!
Update 2: Think i finally managed to mess my phone up. Got the yellow exclamation mark triangle between a phone and pc -__- anyone have any insight on how to go around this? Everything I have read up has more or less got to do with all other variants of Gnex other than GSM!
Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
bk201doesntexist said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Click to expand...
Click to collapse
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.
Devzz said:
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.
Click to expand...
Click to collapse
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium
slim207rc said:
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?
Devzz said:
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?
Click to expand...
Click to collapse
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium
slim207rc said:
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium
Click to expand...
Click to collapse
No problem
OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.
MightyChigger said:
OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.
Click to expand...
Click to collapse
You need a Windows 7 pc.
Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.
Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
well unfortunately for me, I dont have one... can this be done on Windows 8.1?
jpradley said:
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.
Click to expand...
Click to collapse
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??
MightyChigger said:
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??
Click to expand...
Click to collapse
After sending to HTC to have the camera sensor fixed I could no longer get fastboot to work and I had to suffer with stock for a couple of months. I finally resolved this by updating sdk having read recent Windows 7 updates could be the culprit, maybe it was a usb driver update, but was still having issues.I read to try turning usb debug off and on which in the end may have been all that was required. Finally back to S-off running Viper 6.1 which team Viper deserves major props on for a brilliant job. BTW I'm on Windows 7 Ultimate with usb 3 ports only.
Go here and watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585
Hi guys,
So, I used to have some touchscreen issues, like, device going into standby, when waking up touchscreen wasn't working. After a forced shutdown usually solves it, sometimes i have to do it 2 or 3 times... but today.. after a forced shutdown, my tablet refused to boot.
So, following tutorials all around, I used fastboot to flash the original nexus image for 4.4.2, went fine, no errors (after a few retries), also flashed recovery (tried twrp and cwm), but the result is the same, google logo.
I tried flashing just fastboot flash system system.img, same for boot.img, still stuck at google logo. I got fastboot, but even selecting recovery, stays at google logo. I don't know what else to do. I know similar issues happen but usually they get sorted flashing either recovery or the image itself, but in this case, the tablet refuses to boot after a sucessfull image write.
Any tips? Thanks a lot guys, would mean a lot because I cant sent to warranty right away. Im not in my country (holidays) and I kinda need to use the tablet (ended up bringing it instead of my laptop, wasnt expecting this).
Any help is highly appreciated.
cheers!
MidnightDevil said:
Any help is highly appreciated.
cheers!
Click to expand...
Click to collapse
Did you confirm that adb recognized your tablet while in fastboot? Open a command and type adb devices. What is the response? Do you have adb.exe and fastboot.exe downloaded so you can flash the zips?
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
Did you confirm that adb recognized your tablet while in fastboot? Open a command and type adb devices. What is the response? Do you have adb.exe and fastboot.exe downloaded so you can flash the zips?
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb nothing cause it stays in bootloader, its recognized in fastboot, thats how i was able to put the official google image.
I got it to boot now, randomly, out of nothing, did nothing at all and its okay.
I dont know why it happens but its the third time it does this after touchscreen stops working.
Anyway, until the next time.
I know touchscreen issues happen, but this random thing is driving me nuts.
Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Use wugs program but tick tablet is in bootloop.
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!