I made a wipe data/factory reset while on CWM Touch (I didn't know about the issues yet) and, of course, it didn't work. So now, everytime I try and flash an Odin ROM (because it doesn't work with the recovery), it gets stuck at data.img/datafs so there's no way I can boot my phone although it does have recovery, download and it gets to the Samsung bootscreen (I flashed a stock ROM).
Has anyone got any ideas on how to fix this? Thanks
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
praetorius said:
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I was on AOSP ICS v04 with the infamous AbyssNote 1.2 kernel (but I don't have the same factoryfs problem as the others) with Touch CWM (that's where the problem comes from I believe) and the only problem is that neither Odin nor CWM can access the /data partition. So a wipe doesn't work.
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
chasmodo said:
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
Click to expand...
Click to collapse
Are you sure? Even though it's never stuck at factoryfs and it only bootloops? Because the problem is I have no service center I can go to so sending it via La Poste (in France) isn't exactly what I'd call safe... Or is there a way to send iut directly to Samsung and get a new one?
Up.............
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Akiainavas said:
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Click to expand...
Click to collapse
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
nico53laval said:
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Click to expand...
Click to collapse
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
no id agree with what the guys have told you, looks like a service center job, did you just flash this recently or were you one of the users who flashed it weeks back, and youve only just attempted a wipe now??
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
graemeg said:
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
Click to expand...
Click to collapse
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
chasmodo said:
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
Click to expand...
Click to collapse
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
Too late ^^ I sent it to a repair center.. But I don't think it would have worked. I already did a wipe on a tock rom with stock recovery and it worked but the phone still couldn't boot.
Akiainavas said:
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
Click to expand...
Click to collapse
The problem is that in France the repair centers have an agreement with Samsung but they're not directly related to Samsung so do you think it'll only be 14 days (even though I might neeed a new mobo or a new phone)?
Not sure how youre postal system works there but make sure you get recorded delivery or france similar so you have proof of posting etc.
Also considering the issue ive read most times lads have had a quick turn around, but who knows, depends how fast samsung receive it, i would suggest UP TO 2 weeks, more likely a week, but then it me be 2 week, depends what they have to do to repair it.
I recently took a phone to the o2 shop to be repaired, i received it back via post 4 days later, that was really fast, and im quite lucky here that theres an abundance of walk in repair centres around the uk, it just made me wonder if there one close to you and would it be economical to take it in person, samsung repair shop where i live if ya take your phone in by hand theyll usually say come back in a couple of hours and then they fix it there and then, that would be better for you because you arent messing around with posting then, i know a lot of countries guys dont have that option but i would have thought france and germany would be similar to the uk as they are both quite large mobile manufacturing countries so my fingers are crossed for you that you can find a quick solution.
No idea mate, but you shouldn't wait more than 2 weeks. The repair will take one hour probably, the rest is testing, posting, filling papers etc.
You'll probably have it back after 1 week or so. So let's hope you'll received it fixed as soon as possible.
nico53laval said:
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
Click to expand...
Click to collapse
Oh, I see. Should've read angelom 1.2 thread first.... sorry
Good luck with service.
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
what stock rom? which version you used?
Related
Please bear with me. I tried posting questions about this in the Q/A forum and received no real help.
I recently went from FRF50 to FRF83 and started getting random reboots. I'm on the 4.06.00.12_07 radio with the stock kernel. I wiped everything before flashing.
Today I wiped again and reflashed FRF50 and everything seemed to be okay aside from maybe 1 reboot.
I just flashed the stock FRF85B and rooted it and I'm back to rebooting. It's even worse now. It reboots the instant everything loads.
I got the last_kmsg:
http://pastebin.org/365407
Please let me know what's wrong. I'm dying to know. Is it hardware? Is it the battery? Am I going to have to pay a buttload of cash for HTC to fix it?
Thanks for any help
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
Is it the wrong forum? Do people at the Q/A or general forum know about kernels/deeper info and do the people who know about that stuff venture over to those forums?
I tried getting info there, and I got none. This is the last place to turn.
What would wiping and starting from stock achieve?
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
S_Dot said:
No excuse for posting in the wrong location. But wipe data, all caches and reflash stock rom + radio. Report in General Section.
Click to expand...
Click to collapse
How will this help me? Okay if stock works, but what about the update?
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Prod1702 said:
Why not maybe looking at using one of the moded versions of the Rom. If those dont work then maybe you need to think of going back to the Stock 2.1 and waiting for OTA to hit your phone. Going back to 2.1 will fix the problem and getting the OTA should work. Other wise wiping and reflashing is all that someone can tell you to do since I know i am using FRF83 right now with no reboots.
Click to expand...
Click to collapse
leonnib4 said:
Just wipe everything inc dalvik-cache
Stock kernel keeps rooting so I guess its a framework issue
Click to expand...
Click to collapse
I'm going to try to go back to stock and see if it works. If not I can only assume that it is a hardware problem and I'll have to bite the bullet and pay for repairs.
What kind of a hardware problem could it be???
Can someone help me get back to stock properly?
See sticky.
Mod move to q&aplease.
leonnib4 said:
See sticky.
Mod move to q&aplease.
Click to expand...
Click to collapse
Sticky is full of bad info. I have new radio (4.06.00.12_07).
I'm assuming that if I get stock radio and the ERD79 update.zip I should be fine?
GldRush98 said:
1) This is the wrong forum and you know it.
2) Wipe everything, start over from stock rom.
Click to expand...
Click to collapse
You sir, are a complete asshole.
Sent from my Nexus One using XDA App
Yes the new radio won't work on 2.1 so change Ur radio and flash that update.zip and cross Ur fingers that Ur problem is fixed good luck let us know
Sent from my Nexus One using XDA App
FML. Hardware issue. Just went through CM 5.0.8. flash from scratch including re-flashing new radio and new recovery and I got a reboot during sign-in to Google.
God ****ing dammit.
Any logcat?
if you have an ext partition.. wipe that as well..
might be a battery issue. my battery had been overheated during navigation and right after boot it would give out turn off and boot again. just replaced it and worked fine.
To check battery issue, I suppose running with charger inserted would be enough.
Jack_R1 said:
To check battery issue, I suppose running with charger inserted would be enough.
Click to expand...
Click to collapse
What do you mean by this?
I'm pretty sure it is the battery. Been keeping minimal use today without USB charging and haven't had a reboot.
Any other ways I can confirm a bad battery?
Sent from my Nexus One using XDA App
If you can successfully boot and use the phone heavily while connected to a charger (preferrably AC charger - it can provide twice the current of USB cable), and you see no reboots - I believe that would point to your battery with a very high probability.
Any ideas?
I have been experimenting with upgrading and down-grading my tab, it now seems that I can't flash any ROM that contains a hidden.rfs, the flash will just stop near the end of flashing the hidden.rfs and never continue, then I have to go through recovery processes to get a working tab back.
I managed to get my Tab back to CPW standard UK JJ3 by dumping the ROM from my other Tab and writing it, I then tried to update with Kies, which also hung at what seems to be exactly the same place.
I have tried repartitioning several times with the p1_add_hidden.pit but it just doesn't seem to work.
Any ideas? Can I check the size of the hidden partition see if that' the problem? Then modify the hidden.rfs to make it smaller so it fits?
Nobody at all got any feedback on this?
Anyone had any luck with this? I'm guessing it's a partitioning issue but it'd be good to know.
alias_neo said:
Nobody at all got any feedback on this?
Click to expand...
Click to collapse
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
rotohammer said:
...use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
Time to upgrade to JMD me thinks
rotohammer said:
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
Roto i wanna ask you something. You say "safely" upgrade why ? Because on your FW's you remove the boot.bin and the SBL.bin ? So that a user wont be able to flash them and something go wrong ?
As far as i know my tab ( A euro one ), is factory unlocked and i will have no problem whatsoever in upgrading the bootloader and the baseband.
Isnt that right ?
sedde said:
Roto i wanna ask you something. You say "safely" upgrade why ? Because on your FW's you remove the boot.bin and the SBL.bin ? So that a user wont be able to flash them and something go wrong ?
As far as i know my tab ( A euro one ), is factory unlocked and i will have no problem whatsoever in upgrading the bootloader and the baseband.
Isnt that right ?
Click to expand...
Click to collapse
Unlocking is unrelated. I say safely because flashing a bootloader is the only thing that makes me squirm. If it fails your device is toast. I never want to give anyone firmware that has the potential to destroy their device. I'd feel bad
daniel.weck said:
Time to upgrade to JMD me thinks
Click to expand...
Click to collapse
Me too : ) maybe tonight after my guests leave.
rotohammer said:
Unlocking is unrelated. I say safely because flashing a bootloader is the only thing that makes me squirm. If it fails your device is toast. I never want to give anyone firmware that has the potential to destroy their device. I'd feel bad
Click to expand...
Click to collapse
And you are so right in removing them...
The leaks from Samsung's servers of JM6/JMA/JMC/JMD flash a signed recovery, after flashing it is impossible to flash unsigned sbl, boot, and zImage. No more downgrade (and possibly upgrade).
rotohammer said:
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
I thought my original post covered this? I can't flash _any_ ROM that uses the hidden partition. I have tried repartitioning a dozen times wit hthe p1_add_hidden.pit, that goes through fine, but NO ROM, full or otherwise, down or up from my current one will successfully complete flashing the "hidden" partition.
alias_neo said:
I thought my original post covered this? I can't flash _any_ ROM that uses the hidden partition.
Click to expand...
Click to collapse
You never mentioned JJ4 or Odin specifically, hence my post. Unless you spell out exactly which firmwares you tried and which software you used to flash with, how can anyone offer assistance?
If you've tried ALL firmware and All flashing software, that leaves only your computer or Tab at fault.
rotohammer said:
You never mentioned JJ4 or Odin specifically, hence my post. Unless you spell out exactly which firmwares you tried and which software you used to flash with, how can anyone offer assistance?
If you've tried ALL firmware and All flashing software, that leaves only your computer or Tab at fault.
Click to expand...
Click to collapse
Im not really worried about my Tab, i just think its a cause for concern that somehow iv stumbled on this problem. If its just the flash in my tab thats damaged its not a problem.
I have tried every firmware available on samfirmware as well as ripping the firmware from an identical tab i have.
Neither Heimdall, Kies nor Odin (either version) would get past flashing hidden and they all stop at about the same point. I have tried flashing various firmware without hidden with no problems. If i then repartition it will flash about 80% of the hidden then just stops.
Problem isnt my pc, i have tried several machines and virtual machines.
I think its a curious problem that would be good to find the cause of.
alias_neo said:
I think its a curious problem that would be good to find the cause of.
Click to expand...
Click to collapse
I agree. Do you have time to jump on irc #ModADroid-Galaxy-Tablet?
rotohammer said:
I agree. Do you have time to jump on irc #ModADroid-Galaxy-Tablet?
Click to expand...
Click to collapse
Cant at the mo, just off out to visit family, xmas and all...
Ill get back to you later tonight?
alias_neo said:
Cant at the mo, just off out to visit family, xmas and all...
Ill get back to you later tonight?
Click to expand...
Click to collapse
Sure, we're about to get a blizzard on the east coast of the US, so I may be cancelling my family visiting plans. Just ping me later.
rotohammer said:
Sure, we're about to get a blizzard on the east coast of the US, so I may be cancelling my family visiting plans. Just ping me later.
Click to expand...
Click to collapse
I'm around and will hop on the channel now. Don't have too long but maybe we can look into this a bit.
I just noticed what has veen going on with tje secured boot loaders etc. I will check mine with the script once I get home from my trip tomorrow to see if any info froem my tab is relevent to fixing the problem. I noticed a mention of creating jigs, im not sure what hardware is required but I have a couple of usb-rs232 connectors on order for an unrelated project so if it requires the same hardware I can put a spare one to use and build a jtag/jig cable for the tab and see if I can help the cause.
Sent from my GT-P1000 using XDA App
Question for rotohammer
Once upon a time I bricked my Verizon Galaxy Tab trying to flash a custom ROM, the only way I could bring it back was by using Odin and flashing the hidden pit. Now every time I install the original verizon rom my tab is extremely, extremely slow. I have been trying to reformat and wipe clean to start over, but I haven't had any luck.
Any suggestions on how to: either flash the right pit on it or remove the hidden partition? Anything I can do to bring my tab to full speed. I have also tried the overclocked rom with voodoo5, and at this point anything I put there is extremely slow. The only way I can get it to operate normally (Kind of) is to flash the Honeycomb Alpha rom, then restore to a day when it was working fine, however this breaks my auto rotate sensor.
That is how I use it now a days, but it sucks that I cannot use it on landscape mode.
Any help will be greatly appreciated.
Follow up from my previous question to rotohammer
By the way, just in case you were wondering, the rom I flashed to unbrick it was a GSM ROM, that was the only way to make it past the Samsung logo.
So, my theory is that I have problems with it because now I am trying to flash CDMA roms to a GSM partition/files system? Excuse me if my post does not make much sense or I am using the wrong terminology, I am extremely new a this. I just know enough to get myself in trouble.
Thank you again for any help.
I've encountered the same problem as the original poster. SGT with CPW CSC causes problems with the hidden.rfs when trying to flash ROMs. Does appear to be a size issue with the hidden partition - I wonder whether this has been sized incorrectly when it was originally flashed as re-partitioning doesn't help. I'm currently on a XEU ROM so I guess I'll find out when Gingerbread is officially released whether I can flash that or not. If not, I think it'll need to the internal SD card repartitioning.
Anyone got any tips on how to do this?
I have a note here...its bricked, the owner tried flashing angelrom ICS, and bricked it.
It gets stuck when it starts writing factoryfs.img.
I have tried properly repartitioning it, installed a stock bootloader from a gt-n7000 stock rom, and that at least allowed me to get back into android system recovery. I wiped the data and cache and tried again.
I tried a stock rom that had multiple parts, and one that had the individual parts. I can flash all of the individual parts successfully but the PDA.
Anybody encounter this, and know a fix? I would really appreciate any tips or suggestions.
Just wanted to give some more information. I followed Ketan's guide to flash to stock rom, and tried multiple stock roms with the same results.
So I also tried repartioning with the proper pit file (the 16gb n7000) and that didn't work.
The only bootloader I could seem to find (because that was the next logical step to me) was "KERNEL_N7000XXKJ1_CL627135_REV02_eng_mid_ship.tar.md5" , would that be compatible with all stock roms or just a specific one?
I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
There isn't anything one can do if you flashed that kernel. If you have warranty head to Samsung service.
Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.
anilisanil said:
I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
Click to expand...
Click to collapse
chasmodo said:
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
+1
Sorry, it seems You have no option but to go service centre.
chasmodo said:
Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
How the duck is that physically possible? What an enormous embarrassment for angelom. I doubt hell ever post another kernel again...
Sent from my superior GT-N7000 using Tapatalk
Yeah...I figured it was beyond hope after reading through a lot of the threads....
I did reset the counter with a jig, and took away the yellow triangle...but I was told samsung won't warranty this model in the USA.
Thanks for your replies!
Just a little query. Whats the actual physics behind this? Like how can some software fry the drive? Just a little interested and wondered how it actually physically happened. Because my assumption before all this was that it cant be truly completely bricked (obviously i was wrong). but wondering how!
Sent from my GT-N7000 using Tapatalk
Hey i'm one dumb guy who managed to brick his Galaxy Note...
I received the ICS Update OTA yesterday, i discovered later that i what on the LPY kernel. Then i though it doesn't matter cause i didn't need to flash any rom because the stock gingerbread was perfectly fine for me.
But the update made my phone (had it for only 2weeks) painfull to use. FC all the time etc... Couldn't do a factory reset because of all the warning over here...
So i flashed the franco Kernel wich was to my knowledge a "safe kernel", then i tried to install the Kingdroid Rom, after all 3 wipe. Wich lead me to brick... I've waited 25 minute for the phone to boot up but nothing... So i tried to restore my backup ok ICS that didn't go well either.
After that i tried to flash trough Odin a Gingerbread Rom, before doing so i've read multiple Guides et threads. Odin got stuck at factoryfs.img every time.
So i did some search and achieved to go through this guide: http://forum.xda-developers.com/showthread.php?p=26285877#post26285877
I went through the process. And i tried to flash a CM9 rom through recovery as the guy recommends. But i'm still stuck on the Galaxy Note bootscreen.
I believe you guys can help me, i still have access to recovery et Download mode.
I believed i wasn't a Noob since My HD2 i've had numerous phone and rooted\flashed countless roms on HTC/Samsung/Motorola/Sony Ericsson phones... In the end i'm finally juste one big noob...
Thanks for those who will help me, and even take some time to read this.
First thing you should do is check other threads about that around here.
If you can get it into download mode, you could give flashing with Odin a try. If it doesn't get stuck at factory.fs, then you're not superbricked.
If it does get stuck, then you have 2 more hopes:
- HOPE 1
- HOPE 2
If those don't work either...I'm afraid it's off to the Samsung Service center for a shiny new motherboard.
Best of luck to you and hope you get your Note up and running as soon as possible...
The problem is My flash count is at 3 and i have the big yellow logo...
Atomos33 said:
The problem is My flash count is at 3 and i have the big yellow logo...
Click to expand...
Click to collapse
First try to revive your phone, after that this will fix your triangle/flash counter http://forum.xda-developers.com/showthread.php?t=1354888
Atomos33 said:
The problem is My flash count is at 3 and i have the big yellow logo...
Click to expand...
Click to collapse
If we revive your phone, that's easily sorted.
If we don't, you can make it so that the service center can't really tell.
Right now i am trying to install Rocket Rom after installing, Abyss kernel 4.2 and doing a Full wipe. Waiting for the installation.
Edit: Got through the process after two days. It just took me to write this. And tired the whole process once again desperatly and it worked... Can't believe it...
Android.process just keep crashing what should i do ?
Full wipe? Kinda scared now ^^'
Atomos33 said:
Right now i am trying to install Rocket Rom after installing, Abyss kernel 4.2 and doing a Full wipe. Waiting for the installation.
Edit: Got through the process after two days. It just took me to write this. And tired the whole process once again desperatly and it worked... Can't believe it...
Android.process just keep crashing what should i do ?
Full wipe? Kinda scared now ^^'
Click to expand...
Click to collapse
Wow. You're pretty safe now mate, I guess.
If you're on RocketRom, you can full-wipe, no worries...maybe flash Abyss and reboot recovery and wipe with that, just to be ultra-sure.
You should be clear of any damaging kernels.
------
LE: Did it work...? You're welcome...?
Haha sorry was late yesterday, i didn't do anything went straight to get some sleep ^^'
I really wanted to thank you guys! I'm sorry if you tought i forgot you...
Well i didn't change the rom neither did i wipe anything. Juste went to work this morning so...
I think i am going to change the Rom the battery consumption is to damn high... Was at 100% this morning and i'm already at 30%...
So it worked my Note is saved! I've tried the link in the OP (And your Hope 1 ^^') a second time flashed Abyss kernel, then flashed Rocket Rom.
The flashing took 10minutes so for the people who went through this wait!
And the first boot took 5 minute.
Once again big big thank to Eug3n91 and Gee2012 been around here for long and this has been one of the best response time ever!
HERE is easy way to fix bricked N7000...
http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
ingbrzy said:
HERE is easy way to fix bricked N7000...
http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
Click to expand...
Click to collapse
That's not an easy brick fix, that's a tutorial on how to use PCO to flash GB with repartition.
In other words, useless.
In the comment section of the website, quite a few people recovered, so not as useless as it seems!
Sent from my GT-N7000
Atomos33 said:
Haha sorry was late yesterday, i didn't do anything went straight to get some sleep ^^'
I really wanted to thank you guys! I'm sorry if you tought i forgot you...
Well i didn't change the rom neither did i wipe anything. Juste went to work this morning so...
I think i am going to change the Rom the battery consumption is to damn high... Was at 100% this morning and i'm already at 30%...
So it worked my Note is saved! I've tried the link in the OP (And your Hope 1 ^^') a second time flashed Abyss kernel, then flashed Rocket Rom.
The flashing took 10minutes so for the people who went through this wait!
And the first boot took 5 minute.
Once again big big thank to Eug3n91 and Gee2012 been around here for long and this has been one of the best response time ever!
Click to expand...
Click to collapse
So, you are back up and everything I'm gathering, correct?
And, also, from what I gather in your OP, you flashed/wiped with Franco kernel? It shouldn't cause bricks and I'm glad it ended up not "bricking" your phone because so far I don't think it has bricked anything.
Stay clear of anything stock from now on and I highly recommend sticking to CM9 kernel/ROMs. They are smooth, safe, efficient, etc.
Atomos33 said:
Haha sorry was late yesterday, i didn't do anything went straight to get some sleep ^^'
I really wanted to thank you guys! I'm sorry if you tought i forgot you...
Well i didn't change the rom neither did i wipe anything. Juste went to work this morning so...
I think i am going to change the Rom the battery consumption is to damn high... Was at 100% this morning and i'm already at 30%...
So it worked my Note is saved! I've tried the link in the OP (And your Hope 1 ^^') a second time flashed Abyss kernel, then flashed Rocket Rom.
The flashing took 10minutes so for the people who went through this wait!
And the first boot took 5 minute.
Once again big big thank to Eug3n91 and Gee2012 been around here for long and this has been one of the best response time ever!
Click to expand...
Click to collapse
My pleasure! Sorry I got impatient. Was a bit anxious and...well...to be honest...these methods haven't always gone the same for everyone. Glad you were in luck!
Enjoy your Note!
Guess what it worked to recover my note but i tried a Wipe after it died. Once again i flashed abyss kernel and then the abyss kernel just never booted...
So i tried to flash via Odin didn't either... And then it's just dead... I have access to recovery trought pda4 kernel flahed with Odin.
I don't know if i want to re format re partion everything through ADB...
I'm without phone since yesterday... My case seems to be different.
As you said the Franco kernel wasn't supposed to brick my phone but every single move i try to make it seems to kill it...
Had one day without hassle. Worst phone i had.
Edit @Andreww88: i swear it was bricked i wiped everything and installed the Kingdroid Rom never went through. So i just went back to recovery and flashed bac the Stock rom and then nothing. Just nothing Odin, couldn't do anything.
Edit2: So i've done everything again it's working again on paranoid rom! I'm kinda frustrated on CM9 i have no codecs, the lockscreen is not Note-adapted, and the Stylus is of no use...
Edit3: Can anyone help me getting back to a Stock rom without using Odin?
I'm sorry for the double post but can someone tell me if the Odin Mobile will work even if the Odin desktop doesn't work?
Atomos33 said:
I'm sorry for the double post but can someone tell me if the Odin Mobile will work even if the Odin desktop doesn't work?
Click to expand...
Click to collapse
Unfortunately, no.
Congrats for unbricking your note
Its like a Motivational story .
I was also softbricked my Note many times. But managed to unbrick always.
Moral of the story....
Our not is hard to brick if we will not give up..
Because
Winners never quit.... quitters never win
I've sent it back to the repair center. After cyanogen worked, i've used Triangle Away to reset flash counter. Flashed a stock rom. It didn't go well as exepted.
When i sent the phone it had no triangle no flash counter and of course no custom rom!
So as chintamanijaipuri (As Indian i found it very hard to write ^^') said never give up!
Use the link in the OP and flash Cyanogen mod trought recovery. Use the recovery of that thread for me it worked well, Abyss kernel on top didn't work for me. Once you boot cyanogen use triangle away, and Flash a stock rom that will brick your Note in good way, (Without Triangle, flash counter, custom recovery) so it will never be your fault!
Good Luck thanks everybody!
Hi,
I have got my Gnote super bricked and I used pit file method to revive it but now these freezes are killing me. I have bought it 9 months ago from mediamarkt in Germany.
Do you think they will accept it now? I mean it is working but every several hours it freezes. What should I tell them about the problem?
I revived my note using the pit files but it isn't giving me problems as you say
I really have no idea where these freezes are coming from. I think sooner or later I should give it for warranty
have you tried already doing the 3 wipes on your phone in CWMR?
if you have tried it already and still getting the hangups on it.. my reasonable suggestion is.... just BORK it more. I mean what have you got to lose if Samsung can't boot your phone anymore right? No more explanations to them other than your phone got toasted when you tried to update via KIES....
end of discussion.
ashkan_mc said:
I really have no idea where these freezes are coming from. I think sooner or later I should give it for warranty
Click to expand...
Click to collapse
As long as the binary counter is set to 0 and there's no yellow triangle you should be able to take it to warranty. Of course unroot it first and leave no trace of any customization.
So I'd they ask you what's the problem with your note what shall you say?
letters_to_cleo said:
have you tried already doing the 3 wipes on your phone in CWMR?
if you have tried it already and still getting the hangups on it.. my reasonable suggestion is.... just BORK it more. I mean what have you got to lose if Samsung can't boot your phone anymore right? No more explanations to them other than your phone got toasted when you tried to update via KIES....
end of discussion.
Click to expand...
Click to collapse
You mean again I try to make it bricked? Just like the last time or with another method? Can they find out I did it deliberately?
The problem is now my internal sd is showing 9.33 GB and if they dig in more, they will find out what I have done to it.
Of course samsung is responsible for this matter cause it is they fault not mine.
Now my phone is unroot and has official LRQ on it.
ashkan_mc said:
You mean again I try to make it bricked? Just like the last time or with another method? Can they find out I did it deliberately?
The problem is now my internal sd is showing 9.33 GB and if they dig in more, they will find out what I have done to it.
Of course samsung is responsible for this matter cause it is they fault not mine.
Now my phone is unroot and has official LRQ on it.
Click to expand...
Click to collapse
Yeah sure why not... I mean it may seem ridiculous to advice you this but bricked it back until you can't turn it back on again. I know most other users before who have bricked their phone big time (can't boot up their phone anymore) and they've return it back to Sammy to have the mobo replace. No questions asked. If they try to ask you what you did.. just give them an innocent smuck and say.. "My phone's not turning ON after I tried to update it thru Kies. I dunno what's the problem with it." Give them a casual after stupid innocent look. Most likely they won't drill you anymore.
letters_to_cleo said:
Yeah sure why not... I mean it may seem ridiculous to advice you this but bricked it back until you can't turn it back on again. I know most other users before who have bricked their phone big time (can't boot up their phone anymore) and they've return it back to Sammy to have the mobo replace. No questions asked. If they try to ask you what you did.. just give them an innocent smuck and say.. "My phone's not turning ON after I tried to update it thru Kies. I dunno what's the problem with it." Give them a casual after stupid innocent look. Most likely they won't drill you anymore.
Click to expand...
Click to collapse
Do they give a new phone or just replace its motherboard?
And btw what did you mean by 3 wipes? I did not wipe the whole internal and external sd though
Thanks alot
ashkan_mc said:
Do they give a new phone or just replace its motherboard?
And btw what did you mean by 3 wipes? I did not wipe the whole internal and external sd though
Thanks alot
Click to expand...
Click to collapse
No, they're just going to replace your motherboard.
3 wipes is Wipe DATA, Wipe Cache Partition and Wipe Dalvik... all of these are in CWMR (if your still able to boot in recovery).
hmm, on a lighter point, before you begin the steps above(if you would like to try though), try to format your external SD card and try to place it back again to your phone. See if you still have the hangups.. If you do have it still, then go with the 3 wipes I mentioned above.
letters_to_cleo said:
No, they're just going to replace your motherboard.
3 wipes is Wipe DATA, Wipe Cache Partition and Wipe Dalvik... all of these are in CWMR (if your still able to boot in recovery).
hmm, on a lighter point, before you begin the steps above(if you would like to try though), try to format your external SD card and try to place it back again to your phone. See if you still have the hangups.. If you do have it still, then go with the 3 wipes I mentioned above.
Click to expand...
Click to collapse
If I try to get it bricked and mediamarkt in germany won't accept it, is it possible that I revive it with pit file method again?
Like I've said..skip the 3 wipes for now and just format first your SD card and see if the hangups wouldn't be there after.
If it's not there anymore then GOOD.. if it's still there, then you do the 3 wipes. I would assume your already using a safe kernel already right?
letters_to_cleo said:
Like I've said..skip the 3 wipes for now and just format first your SD card and see if the hangups wouldn't be there after.
If it's not there anymore then GOOD.. if it's still there, then you do the 3 wipes. I would assume your already using a safe kernel already right?
Click to expand...
Click to collapse
I did use hydracore kernel for a while but with that I had freeze more. Now I am in unroot condition with stock kernel. So I can not do the 3 wipes now.
I will try to remove my external sd card and see without that what is gonna be ...
sure, just post back later on your results.
I did all kinds of wipes and formats but again freeze don't know what to do
Well, it's apparent that your phone's boot partition has some bad sectors on it still. That's why everytime your phone reads those particular bad sectors.. it freezes itself up.
try to repartition your phone back to remove those bad sectors or you can try the link here http://www.alliance-rom.com/communi...-superbricked-stage-from-ics-kernel-bug.8018/ , as your reference to remove those bad sectors and scan for possible partition errors as well.
letters_to_cleo said:
Well, it's apparent that your phone's boot partition has some bad sectors on it still. That's why everytime your phone reads those particular bad sectors.. it freezes itself up.
try to repartition your phone back to remove those bad sectors or you can try the link here http://www.alliance-rom.com/communi...-superbricked-stage-from-ics-kernel-bug.8018/ , as your reference to remove those bad sectors and scan for possible partition errors as well.
Click to expand...
Click to collapse
I have tried this thread before ... The one which belongs to forest1971 ... Again nothing ...
Mate best thing is return to gb stock with counter 0... ensure everything is stock... give the mobile to ur girlfriend and ask her to take it to sammy center...
Ull get the replacement for sure... tell them updating from kies did this...
Why GB? If it would be ICS it has problem? I mean I want to tell them that I was on LRK and I updated it to LRQ via Kies and then my phone got bricked. Do you think it is ok? GF idea is perfect
ashkan_mc said:
Why GB? If it would be ICS it has problem? I mean I want to tell them that I was on LRK and I updated it to LRQ via Kies and then my phone got bricked. Do you think it is ok? GF idea is perfect
Click to expand...
Click to collapse
Bro u have already revived ur mobile... so best thing to do is take it sammy and tell them that ur mobile lags a lot and u have some lost space on ur memory card... (play innocent).... they'll check it and replace ur mobo if needed... so doesnt matter if u r on gb or ics