I read in another thread that deleting Bricked Kernel using Internalz Pro breaks WiFi. When I upgrade from Bricked ROM to another CM9 ROM, WiFi cannot be activated by the default kernel or Bricked Kernel. Could this be the reason why?
Also, Bricked Kernel has given me the screen of death + infinite battery drain (even when the device is off, the battery is drained until the device cannot even boot by holding the power button + the center button) since version 0.4. Any updates on a fix and Bricked ROM v5?
Thanks
Related
I am facing the problem of Ph.booting on my galaxy ace. Previously I have rooted my ph.wid cynogenmod 7.2 but den after 10 days I hav again loaded with official rom 2.3.4 & then updated via KIES to 2.3.6 …
after all this I have got one problem on my ph. is that my phone is no longer getting ON after switching OFF. The only way I can make my ph. ON is that I need to connect charger then by pressing the power Key ph. will be turned ON.
I have tried above all options including hard reset (clock recovery mode) still having the issue.
can any1 guide me on this?
Thank in advance.!!!
Hi guys,
recently i had a problem with my phone whenever i change my battery the date show as 1 jan 2000 and i had to rectify it manually..I thought cause i was on a custom rom ..so i flashed philz safe kernel (latest 2.99) and JB GT-N7000XXLSC_N7000OXALSC_N7000XXLSC rom...
everything was ok until...i replaced my battery again as i use two batteries on the go and then my fone was stuck again on the first boot samsung image...when i tried the up+home+power keys it went to the original safe recovery android rather than philz ... it looks like everytime i replace battery this is going to happen again...any one had same issue ...i was reading the posts on this forum and someone had similiar issue with battery and was suggested it is a fault on the fone itself....
any suggestions are welcomed ..and thx in advance
How did you flash the xxlsc rom?
nokiamodeln91 said:
How did you flash the xxlsc rom?
Click to expand...
Click to collapse
Hi thx for reply...i used oden ...pressed the down+power +home then it went to download mode then oden pc connected thru cable...
When you installed the new rom, philz recovery was replaced by the stock recovery. And JB leak has issues of getting bootloops if not shut down properly. So when you power off the phone wait till the last haptic feedback and then change the battery. Still not 100 % but will save some bootloops
yeah although after i installed jb i reflashed again philz...but i will keep an eye on this ..as i suspect could be hardware issue ...usually it should not lose the time and date once you replace battery ...
its normal on that rom I think
since i bought my gnote even on ICS when the battery run out and get to 0% the phone perform unclean shutdown ( screen brightness changes frequently , touch malfunction and then the screen goes black ) but no boot loop on ics after upgrading to official android 4.1.2 jplsb via odin including the new bootloader the same happen when the battery run out but it is followed by a bootloop
this only happen when i continue using my phone at 1% then the battery run out while the screen still on.
if the phone was left on the table it will safely shutdown
( that annoying problem can only be solved by wiping and reflashing the rom )
my question is :
is there any hardware problem with my phone ?
is there any step i need to do before flashing again to avoid this problem?
my rom:
stock JB 4.1.,2 jplsb no root
sorry for my bad english
Instead of flashing rom again and again and wiping data why no you just connect your phone to charger when it reaches 5% that should be much more easier
Sent from my GT-N7000 using Tapatalk 2
I know that but i want to know if there is a solution
terminator_5505 said:
I know that but i want to know if there is a solution
Click to expand...
Click to collapse
No, not really. Because there is no problem with the device but more with your handling. Forcing a device to brute-force-shutdown will always result in an "unclean" condition.
And with JB you get an extra condition with boot loop.
So you should work on your problem and follow the advice - charge.
HI,
I'm working on a friend's soft bricked W8. (I'd gotten it soft bricked bout 2 weeks back but that's a different story) I've been flashing a stock rom through flash tools, rooting and flashing cm 7.2 just to restart it and find it soft-bricked all over again.
This latest time, i flashed the stock rom n rooted it. i wanted to flash this ice cream bread rom i found in the forums which said i needed an 'nAa-13' kernel for it to work. but on flashing it through flashtools and restarting the phone, it showed an nAa logo and then shut down. i think the phone is hard bricked cos it doesnt even light up any led on connecting it to the PC.
any solutions??
A few months ago I decided that I'd root my n7000 as it was a backup phone. It didn't work and now I need it.
Because I'm an idiot, I don't know what ROM I used, what my kernel was or anything very useful. I know I used Odin.
So. My phone when I turn it on gives me the n7000 splash screen with a big yellow warning triangle then turns off.
I can still get into the custom boot menu with the power button, home button and volume switch.
Can anyone offer suggestions as to how to fix (and ideally root) the phone?
I don't think I still have the original USB cable, but have one for a galaxy S4. Will that be an issue and could it have caused the initial brickage?
I know I should have made a note of the kernel, I'm aware I made a mess. But please be charitable.
Cable of s4 should ideally work. Download a stock firmware like xxlta or any recent 4.1.2 ROM from samfirmware.com and flash it using Odin and phone in download mode.