Develop Bugs

a very strange hard brick

Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks

Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse

biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250

I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..

owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705

TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..

owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )

[Q] Stuck in recovery mode; no buttons working

I have a Google Galaxy Nexus and was using it last night (8/11)--it was a bit slow, as it has been for a few weeks, so I shut it down and hope restarting may help. When I started it back up, it was stuck on the "Google" word for about an hour and then I suppose lost power. I was not near a computer to plug it in.
When I got home, I plugged it into my pc to charge, then read online to hold down Power + Up + Down, which I did. I got to the Recover console with the "start" and little Android guy and the white arrows. However, no matter what I press (power, up, down) nothing happens. I cannot get past this screen. Also, my pc was trying to find drivers for it and couldn't. What should I do? And is there a way to preserve anything on the phone? I have not modified the phone in any way (rooted or whatnot).

I think you cannot move between options because the bootloader is locked. Can't say 100% that's the cause of it though.

Thank you for replying. If that is the case, how do I fix that?
And after it ran out of power, I charged it again and tried starting it normally and it started. So I have no idea what is going on. However Im now afraid to restart it in fear it will be stuck on the logo again. It still runs a bit slow.
So I guess I have 2 questions:
1) If I have to load it into recovery again and no buttons work, how do I fix that?
2) Since it did start again, but runs slow, what could be going on? Any tests I can run?
Thanks!

[Q] SM-T700 Froze, Powered off - Soft bricked?

Hey guys,
Appreciate it if you could spare me some advice on how to proceed.
So I was watching a twitch stream and all of the sudden tablet froze, and the audio froze as well causing a large super high pitch noise, I hard-reset the tablet but instead of resetting it just turned off, I started to browse the forums and found that a combination of (POWER + VOL UP & DOWN + HOME) would reset the tablet,now what this did for me is turn the tablet on but it was stuck in SD CARD Mode, back again to the forums, read that letting it discharge fully and then it will be able to be charged and turned on, that worked tablet was back doing some various tasks no video again and then boom freezes again same symptoms except this time I couldn't get it to go to SD CARD Mode its very finicky after trying at various times in the day I finally got it to work, same process except this time as soon as it turned on I went into recovery factory reset it to stock, worked a bit longer this time only installed chrome, and it froze again (don't think it was chrome) , rinse repeat and I flashed the latest firmware with ODIN worked fine, I've gotten to the home screen ran through the "factory new" set up and it turned off of me again.
I plugged it in let it charge, came up with battery icon 5% 10% ect, then I left it for a while, I came back and I cant even get it to show the battery percentage(tap power) let alone turn on.
I'm fairly sure that eventually I can get it turn back on but from there I don't know what to do.
TL;DR - Tablet Froze, Hard Reset, Froze again - Rinse Repeat, ODIN to latest STOCK firmware, tablet worked for 5 min before turning off again (plugged in), present situation
Any ideas as what to be causing the freezing and how I could remedy it?
Also sometimes when it froze it turned itself off without me hard resetting it.
Thanks its been driving me insane,
Please do not hesitate to ask me to clarify or provide more information so I can help you help me.

Maybe youve got the loose battery connector problem?

ashyx said:
Maybe youve got the loose battery connector problem?
Click to expand...
Click to collapse
What would you suggest I do, submit it to warranty ? Will they disregard the fact that knox has been tripped if its a hardware issue ?

sunb3ar said:
What would you suggest I do, submit it to warranty ? Will they disregard the fact that knox has been tripped if its a hardware issue ?
Click to expand...
Click to collapse
I had the loose battery connector problem, but the symptoms do not sound the same as mine. I could get mine to boot up, but the screen would flicker and a few white lines would appear before it would reboot itself. I actually started a ticket with Samsung and got the packaging label but, upon further reading, realized that I was pretty much SOL after tripping knox, and didn't want to risk the chance of getting charged for just sending it in. If it is indeed the loose battery connector, you should be able to remove the back cover yourself and fiddle with it. Ultimately, mine needed re-soldering, and I was able to find a local electronic repair shop to do it for me for cheap.
Good luck!

UPDATE: I've managed to get into SDCARD MODE yet again, except discharging seems to get out of it, but once I plug it back in it doesn't come up charging it just black screen, until I hold some buttons and arrive back at sdcard mode. Good times.
Trying various things to get it to boot..
EDIT: Appreciate the insight Squez, I want to exhaust all the other options before opening it myself, if Knox didn't void the warranty to some degree, opening it up should put the final nail in the coffin.
EDIT2: Good news, sort of, tablet isn't dead! after numerous attempts with charge SDCARD mode, discharge, It finally start to charge properly and I managed to get it to boot, worked for a few hours then I left it to charge, and went to sleep, woke up and wont turn on again, but I am in SDCARD Mode again but need wait for it to discharge from presumably 100% ....

[What do you mean Sd card mode? DOWNLOAD mode?
Also no need to let the battery drain.
Just press VOLUME DOWN(not volume up) and POWER together then hold until it restarts.
This is a hard reset and will ALWAYS work unless the device is hard bricked. It is the equivalent of a battery pull.
I continually see here and there incorrect information regarding key combinations, even in so called guides, this forum is even guilty!
Here is what works on the 10.5lte, as far as I'm aware its the same for all versions, indeed pretty much any Samsung device.
HARD RESET:
VOLUME DOWN - POWER.
Hold until the device restarts.
DOWNLOAD MODE:
HOME - VOLUME DOWN - POWER.
Hold until the device boots.
RECOVERY MODE:
HOME - VOLUME UP - POWER.
Hold until the device boots.

ashyx said:
[What do you mean Sd card mode? DOWNLOAD mode?
Also no need to let the battery drain.
Just press VOLUME DOWN(not volume up) and POWER together then hold until it restarts.
This is a hard reset and will ALWAYS work unless the device is hard bricked. It is the equivalent of a battery pull.
I continually see here and there incorrect information regarding key combinations, even in so called guides, this forum is even guilty!
Here is what works on the 10.5lte, as far as I'm aware its the same for all versions, indeed pretty much any Samsung device.
HARD RESET:
VOLUME DOWN - POWER.
Hold until the device restarts.
DOWNLOAD MODE:
HOME - VOLUME DOWN - POWER.
Hold until the device boots.
RECOVERY MODE:
HOME - VOLUME UP - POWER.
Hold until the device boots.
Click to expand...
Click to collapse
I should of posted a photo earlier but here is one I found on google of same screen: (check attachments)
Except UP KEY and DOWN KEY don't do anything, its just this screen, if you attempt to hard reset ect, it will just reload this screen, hence the discharge, then plug it back in and hope it begins to charge "battery icon appears". I have gotten it to boot like this a few times.

sunb3ar said:
I should of posted a photo earlier but here is one I found on google of same screen: (check attachments)
Except UP KEY and DOWN KEY don't do anything, its just this screen, if you attempt to hard reset ect, it will just reload this screen, hence the discharge, then plug it back in and hope it begins to charge "battery icon appears". I have gotten it to boot like this a few times.
Click to expand...
Click to collapse
Wtf
How did you get to that mode? Looks like its trying to flash from the sd card. Ive seen safe mode but not that.
see here: http://forum.gsmhosting.com/vbb/10127092-post62.html

ashyx said:
Wtf
How did you get to that mode? Looks like its trying to flash from the sd card. Ive seen safe mode but not that.
see here: #
Click to expand...
Click to collapse
Yeah its strange as.
I'll have a look at that, thanks.
EDIT: It just finished discharging and now I am on the battery screen.. Usually once it charges here I can get it to boot, what I'm curious is what on earth keeps causing it to freeze up, because in download mode and twrp (gone since i flashed stock via odin) it wouldn't freeze at all, only have issues with it once its booted or charging. I installed a logcat earlier hopefully that should shed some light on the situation,
EDIT2: Well another very interesting thing, the official Samsung charger wont charge it, only works if I plug it into pc or use a non-official charger, strange thing is nothing is wrong with the samsung charger or cable since I can charge my phone fully from it. These have to be some of the strangest symptoms.
EDIT3: Only works through USB port on PC for now, non official charger comes with red X on battery once booted. I assume you can work around this once rooted but that's for another time..
EDIT4: Charge through pc to around 2-3%, boot device, plug into official samsung wall charger and it begins to charge properly.
EDIT5: Hooray back to step one, trying get into SDCARD Mode, same thing happened left it overnight and it wont turn on or charge anymore.

ashyx said:
Wtf
How did you get to that mode? Looks like its trying to flash from the sd card. Ive seen safe mode but not that.
Click to expand...
Click to collapse
i am pretty sure the HOME - VOLUME DOWN - POWER. puts the 10.5 into the sdcard mode.
my tablet is doing very similar to sunb3ar findings.
have had it come back to me once from sdcardmode.. (let if go flat and starting charging then it would start via normal buttons)
it crashed not long after that. it got stuck in sdcard mode again, but this time none of the drain flat, put on charge has worked.. just blank..
fyi- we try to put it in RECOVERY MODE, but it does not work when in this crashed / sdcard mode state
i even disconnected the battery and then plugged back on charge.. nothing..
today i tested the battery volts, 2.8v , for a 3.8v i thought that was ok. i attached my RC lipo multi charger set to 1amp 3.7volt charge, direct to the - + on the battery- got it up to 3.5v, plugged back in, put the charger on- the sdcard mode (most life it has shown in a week).
still not coming up with 'battery' display to say its 'turn-off and being charged'. just the sdcardmode might disappear and return..
i am currently adding mode charge to battery... will try to HARD RESET next.. since i have not tried that combo yet..
HARD RESET:
VOLUME DOWN - POWER.
Hold until the device restarts.
edit: i took it off 'direct' charge, battery at 3.7volts.. then plugged in normal charger, i got a 'battery symbol' but it had the lightening bolt, not a %.. so i unplugged and reconnected to my direct charge to give the battery more volts. i am surprised that the unit seems to think a battery with 3.8volt as it specs seems to not be like with volts not much lower than 3.8.. could be time for a new battery if we can get this thing to restart

Bricked Nexus 7 [Solution?]

Hi folks,
first post but an important one. Important enough to join and hopefully get some answers.
My LTE Nexus 7 (running 5.0.2) bricked last night. It got stuck on the Google screen and I had no way to unlock the bootloader to flash a different version of the OS. SO this morning thinking I had nothing to lose I removed the back panel with the intention of tearing the thing down. Then it hit me. The common theory seems to be that it's the way the bootloader is not mounting the storage. So as the device never completely powers off what would happen if I cut the power manually. Hopefully a hard reset. So I detached the battery cable from the board and left it alone for a few moments. After popping the kettle on I returned, replaced the cable and tried turning on my Nexus. Lo and behold it works!
I have an unbricked device.
Which is great an all, but I have the proper tools and knowhow to delve into the hardware. More importantly though I'm trying to find out why that might have worked.
Any thoughts?
Has anyone else tried this as a solution to unbrick their device? Did it work?

There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button

Gorgtech said:
There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button
Click to expand...
Click to collapse
But surely that's not the same as disconnecting the battery?
Trev

It´s not the same but once you´re in a "boot loop", you have no chance of eg. entering the recovery. This is why you need a way to shut down the device first.
But in case even this "forced shut down" doesn´t help and you´re out of warranty, maybe it´s not the worst idea to open the device anyway since you´ve got nothing else to lose

Sony Xperia Z1 compact - Hard Brick?

Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver

olik79 said:
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
Click to expand...
Click to collapse
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.

levone1 said:
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
Click to expand...
Click to collapse
Thank you SO much! I wasn't really able to boot using power and volume up, BUT after your encouraging words and the idea that I might just be using wrong keys, I researched some more and found out about this little red button within the sim card slot! It allowed me to reboot, get into fastboot, install recovery and cyanogenmod afterwards! I'm happy again