Related
Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the stunner ics 4.5 beta showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Try taking out the battery for a few minutes, put it back again and try entering download mode again.
What's sky ics rom?
Sent from my GT-N7000 using Tapatalk
hey thanks for the reply, i've tried that already as well. no download mode working here.
itsjiffybruh said:
Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the sky ics showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Click to expand...
Click to collapse
hmmm try to pull down battery, put it back again, try to turn on download mode, do this several times if it wont help, try to charge phone and do same. goodluck
sorry, i meant stunner ics. got confused with sky ics cuz i just put that into my friends skyrocket.
You didnt follow the instructions ti install the rom so you now have a brick
Try pluggingn it top the pc , if you hear some noises on the pc then your noté is alive
Sent from my GT-N7000 using xda premium
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
thor2001 said:
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
Click to expand...
Click to collapse
Well, i was in CWM and then installed the rom then pressed restart phone on CWM menu. Went downstairs and when I came back it didn't turn on.
if it doesn't turn on at all is it a hard brick?
I ordered a usb jig from amazon for $7.00 and it will arrive tomorrow, I heard the usb jig only works on soft bricked phones though and since mines won't even turn on will there be any chance at all of it working?
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
itsjiffybruh said:
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
Click to expand...
Click to collapse
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
.Hell. said:
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
Click to expand...
Click to collapse
Ill definitely keep you guys updated. My usb jig isn't scheduled to arrive until monday so i might just try to go to the att store today and try to get a replacement.
siuming720 said:
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
how would they be able to test it if it doesn't even turn on?
hi try this not my work dont now if it works
Default Bricked Galaxy Note N7000 or Incorrect ROM Flash Easy Fix
Ok simple you won't see nothing on the screen because the bootloader is wrong.....
Just put the battery in then do following.
1. hold vol down+home+power for 15 seconds...
2. release then press volume up...
Note: Don't worry about seeing anything on the screen or any keys light
it will be blank this is because bootloader is incorrect
3. open odin you should see comxx in listed flash the original bootloader back
into phone this will/should resume visual display.
I have attached necessary files to resume
Load File in PDA NOT BOOTLOODER
4. Wait 10 seconds.. Remove Battery Then Boot Back into Bootloader following steps 1&2
5. finally flash Stock Rom to resume the whole phone to original state.
Hope That Helps......see hear for post http://forum.xda-developers.com/showthread.php?p=23052721#post23052721
Sent from my GT-N7000 using Tapatalk
thanks for the help. i read that on another post and already tried it. unfortunately its a no go.
Just came back from att center and they said that they couldn't replace it for me on the spot because they don't have the phone in stock since its a newer phone. I gotta call the number they gave me now.
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
itsjiffybruh said:
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
Click to expand...
Click to collapse
First of all I think It wouldnt have raised the binary counter and give triangle because you didnt use Odin to flash (Am I right?).
Second thing Thought it had given you a triangle since your phone is dead.
So they cant find that you flashed a custom kernel or the binary.
itsjiffybruh said:
how would they be able to test it if it doesn't even turn on?
Click to expand...
Click to collapse
Oh.. I didn't see you can't enter to cwm
Sent from my GT-N7000 using xda premium
Hello! I have an unrooted N7 that is stuck with 4.1.1. I regularly get a notification advising me of an update & I run it through the process only to be discouraged to find I'm still stuck with 4.1.1.
Can anyone help? I don't want to root & do a bunch of crazy stuff to get the update. Is there a good fix without rooting?
FYI, I found a "fix" that required turning off WiFi, clearing the some of the systems cache, turning the WiFi back on & searching for an update. No dice...
Sent from my Nexus 7 using xda app-developers app
If you have nothing to lose your best and easiest fix would most likely be to perform a factory reset.
Cheers
Sent from my Nexus 7 using XDA Premium HD app
My N7 stuck at stock 4.1.2(JZo54K), I force clean Google Service Framework and checked update. N7 found 4.2 and downloaded 80.6mb file then restart and install. After install N7 still show 4.1.2. pleas help me.
clintjames77 said:
Hello! I have an unrooted N7 that is stuck with 4.1.1. I regularly get a notification advising me of an update & I run it through the process only to be discouraged to find I'm still stuck with 4.1.1.
Can anyone help? I don't want to root & do a bunch of crazy stuff to get the update. Is there a good fix without rooting?
FYI, I found a "fix" that required turning off WiFi, clearing the some of the systems cache, turning the WiFi back on & searching for an update. No dice...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Try applying the update. When your tablet reboots and you see the Android on your screen, hold down the power button then, while holding it down, press volume up. That'll put the stock recovery in verbose mode. When it errors out, post what the text says here.
Similar thing here.
Brand new 32gb Nexus 7, finds the 4.2 update but half way through I get a Android with a red triangle/exclamation mark which then reboots back to 4.1.2
Be happy your stuck on jelly bean 4.1.x!
Sent from my NOOK using xda app-developers app
SimonCraddock said:
Similar thing here.
Brand new 32gb Nexus 7, finds the 4.2 update but half way through I get a Android with a red triangle/exclamation mark which then reboots back to 4.1.2
Click to expand...
Click to collapse
Tried half a dozen times then did a manual forced update using this guide, easy to follow and worked first time.
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
3dwarehouse said:
Be happy your stuck on jelly bean 4.1.x!
Sent from my NOOK using xda app-developers app
Click to expand...
Click to collapse
Yes, I wanted to say this. stay on 4.1.1 or 4.1.2,.... 4.2.x is a piece of crap. Much slower, not the same device at all.
Thanks for advice, then I tried not to update to 4.2 and be happy at stucked 4.1.2
finger crossed and wait for next stable version instead.
dopodMyanmar said:
Thanks for advice, then I tried not to update to 4.2 and be happy at stucked 4.1.2
finger crossed and wait for next stable version instead.
Click to expand...
Click to collapse
4.2.1 is pretty stable, stability is not the problem, but initially it broke a lot of apps compatibility (ok, this will be solved in time), but no matter what I do I have feeling it is slower, and it stutters. I never had this with 4.1.1 or 4.1.2. And I was so happy with my Nexus until 4.2 Anyways, I had 4.2 on my original Nexus, then it died and I sent for repairs, now I have new motherboard (so it counts as different device) and factory-installed 4.2 and it is the same. Even sometimes when playing a game it just stops for a split second... Trust me, new notifications and multi user (if you're not using it) is not worth the smoothness of 4.1.1
Cheers,
D.
dalanik said:
4.2.1 is pretty stable, stability is not the problem, but initially it broke a lot of apps compatibility (ok, this will be solved in time), but no matter what I do I have feeling it is slower, and it stutters. I never had this with 4.1.1 or 4.1.2. And I was so happy with my Nexus until 4.2 Anyways, I had 4.2 on my original Nexus, then it died and I sent for repairs, now I have new motherboard (so it counts as different device) and factory-installed 4.2 and it is the same. Even sometimes when playing a game it just stops for a split second... Trust me, new notifications and multi user (if you're not using it) is not worth the smoothness of 4.1.1
Cheers,
D.
Click to expand...
Click to collapse
Thanks for reply, I'm curious to know as why my N7 stuck at 4.1.2, there may be reason as I tried several times update (reboot and installed, stuck at 4.1.2) no matter how I tried) but I'm peace in mind as 4.1.2 stability.
First of all, recently im seldom visit n7000 forum since I has upgraded to n7100. Now my n7000 using by my wife.
Last week malaysia jelly bean firmware has been out. All my friends and colleagues are upgrade thru kies.
Unfortunately something happened. 2 of my colleagues called me for sos at the same day. ( the 2nd day after upgraded). Both told me stucked at note logo. They both passed the devices for me and check whats the problem.
1st devices.
- completely stock and ugraded to official jelly bean firmware thru kies.
- failed to boot into recovery mode. Download mode ok.
- use odin flash stock ginger rom but failed at nand write start.
- sent to ssc and get mobo free replacement within 3 hours. ( under warranty.
2nd devices.
- completely stock and ugraded to official jelly bean firmware thru kies.
- totally no respond, unable to boot in any mode even using what kind of method, pull out battery and using spare battery.
-sent to ssc, get replied from ssc within 1 hour and need replace mobo with all cost rm740.50.
Both of my frends told that they did NOTHING. But the devices automatically get turn off and another keep restart and stucked.
As my knowledge, this syndrome can be consider as sds, which great different as n7000 brick bug.
Im really wonder why this will happen. Is this related to jelly bean firmware which caused the sds occured?
Sent from my GT-N7100 using xda premium
Brought to you by the world's largest Android phone manufacturer, Samsung.
Im afraid what happen to both phone is what we called 'bootloop bug' on JB.. Stuck on N7000 logo and not going to Samsung animation.... happen when you pull out the bettery without properly power off the phone or when you make a force Reboot.. Its sucks when happened to average user, my phone also infected by bootloop bug...solved by flashing Philz kernel, Speedmod kernel or TWRP kernel by Ficeto...
Sent from my GT-N7000 using Tapatalk HD
zai89 said:
Im afraid what happen to both phone is what we called 'bootloop bug' on JB.. Stuck on N7000 logo and not going to Samsung animation.... happen when you pull out the bettery without properly power off the phone or when you make a force Reboot.. Its sucks when happened to average user, my phone also infected by bootloop bug...solved by flashing Philz kernel, Speedmod kernel or TWRP kernel by Ficeto...
Sent from my GT-N7000 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reply. I know about the bootloop bug. My n7000 previously also having the same bootloop issue before fixed method out. But now the case was different. Is refuse to boot in recovery mode. ( my both fren completely in stock recovery). And one of the affected devices was totally unable to manually boot into any mode..no download mode and no recovery mode.
And both devices confirmed by ssc was need to replace mobo.
Worst to worst ssc only give 1month warranty for the new mobo replacement.
Sent from my GT-N7100 using xda premium
Well my best advice that root your phone and change the kernel to a safe one like philz if you are using jb.
Sent from my GT-N7000 using xda premium
Just a question what's the RM? Thanks.
Sent from my GT-N7000 using xda premium
TheNoticer said:
Just a question what's the RM? Thanks.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Ringgit Malaysia...Malaysian currency
I recently upgraded to JB using PC Odin and while fiddling around, got locked at boot screen. It no longer went to recovery mode but luckily was able to boot to download mode and I flashed Philz's kernel using PC Odin. Got phone working but with yellow triangle. Chainfire's remove triangle did not run in JB. So switched back to GB, removed triangle and back to JB with Philz's kernel ready in sd card to flash ASAP. So far so good.
i have a i9505 S4 that i rooted and flashed with 4.3.
it worked fine for 2 days.
now it only turns on the SAMSUNG logo comes on and then it vibrates and turns off then back on again.
it keeps on doing this for ever.
with pressing V.d Home & P i go to down lode mod. that's all i can do
please help.
Well, your first step should probably be to post in the correct forum rather than shotgunning the same post in multiple forums, none of which are for your device.
Sent from my SCH-I545 using Tapatalk 4 Beta
Moved to correct section's Q&A
aassami said:
i have a i9505 S4 that i rooted and flashed with 4.3.
it worked fine for 2 days.
now it only turns on the SAMSUNG logo comes on and then it vibrates and turns off then back on again.
it keeps on doing this for ever.
with pressing V.d Home & P i go to down lode mod. that's all i can do
please help.
Click to expand...
Click to collapse
Hi,
Look HERE
Flash stock firmware for your phone.
[Q] [ROM] KOT49H【4.4.2】GE 01-09-2014 (at&t gs4) By Danvdh Battery Issues
Phone reboots when powered off while plugged into charging cable. Also, takes super long time to charge and battery drains a little quicker. Any help would be appreciated, as I am not able to post to the Rom thread direct (This is my 2nd post ever, says I need 10 posts before I can post direct). Anyone??
xjimmy said:
Phone reboots when powered off while plugged into charging cable. Also, takes super long time to charge and battery drains a little quicker. Any help would be appreciated, as I am not able to post to the Rom thread direct (This is my 2nd post ever, says I need 10 posts before I can post direct). Anyone??
Click to expand...
Click to collapse
Did you try to reflash the rom ? Have others had your same issues ? if not maybe you got a back download or something keeping your phone awake
hednik said:
Did you try to reflash the rom ? Have others had your same issues ? if not maybe you got a back download or something keeping your phone awake
Click to expand...
Click to collapse
I did reflash, factory reset, let it settle for 5 minutes. Didn't install anything, just powered off while plugged in and it still does it. What do you mean back download? If you meant bad download, I checked md5. I've read through so many posts and found a few people with battery issues similar, but they weren't answered. I have twrp, wanted to try cwm, but rom manager doesn't seem to be able to flash over twrp.
Never, ever use ROM manager
Sent from my GT-I9505G using xda app-developers app