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
alright my brand new kindle fire i was trying to root, the utility wasnt working on my comp so i decided to follow a guide on how to do it manually, i did the fbmode push but it never went to yellow triangle and stuck on stock boot screen, then for some reason a hearrd a buh bing! and it says usb device not recognised. help?! please this thing is brand new and my father got it for me for school. i just want it to boot baack up and i am never going to touch it through any prompt again
Kole_Ackerson said:
alright my brand new kindle fire i was trying to root, the utility wasnt working on my comp so i decided to follow a guide on how to do it manually, i did the fbmode push but it never went to yellow triangle and stuck on stock boot screen, then for some reason a hearrd a buh bing! and it says usb device not recognised. help?! please this thing is brand new and my father got it for me for school. i just want it to boot baack up and i am never going to touch it through any prompt again
Click to expand...
Click to collapse
Do you have the drivers installed?
Kole_Ackerson said:
alright my brand new kindle fire i was trying to root, the utility wasnt working on my comp so i decided to follow a guide on how to do it manually, i did the fbmode push but it never went to yellow triangle and stuck on stock boot screen, then for some reason a hearrd a buh bing! and it says usb device not recognised. help?! please this thing is brand new and my father got it for me for school. i just want it to boot baack up and i am never going to touch it through any prompt again
Click to expand...
Click to collapse
Make sure drivers are installed man if you need help pm me and I will waljbypy through it with team viewer/gtalk
Sent from my Galaxy Nexus using xda premium
Thank you guys I was all the way up till 4 this morning. Found out my USB cable is wonky so I ordered a new one, but I got it fixed with the USB pin short and got to recovery to flash the boot loader and jandycane
Sent from my Amazon Kindle Fire using xda app-developers app
How do you like Jandycane?
Sent from my Amazon Kindle Fire using Tapatalk 2
thejuki said:
How do you like Jandycane?
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Its pretty darn spectacular, I would love it better if lithium would incorporate beats audio in it. But so far no issues at all and smooth as a baby's butt
Sent from my Kindle fire 6.3 running JandyCane
*devices*
My new baby- Kindle Fire 6.3 running Jandycane
Samsung Skyrocket SGH-I727 running CM10
HTC EVO 3D running TeamGenesisRom (-*Retired*-)
HTC Status running SuperOSR/CM7 (-*Retired*-)
iPhone 3gs jail broken/unlocked(-*Retired*-)
iPhone 3g jail broken/unlocked(-*Retired*-)
I am using the latest Jandycane version and I love it also. Made a video on it on YouTube to help people understand that everything works fine. It is amazing that it is better than AOKP milestone 6. I had many problems with it that I don't have anymore. The only thing I would suggest is AOKP ROM Control. But it seems the developers are on the right track with status bar UI changes.
Sent from my Amazon Kindle Fire using Tapatalk 2
Okey so yesterday I couldn't wait anymore and wanted to update my Nexus 7 to 4.2 but couldn't.
After restarting it did initiate the update but right after it gave me a red triangle with a (!)
And now I can't see any updates anymore. I yet I'm on 4.1.2 still
Dang it..
Sent from my Nexus 7
Download the 4.2 factory images from google and flash via fastboot.
Consider yourself lucky and stay with 4.1.2
I have the same problem as well. When I first tried to get the update, the Android had a red ! And failed the update. Now, it says no update available....
I'm not sure if I should wait until a more stable version is out, however.
Sent from my Nexus 7 using xda app-developers app
Meh rootbrain is right. Jag ive been reading upp on 4.2 and i better stay on 4.1.2
Sent from my Nexus 7
It's all subjective. Some like it, while others don't. Neither opinion is the end all, be all gospel truth.
Sent from my Nexus 7 using Tapatalk 2
rootbrain said:
Consider yourself lucky and stay with 4.1.2
Click to expand...
Click to collapse
Aren't there enough 4.2 bashing threads that you feel the need to take this one off-topic?
The OP asked for help not for your opinion.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x
Any help would be appreciated...I want to have the latest update, not be stuck...
Sent from my Nexus 7 using xda app-developers app
yanksrock1000 said:
Any help would be appreciated...I want to have the latest update, not be stuck...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Have you modified, frozen, or deleted any of the stock system files? The update checks for approximately 200 files and if any aren't stock, will fail. Your best bet, as someone else said, is going to be to fastboot flashing the stock image. Be forewarned that you'd be essentially starting from scratch as it would wipe your tablet, but I'd personally find that preferable since you'd be circumventing some of the issues that are irking the most vocal of 4.2's critics.
Sent from my Nexus 7 using Tapatalk 2
I actually just purchased the tablet, and out of the box the first thing I tried to do was update, and it failed.
I'm not very knowlegable about flashing the factory image myself, but I've heard about updating using a "toolkit"? Is this easier?
Sent from my Nexus 7 using xda app-developers app
yanksrock1000 said:
I actually just purchased the tablet, and out of the box the first thing I tried to do was update, and it failed.
I'm not very knowlegable about flashing the factory image myself, but I've heard about updating using a "toolkit"? Is this easier?
Click to expand...
Click to collapse
Yup, easier. But using a command line and the android SDK/fastboot isn't all that hard... maybe your issue is just the universes way of saying you should go learn a new trick. :cyclops:
However I doubt the universe will waste any energy punishing you if you choose to go the easy route. Plus, you can always read the thorough directions for both routes and make an educated decision before you get your hands even the least bit dirty.
using Fastboot: http://forum.xda-developers.com/showthread.php?t=1907796
Wugs Windows toolkit: http://forum.xda-developers.com/showthread.php?t=1766475
najaboy said:
Have you modified, frozen, or deleted any of the stock system files? The update checks for approximately 200 files and if any aren't stock, will fail. Your best bet, as someone else said, is going to be to fastboot flashing the stock image.
Click to expand...
Click to collapse
i have the same issue, but i dont want to fastboot it, what should i do? i havent rooted or anything yet. i have a 32gb no 3g version...
PenguinDroid said:
i have the same issue, but i dont want to fastboot it, what should i do? i havent rooted or anything yet. i have a 32gb no 3g version...
Click to expand...
Click to collapse
Why not, it's a safe operation.
If you're completely stock, and update fails, either try again (and again, and again), or send it to repair (slowest). Or fastboot (fastest).
issak42 said:
Why not, it's a safe operation.
If you're completely stock, and update fails, either try again (and again, and again), or send it to repair (slowest). Or fastboot (fastest).
Click to expand...
Click to collapse
well, in that case, id rather root it and flash a custom rom, and thats probably what i am gonna end up doing... ill see, thanks for the answer
Hello everybody.
A few days back I managed to brick my Nexus 4 after using it for 1 day!!!! I realize that this all is a very moronic situation and there isn't a fix for my brick because a used a *Toolkit*. Well, I'm already receiving my replacement and it will be here in an hour.
I know how everyone here feels about Google paying for our mistakes but I'm so lucky they're so kind. The advice that I need is on how to NEVER be in this same position. If I were to have set up fastboot instead of a toolkit would all of this have been avoidable? Btw, CM 10.1 is how I bricked my phone....I never have had any luck with that rom.
Thanks everyone for your advice.
Almost all errors are caused by, you guessed it, users. I am skeptical when people claim the toolkit bricked their phone. Also, if cm 10.1 has been troublesome for you, why keep using it? Its the very definition of insanity: keep doing the same thing over and over and expecting different result.
Sent from my Nexus 4 using xda premium
Sooooo, in your professional opinion....would my brick have been less severe if I used fastboot?
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
blitzzz3434 said:
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
Click to expand...
Click to collapse
Well what happened was when I tried to flash it the first time I got a boot loop. So I restored from a backup. Then I redownloaded and when I was in my custom recovery I did a factory reset, a cache wipe and a factory wipe. Then I installed CM.
No after like 3 minutes of booting, I got to my homescreen. I think what happened was I wanted to get off CM because it wasn't working right so I tried to boot into recovery so I held down power and volume keys. I got a yellow light then a red light and now bootloader. After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
My excuse for all of this stupidity is that it was 6am and I hadn't slept yet. Nothing good happens for me without sleep lol. btw, thats as accurate as I remember.
Alpha-Wat3rloo said:
After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
Click to expand...
Click to collapse
What is smirkit? The only hits I could find on it were for the Kindle Fire. It sounds to me like you flashed a bootloader for another device, that would certainly give you a hard brick.
Sent from my Nexus 4
As I suspected, user error.
Sent from my Nexus 4 using xda premium
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Thank you you've actually helped Mr to figure out why it happened. It was super late/early. Serves me right flashing anything without proper rest.
Sent from my Nexus 4 using xda app-developers app
If you had flashed the wrong bootloader or kernel (one meant for a different device) via fastboot then you would still have a hard brick.
Using fastboot instead of a toolkit does mean you have more control over what your are doing, but you still need to make sure you are still flashing the right things.
Sent from my Nexus 4
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your original post made it sound like you used one of the toolkits made specifically for the Nexus 4 and that is what had bricked your phone. It wasn't till half way down the thread you mention you used a tookit for another device. Toolkits are not free from user error even when you use the correct one as you still have to download the correct files and place them in the correct folders. There have been a lot of newbies bricking phones because they have downloaded the incorrect files and then blame it on the developers and or phone for being defective. So this is why people are skeptical when they read these threads.
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that`s what happens when your SMARTphone is Smarter than you.....
Hi,
I had a Nexus 7 (first gen) running 4.2 stock, but it was unlocked and rooted using the Wugfresh toolkit. I updated to 4.3 and can't seem to be ADB working. I'm pretty sure I have the drivers correct, and USB debugging option is checked. I tried going through the driver installation again. But still no ADB.
Does 4.3 work differently? Can you think of something I might be missing?
This is a Win 7 machine, 64bit.
Are you using his newest one? Worked fine for me (once I figured usb mod had to be camera and not mass storage).
Sent from my DROID RAZR using Tapatalk 4
iresq said:
Are you using his newest one? Worked fine for me (once I figured usb mod had to be camera and not mass storage).
Sent from my DROID RAZR using Tapatalk 4
Click to expand...
Click to collapse
Darn, yeah I remember having to do that the first time, and I forgot this time around. Thanks for reminding me. I was feeling pretty frustrated. I'll go try it now.
Really, thanks for taking the time to mention that.
Yup, that was the issue. Ugh! Wasted hours trying to get it to work, trying multiple computers. There's so many notes on the toolkit about enabling USB debugging, and in every guide. The MTP/camera setting really gets under the radar.
coachclass said:
Yup, that was the issue. Ugh! Wasted hours trying to get it to work, trying multiple computers. There's so many notes on the toolkit about enabling USB debugging, and in every guide. The MTP/camera setting really gets under the radar.
Click to expand...
Click to collapse
I had the same issue as well. Hopefully Wug will make a note for the next update to switch to the MTP/Camera,
Glad I could contribute, I usually just learn.
Sent from my DROID RAZR using Tapatalk 4
Droidnoobi said:
I had the same issue as well. Hopefully Wug will make a note for the next update to switch to the MTP/Camera,
Click to expand...
Click to collapse
Same here...I hope he updates his thread with that note to save others time and effort...
Sent from my Nexus 7 using xda app-developers app
Well the #1 driver solution didn't work for me so i try #2 driver solution and it worked . Have u try all driver solution?