i flashed this through CMW recovery and phone wont boot wont do anything at all and its says it for the galaxy note
https://play.google.com/store/apps/details?id=com.franco.kernel.note
Wrong note. Franco kernel only out for the international version, not ours (ATT VERSION).
Im guessing you can put your phone in download mode and flash a stock kernel using ODIN.
Search for stock kernel in this forum. Instructions in OP
Sent from my SAMSUNG-SGH-I717
Reading is everything. The international note n7000 is not compatible with the US Canada i717. Sorry
Sent from my SAMSUNG-SGH-I717 using xda premium
i did read it in market and it didnt say that is was for either one but it doesnt even pick up at all
it would be easy to confuse people...I read the app...it does say note...and not anything about what model either?....so it can mislead people...he should correct that..if someone can pm him to update so thos wont happen to another person
Sent from my SAMSUNG-SGH-I717 using XDA
i tried talking to him about his mistake but i dont know what to do when he failed to post something vital and now i have a brick
thatruth132 said:
i tried talking to him about his mistake but i dont know what to do when he failed to post something vital and now i have a brick
Click to expand...
Click to collapse
Less complaining, more recovering. Download mode and stock rom, you have not bricked anything.
khaytsus said:
Less complaining, more recovering. Download mode and stock rom, you have not bricked anything.
Click to expand...
Click to collapse
less sarcasm because i know how to do all of that next time ask first before assuming you know what that makes you look like the device wont boot period and no download mode and no recovery at all no pc connectivity nothing i have been doing this for a long time and thank you for your help
thatruth132 said:
i tried talking to him about his mistake but i dont know what to do when he failed to post something vital and now i have a brick
Click to expand...
Click to collapse
actually i see it this way. You have the skills to read a forum. thats why you are in the correct forum with the correct device posting about your brick. Since you flashed with recovery and did not have a brick you also know that there is a difference between the devices.
That said. Dont you think there would be a thread (probably somewhere on the first page of this forum) about the kernel if it was for this device?
In conclusion. You failed to demonstrate reading comprehension and now have a brick.
just my .02
Now, your only options are to do one of the following.
1. try to go into download mode and flash stock recovery and rom.
2. ( make sure you read THIS one properly) Take an old laptop charger. cut the cord right where the charger would plug into the laptop. separate the two wires and twist the copper on each wire nice and tight NOT TOGETHER. Take out battery from the device and then plug in the laptop charger. DO NOT WORRY. Laptop chargers will not kill or harm you. Tap the wires on the gold prongs on the device a few times then unplug.
try your device and make sure you cannot turn it on under battery power. If you can not... Call att and have them exchange it.
i did jump the gun when i saw this in the market but i did look for links to your site but it linked to his and i installed it without seen a thread here because i thought to test it before posting he is still at fault in a way of not notifying that it wasnt for att but like i said you are right for not looking here first .....but i didnt know about xda then what ?...and i will try the laptop charger thing now lol wont hurt right... thanks for the sane answer
thatruth132 said:
i did jump the gun when i saw this in the market but i did look for links to your site but it linked to his and i installed it without seen a thread here because i thought to test it before posting he is still at fault in a way of not notifying that it wasnt for att but like i said you are right for not looking here first .....but i didnt know about xda then what ?...and i will try the laptop charger thing now lol wont hurt right... thanks for the sane answer
Click to expand...
Click to collapse
how is it his fault??? im lost??? YOU chose to flash it correct so that would make you 100% at fault not someone that posted something on the internet lol
EDIT i really hope the part where it says NOTE FOR ATT GALAXY NOTE wasn't there earlier
Description
NOT FOR ATT GALAXY NOTE
The famous franco.Kernel series is back now for the Galaxy Note. This kernel has being very well acclaimed by users all around the world, and now with this application you'll be able to stay in touch with the latest kernel updates and change a lot of internal settings to improve your device. This is a work in progress
This is obviously ONLY for the Galaxy Note and for rooted devices.
Testimonials:
"Franco, do you remember what I told you yesterday???? I trust in another version of your kernel, hoping for solving problems... And you know what???????????
A M A Z I N G O N E !!!! Francoooooo
CONGRATULATIONS for this one version I'm testing, device is smooth, SO FAST to revives after sleeping and DUDE..................
BATTERY USAGE IS SIMPLE UNBELIEVABLE MAN! UNBELIEVABLE! Even with a strong usage that little number of battery' percent seems STUCK INTO the same number
You ROCK man! You did it! THANK YOU A LOT!" by [David]
"excellent kernel, first time I have managed to get -2mA" by kivine
celljunkie707 said:
actually i see it this way. You have the skills to read a forum. thats why you are in the correct forum with the correct device posting about your brick. Since you flashed with recovery and did not have a brick you also know that there is a difference between the devices.
That said. Dont you think there would be a thread (probably somewhere on the first page of this forum) about the kernel if it was for this device?
In conclusion. You failed to demonstrate reading comprehension and now have a brick.
just my .02
Now, your only options are to do one of the following.
1. try to go into download mode and flash stock recovery and rom.
2. ( make sure you read THIS one properly) Take an old laptop charger. cut the cord right where the charger would plug into the laptop. separate the two wires and twist the copper on each wire nice and tight NOT TOGETHER. Take out battery from the device and then plug in the laptop charger. DO NOT WORRY. Laptop chargers will not kill or harm you. Tap the wires on the gold prongs on the device a few times then unplug.
try your device and make sure you cannot turn it on under battery power. If you can not... Call att and have them exchange it.
Click to expand...
Click to collapse
and is this to make so that it wont power on or is this a fix lol
Does it hurt? Meh. Not really. i zapped myself by accident. dont know if you have ever been around electric fences for cows, horses things like that. but if you have and have touched the fence. its about that same amount of discomfort.
It will kill the device and they wont be able to check to see if you flashed anything you are not supposed to.
BLOWNCO said:
how is it his fault??? im lost??? YOU chose to flash it correct so that would make you 100% at fault not someone that posted something on the internet lol
Click to expand...
Click to collapse
because lol its his app/recovery lol and its not for att notes lol and he doesnt have that on the download page lol lol ......ha hah hah lol....lol
so in short i would of took 100% responsibility if it said that it wasnt for att and i flashed it it said for galaxy note and he is a known developer lol lolololol
Franco didn't Know
Franco didn't know htere was a I717 Galaxy Note, he just wants to relax with his girl friend and play a song for her on his guitar school is tough.
BLOWNCO said:
how is it his fault??? im lost??? YOU chose to flash it correct so that would make you 100% at fault not someone that posted something on the internet lol
EDIT i really hope the part where it says NOTE FOR ATT GALAXY NOTE wasn't there earlier
Click to expand...
Click to collapse
it was not at the time. ive seen it myself. but still. I disagree that it is in any way shape or form the developers fault.
Its pretty common knowledge that what YOU do to YOUR device no matter where the code comes from is YOUR responsibility and choice.
but i dont see whats funny when me and a dev are in this situation and i am not taking a lost for his mistake
thatruth132 said:
but i dont see whats funny when me and a dev are in this situation and i am not taking a lost for his mistake
Click to expand...
Click to collapse
its funny because your blaming someone for something they didn't do!DUDE its not his mistake holy crap YOU CHOSE TO FLASH IT CORRECT? ya there ya go its your fault
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
celljunkie707 said:
it was not at the time. ive seen it myself. but still. I disagree that it is in any way shape or form the developers fault.
Its pretty common knowledge that what YOU do to YOUR device no matter where the code comes from is YOUR responsibility and choice.
Click to expand...
Click to collapse
exactly the dev didn't make him flash it man these posts are so ridiculous people will never take responsibility for there own actions
and yes he changed and added not for galaxy not i already saved a screen shot of it before he changed it
Okay, guys. I'm new to this forum (I own the ATRIX since yesterday, so...). I had the HTC Desire, Desire HD and EVO 3D before and never had such problems with them (instead, I used to have other issues such as crappy sound, ghost touching etc.).
Flashed Neutrino GT+ ROM, set the max CPU freq to 1 GHz, instead of 1.45 - I don't feel like I need that extra power (at least not yet, anyway). Flashed the Superuser 3.0.7 pack, flashed several Addons, also set the NitroCharger.sh script on boot... I think I pretty much did everything that mattered.
Oh, I flashed the ROM from the internal sdcard (emmc). I don't get why it's reccomended not to flash from the external sdcard, anyways, but... oh well...
-----
The best way to describe the problem(s) I am experiencing is through this movie I've made. I filmed it with a Nokia 6233, so it's not really high definition, but hey, at least it's 480p, not QVGA . Oh well, you can figure, I suppose / hope.
Okay, the problem is the touch panel is acting weird. When I'm browsing through the app drawer, and I slide my finger across and then stop or do something like that, the app that the finger was on is being launched (like I released my finger = touch ended, registered, whatever).
Also, the left and right sides of the screen seem to be less responsive (you can clearly see that in Multitouch Visualiser), especially as you get closer to the edges. Not ALL THE TIMES, though, but roughly 95%, the problem occurs and... well... the touch goes crazy.
----------------------------------------------------
Can anyone confirm that this is happening to them, and not only to me? Perhaps use Multitouch Visualiser yourself and see if you get the same results?!
VIDEO HERE
Formhault said:
Okay, guys. I'm new to this forum (I own the ATRIX since yesterday, so...). I had the HTC Desire, Desire HD and EVO 3D before and never had such problems with them (instead, I used to have other issues such as crappy sound, ghost touching etc.).
Flashed Neutrino GT+ ROM, set the max CPU freq to 1 GHz, instead of 1.45 - I don't feel like I need that extra power (at least not yet, anyway). Flashed the Superuser 3.0.7 pack, flashed several Addons, also set the NitroCharger.sh script on boot... I think I pretty much did everything that mattered.
Oh, I flashed the ROM from the internal sdcard (emmc). I don't get why it's reccomended not to flash from the external sdcard, anyways, but... oh well...
-----
The best way to describe the problem(s) I am experiencing is through this movie I've made. I filmed it with a Nokia 6233, so it's not really high definition, but hey, at least it's 480p, not QVGA . Oh well, you can figure, I suppose / hope.
Okay, the problem is the touch panel is acting weird. When I'm browsing through the app drawer, and I slide my finger across and then stop or do something like that, the app that the finger was on is being launched (like I released my finger = touch ended, registered, whatever).
Also, the left and right sides of the screen seem to be less responsive (you can clearly see that in Multitouch Visualiser), especially as you get closer to the edges. Not ALL THE TIMES, though, but roughly 95%, the problem occurs and... well... the touch goes crazy.
----------------------------------------------------
Can anyone confirm that this is happening to them, and not only to me? Perhaps use Multitouch Visualiser yourself and see if you get the same results?!
Click to expand...
Click to collapse
The app drawer thing is the manner in which you stop it, to stop the app drawer from scrolling, just give a quick very light tap, it also helps to try and tap between two of the apps, if you're using your right hand try to tap between the 3rd and 4th columns, this way you don't tap any icons. To be honest, I never really have any problems at all. Can you give me DETAILED information on how you flashed the ROM? It could be cause by a mistake in the flashing process.
Erebus671 said:
The app drawer thing is the manner in which you stop it, to stop the app drawer from scrolling, just give a quick very light tap, it also helps to try and tap between two of the apps, if you're using your right hand try to tap between the 3rd and 4th columns, this way you don't tap any icons. To be honest, I never really have any problems at all. Can you give me DETAILED information on how you flashed the ROM? It could be cause by a mistake in the flashing process.
Click to expand...
Click to collapse
I forgot to put the video link in the first topic (I edited it, it is there now).
I put Neutrino GT+ .zip in the emmc (along with all other flashables, actually). I still don't get why it is reccomended to flash from the internal memory instead of an external sdcard. Speaking of internal memory, is it an internal SD card (just like HTC devices with WP7) or NAND?!
Wiped everything in recovery (using the latest RomRacer's CWM). Then, I flashed Neutrino V2.6 GT+.zip, then Lite Gapps, then Deskclock addon, then Languages addon, then Live Wallpapers addon, then Sync addon, then Theme Chooser addon, then TTS addon, then VPN addon. Then rebooted the phone.
The red M logo appeared, and a few seconds after that, it seemed like the phone turned off and turned itself on again (M logo appeared second time, then the boot animation showed up and the ROM booted). I remember that was happening back when I was using CM7 on my old Desire and I was flashing the Gapps right after the ROM. If I were to flash MIUI and then the DarkTremor script (for A2SD), without rebooting in between, the boot splash would appear three times .
Formhault said:
I forgot to put the video link in the first topic (I edited it, it is there now).
I put Neutrino GT+ .zip in the emmc (along with all other flashables, actually). I still don't get why it is reccomended to flash from the internal memory instead of an external sdcard. Speaking of internal memory, is it an internal SD card (just like HTC devices with WP7) or NAND?!
Wiped everything in recovery (using the latest RomRacer's CWM). Then, I flashed Neutrino V2.6 GT+.zip, then Lite Gapps, then Deskclock addon, then Languages addon, then Live Wallpapers addon, then Sync addon, then Theme Chooser addon, then TTS addon, then VPN addon. Then rebooted the phone.
The red M logo appeared, and a few seconds after that, it seemed like the phone turned off and turned itself on again (M logo appeared second time, then the boot animation showed up and the ROM booted). I remember that was happening back when I was using CM7 on my old Desire and I was flashing the Gapps right after the ROM. If I were to flash MIUI and then the DarkTremor script (for A2SD), without rebooting in between, the boot splash would appear three times .
Click to expand...
Click to collapse
Okay, I'm not exactly sure about what the "Internal SD Card" is, but it is not an actual SD card, I do know that.
Are you at all familiar with fastboot? I would assume so, but I would like to know before I go any further.
Yeah, the double boot before the boot animation is normal.
Erebus671 said:
Okay, I'm not exactly sure about what the "Internal SD Card" is, but it is not an actual SD card, I do know that.
Are you at all familiar with fastboot? I would assume so, but I would like to know before I go any further.
Yeah, the double boot before the boot animation is normal.
Click to expand...
Click to collapse
I was assuming it is a SD card, so... Okay, so it is internal memory, so NAND .
I am familiar with fastboot, of course. That's how I was flashing recoveries, radios etc. on the HTC devices : fastboot flash recovery <file.img> etc...
I saw that for Motorola the fastboot commands are a bit different, and this system being somewhat different than it is on HTC devices, I am a bit afraid
Formhault said:
I was assuming it is a SD card, so... Okay, so it is internal memory, so NAND .
I am familiar with fastboot, of course. That's how I was flashing recoveries, radios etc. on the HTC devices : fastboot flash recovery <file.img> etc...
I saw that for Motorola the fastboot commands are a bit different, and this system being somewhat different than it is on HTC devices, I am a bit afraid
Click to expand...
Click to collapse
lol, okay, I'll give you a thanks for that one.
TBH, I don't use the "moto fastboot" commands, you can just use the general fastboot commands, so try this out..
Do a clean install, using fastboot wipe everything:
Code:
fastboot -w
fastboot erase system
fastboot erase preinstall
fastboot erase boot
fastboot reboot (make sure you're pressing the VOL Down button when you press enter)
reboot into recover and erase the Dalvik cache, once all that is done, flash the ROM as usual and see how it goes... Sometimes all you need is a clean install.
That's how most of my problems get fixed.
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
xploited said:
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
Click to expand...
Click to collapse
That sounds like my problem... but to hell with motorola, I'll buy my own digitizer, damned fools sent me a sim locked phone to replace a sim unlocked phone when I am under a carrier that does not have the equipment to support locking the phones to its network...
Erebus671 said:
TBH, I don't use the "moto fastboot" commands, you can just use the general fastboot commands, so try this out..
Do a clean install, using fastboot wipe everything:
Code:
fastboot -w
fastboot erase system
fastboot erase preinstall
fastboot erase boot
fastboot reboot (make sure you're pressing the VOL Down button when you press enter)
reboot into recover and erase the Dalvik cache, once all that is done, flash the ROM as usual and see how it goes... Sometimes all you need is a clean install.
That's how most of my problems get fixed.
Click to expand...
Click to collapse
No fastboot erase data and etc.? Just those? Mmmmkay . Should I do this when the battery is ABSOLUTELY FULL?! Cause yesterday I flashed when the phone was @ ~20%, and today, when the battery reached 15%, it dropped to 4% as I blinked, rofl (fully charged it earlier today).
Erebus671 said:
lol, okay, I'll give you a thanks for that one.
Click to expand...
Click to collapse
read my signature, carefully (I'll edit it to match the current state... soon... some day...)
"I've had the Wildfire, Desire & Desire HD before, so I know flies are not eatable "
God damn it, this post is a fail. Head on to the second page, rofl.
xploited said:
OK, I am no longer sure if it's a digitizer malfunction.
What I would do is wipe the screen completely clean with a wet PC cloth or something.
Also, try installing a different launcher (Go Launcher, ADW) and check if it does the same thing.
Usually, when the digitizer dies, the symptoms are - digitizer registers random touches without you touching it.
Click to expand...
Click to collapse
Erebus671 said:
That sounds like my problem... but to hell with motorola, I'll buy my own digitizer, damned fools sent me a sim locked phone to replace a sim unlocked phone when I am under a carrier that does not have the equipment to support locking the phones to its network...
Click to expand...
Click to collapse
Guys, have you tried Multitouch Visualiser?
I mean seriously... Clean your screen (like I did) with a cloth (not NASA-ultrasmooth-bacteria-remover) and then try it in that program... like I did... see if you get the same outcome...
Formhault said:
No fastboot erase data and etc.? Just those? Mmmmkay . Should I do this when the battery is ABSOLUTELY FULL?! Cause yesterday I flashed when the phone was @ ~20%, and today, when the battery reached 15%, it dropped to 4% as I blinked, rofl (fully charged it earlier today).
read my signature, carefully (I'll edit it to match the current state... soon... some day...)
Click to expand...
Click to collapse
nope.. fastboot -w takes care of that.
The battery thing is simple, once it is fully charged calibrate the battery with a battery calibration app. It's that simple.
I'm not sure what I'm supposed to be reading, the device history? or the thanks message?
---------- Post added at 05:48 AM ---------- Previous post was at 05:46 AM ----------
Formhault said:
Guys, have you tried Multitouch Visualiser?
I mean seriously... Clean your screen (like I did) with a cloth (not NASA-ultrasmooth-bacteria-remover) and then try it in that program... like I did... see if you get the same outcome...
Click to expand...
Click to collapse
I have actually and I've gotten up to 8 fingers on there with fairly accurate precision...
Edit: You'll have to elaborate on the non-eatable flies thing, understand I do not... (I didn't see you point that out until after I posted this)
Erebus671 said:
nope.. fastboot -w takes care of that.
The battery thing is simple, once it is fully charged calibrate the battery with a battery calibration app. It's that simple.
Click to expand...
Click to collapse
I thought the thing with the battery calibration was sorted already (it is a placebo?). Anyway, I'll do that (placebo DOES have effect, rofl).
Erebus671 said:
I'm not sure what I'm supposed to be reading, the device history? or the thanks message?
Click to expand...
Click to collapse
I edited the original post. Oh well, what I meant is... I'm not REALLY a newbie. Not THAT much of a newbie
Erebus671 said:
I have actually and I've gotten up to 8 fingers on there with fairly accurate precision...
Click to expand...
Click to collapse
I can only get FIVE touch points :/
Also, it seems that 5 is the maximum, lol. So how the heck did you get 8 touch points, and even working PERFECTLY :/ https://www.google.ro/search?sourceid=chrome&ie=UTF-8&q=motorola+atrix+multi+touch
-----
WHY WON'T posts merge?! -.-
Formhault said:
I thought the thing with the battery calibration was sorted already (it is a placebo?). Anyway, I'll do that (placebo DOES have effect, rofl).
I edited the original post. Oh well, what I meant is... I'm not REALLY a newbie. Not THAT much of a newbie
Click to expand...
Click to collapse
Uh, no, you're right, the battery life problem was solve, but there is no real solution to the battery calibration issue, that is cause by battery stats remaining over multiple flashes. At least that's how I comprehend it from what I have read in the past. I calibrate my battery on every flash, never once had the problem.
And I edited mine as well, and believe it or not I AM a newbie. I simply seem to not be a newbie (well not a total newbie at least) because I actually follow the first rule of XDA, unlike a lot of the people who have a million questions... Present company excluded... Basically what I just said is, I READ BEFORE I POST. Once again, I will note that I am excluding the present company when I state this.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
Formhault said:
I can only get FIVE touch points :/
Also, it seems that 5 is the maximum, lol. https://www.google.ro/search?sourceid=chrome&ie=UTF-8&q=motorola+atrix+multi+touch
-----
WHY WON'T posts merge?! -.-
Click to expand...
Click to collapse
hmm, I'll have to test again... I'll let you know what I get.
Edit: Okay, you got me, 5 it is. I seem to have forgotten and over guestimated. XD
Okay... I say again : should I flash ONLY when the battery is full? I know it wasn't much of a problem on HTCs... The difference was I had to make a few battery cycles afterwards so the battery percentage is displayed right.
Formhault said:
Okay... I say again : should I flash ONLY when the battery is full? I know it wasn't much of a problem on HTCs... The difference was I had to make a few battery cycles afterwards so the battery percentage is displayed right.
Click to expand...
Click to collapse
It's not all that important to be fully charged... I do it between 25-30% when I really have to...
Off topic... Is it safe to remove the stock messenger app? Or am I being a newbie?
Erebus671 said:
It's not all that important to be fully charged... I do it between 25-30% when I really have to...
Click to expand...
Click to collapse
As I thought .
I was thinking, somewhat, since the Motorola system is a bit different, it may require a battery closer to full... I had the Motorola V360 before and... oh well, if you know what I'm talking about, nuff said
Formhault said:
As I thought .
I was thinking, somewhat, since the Motorola system is a bit different, it may require a battery closer to full... I had the Motorola V360 before and... oh well, if you know what I'm talking about, nuff said
Click to expand...
Click to collapse
Lol, I know what you're talking about... Horrible customer service aside, I am a tried and true moto fan.
Erebus671 said:
Off topic... Is it safe to remove the stock messenger app? Or am I being a newbie?
Click to expand...
Click to collapse
I remember this part from the time I was using CM7 on my Desire. God, at that time, I thought CM7 is the ONLY ROM, lol.
Some people were saying that you need to remove/replace some libraries & some other additional files in order to be able to fully replace the stock Messaging app. I ended up just adding Handcent SMS and using the option from within its Settings menu to disable the stock Messaging app notification.
Of course, I no longer use Handcent. I was, almost a year ago. Now I'll just wait for MIUI to be fully working on the ATRIX then...