Database Users

Brick (I guess)

I just bricked my device I guess.
First off flashed:
http://forum.xda-developers.com/showthread.php?t=1162302
TouchWiz UX for 10.1
- Cleared all (factory reset)
Which was working nicely, but then I needed some extra kernel modules, so I installed:
http://forum.xda-developers.com/showthread.php?t=1175299
3.1 Galaxy Tab Wifi OC1.6
- Cleared all (factory reset)
It booted at first, but then rebooted and eventually went to black screen. Now powering up won't work.
So yes it really won't come to life out of it's own.
-------------
My first step: Hang it to a PC
Well it recognized the tab, and was asking for the APX driver, which I found over here: http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75
Which installed correctly, and is recognizing my device (for now).
Who can help me further (it is possible to backup and restore using nvflash)
-- Update 0x4 error...
NVFlash seems to be a dead end. You can't use it without sbk, which we don't have. Any more suggestions?

Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras

Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App

sassafras_ said:
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Click to expand...
Click to collapse
Been there, done that... I've flashed all through CWM recovery, always made a backup, but it doesn't go through the bootloader anymore, so I can't access the recovery, nor the download mode (for Odin flashing).
The only thing I can access at the moment is that stupid NVFlash, and since my device is I/O locked, I can't flash anything.

tmbk said:
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I will check on this. It's the only way to fully reset my device. Since it is I/O locked, it can't have harmed my bootloader or CWM recovery.
I made sure before flashing that the MD5 checksum was right (which it was). The only thing it flashed was a kernel. Well I will drain my battery and check if it is possible to boot it up after that. Else I buy a new one

Exact same thing happened to me.. ran poitee kernel over OTA update.. killed everything but nvflash + all black screen.
Cannot get it to flash w/ bootloader.. Have 2 days to RMA and I really don't want my data out there in the event this thing comes back up after the battery dies.
PS- My unit was bootloader unlocked and rooted.

Need help, please!

Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk

Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.

I also think there's a problem with your battery, it might need to be replaced.

ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk

Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.

norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?

Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app

Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped

[SOLVED] Nexus 4 not turning on after flashing latest faux kernel.

So I flashed mako-jb-kernel-028u-JWR on my nexus 4 and when I rebooted the notification light was flashing red. I booted back into TWRP and flashed mako-jb-kernel-027m-JWR to try and fix it. After I rebooted it was stuck on the boot animation with the flashing light. Whenever I started up TWRP the light would start flashing and the phone would turn off before I could reflash carbon rom. The light wouldn't flash when I was in fastboot . Now it won't even turn on, even if I plug it into power. I looked around and couldn't find anyone else with this problem. I'm assuming the battery ran out of power and I need to let it charge before I can do anything. Though last time I booted into TWRP the battery was above 90%. If someone could suggest something to do it would be great.

if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454

simms22 said:
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
Click to expand...
Click to collapse
I'm hoping I won't need to do that since I don't have a T5 screwdriver and I don't trust myself with manually charging a battery with a power supply.

I should also mention that I used this https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en about an hour before flashing the new kernel.

Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4

RASTAVIPER said:
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
The problem is that it won't even turn on. I think it ran out of battery and its refusing to charge.

Alright so I did some searching and found this post http://forum.xda-developers.com/showpost.php?p=43291951&postcount=27 I did that and my phone can actually boot up now. Also I should mention that you need to hold the buttons for EXACTLY 60 seconds or it won't work. I'll let it charge and attempt to reflash Carbon Rom after.

TWRP kept closing on me before I could reflash Carbon, so I restored to the stock rom and kernel using WugFresh's toolkit. I couldn't boot into the rom until I went into fastboot, went into stock recovery, and restarted my phone. Now I can boot up perfectly fine! Also I flashed the latest faux kernel again just to make sure it was the problem, and after flashing mako-jb-kernel-028u-JWR I got the red led again, So I'm advising everyone to stay away from that build.

[Q] Defy does not start anymore

(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.

tmcookies said:
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
Click to expand...
Click to collapse
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Click to expand...
Click to collapse
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...

tmcookies said:
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
Click to expand...
Click to collapse
Is RSD recognizing it?
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
Is RSD recognizing it?
Click to expand...
Click to collapse
Who would have thunk? RSD Lite did recognize the phone and when it started flashing, the phone showed
"SW Update
In Progress.."
So, now what? Which sfb file should i flash?
Anyway, thank you so very much!

Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?

tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Yes, root again if needed.

I saw your other post in the cm11 thread about how your phone died.
I remember reading somewhere in the forums that you should go to cm10.2 before installing the updated recovery, and then install cm11.
I'm not sure if that's 100% accurate, and I couldn't find the link (sorry).
Couldn't hurt, though, seeing as you'd just have to do a few extra ROM flashes.
Good luck!
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse

Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:

after some effort - great on CM11!
leandrolutz said:
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
Click to expand...
Click to collapse
I had a simiilar problem - somehow after a similar failed CM11 install, I pressed that "reboot" button and my mb525 was dead. I did as suggested here, Except I happened to have CM10.1 not CM10 on the SD.
However I had a lot of trouble getting a successful boot after installing update-recovery.zip, and then also after installing CM11 with the updated recovery.
Now I have a great well-running defy on CM11. I don't exactly why it succeeded when it did - just repeatedly wipe and install and wipe until it worked.
The defy really runs well on CM11 - very responsive - it is robust both in HW and SW! - maybe I'll myke it my main phone again! (before the S3 or the xperia V) - Samy just ain't interested in my S3 - the community provides the same Android version for my defy as I have on my nexus 7 2013!!!
Many thanks to all who have contributed, especially quarx -

try this http://forum.xda-developers.com/showthread.php?p=48501247

[Q] i9505 No OS

Hi guys
I had my rooted S4 (TWRP)
Every now and then it would reboot like there was no battery power left (battery history graph always showed 0% just in that very moment when my phone would reboot)
So I thought I'd re-root it and what I did first was saving all my files to my computer.
Then I went to Teamwin Recovery menu and deleted all the caches and all files and everything A FEW TIMES. (don't ask why, I don't even know)
After that I tried to flash it again with the root-OS and it did everything wonderfully fast and everything (using Odin)
Then I tried to boot but it didn't work.
I flashed the recovery tar (I think it was a tar file)
and thus the process of rooting was done as far as the tutorial went that I used
I turned my phone on and that's where I am now:
No OS (seemingly, also it was written in I think the stock recovery menu [because I tried to flash the stock files])
Phone keeps showing me the "Samsung Galaxy S4 GT-i9505"-screen and does nothing else.
Have I bricked this thing or is there a way to get it working again?
Thank you all in advance.

mistervinni said:
Hi guys
I had my rooted S4 (TWRP)
Every now and then it would reboot like there was no battery power left (battery history graph always showed 0% just in that very moment when my phone would reboot)
So I thought I'd re-root it and what I did first was saving all my files to my computer.
Then I went to Teamwin Recovery menu and deleted all the caches and all files and everything A FEW TIMES. (don't ask why, I don't even know)
After that I tried to flash it again with the root-OS and it did everything wonderfully fast and everything (using Odin)
Then I tried to boot but it didn't work.
I flashed the recovery tar (I think it was a tar file)
and thus the process of rooting was done as far as the tutorial went that I used
I turned my phone on and that's where I am now:
No OS (seemingly, also it was written in I think the stock recovery menu [because I tried to flash the stock files])
Phone keeps showing me the "Samsung Galaxy S4 GT-i9505"-screen and does nothing else.
Have I bricked this thing or is there a way to get it working again?
Thank you all in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2265477
or just flash a custom rom trough twrp.

sadly, i tried re-flashing like 10 times.
ill try it again a bit later today but im not expecting much from it

Lennyz1988 said:
http://forum.xda-developers.com/showthread.php?t=2265477
or just flash a custom rom trough twrp.
Click to expand...
Click to collapse
so i tried what you recommended and it worked.
but... it feels like something isnt right.. for example it wont activate wifi...
but seriously: thanks so far

Did you try ODIN?
Sent from my GT-I9505