Related
Hi all, I've been having problems with my transformer... again. This time I have my transformer successfully rooted with an updated CWM, and flashed PRIME 1.6 and Netformer 1.5. The problem started when I held down power and selected the recovery option in the shutdown menu. the tablet went into a bootloop until I put it into APX mode to run the unbricking tool stickied in the dev section. For some reason, the tool didn't work and it did NOT say "phone update success on the tablet screen."
I then turned it off and my computer makes the USB disconnect sound, but then makes the connect sound right after, and Nvidia USB recovery shows up in device manager again, which means that it is stuck in APX mode. I cannot boot into CWM and I cannot boot up normally because it just dumps me back into APX.
I found a thread of someone who was also stuck in APX mode, but it doesn't help because he just returned the tablet whereas I cannot. http://forum.xda-developers.com/showthread.php?t=1169097
So to recap, I am stuck in APX mode, I can't boot normally or into CWM, and the unbricking tool does not work. Help please? I am starting to seriously regret flashing anything
EDIT: I did it! Thanks to all for the responses, I finally followed this guide to nv_flash prime 1.6r2 to my tablet and now it boots! The problem turned out to be that when I used the unbricking tool, it formatted all my data so the tablet was not able to boot into anything. By nv_flashing a rom onto it, it had something to boot into... again, thanks!
Anyone have any ideas? If I can't fix this then $400 went down the drain
Have you tried nvflash? I had that problem but nvflashing prime worked for me.
Sent from my PC36100 using Tapatalk
Vertiginouz said:
Hi all, I've been having problems with my transformer... again. This time I have my transformer successfully rooted with an updated CWM, and flashed PRIME 1.6 and Netformer 1.5. The problem started when I held down power and selected the recovery option in the shutdown menu. the tablet went into a bootloop until I put it into APX mode to run the unbricking tool stickied in the dev section. For some reason, the tool didn't work and it did NOT say "phone update success on the tablet screen."
I then turned it off and my computer makes the USB disconnect sound, but then makes the connect sound right after, and Nvidia USB recovery shows up in device manager again, which means that it is stuck in APX mode. I cannot boot into CWM and I cannot boot up normally because it just dumps me back into APX.
I found a thread of someone who was also stuck in APX mode, but it doesn't help because he just returned the tablet whereas I cannot. http://forum.xda-developers.com/showthread.php?t=1169097
So to recap, I am stuck in APX mode, I can't boot normally or into CWM, and the unbricking tool does not work. Help please? I am starting to seriously regret flashing anything
Click to expand...
Click to collapse
Did you actually flash a rom? That can happen when you dont have the appropriate files in the directory. Refer to the video that demonstrating an NVflash.
Sent from my Transformer TF101 using XDA Premium App
Yes, I flashed prime 1.6 and booted it successfully. I used the "recovery" option in the shutdown menu and that caused the bootloop, i never got into cwm
Did you compare md5's?
Sent from my Transformer TF101 using XDA Premium App
Backwardsblade said:
Did you compare md5's?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I didn't, but it did boot up fine, which means it was a legitimate download right?
I think I'll just try to send it to asus and see what they can do since NVflash doesn't work
I would probably download again, check the MD5 and reinstall.
Skickat från min ASUS Eee Pad TF101
I can't reinstall if I can't boot into cwm
Vertiginouz I can't reinstall if I can't boot into cwm
Click to expand...
Click to collapse
Are you sure you know what nv_flash is? This is only run in apx mode.
Did you try the one click batch method: http://forum.xda-developers.com/showthread.php?t=1185104
See whether that works for you...
keep this thread open, I would really like to know what the OP did to get out of this mess.
I would also like to know if other peeps running Prime 1.6 can press the recovery button instead of shutdown for some testing.
What kind of testing? I just did root a TF, backed it up, installed Prime, clicked the Recovery button and did a back up. Zero trouble.
I think this is my 7th or 8th root. People at work just keep bringing them to my office
It sounds like you didn't have a Rom when you nvflashed. If you just downloaded nvflash file in the stickied unbricking post then you will format everything without putting anything back on. You need to Rom that was built nvflash and put it in the root directory of the nvflash folder. There are some stock Roms available somewhere & also a prime 1.4 nvflash. They will install a recovery and then you can flash whatever you want from there.
Sent from my Transformer TF101 using XDA Premium App
boglwe said:
keep this thread open, I would really like to know what the OP did to get out of this mess.
I would also like to know if other peeps running Prime 1.6 can press the recovery button instead of shutdown for some testing.
Click to expand...
Click to collapse
I am currently running Prime 1.6 and i did a recovery method the other day to update a rom and it worked just fine.
I did it since i updated from 1.5 to prime 1.6 and had to re install the Clemsyn-blades cause the overclocking rom got disabled after update...
Thanks for the suggestions guys, I'll try the link that Q.Entity posted first.
housry23 said:
It sounds like you didn't have a Rom when you nvflashed. If you just downloaded nvflash file in the stickied unbricking post then you will format everything without putting anything back on. You need to Rom that was built nvflash and put it in the root directory of the nvflash folder. There are some stock Roms available somewhere & also a prime 1.4 nvflash. They will install a recovery and then you can flash whatever you want from there.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Okay so the unbricking nvflash formats everything, meaning I can't boot normally because I have no ROM? Shouldn't I still be able to boot into CWM though?
Also, the prime 1.4 nvflash thread you're talking about is this right? If I follow that guide will it install prime 1.4 during the nvflash process? If so, that will probably solve my problem
should work, but why stop there, I went ahead and popped on Prime 1.6 and then flashed a different kernel as well. I mean, I nvflashed from temp brick, perhaps like yours, and instead of flashing 1.4 prime I went ahead and did 1.6 since I already had the zip. I also at some point did the unbricking nvflash to stock rom, then used the pure root for tranformer method that includes CWM and then flashed Prime. regardless, both ways I was temp bricked. The key for me was knowing that I was in APX mode even though Device Manager in wndows 7 64bit did not show I was. Hope I could help, I am only speaking from my OWN experience with this device and prior mistakes.
EDiT: I also noted as some point that I could not get into recovery becuase I was not paying attention to my recovery screen. If all is correct, then when you hold down Vol- and power button, you are only given 5 seconds to press vol+ button to enter CWM.
Sent from my Transformer TF101 using XDA Premium App
The batch pure root script didn't work for me, even though I tried nvflashing the stock boot.img and recovery. No matter what, I couldn't get out of APX mode. The transformer immediately turns back on and puts me back into APX mode after I turn it off. Device manager and the USB connect/disconnect sounds confirm this. I'm afraid there's no way to get out
Why are you doing a pure root, after nv_flash. Why not just nv_flash prime 1.6 and be done? That will have everything working.
Yep.. your doing things kinda backwords.
Sent from my PG86100 using XDA Premium App
I have a Huawei u8800-51 that I tried to install the official 2.2.2 ROM from Huawei, File name "U8800V100R001C00B138SP04CUSTESTC205D001 (Estonia Elisa)". I double checked that it wasn't the pro file.
It went through both steps fine, and said upgrade complete Rebooting. When it "Reboot", it vibrated slightly, but went no further, only a black screen. I left it alone for about 10 minutes, in case it was part of the upgrade process, but it never powered back on. I tried to reboot manually, with the same results, just a short vibration, and black screen. I have searched high and low, to no avail. I have tried putting the same dload file from the file on the SD card, pull the battery and plug to computer ( one of the possible fixes that I found ), but again, same results.
Is the phone officially bricked now, or can it be recovered? ANY help would be greatly appreciated.
Thanks.
You installed u8800 rom to u8800-51???
Sent from my U8800 using Tapatalk 2
From the links I followed for the 8800-51, that was the ROM to use.
Sent from my Galaxy Nexus using xda premium
Can you still get to pink screen?
Sent from my locked MB865 on Ice Cream Sandwich.
thenewguy821 said:
I have a Huawei u8800-51 that I tried to install the official 2.2.2 ROM from Huawei, File name "U8800V100R001C00B138SP04CUSTESTC205D001 (Estonia Elisa)". I double checked that it wasn't the pro file.
It went through both steps fine, and said upgrade complete Rebooting. When it "Reboot", it vibrated slightly, but went no further, only a black screen. I left it alone for about 10 minutes, in case it was part of the upgrade process, but it never powered back on. I tried to reboot manually, with the same results, just a short vibration, and black screen. I have searched high and low, to no avail. I have tried putting the same dload file from the file on the SD card, pull the battery and plug to computer ( one of the possible fixes that I found ), but again, same results.
Is the phone officially bricked now, or can it be recovered? ANY help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Try connecting USB cable from PC to your phone with out battery....
krish_nank said:
Try connecting USB cable from PC to your phone with out battery....
Click to expand...
Click to collapse
Tried that as well
Sent from my Transformer TF101 using xda premium
Disk image
thenewguy821 said:
Tried that as well
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
You didn't make a disk image?
Can you give me a link to the rom/guide you followed?
Somcom3X said:
You didn't make a disk image?
Can you give me a link to the rom/guide you followed?
Click to expand...
Click to collapse
I was jumping back and forth between here, rootzwiki and another site, hard to follow the trail. I did do a backup in CWM Recovery, but I couldn't get into recovery to try to restore.
Ended up taking the phone into AT&T, told them the hone wouldn't boot after an update. They replaced the phone, no charge.
Sent from my Transformer TF101 using xda premium
thenewguy821 said:
I was jumping back and forth between here, rootzwiki and another site, hard to follow the trail. I did do a backup in CWM Recovery, but I couldn't get into recovery to try to restore.
Ended up taking the phone into AT&T, told them the hone wouldn't boot after an update. They replaced the phone, no charge.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I have the same problem. No one know how to fix this??
Let me try making a disk Img for you
Sent from my GT-I9300 using xda premium
u8800-51 black screen, not booting at all. no pink/blue or even recovery. a little vibration and that's it..
any help is appreciated, thanks.
Somcom3X said:
Let me try making a disk Img for you
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
How can the disk image help if we cannot load without getting to a pink/blue screen?
when you took your phone to att
did you have service with them at the time?
http://forum.xda-developers.com/showthread.php?t=2000509
I have same problem after update ... any solution
Can't help due to it screwing up your process to motherboard connection
Somewhere in the sticky section of this forum should be "Back the kcuf up!" with links to image backup instructions. I have started doing it routinely. I bricked my phone this morning with a mundane font manager (who'd a thunk?). An hour later it was working just fine.
eyeconic said:
Somewhere in the sticky section of this forum should be "Back the kcuf up!" with links to image backup instructions. I have started doing it routinely. I bricked my phone this morning with a mundane font manager (who'd a thunk?). An hour later it was working just fine.
Click to expand...
Click to collapse
Its a pinkscreen backup no? I use it rarely, more likely for Official roms such as froyo, ging.
Somcom3X said:
Its a pinkscreen backup no? I use it rarely, more likely for Official roms such as froyo, ging.
Click to expand...
Click to collapse
Absolutely. I made one paperweight that CWM refused to restore from a blue screen. I have two scripts:
#!/bin/bash
dd if=/dev/sdb of=u8800.img bs=512
#!/bin/bash
dd if=u8800.img of=/dev/sdb bs=512
I'm sure that there is a WinDoze equivalent. Before installing any app that needs root, I do a complete BU.
Hello everyone,
I'm hoping someone will be able to help me. I seem to have gotten in over my head. I have flashed various ROMs to my a500 over it's life without trouble. But about a month ago I tried to flash a new one and it didn't work. Came up with an error about partitions (I don't think it's important at this point). I was using TWRP recovery at that point. After the error, I could not get anything to work. My back up wouldn't recovery, I couldn't flash the last ROM I used, nothing worked.
I tried a few things to attempt to fix it, but I think I only made matters worse. I no longer have TWRP recovery installed. I think I have only the stock recovery. Tablet sits on acer screen when powered on. I haven't been able to install any update.zip packages. PC doesn't seem to see device when plugged in via USB. I can't put device into USB debugging as it doesn't boot so I'm unable to follow most guides I see.
Can anyone help me? I'll be happy to provide whatever information I can.
You can't get into Fastboot? You sure you have the correct drivers? What bootloader were you using and what kind of rom were you trying to load? Your gonna have to be more specific to garner more responses
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Vintage144 said:
You can't get into Fastboot? You sure you have the correct drivers? What bootloader were you using and what kind of rom were you trying to load? Your gonna have to be more specific to garner more responses
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
No, I can't seem to get into Fastboot. If it works, the tablet should display fastboot in the corner, right?
I have the Acer USB drivers installed. I believe they are correct.
I was using TWRP and attempting to install Jelly-Bean_4.1.2_CM10-FLEX_v6supercharged_Aroma(22-Nov-2012)
Also, thank you for responding. Sorry if I seem a bit noobish. All the ROMs I have used up until now just worked so I didn't think about too much.
I'm really missing my tab. Hopefully someone can help me out.
My TAB appears to be completely bricked as stated above. No boot. Just the Acer logo on the screen on power up.
I think what I did was format the entire thing. So that there is nothing on it. I have blackthund3r A500 Manager v1.02 installed and it displays "NO A500 Connected!" in the bottom corner. As I stated most guides tell you to turn USB Debugging on, but I can't do that since it doesn't boot, and really I don't think there is an OS installed on it at all.
Anyone have any suggestions, advice, ect?
I have a client's Atnt galaxy s4 that will not boot up normally and will not boot into recovery also.
when i try to boot into recovery i get the blue lettering in the top left and it just sits there i have let it sit for sometime like that with no change.
this is not my first go around with flashing android devices so please even give me Dev only options if that is what you think will fix it. i feel bad because he just bought this phone 2 weeks ago and cant use it. not sure what the other guy that tried to root it did and neither does he so i am shooting in the dark so any help would be great.
I have tried flashing the stock Odin package with no luck.
Also tried Kies Firmware upgrade with no luck
Most of the custom recovery for this phone from what i read are not flashed threw odin anymore, but if i am wrong please link me and i will give it a shot.
Dose anyone have any ideas someone told me to use the .PIT file and re-partition the device and reflash the stock odin package. but i have had no luck locating the .pit file for the I337 galaxy S4 could anyone grab it from there phone and upload it for me or any ideas on how i could possibly fix this issue.
Thanks in advance
Since you already tried ODIN, why don't you try KIES.
I tried that allrdy just forgot to add it to the list updated first post
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
ok i will have him give it a try
and yes it goes into downloading mode with no issues at all.
if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.
C13v3r0n3 said:
if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.
Click to expand...
Click to collapse
The OS wont boot that is why we are having such a issue cause we have to get into the recovery to fix the phone
thanks thou
If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app
In addition to letting go of the power button after the vibrate, here are a couple of other things that appear to have worked for other forum members. I didn't discover any of these fixes, I just did a lot of reading and saw where others have had similar problems and found ways to solve them. That is what makes the XDA community great:
Uppercuticus said:
I've had this happen to me several times while playing around with flashing. Basically (without fail in my experience), hold power+volume up+home as you'd normally do until you see the booting recovery message and let go. It will do one of two things - boot into recovery- or - restart and vibrate-. If it restarts and vibrates, immediately hold power+volume up+home until the booting recovery message pops up again and let go. It should then boot into recovery and you shouldn't have trouble in subsequent attempts.
It took me a while to figure this out and I actually thought I had permanently bricked my phone as the phone wouldn't boot and I couldn't get into recovery. Hope this helps.
Click to expand...
Click to collapse
RiNo808 said:
Those trying to boot into recovery mode, dl quick reboot from the play store. That's what I use and it works great.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.
C13v3r0n3 said:
If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
After using ODIN, make sure to do a software (factory reset) to get rid of any data and settings that stayed behind. The firmware packages that we have for Odin, do not wipe everything on their own.
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanks - was having the same problem. At last somebody explains it properly. It worked.
(Why on earth is the script on the stock recovery screen so small. You need a microscope to read it. I am going to install CWM right away....)
Cheers LJ
S4 on veriozon only boots into download mood
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!
Yankeetim92 said:
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2316
any luck? im having the same problem after enabling the t-mobile aws bands on my i337. i could only get into odin mode, recovery boot sits there on end and i have no access to the phone settings. ive tried the odin with stock firmware but nothing.
xBeerdroiDx said:
http://forum.xda-developers.com/forumdisplay.php?f=2316
Click to expand...
Click to collapse
you are not playing fair sir...but a good one.
TheAxman said:
you are not playing fair sir...but a good one.
Click to expand...
Click to collapse
My unrooted s4 phone gets stuck with the blue colour legend Recovery booting with any mentioned method. I am unable to enter safe mode, any ideas? been surfing google for 6hrs with no proper answer. Thanks!!
C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanx bro, This is solve my problem.
Having allmost the same problem with my S4...
http://forum.xda-developers.com/showthread.php?t=2498285
continuation of SGH_1337 will not boot into recovery
norml said:
Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.
Click to expand...
Click to collapse
here are all the details;
Rooted ATT Galaxy S4 MK2 with Busybox. all went well until I tried to flash and boot into recovery. Installed ClockworkMod Recovery, tried to reboot into recovery...permission error. Installed Team Win Recovery, same problem.
investigated... Superuser.apk for some reason is NOT present in app directory. hmm. checked for root, have root.
installed ClockworkMod Superuser from play store... asks to update superuser... fails with signature error.
There seems to be no way to flash this phone. I have the original backup I made with ClockworkMod but restore fails with signature error.
The phone works fine, has root but I am concerned I will not be able to update to 4.4 when it's available. I am also NOT able to flash any alternative ROM. frustrating.
I see there are relatives to this issue all over xda but as far as I can tell after a weekend of trying is there's NO WAY to boot into recovery with write permissions being allowed.
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
Can you get into the bootloader?
DaanJordaan said:
Can you get into the bootloader?
Click to expand...
Click to collapse
No. it's really gone. Just spoke with google and getting a replacement. I really can't do jack....bleep...with it.
all this for changing a font with Rom toolbox.
Yeah, bricked, but I'll buy it for 30
So it's permanently stuck on the Google logo and you can't access recovery or bootloader? No boot animation?
I wonder why something so trivial as a font change caused this... I've had font changes cause bootloops but never a bricked device.
Sent from my Nexus 7 using XDA Premium HD app
neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
You aren't alone.
That app is made by the ROM Toolbox dev, lotsa complaining in the reviews about it bricking. You did connect it to your PC via USB and tried pushing the needed bits and starting from scratch didn't you? I'd even try one of the toolkits available for rooting and recovery.
After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
I'm glad I was able to fix it. My computer was not able to recognize the device while I was on the fastboot screen (android laying down.) THe only other screen I ever was able to get was the bootlooping screen. By chance I realized the computer was connected to the device only if it was on the bootloop screen. When I saw that, then I was cooking with fire.
Sounds like you should install your fast boot drivers
Sent from my Galaxy Nexus
I've only just got my nexus (first tablet) had it for two weeks, decided to root mainly because I hate adverts popping up everywhere, anyway I digress. I purchased toolbox pro for my hox ages ago and even though I haven't installed it, for the last few days I've been thinking of it so cheers buddy for bringing this to my attention
Sent from my Nexus 7 using xda premium
player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
Best. Idea. Ever.
Also, with a Nexus device at least that was a shot. Many others would keel over and die for good if that sort of stuff happened.
neiander said:
After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks
Click to expand...
Click to collapse
Cool, and agreed with the above. If you can see stuff on the screen, it's technically not bricked.
Bricked an N7 once, it was stuck in APX mode, the lowest recovery mode for tegra chips I believe.
At the time there was no way recovering from it using NVFlash, maybe there is now though.
Mind telling us how you got yours back to life? Just curious
Cheers
all nowellel
Was really luck. I was working on trying to get the computer to sees the device. Trying to load drivers. Anything I could do. The computer kept saying no adb device plugged in. Finally after deleting drivers and reloading drivers, I plugged in the device while it was bootlooping and heard the correct "connected" sound and saw the device in device manager. Then with toolbox, was finally able to reboot into recovery and wipe and reinstall rom. Didn't lose anything in the process.
Oh, the thing that was really the biggest mind blower was that there were 2 screens I could get to, bootlooping screen and what appeared to be the correct fadtboot screen, the computer would not recognize the device when I was on the fastboot screen. That was why I thought I was SOL.
player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
What is this NVedit tool? I cant seem to find that anywhere. I'm working on my buddy's N7 32GB Wifi, he tried to revert to stock from having CWR and CM10.1 using the Nexus Root Toolkit and now there is that problem happening you mentioned, backlight wont light up and computer doesnt recognize the device and I cant get into the bootloader either. Already checked the Screen itself and it works (disassemble and connected to my N7) and the battery has power, just no luck.