Related
Hello XDA!
I managed to brick my Note, so I'd like to sent it to the repair under warranty.
But my problem is, I'm currently on a stock ROM (I've flashed it with patched PIT) and I don't know how I should show to the repair centre that my partition is damaged and what to tell. Also my note has currently 3 flash counters.
I thought about the CF-Root Kernel -> TriangleAway.apk -> Flash a ROM with Mobile ODIN (Think doesnt increase the counter), but when I do it like this, my phone is still re-partionated with the patched PIT, so I have to remove this patched PIT, but when I remove it with ODIN and try to re-partion with stock PIT it would increase the counter? (And wouldn't be able to flash smth else because my note is bricked...)
At the moment I've no perspective how I can manage that. Has someone tip or knows how I could do that?
Thanks!!
// Sry for my rly bad english!
Go here. http://forum.xda-developers.com/showthread.php?t=1354888
jonpaslim said:
Go here. http://forum.xda-developers.com/showthread.php?t=1354888
Click to expand...
Click to collapse
Only possible with JIG?
thommysenf said:
Only possible with JIG?
Click to expand...
Click to collapse
Yes theres no other way.
You can buy it in ebay. Its better to buy the jig than to pay the repair, because they will surely see the binary count and void your warranty and also tell them you hardbrick your note by factory reset your phone.
jonpaslim said:
Yes theres no other way.
Click to expand...
Click to collapse
Please.
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&hl=sv
Already used it twice on my 2 weeks old Note.
3mL said:
Please.
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&hl=sv
Already used it twice on my 2 weeks old Note.
Click to expand...
Click to collapse
Is it not working on your note?
jonpaslim said:
Is it not working on your note?
Click to expand...
Click to collapse
Of course it's working - it's made by Chainfire!
3mL said:
Of course it's working - it's made by Chainfire!
Click to expand...
Click to collapse
Triagle away is good for working phone but if you hardbrick your phone, how can you use it?
jonpaslim said:
Triagle away is good for working phone but if you hardbrick your phone, how can you use it?
Click to expand...
Click to collapse
Hmm, isn't it working through CWM? Can't one enter CWM when bricked?
The funny part is that my note is actually working with custom pit, but I have to show to the repair centre that they wont be able to flash a normal ROM, so I have to reset my counter first (this is possible with custom pit and stock rom & triangle_away.apk), but then I have to flash again the normal pit, thats the point. To flash again original pit increases the counter, or I am wrong?
Dude your commiting fraud and should be reported
You knew what you were doing when voiding warantee
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Dude your commiting fraud and should be reported
You knew what you were doing when voiding warantee
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Read all the threads here in Q&A. You'll find alot of threads like this, every one knew what the were doing when voiding the guarantee, but it's not prohibited to ask what they told to the repair centre? So where's the problem?
baz77 said:
Dude your commiting fraud and should be reported
You knew what you were doing when voiding warantee
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Let's be frank, the eMMC bug is a manufacturing defect and Samsung knew it. That's fraud.
joe2316 said:
Let's be frank, the eMMC bug is a manufacturing defect and Samsung knew it. That's fraud.
Click to expand...
Click to collapse
Well you got me there
Sent from my GT-N7000 using Tapatalk 2
thommysenf said:
Hello XDA!
I managed to brick my Note, so I'd like to sent it to the repair under warranty.
But my problem is, I'm currently on a stock ROM (I've flashed it with patched PIT) and I don't know how I should show to the repair centre that my partition is damaged and what to tell. Also my note has currently 3 flash counters.
I thought about the CF-Root Kernel -> TriangleAway.apk -> Flash a ROM with Mobile ODIN (Think doesnt increase the counter), but when I do it like this, my phone is still re-partionated with the patched PIT, so I have to remove this patched PIT, but when I remove it with ODIN and try to re-partion with stock PIT it would increase the counter? (And wouldn't be able to flash smth else because my note is bricked...)
At the moment I've no perspective how I can manage that. Has someone tip or knows how I could do that?
Thanks!!
// Sry for my rly bad english!
Click to expand...
Click to collapse
IF u can re-partion with stock pit i guess u can flash stock rom too.
just tell me how exactly did u brick your note
So ive the same problem.. Updated OTA to ics, made a factory reset -> Damaged partition. So i used the patched PIT to get it working again. All working fine now, except that there are much more lags than before.
So i want to send it back to samsung to get it repaired / changed. What can i do now? I think samsung will check the phone and they will notice that it was flashed with patched pit. Is it possible to get it back to stock (with stock pit) to send it back?
thommysenf said:
Only possible with JIG?
Click to expand...
Click to collapse
My guess as to WTF it is you're talking about :
JIG
Because, yes, it's cute to flaunt acronyms, but in the end it doesn't help anybody.
Donald Nice said:
So ive the same problem.. Updated OTA to ics, made a factory reset -> Damaged partition. So i used the patched PIT to get it working again. All working fine now, except that there are much more lags than before.
So i want to send it back to samsung to get it repaired / changed. What can i do now? I think samsung will check the phone and they will notice that it was flashed with patched pit. Is it possible to get it back to stock (with stock pit) to send it back?
Click to expand...
Click to collapse
Not 100% on this. Don't think repetition ingredients to stock would work as it would fail, but this might actually be a good root to go down. There's a chance the partition would be damaged enough to pose a re- superbrick. Alternatively, install stock ics and go for another superbrick.
Sent from my GT-N7000 using xda premium
Hey guys, I'm new to this forum and I got my Galaxy Note a few weeks ago.
And today I tried to root it, but I think somehow it went wrong, now my Note could be turnned on, but the screen just stayed black. No logo, just sounds. The two 'buttons' below would light up too.
Any suggestions on how to fix it?
Try to go into download mode and reflash a gb stock rom via odin
Sent from my GT-N7000 using xda app-developers app
Jestina said:
Hey guys, I'm new to this forum and I got my Galaxy Note a few weeks ago.
And today I tried to root it, but I think somehow it went wrong, now my Note could be turnned on, but the screen just stayed black. No logo, just sounds. The two 'buttons' below would light up too.
Any suggestions on how to fix it?
Click to expand...
Click to collapse
Why do you not give us a few more details?
What did you do, where did you start, what went wrong?
ThaiDai said:
Why do you not give us a few more details?
What did you do, where did you start, what went wrong?
Click to expand...
Click to collapse
Okay, I tried to root it using a pre-rooted rom, N7000DXLC2 and some md5 and tar file that came along with it, but I'm not sure if I'm doing it correctly, my actual baseband is LR1 and the kernel is LR2.
At first, after attempting to root it, I kinda of did it successfully, I reached the green android alien place, but there's alot of pop up saying that this progress ended (something like that, couldn't remember.)
So I decided, to find and download my actual baseband's stock rom and try to use Odin to flash it, it succeeded, but the problem is, my screen is staying black this time, But I know that my phone is still working, just that the screen is not displaying anything..
Are you able to get into download mode?
When you tried to flash the rooted ROM in ODIN was it a 3 part file or a single file?
Did you setup ODIN correctly as per instructions on this site?
CJSlim79 said:
Are you able to get into download mode?
When you tried to flash the rooted ROM in ODIN was it a 3 part file or a single file?
Did you setup ODIN correctly as per instructions on this site?
Click to expand...
Click to collapse
Yeah I did get into the download mode, the first ROM was 3 part file, second one was a single file.. and yeah setup correctly.
Nobody knows a fix for this?
Jestina said:
Nobody knows a fix for this?
Click to expand...
Click to collapse
Ok -
You can get back into download mode - what happens when you try to flash a stock GB ROM in PC Odin, *Use a 1 part file from here*
http://forum.xda-developers.com/showthread.php?p=26455511#post26455511
You need to provide as much info as you can otherwise it is hard to help...
In ODIN - You said it was setup correctly? Where did you confirm this?
Jestina said:
Nobody knows a fix for this?
Click to expand...
Click to collapse
Read here. http://androidadvices.com/update-galaxy-note-n7000-gingerbread-xxlc1-236-firmware/2/
Read it carefully and do it at your own risk if you decide to flash it.
I don't think it'll work.. I'm already back on my actual baseband, its just the problem with the screen, its black and it won't display anything. My phone is still working.
Jestina said:
I don't think it'll work.. I'm already back on my actual baseband, its just the problem with the screen, its black and it won't display anything. My phone is still working.
Click to expand...
Click to collapse
Are you on a complete STOCK setup? or custom kernel?
This is very odd - sounds like possible hardware fault if your phone is working but no screen - You definitely flashed the correct ROM yeah? I would still give a try to reflashing the STOCK GB via PC Odin..
Question - When you goto Download Mode - Do you see the Android Guy? If so there's something wrong with your flashed ROM and not a screen fault so a re-flash should resolve that..
+1, Definitely not a screen problem if you are able to go in download mode & see the green guy.
Just try to reflash via PC odin a GB ROM.
CJSlim79 said:
Are you on a complete STOCK setup? or custom kernel?
This is very odd - sounds like possible hardware fault if your phone is working but no screen - You definitely flashed the correct ROM yeah? I would still give a try to reflashing the STOCK GB via PC Odin..
Question - When you goto Download Mode - Do you see the Android Guy? If so there's something wrong with your flashed ROM and not a screen fault so a re-flash should resolve that..
Click to expand...
Click to collapse
I will try re-flashing it again, the problem is now I can't see whats on my screen, but I can get to download mode by prediction though...
Jestina said:
I will try re-flashing it again, the problem is now I can't see whats on my screen, but I can get to download mode by prediction though...
Click to expand...
Click to collapse
Ok but in download mode - do you see the Android guy?.....or girl..........
If not there's a chance you've a screen problem.. or you flashed something you shouldn't have...
Give the Stock GB Flash a go through ODIN and report back..
Black Screen
Jestina said:
I will try re-flashing it again, the problem is now I can't see whats on my screen, but I can get to download mode by prediction though...
Click to expand...
Click to collapse
First sorry for my english.
If your phone is open but screen is not open. TRY following steps.
Flash this rom with Odin ( N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar )
Kernel: CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5
if loading stop to hidden.img dont worry. try again loading rom.
i think solving the problem.
CJSlim79 said:
Ok but in download mode - do you see the Android guy?....or girl..????........
..
Click to expand...
Click to collapse
Seriously... your kidding right??
geist_100 said:
First sorry for my english.
If your phone is open but screen is not open. TRY following steps.
Flash this rom with Odin ( N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar )
Kernel: CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5
if loading stop to hidden.img dont worry. try again loading rom.
i think solving the problem.
Click to expand...
Click to collapse
I would go with this route as well
@OP, I think what messed up your phone is you inadvertently flash either a wrong kernel..(a kernel meant for GB but your already on ICS or the other way around as well)
had the same issue you have before... **** I flashed a kernel not design for our NOTE....
After that, my phone just stays black.. but I could actually go to download mode... so what I did? Flashed it back to GB stock and work my way from there...
Hope that helps something bud
Cheers!
CJSlim79 said:
Ok but in download mode - do you see the Android guy?.....or girl..........
If not there's a chance you've a screen problem.. or you flashed something you shouldn't have...
Give the Stock GB Flash a go through ODIN and report back..
Click to expand...
Click to collapse
lol that cracked me up thanks,
Thought android was androgenious, mwahahah
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
lol that cracked me up thanks,
Thought android was androgenious, mwahahah
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I'm pleased a couple of people picked up on it
Erm.. I've downloaded the CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5, but when I open it up its a zImage file.
What am I suppose to do with it? x_x
Edit; Nvm, got it!
letters_to_cleo said:
Seriously... your kidding right??
I would go with this route as well
@OP, I think what messed up your phone is you inadvertently flash either a wrong kernel..(a kernel meant for GB but your already on ICS or the other way around as well)
had the same issue you have before... **** I flashed a kernel not design for our NOTE....
After that, my phone just stays black.. but I could actually go to download mode... so what I did? Flashed it back to GB stock and work my way from there...
Hope that helps something bud
Cheers!
Click to expand...
Click to collapse
I did what you said, but now my note still stays black.. I guess its my screen problem now huh.. Weird..
I flashed via CWM MUI v.3 cuz the v.4 needed v3 due a bug but it hang on flashing boot.IMG. so i had to took out battery. Since then no charging / detection / download mode by buttons. Possible Ultimate brick?
Can access recovery mode?
Thanks
dr.ketan said:
Can access recovery mode?
Click to expand...
Click to collapse
Dr. Ketan,
Black screen no detection no recovery
First make sure your battery is not completely empty. Try to charge with external charger or manage for other battery
Still nothing then manage for JIG as last option
Dr. KEtan,
I bricked the note with 95% then removed battery to prevent drain while briked. Will try JIG tonight., Will let u know
jeroen180 said:
Dr. KEtan,
I bricked the note with 95% then removed battery to prevent drain while briked. Will try JIG tonight., Will let u know
Click to expand...
Click to collapse
Jigged it... Its confirmed. It is the SUPER-brick. Superbrick via CWM wattaf...
jeroen180 said:
Jigged it... Its confirmed. It is the SUPER-brick. Superbrick via CWM wattaf...
Click to expand...
Click to collapse
What do you think it is related with brick? Is it your fault of kernel or ROM fault. It is really annoying situation... Im sorry for your loss man...
Im not really an expert on android, but i would consider myself an advanced user so correct me if im wrong....
Couldnt it be, that the boot.img from the rom got corrupted somehow and thats the reason why it hanged while flashing it? Coz as of how i understood what the boot.img is used for, it would explain why u cant boot in recovery/dl-mode. Simply coz there is no bootloader on ur phone. Just an idea...
Sent from my GT-N7000 using xda premium
shrooms90 said:
Im not really an expert on android, but i would consider myself an advanced user so correct me if im wrong....
Couldnt it be, that the boot.img from the rom got corrupted somehow and thats the reason why it hanged while flashing it? Coz as of how i understood what the boot.img is used for, it would explain why u cant boot in recovery/dl-mode. Simply coz there is no bootloader on ur phone. Just an idea...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Well, im not a pro too to understand that since CWM erased bootloader and did not replaced it with the other version. How about SSC? Will they notice since my counter was not reset?
Worth a try
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
Worth a try
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
If they found out its my fault.. .will they charge or call me to fix it foor like.... 200 ~ 300 EU?
I have warned in hydracore thread that CWM 6.0.1.2 caused me and another user from a different thread to softbrick.
I got bashed by the fanatics in return.
Sorry to hear about your incident.
praetorius said:
I have warned in hydracore thread that CWM 6.0.1.2 caused me and another user from a different thread to softbrick.
I got bashed by the fanatics in return.
Sorry to hear about your incident.
Click to expand...
Click to collapse
LoL i should read that..... Im getting JTAGGED soon..
jeroen180 said:
Well, im not a pro too to understand that since CWM erased bootloader and did not replaced it with the other version. How about SSC? Will they notice since my counter was not reset?
Click to expand...
Click to collapse
Looks like MIUI bug
Look hère : http://miuiandroid.com/community/index.php?threads/17408/
Envoyé depuis mon GT-N7000
@jeroen180 send it in, they wont notice, just tell them ur phone got slow sow u did a factory reset and now it refuses to boot send my sgs in that way, before the jig was know, and my gf sent her sgs plus in abot 2 weeks ago with the same story
Sent from my GT-N7000 using xda premium
Yeah, I agree, if you tell them you just had to do a factory reset because it got really slow and laggy than they shouldn't have a problem. They wouldn't bill you either unless they had prior authorization.
netopyr said:
Looks like MIUI bug
Look hère : http://miuiandroid.com/community/index.php?threads/17408/
Envoyé depuis mon GT-N7000
Click to expand...
Click to collapse
First off before you start quoting other threads in other fourms, take a minute to get your facts in order.. Miui for the note has not been released to the public as of this date because it has the possibility to brick you device as it has the unsafe Samsung kernel (yes the same kernel as your stock note ), so if your running Miui on your note than your running a leaked version (then in that case you should know the risk involved) that is either running the stock kernel or it has one of the hydracore versions as it is the only option miui has at the moment unless your on one of the cm versions. So not defending either the rom/kernel he was trying to flash or what he was coming from as he really doesn't state either .. it would help if he provided such information. Sorry to the owner but before you get your device JTAGGED you may want to check with a samasung service center because the JTAGGED will void your warranty..
jeroen180 said:
Well, im not a pro too to understand that since CWM erased bootloader and did not replaced it with the other version. How about SSC? Will they notice since my counter was not reset?
Click to expand...
Click to collapse
No ,CWM will not erase or even touch the bootloaders ,only PC ODIN can do that ,boot.img refers to the kernel ,I've had a corrupted boot.img flash once ,easily solved via PC ODIN ,the phone would start up and show the logo but nothing more if that happens .I doubt that's the case here but you could try a blind flash in PC odin and see if that works .
MR.change said:
No ,CWM will not erase or even touch the bootloaders ,only PC ODIN can do that ,boot.img refers to the kernel ,I've had a corrupted boot.img flash once ,easily solved via PC ODIN ,the phone would start up and show the logo but nothing more if that happens .I doubt that's the case here but you could try a blind flash in PC odin and see if that works .
Click to expand...
Click to collapse
How you explain the phone stays black screen after hanging in CWM with boot.img? U suggest my board broke by accident? Someone can explain?
Could it be,
that,,,, i forgot to reboot after flashing the Hydrakernel... and eMMC bricked the bootloader perhaps? since the bootloader is stored on the chip as well?
Guys i have a big problem. Every time i turn of my phone or try to put it on download mode or recovery mode it stucks in black screen and dont responding like it's been bricked. But when i remove the battery for 2 min and place it again it's opening normaly. Im in stock filmware and just rooted. Can u tell me why this is happening? Maybe i have to flash the official filmware again or somethink?
bagelismar said:
Guys i have a big problem. Every time i turn of my phone or try to put it on download mode or recovery mode it stucks in black screen and dont responding like it's been bricked. But when i remove the battery for 2 min and place it again it's opening normaly. Im in stock filmware and just rooted. Can u tell me why this is happening? Maybe i have to flash the official filmware again or somethink?
Click to expand...
Click to collapse
Are you on stock kernel? If so then flash some safe kernel and try full wipe, if that too doesn't help, then flash stock firmware using pc odin.
I am assuming you are on ICS, as you didn't provide any info. You should have mentioned the method used for root and everything.
jeetu1981 said:
Are you on stock kernel? If so then flash some safe kernel and try full wipe, if that too doesn't help, then flash stock firmware using pc odin.
I am assuming you are on ICS, as you didn't provide any info. You should have mentioned the method used for root and everything.
Click to expand...
Click to collapse
Sorry man your right. I used cursed4eva way that i found on a youtube video and im in ICS your right. All my broblems start when i wanted to flash a custom rom and with android recovery i tried to install AbyssNotekerne.zip from my external sd. Since i couldn't cause i was getting some kind of error i think somethink about licence i stop cause i didnt want to brick my phone and after this all problems began. So any help is welcome thank you
bagelismar said:
Sorry man your right. I used cursed4eva way that i found on a youtube video and im in ICS your right. All my broblems start when i wanted to flash a custom rom and with android recovery i tried to install AbyssNotekerne.zip from my external sd. Since i couldn't cause i was getting some kind of error i think somethink about licence i stop cause i didnt want to brick my phone and after this all problems began. So any help is welcome thank you
Click to expand...
Click to collapse
Now i cant even get to download mode to use odin to flash GB rom. I tried flashing abyss kernel using srock ICS recovery and that's the main reason for current situation i think. Any help?
bagelismar said:
Now i cant even get to download mode to use odin to flash GB rom. I tried flashing abyss kernel using srock ICS recovery and that's the main reason for current situation i think. Any help?
Click to expand...
Click to collapse
Take it to a samsung service center and ask them to reset the phone. Tell them its too slow after the latest update using kies. If there is a problem with the motherboard they will report back and replace under warranty.
Else they will install the OS completely new and you can start from scratch to root and install other custom roms.
Try using USB jig to go to download mode, try it first. Jig is not expensive.
Sent from my U1 using xda premium
heavenhated said:
Take it to a samsung service center and ask them to reset the phone. Tell them its too slow after the latest update using kies. If there is a problem with the motherboard they will report back and replace under warranty.
Else they will install the OS completely new and you can start from scratch to root and install other custom roms.
Click to expand...
Click to collapse
Will my warranty be still active cause my phone is rooted...? Somehow my phone start up this morning but im afraid trying to flash somethink like GB official with odin or somethink like that cause i dont know if it will open again That means that my phone isn't bricked yet cause it's open now? Thanks a lot for help
jonpaslim said:
Try using USB jig to go to download mode, try it first. Jig is not expensive.
Sent from my U1 using xda premium
Click to expand...
Click to collapse
because he tries the jig before it cost anything
bagelismar said:
Will my warranty be still active cause my phone is rooted...? Somehow my phone start up this morning but im afraid trying to flash somethink like GB official with odin or somethink like that cause i dont know if it will open again That means that my phone isn't bricked yet cause it's open now? Thanks a lot for help
Click to expand...
Click to collapse
No it's not bricked. Yes you lose your warranty, but you can unroot your Note. Don't warry Note is so good phone, that you don't need warranty
notko said:
No it's not bricked. Yes you lose your warranty, but you can unroot your Note. Don't warry Note is so good phone, that you don't need warranty
Click to expand...
Click to collapse
Then if it's not bricked why i need to remove the battery for 1 hour and wait an other 2 hours to finally open my phone after a simple turn off? Thats why i want the warranty so i can take the phone to samsung and fix this issue. And im afraid to unroot it cause when ever i try to put my phone on recovery mode its stucks and take for ever to open againm\
Hi, this is my first time using Odin3 and flash the note to jelly bean using the manual way.
But it get stucked during <ID:0/003> factoryfs.img
I cancel everything and now failed to open my note.
I have very limited knowledge in android things, this caused me panic.
I have checked the forum yet still not sure what should i do?
Should i install the old GB version to flash it back...and proceed with JB roms?
Please advice me
Thanks !!!
weihsing01 said:
Hi, this is my first time using Odin3 and flash the note to jelly bean using the manual way.
But it get stucked during <ID:0/003> factoryfs.img
I cancel everything and now failed to open my note.
I have very limited knowledge in android things, this caused me panic.
I have checked the forum yet still not sure what should i do?
Should i install the old GB version to flash it back...and proceed with JB roms?
Please advice me
Thanks !!!
Click to expand...
Click to collapse
Panic is ok now: Stuck at factoryfs.img is a strong hint that you bricked your device.
Read in this thread and try the hints from nokiamode. With the e2fsck the member repaired it.
If this doesn't work read about hg42's workaround (repartition) or replace your motherboard.
ThaiDai said:
Panic is ok now: Stuck at factoryfs.img is a strong hint that you bricked your device.
Read in this thread and try the hints from nokiamode. With the e2fsck the member repaired it.
If this doesn't work read about hg42's workaround (repartition) or replace your motherboard.
Click to expand...
Click to collapse
Thanks, i will try the hint given by nokiamode.
May i know how to boot into recovery?
I'm very depressed
I know the consequences once i play with it, now i have to live with that.
Failed to open boot recovery (volume UP + home + power button )
Dl the zImage file, but while using PDA cannot find the file, please advise...
weihsing01 said:
Thanks, i will try the hint given by nokiamode.
May i know how to boot into recovery?
I'm very depressed
I know the consequences once i play with it, now i have to live with that.
Click to expand...
Click to collapse
Home-Volume Up-Power-Button. Press them and hold for some seconds until you see the recovery.
And next time read and learn before doing things like this.
ThaiDai said:
Home-Volume Up-Power-Button. Press them and hold for some seconds until you see the recovery.
And next time read and learn before doing things like this.
Click to expand...
Click to collapse
Yes, i learned a lesson on this.
Managed to reset using the .tar
but dont understand this few lines..
once detected.. run
adb shell (should give you a #.. if not then use su command)
dd if=/dev/block/mmcblk0p9 of=/dev/null (if the gets stuck or R/W error) then
e2fsck -f -c –y /dev/block/mmcblk0p9 .. let it finish.. if it freezes then follow as ThaiDai says.. if it says fixed damaged blocks then you could try flashing a stock rom again
cant find any option from the recovery option..please advise..
Thanks!
If you not know what adb is and how to install it with the sdk then I think it will be difficult or impossible to do this.
So better first to try to install a stock JB Rom with PC Odin in download mode again
Make a snapshot and show the error here.
ThaiDai said:
If you not know what adb is and how to install it with the sdk then I think it will be difficult or impossible to do this.
So better first to try to install a stock JB Rom with PC Odin in download mode again
Make a snapshot and show the error here.
Click to expand...
Click to collapse
hmm, okay then.
even my phone is bricked, i can install a stock JB room with PC odin in download mode?
Let me give a try!
will provide a snapshot here if there is an error.
Thanks!
Hi,
Installed JB roms successfully.
It running fine now !!
Appreciated ur guidance.
Thank you !!!
You are one lucky guy
Sent from my GT-N7000 using xda app-developers app
KayKrate said:
You are one lucky guy
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes, I'm very lucky.
However, I found out there is bug on the JB roms. Missing SMEMO after i opened it.
Well try reflashing , cause i got it working fine on stock jelly bean Youll experience more problems on the way like overheating and slow performance , Its not the phone or the hardware because im experiencing the same problems on the note 2 with same 4.1.2 jelly bean stock ... Way to go android >.<
Jellybean sucks anyway , ill downgrade to gingerbread later today
Sent from my microwave using the buttons on em'
weihsing01 said:
Yes, I'm very lucky.
However, I found out there is bug on the JB roms. Missing SMEMO after i opened it.
Click to expand...
Click to collapse
No friend. It is not a bug. Smemo merges with snote.
Sent from my GT-N7000 using xda premium
KayKrate said:
Well try reflashing , cause i got it working fine on stock jelly bean Youll experience more problems on the way like overheating and slow performance , Its not the phone or the hardware because im experiencing the same problems on the note 2 with same 4.1.2 jelly bean stock ... Way to go android >.<
Jellybean sucks anyway , ill downgrade to gingerbread later today
Sent from my microwave using the buttons on em'
Click to expand...
Click to collapse
I am yet to feel the overheating, but slow performance is real.
Gingerbread should be more stable but not much feature im looking at