Database Users

brick boot loader to black screen: no simple solution, simple prevention

Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
- update 31/12/2010 -
Cause
corrupted boot loader , bad sbl.bin flashing
Prevention:
do not flash roms/addons/fixes with sbl.bin
if you must flash sbl.bin, do it while you are sure that your USB configuration is perfect, and do it as less as possible.
Solution (for those who already bricked to black)
you're not gonna like it
find riffbox jtag....

marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Happened to me too. I was tinkering with the Armani source to hopefully find something of use for Axura, and I bricked it. Same things happened to me. I called att and got a new one.

marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Did you try removing battery and putting it back and then opening ODIN, holding the volume up/down and inserting the usb to bring it on the download mode. I guess I might have experience almost similar issue with one of the rom. I almost freaked out. Phone wont show if its charging. It wont mount on the pc. But tried all the possible method available several times including adb shell command. And finally I did hear the magical sound from window when the usb is connected and finally it did work.
Also try the adb method if it doesn't go into download mode using volume button combo.
Sent from my SAMSUNG-SGH-I897 using XDA App

Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App

Happened to me the first time I ran the OTA update from ATT. Paused the update, and when I resumed it - the phone though I finished downloading the JH7 update and tried to apply it.
It failed to apply and when it went to restart, it never powered on. No download mode, recovery, USB power, Odin, nothing. It was completely dead.
I got it replaced at the AT&T store.

If sbl.bin was removed or corrupted you should call the warranty center. Tell them ota update bricked your phone. Lol good luck
sent from my cappy running di11igaf's rom v2.5 at 1280mhz!!

I think it is just bad luck. I was once being careless and had the battery fall out of my phone while flashing, it interrupted the flash and I was still able to get in download mode to Odin it. Needless to say, I'll never flash again without the back cover on

bulletproof1013 said:
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes i'ts probably a bad sbl.bin, but I didn't remove it I flashed a new one, most of the rom's do the same

yeah sounds like it...sry for your luck.but seems like its toast then. keep us posted

But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.

silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
There is a a way. Whenever you need to flash to stock you must use following stock. http://forum.xda-developers.com/showthread.php?t=818439
This is same as normal stock posted by DG except that it includes sbl.bin that we (1008) need. I use it everytime and 3 button combos for Download, Recovery work great.

silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
it seems like this is not my case
I'm still looking for other people who had my case, and recovered (even with the JTAG riff box) or at least find someone who know's what we shouldn't do, so we don't break our phones.
so whats batch 1008?

This happened to me last night. I was trying to flash the Darky port via CWM and during the flash it became unresponsive. I had to pull the battery. This caused 2 different things. Sometimes it would be a never ending loop of boot screens and then others it would just go into recovery where it wouldn't let me do anything.
From here luckily I was able to access download mode by using the "adb reboot download" command. So I then got into dl mode and tried to flash stock (not the 3 button fixed one) and it froze on FACTORYFS (or whatever it is). I had no choice but to pull the battery. Now it won't boot at all. So my assumption is it wiped the bootloader. I'm not 100% sure but I feel that the reason it stopped where it did was because I didn't run odin as admin on my Win7 pc. I read in another thread that someone had the same problem when they didn't do that either.
If you are in a pitch black room and you press power you can see your screen illuminate, it's just very dim.
I have batch 1008 if it makes any difference to anyone.
Either way I'm heading to the device support center in a half hour or so to try to get a replacement. I originally was going to make or order a jig but people are saying it only works if the bootloader is intact. I originally had hopes because one person claimed that they recovered a completely dead phone with it, but upon further reading all others could not. It seems like his phone may not have been completely bricked.
Update:
Just got back from the at&t device support center. They gave me a new phone without any hassle. They asked what was wrong with my phone and I told them that I was trying to update it and now it won't turn on. The guy tried a few combinations of button presses and tried hooking it up to a jig-like device. Nothing worked so he just gave me a refurbished phones. No questions asked. As I was walking out he said a few people have had the same issue so it's not a big deal.
Either way I thought this would help to realize that there is likely no way to get the phone to boot unless you have a jtag handy.

I don't feel safe to flash rom via CWM.
If you really want to do that, delete the bootloader inside the .zip

So i think i killed mine too
so i get black screen, two button combo gives me SEC S5PC110 Test B/d
I opened odin but nothing Is this toast?

I had this exact problem over thanksgiving weekend. My phone was was was hard bricked I was getting the "phone + computer" it took some effort to get it into download but I got it there and when I was recovering with odin the connection got lost the screen went blue and then nothing. It was dead totally unresponsive no charging or boot screen nothing but once I got a black screen with redlines. After a lot of attempts to revive it I gave up called ATT warranty for a replacement. Luckily I opted for the slow mail service and kept reading. Yesterday I saw the above post and now I can say "yes even now your phone is not bricked even though it does NOTHING"
step 1) first thing I did was charge the battery with my replacement phone as the bricked phone was no longer able to charge the battery
step 2) open odin1 click and hooked up the usb to the phone and computer no battery
step 3) inserted the battery holding only volume up+down
step 4) "BOOM" download mode and a happy dance
I posted this in the"read before flashing" thread there are other people who have recovered from this and now I think that the extra trick to this is getting a 100% battery you need this to flash, and state the phone is in now wont charge a battery.
hope this sound encouraging

silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App

RKight said:
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.

norcal einstein said:
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
Click to expand...
Click to collapse
Yeah it's either that or just a misconception spread by the community. Both my old captivate and replacement were 1008. I have been able to get into recovery via the power+volume combination. I was also able to get into dl mode using the vol+insert usb combination.
It's possible I just got lucky on both but who knows.

I, and many others have a 1008 that don't go into download or recovery via the button combos without fixing sbl.bin.
Sent from my SAMSUNG-SGH-I897 using XDA App

I think I bricked my device any help to confirm this would be really nice

I don't know what I did when I was trying to install the orginal rom but, now my phone just shows the mytouch 4g picture, then it goes black and the same picture appears again, while the phone is vibrating. I am able to get into hboot but none of the options work. I upgraded the firmware with clockwork and unrooted the device. Is there a way to unbrick, or is the device just a brick?
Any help I would be thankful toward,
Luke

This may seem trivial, but it was not mentioned and therefore I am asking. Can you get into recovery?
Sent from my HTC Glacier using XDA App

No I can't get into recovery its locks up and stays on t mobile mytouch 4g screen. That is after i select recovery.

Good news is its not bricked. You're just hitting a snag on boot. Have you tried fastboot or hboot?
RIP Cotton Eye Jim

When I try the fast boot method it brings up bootloader i selct it and it takes me back to the main screen, at that point I try recovery again and the device show t-mobile mytouch 4g for a second then goes black and goes back to the screen and vibrates and repeats the same thing over and over.

lukecarr said:
When I try the fast boot method it brings up bootloader i selct it and it takes me back to the main screen, at that point I try recovery again and the device show t-mobile mytouch 4g for a second then goes black and goes back to the screen and vibrates and repeats the same thing over and over.
Click to expand...
Click to collapse
You don't choose bootloader in fastboot. All commands need to be run from your machine.
Sent from my HTC Glacier using XDA App

It does not even show the device in adb. I have install the driver for hboot usb plug, but maybe I got the wrong driver. Do you have a link to download that so I can try to reinstall driver, or is the unit bricked? Or how do I fastboot with the unit not loading to android, but its on hboot screen with usb cable attached. Is there a way to do that?

Press and hold the back button while booting to get into fastboot mode. Then download the clockworkmod recovery img and flash it through fastboot. You can find more detailed instructions in the thread where you download clockworkmod. This will enable you to enter recovery and flash a new rom.

When I followed those steps, fastboot in red came up and it gave me choice of bootloader reboot reboot bootloader and powerdown, it does not load, I have tried the bootloader, it goes to the main screen.

Was being dumb needed to hit restart it boots, thank you I will be reading on clockworks. I a noob as you can tell.

I reinstalled clockworks but now I cant get the hboot up by holding the volume down and power key. Any suggestions?

Volume down+power does nothing?
RIP Cotton Eye Jim

Got it working just wasnt holding it long enough I need to be more patience lol

Lol, I had the same problem the mt4g when I first got it. Very different from the mt3g. For future reference, as long as you get fastboot to come up, or at least get adb to recognize the phone, its not bricked. I actually bricked a mt3g 1.2, and when they're dead they're DEAD. Nothing works except an led notification.
RIP Cotton Eye Jim

I'm glad you got help but this is the wrong section to be asking questions. Go to the Q&A next time.
Sent from my PC36100 using Tapatalk

Please post questions in Q&A section.

[Q] Hard Bricked Nexus 7. PLEASE HELP!

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

[Q] HELP! Stuck in Boot Loop, Locked/unrooted

Was on 4.1.2 OTA (yeah I know dumb of me, but it did it overnight), rooted with TWRP all was fine untill I decided to power cycle and got stuck in a boot loop...
Booted to twrp...tried to recover from a back up, still boot loop....Cleared dalvik and all other caches, Still bootloop....factory reset, still no change...
Last resort was to flash using RSDlite v6.1.5 to VRZ_XT907_9.8.1Q-78-1_1FF.xml ...and i'm still bootlooping!!:crying: Now I've lost root, NO Custom recovery with a locked bootloader. I can't push anything through adb cuz bootlloop interrupts windows recognizing the phone and the drivers don't properly install while in Stock Recovery (I do have the latest drivers BTW)...and only sees it as 'MOT SINGLE ADB INTERFACE' while in fastboot.
Question is, what could still be causing it to bootloop?? Anyone know?.. and is there any way to get this fixed and/or get back root and a custom recovery??
At the end of my rope here! Need some guidance....

Alright Guys and Gals I solved the issue (even though I'm not sure how! LOL)
What I did (with simplified instructions)
1. Let it bootloop till the battery ran down...
2. recharged it up to 100%
3. opened it up while still off
4. disconnected battery cable for 5 secs
5. reconnected battery cable
6. started into boot menu (hold POWER and VOL UP & VOL DOWN together) and chose recovery (VOL DOWN to highlight recovery and VOL UP to select it)
7. While in recovery Hold VOL DOWN and tap VOL UP to get the Recovery Menu
8. Chose wipe cache ( VOL buttons to highlight, Power Button to select)
9. then chose wipe data/factory reset
10. rebooted into boot menu again
11. chose Factory option
*12. Held my breath :fingers-crossed:*
AND IT BOOTED!!!:laugh:
Now just to be clear I am not even sure if it was one of these steps or the combination of all of them that got me off the Boot Loop, but I just thought I'd outline them just in case someone stumbles on the same problem I had. Also please note that all this was after I fastboot flashed the 4.1.2 (.78) firmware using RSDLite v6.1.5
Being stuck on on 4.1.2 (.78) Stock is alot better than being stuck in a Boot Loop at least, so I'm happy!
P.S: F.Y.I... I was getting stuck halfway through the boot animation (just about where the droid eye kinda thing closes up) so I could still recharge my Battery from a powered off state (why I had to let it run down to zero, as it was either that or open it up and manually disconnect the battery cable and I was feeling lazy.
Now I have another Logic Board which doesn't boot past the initial Motorola "M" Logo, and thus can't get into recovery or even charge from a powered down state (can only get into fastboot) even though I've successfully flash 4.1.1 to it TWICE!!

meaty0025 said:
Now I have another Logic Board which doesn't boot past the initial Motorola "M" Logo, and thus can't get into recovery or even charge from a powered down state (can only get into fastboot) even though I've successfully flash 4.1.1 to it TWICE!!
Click to expand...
Click to collapse
Do you know what build that logic board is... if its an older version use Matt's utility on it simply swap with your current one and have the joy of an unlocked device... first time I flashed (well almost every time I flash) 4.3 I get stuck on the boot logo and have to use Matt's utility to bring it to life again....
Sent from my XT907 using xda app-developers app

ezknives said:
Do you know what build that logic board is... if its an older version use Matt's utility on it simply swap with your current one and have the joy of an unlocked device... first time I flashed (well almost every time I flash) 4.3 I get stuck on the boot logo and have to use Matt's utility to bring it to life again....
Click to expand...
Click to collapse
That was my initial thought but, Where on the board can I find that info? and doesn't matt's utility in essence perform a fastboot flash, same as RSDlite?? Would love to have an unlocked device or at the very least a working back up board in case of unforeseen accidents, but this one has me stumped...

It won't say it on the board you'll have to install it to the housing n digitizer n get it to boot... I think you can tell by the fast boot menu but I'm not sure what to look for.... n to be honest I have never used rsd I've always used one of Matt's utilities for all my moto devices he has saved several of my phones...
Sent from my XT907 using xda app-developers app

ezknives said:
It won't say it on the board you'll have to install it to the housing n digitizer n get it to boot... I think you can tell by the fast boot menu but I'm not sure what to look for.... n to be honest I have never used rsd I've always used one of Matt's utilities for all my moto devices he has saved several of my phones...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Utility doesnt seem to work for me for some reason, it just closes when i "hit any key to continue" even flashed it with rsd using the xml from matt's ultilty... Still no go.
It should be an older board though, i bought off ebay with a broken screen just mainly so i could get the pristine back housing off of it (lol) ... and that was in february.
The guy did say he'd dropped a wrench on it breaking the screen while workin on his car, guess it was a bigger wrench than i thought and it damaged the board too :laugh:

[Q] Problem with looping Nexus 7

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