Related
0.00 internal storage and the external reads 0. I have flashed every Odin file I could find, tried the heimdall one click. Nothing is working. Any ideas? I promised the phone to my father in law and he is in town for the weekend.
Sent from my Triumph using xda premium
Wow have you tried Eugene Froyo umm no brick rom? Also have you tried to partition the phone?
Sent from my GT-I9000 using Tapatalk
iwillkillyou said:
Wow have you tried Eugene Froyo umm no brick rom? Also have you tried to partition the phone?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Sure did. About 59 times already lol. Repartition has no effect.
Sent from my Triumph using xda premium
Hmm how about making your phone soft brick, then use odin.
Sent from my GT-I9000 using Tapatalk
I don't really know, but here are some ideas.
Did you disable voodoo lagfix?
Try "eugenes froyo that doesn't brick" for the 60th time.
On ODIN put a check mark next to Re-Partition, but you said that had no effect.
Hmmmmmm, I bet eugene knows the answer. I feel like there is a thread somewhere that discusses this issue.
If you figure it out, let us know!
SamsungVibrant said:
I don't really know, but here are some ideas.
Did you disable voodoo lagfix?
Try "eugenes froyo that doesn't brick" for the 60th time.
On ODIN put a check mark next to Re-Partition, but you said that had no effect.
Hmmmmmm, I bet eugene knows the answer. I feel like there is a thread somewhere that discusses this issue.
If you figure it out, let us know!
Click to expand...
Click to collapse
I was on cm7. No voodoo. I didn't have a SD in the phone and plugged it in for mass storage. Upon realizing that, I popped one in with the phone still connected. That's when I noticed the problem. I haven't been using my phone. I Odin'd from cm7 weeks ago and didn't touch the phone until I plugged it in for mass storage.
Sent from my Triumph using xda premium
Bump it up. Still stuck.
Sent from my MOTWX435KT using xda premium
maybe the information in this post will help?
http://forum.cyanogenmod.com/topic/...ternal-storage/page__view__findpost__p__67870
Take a look at this, not sure if it's the same thing as that on cyanogenmod link above:
http://forum.xda-developers.com/showthread.php?t=1230059
I hope this will help
I had the same issue when I was coming back to a froyo rom from CM 7.1, I did everything you did flashed froyo that didn't brick and nothing so this is what I did I used Odin JI6 file from this thread ODIN JI6 and the zip comes with ODIN 1.3, 512 PIT,T959UVJI6.TAR. I used that version of odin 1.3 to flash JI6 tar and pit files and checked re partition, when it rebooted it was stuck at the factory recovery so I pulled the battery, held vol up vol down and plugged in the usb cord to get back into download mode. Now I opened ODIN 1.7(DL LINK) and flashed froyo that doesn't brick also check re partition when it re boots it will go into a boot loop you know this, so THEN yes one more odin I kept the same version of odin open 1.7 and I flashed Eugene_2E_JK2_Froyo.zip also with re partition checked. After all this I was still having issues with market then I cleared market catch installed trigger rom and now I can install apps again I would like to tell you the three odins was unnecessary but it wasn't until odin with JI6 that now my phone work right as for CM roms I never have one issue flashing then but if I want to revert back to a 2.2 rom it's a all day event hope this helps
EDIT LOL try the two peoples above me^^^ method first they seem to be on the right track ^^^
Also noticed that when I flash JFD, I get no errors(datadata, sd card, mmcblk0) in recovery after it boots from odin. The catch is, it goes black after the boot animation. Only the soft keys will light up. Really super stumped. Adb wont see my phone, so its making it really hard to manually repartition the internal storage. I have never been a adb wiz.
I thought you got this fixed?
Br1cK'd said:
I thought you got this fixed?
Click to expand...
Click to collapse
Negative Ghostrider I thought I did. But no dice.
Well damn. Have you tried different versions of Odin? What about a Voodoo kernel and conversion, any difference? There is something I remember reading a while back about an issue like this, I don't remember exactly what it said, but I'll try to find it for you.
Sent from my ZenDroid, meditating on the XDA App
I can't find the thread I was thinking of, sorry. I was thinking that your issue here sounds very similar to when people had done the partitioning via rom manager/cwm. Perhaps fixes for that will lead you in the right direction.
Sent from my ZenDroid, meditating on the XDA App
Update:
Still no luck. But after screwing with it, it now says I have a damaged internal SD, doest say blank internal SD anymore. I think that the phone is all done : (
Sent from my MOTWX435KT using xda premium
Dan_Brutal said:
Update:
Still no luck. But after screwing with it, it now says I have a damaged internal SD, doest say blank internal SD anymore. I think that the phone is all done : (
Sent from my MOTWX435KT using xda premium
Click to expand...
Click to collapse
format the sd card
laylovj said:
format the sd card
Click to expand...
Click to collapse
Doesn't work. If there was a actual/physical button for it, I would have worn it out already haha.
Sent from my MOTWX435KT using xda premium
Dan, sounds like it's time for a new Galaxy S2!
Vibrantnew-b said:
Dan, sounds like it's time for a new Galaxy S2!
Click to expand...
Click to collapse
Sure does. Im going to jump on the new T-Mobile pre-paid plan. $70 a month for unlimited everything with 5gb of 4g speed before they throttle you. Use my old ass G1 until I either get a sgs2 or a prime.
I was reading a thread about the storage issue(http://forum.xda-developers.com/showthread.php?t=957615), and Im 300% sure that the phone is ****ed. I think I roasted the internal storage completely. A true brick. Do I get a cookie for bricking the un-brickable?
Does anybody knows how to fix it, guys ?!
You have to flash a custom kernel with clockworkmod recovery integrated..
Sent from my GT-I9100 using XDA App
supermult said:
You have to flash a custom kernel with clockworkmod recovery integrated..
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I understand that i must forget, having the original recovery mode restored !
I understand what your saying dude... its a seriously annoying bug that doesn't get talked about.
Sent from my GT-I9100 using xda premium
From previous thread i've read, my phone is partially destroyed !
But you've said it, this one bug for which noone talks about !
not sure if you've solved this but...
my epic 4g tough is in the same mode and my pc wont detect it as a USB device
therefore i cant flash back to stock.
I learned from a tech guy at a cell shop near my house that if you put the stock tar file on an sd card and name it 'update.zip'
the phone will automatically recover using it.
Im preparing my sd card now and I'll post my results.
I don't get what if ur saying but if u can't use USB then useobile Odin to flash cf root and then u have cwm recovery
Sent from my GT-I9100 using Tapatalk
I am having bootloop problem with my galaxy note n7000
I had stock LP8 version of ICS before. I rooted it using cf-root cwm v5.5. I took a nandroid backup of my rom. And then used triangle away app to remove the triangle. It went to special boot mode and resetted my counter.
I tried formatting my phone from clockwork recovery but failed to do so as it seemed to stuck there for long. I switched it on and restarted it went into bootloop showing galaxy note again and again.
I went ahead and flashed LP8 rom via odin. It didnt seemed to help as it was stuck again in bootloop. Tried factory wipe from stock recovery and cache wipe. Still no respite.
I thought rom was buggy and went ahead and flashed gb KK1 rom via odin. But still it didnt helped and i am stuck in the bootloop.
Please help me. Also it shows custom count as 'no' and binary as
'Samsung official'. Does it means I can claim warranty?
Sorry for the long post, but it was my first post and wanted to put all details. Please help me.
Sent from my GT-I9100 using xda app-developers app
aziz981 said:
I am having bootloop problem with my galaxy note n7000
I had stock LP8 version of ICS before. I rooted it using cf-root cwm v5.5. I took a nandroid backup of my rom. And then used triangle away app to remove the triangle. It went to special boot mode and resetted my counter.
I tried formatting my phone from clockwork recovery but failed to do so as it seemed to stuck there for long. I switched it on and restarted it went into bootloop showing galaxy note again and again.
I went ahead and flashed LP8 rom via odin. It didnt seemed to help as it was stuck again in bootloop. Tried factory wipe from stock recovery and cache wipe. Still no respite.
phone now , whats showing on the screen
I thought rom was buggy and went ahead and flashed gb KK1 rom via odin. But still it didnt helped and i am stuck in the bootloop.
Please help me. Also it shows custom count as 'no' and binary as
'Samsung official'. Does it means I can claim warranty?
Sorry for the long post, but it was my first post and wanted to put all details. Please help me.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
pretty sure cf-root v5.6 has the possible fix , 5.5 doesnt , so you have more than likely bricked your phone ( did you read any of the warnings before you started flashing...there are several of them) what is the situation with your phone now , whats showing on the screen? can you go into download mode , also there is an app for checking your emmc condition see if it passes that first http://forum.xda-developers.com/showthread.php?t=1709054
Flash stock Gingerbread firmware then factory reset from recovery
DO NOT perform factory reset on stock ICS kernel or CF-Root 5.5
----
If it is not yet superbricked phone won't stuck at flashing firmware.
My phone is still able to go into stock recovery and downloading mode. And flashing via odin, it completes normally and reboots. But then bootloops. About you suggesting emmc phase check, will search abou it. Thanks for advice.
Sent from my GT-I9100 using xda app-developers app
Boy124 said:
Flash stock Gingerbread firmware then factory reset from recovery
DO NOT perform factory reset on stock ICS kernel or CF-Root 5.5
----
If it is not yet superbricked phone won't stuck at flashing firmware.
Click to expand...
Click to collapse
I think i made that mistake before. I was on ICS kernel and cwm 5.5. And i did a factory reset. I never thought it would be a problem. Should have researched more. But please help me. Is there a workaround for this?
And flashing via odin completes normally.
Sent from my GT-I9100 using xda app-developers app
aziz981 said:
My phone is still able to go into stock recovery and downloading mode. And flashing via odin, it completes normally and reboots. But then bootloops. About you suggesting emmc phase check, will search abou it. Thanks for advice.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If flashing succeeds, then do not worry.
As I said flash stock gingerbread rom then factory reset from recovery.
And use only safe kernels on ICS.
Safe kernels:
CF-Root 5.6 Safe but do not use it to flash roms
Franco kernel R3 and above
SpeedMod kernel
Goku kernel
NoteCore Kernel
DAFUQ kernel
Boy124 said:
If flashing succeeds, then do not worry.
As I said flash stock gingerbread rom then factory reset from recovery.
And use only safe kernels on ICS.
Safe kernels:
CF-Root 5.6 Safe but do not use it to flash roms
Franco kernel R3 and above
SpeedMod kernel
Goku kernel
NoteCore Kernel
DAFUQ kernel
Click to expand...
Click to collapse
I did flash my regional stock kernel xxkk1 via odin and did factory reset too from stock recovery. But still bootloops. Do i have to flash any of the kernel above seperately? The question might seem stupid, but tell me if i got it right.. 1. Flash stock kernel 2. Factory reset 3. Flash one of the above said kernels
Sent from my GT-I9100 using xda app-developers app
Flash stock gingerbread rom with pc odin.
If it succeeds, boot into recovery (volume up + home key + power button)
then select factory reset.
then reboot.
----
The kernels I mentioned in the previous post are ICS kernels. Do not use those on gingernread.
Boy124 said:
Flash stock gingerbread rom with pc odin.
If it succeeds, boot into recovery (volume up + home key + power button)
then select factory reset.
then reboot.
----
The kernels I mentioned in the previous post are ICS kernels. Do not use those on gingernread.
Click to expand...
Click to collapse
I already did as u said word to word. I flashed stock gb rom, succeeds in flashing, wiped factory data reset goes into bootloop. The galaxy note logo keeps appearing. Not once i flashed that twice. With same steps.
Sent from my GT-I9100 using xda app-developers app
aziz981 said:
I already did as u said word to word. I flashed stock gb rom, succeeds in flashing, wiped factory data reset goes into bootloop. The galaxy note logo keeps appearing. Not once i flashed that twice. With same steps.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I am sorry. I really do not know what is wrong.
It does not sound like superbrick though.
Wait till experts help you with this problem, good luck.
I read this post http://forum.xda-developers.com/showthread.php?t=1633943
and have realized that i have bricked my phone.
Because i attempted a factory wipe on unsafe official kernel and recovery cwm 5.5.
It corrupted a drive and is hardbricked.
However is there any workaround? My recovery and downloading mode both are working.
Again summarizing
1. on official kernel rooted with cf-5.5
2. Attempted factory wipe from recovery - stuck and restarting stuck in bootloop
3. Flashed the official ics kernel again - no boot up, went to recovery wiped, still stuck at logo
4. Flashed an old gb official kernel, still stuck at logo.
Is there anything i can do? Or my SGN is as good as dead?
aziz981 said:
I read this post http://forum.xda-developers.com/showthread.php?t=1633943
and have realized that i have bricked my phone.
Because i attempted a factory wipe on unsafe official kernel and recovery cwm 5.5.
It corrupted a drive and is hardbricked.
However is there any workaround? My recovery and downloading mode both are working.
Again summarizing
1. on official kernel rooted with cf-5.5
2. Attempted factory wipe from recovery - stuck and restarting stuck in bootloop
3. Flashed the official ics kernel again - no boot up, went to recovery wiped, still stuck at logo
4. Flashed an old gb official kernel, still stuck at logo.
Is there anything i can do? Or my SGN is as good as dead?
Click to expand...
Click to collapse
There are threads on getting it working again with the use of pit files and partitioning etc but you may end up with hardly any storage left and might still not be usable.either take it in to Samsung service center or send it in and tell them you had an ota update and it never rebooted or say you did a factory reset as your phone was acting up..Don't tell them any thing about rooting or roms... it was on stock .you get me! They will change your mobo for free then mate
@denny said:
There are threads on getting it working again with the use of pit files and partitioning etc but you may end up with hardly any storage left and might still not be usable.either take it in to Samsung service center or send it in and tell them you had an ota update and it never rebooted or say you did a factory reset as your phone was acting up..Don't tell them any thing about rooting or roms... it was on stock .you get me! They will change your mobo for free then mate
Click to expand...
Click to collapse
Yes, thanks for the tip mate.
I was planning to do the same and that too today. Also the counter says no and binary as samsung official on the downloading mode. This means they can never know if it was rooted? Am i correct? Just this last question. Thanks for your replies. They were helpful..
Sent from my GT-I9100 using xda app-developers app
aziz981 said:
Yes, thanks for the tip mate.
I was planning to do the same and that too today. Also the counter says no and binary as samsung official on the downloading mode. This means they can never know if it was rooted? Am i correct? Just this last question. Thanks for your replies. They were helpful..
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
No yellow triangle, counter is zero, custom binary says NO, can't boot up => there's no way to check if it was rooted.
kopitalk said:
No yellow triangle, counter is zero, custom binary says NO, can't boot up => there's no way to check if it was rooted.
Click to expand...
Click to collapse
Yup all true. Puts asides my worries...
Sent from my GT-I9100 using xda app-developers app
I've done something similar to my note, despite flashing stock gb etc through odin (which goes through with no errors etc..) i'm still stuck at the galaxy note startup screen. If i try an ICS stock rom it'll go a little further to the samsung startup logo/jingle and then sits there.
is there nothing that can be done at this point?
my binary count is 4 now so i'm guessing i will have to pay samsung to get it resolved if it is indeed bricked, does anyone know who much this is likely to cost?
also, is there a way of determining for sure if my phone is bricked/caught he emmc bug?.
thanks all in advance, i spent hours and hours trying to get my phone back so i'm pretty deperate now.
aziz981 said:
Yup all true. Puts asides my worries...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
that what happen to my note as well .... i did not read carefully and preform the full wipe and superbrick my note and use the same excuse saying OTA update to 4.0 and after it reboot i got my phone brick
samsung refuse to give me warranty on it as in my recovery screen i have a something like a "phone . . yellow exclamation . . monitor" and stated firmware upgrade encountered an issue. please select recover mode in kies & try again "
You had a binary counter and the custom firmware yellow triangle it seems :-(. That explains it, it is an indicator that you flashed unofficial firmware to your phone and voided the warranty
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Markuzy said:
You had a binary counter and the custom firmware yellow triangle it seems :-(. That explains it, it is an indicator that you flashed unofficial firmware to your phone and voided the warranty
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
in download mode ... my binary counter is zero and no yellow triangle ...
Russc73 said:
I've done something similar to my note, despite flashing stock gb etc through odin (which goes through with no errors etc..) i'm still stuck at the galaxy note startup screen. If i try an ICS stock rom it'll go a little further to the samsung startup logo/jingle and then sits there.
is there nothing that can be done at this point?
my binary count is 4 now so i'm guessing i will have to pay samsung to get it resolved if it is indeed bricked, does anyone know who much this is likely to cost?
also, is there a way of determining for sure if my phone is bricked/caught he emmc bug?.
thanks all in advance, i spent hours and hours trying to get my phone back so i'm pretty deperate now.
Click to expand...
Click to collapse
Ur note is pretty much hosed. U had the exact same issue that i had. But samsung replaced my motherboard for free as counter was zero. Now they can replace the mobo.. and the associted cost with it.
Are u sure it is hardbricked, have u tried jtag usb jig to recover it back? It may not work..but worth a try
Sent from my GT-I9100 using xda app-developers app
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not be able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
altae said:
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
Click to expand...
Click to collapse
I have never considered the "hex-patched" kernels to be safe...
jeriz said:
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
Click to expand...
Click to collapse
Yep. I don't think the drivers are the problem since the phone is recognized. But it does not start to flash. It simply does nothing and the phone stays in download mode forever.
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
this in itself is a huge statement
altae said:
I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash.
Click to expand...
Click to collapse
This is diferent... not even start to flash...
Sent from my GT-P3110 using Tapatalk 2
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
It seems that remaining on Gingerbread (until official JB) for the moment is the best thing for people who do not have a warranty for their Note.
Many people confuse superbrick (phone dead right away, no life even if you plug a charger) and other bricks. This is just an unfortunate other brick not related in any way to emmc described one. Good luck at RMA
Also, copying big video to your sdcard is a good way to kill it. Old i9000 thread was popular with that
Sent from my GT-I9100 using Tapatalk 2
Was running Paranoid Android
Tried to restore the Note back to the latest UK stock ICS ROM via ODIN
Forgot to wipe/davlik before hand
then got stuck in boot loop
more boot loops
Then tried flashing a rooted GB rom in ODIN
stuck now on the Samsung Note boot screen occasionally looping.
Then tried flashing an original non-rooted GB rom in Odin
got stuck on Data.img
Then tried again and it stuck on FACTORYFS wont even get passed this.
Took battery out, then back in...
Now the screen shows three images and the message
firmware upgrade encountered an issue
Now with the Samsung Repair centre in Eastbourne and they are failing to be able to do anything...they still have my NOTE:crying:
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
Sure, you can theorically miss the binary check in rare circumstances. But this is just "an other brick" without any common relation typical to described emmc brick: no wipe, no flash, and mainly no right away (or even) complete dead phone
Sent from my GT-I9100 using Tapatalk 2
@ Entropy. Even guy above Phil3759 his bricked his note starting from PA which has a "safe" kernel, and eventually superbricking just useing PC Odin (long time considered safe). No wipes involved. Anyway, is Tungstwenty's detection method flawed for stock ICS kernels? Or is there are problem changing the offending byte from a 1 to a zero
Sent from my GT-N7000 using xda app-developers app
At least this brick has made me decide to leave my note well alone, after flashing roms practically daily for the last month or so, I have become insanely addicted to changing roms...once i get the Note back from the Sammy Service place, I am sticking with stock and wait till the official JB update arrives, which looks fantastic.
As it states on all these roms flashing custom roms at your own risk, thus its my own fault, finger crossed it can be sorted.
You can brick any phone, it happens, yes. Superbrick related to emmc bug occurs under special circumstances with typical symptoms.
Binary patching kernels, in theory, if you happen to have duplicate binary code or different, you could miss it. But, as far as i know, and for all manual checks i did, it never happened...
Sent from my GT-I9100 using Tapatalk 2
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Markuzy said:
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
As i said, it is really non recommended to use your internal sdcard for regular heavy write operations like videos. It will be corrupted at a certain point. On the i9000 this used to be a way for some to get warranty. Phone stuck often after a continuous write/wipe overnight
But this is not the superbrick. And one day, all your phones will brick. That's flash storage
Sent from my GT-I9100 using Tapatalk 2
altae said:
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
Click to expand...
Click to collapse
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
If you read across HTC and other forums, you'll see so much bricks and unhappy people. Why blame Samsung, there will be always faulty devices and unhappy unfortunate people
Sent from my GT-I9100 using Tapatalk 2
Yeah, you're right. Even PC Nand causes grief. Just hoped a Company on the cutting edge of technology like Samsung would have been able to resolve such problems.
Sent from my GT-N7000 using xda app-developers app
I would better trust seagate or corsair to push it further. Samsung HDD always failed on me. Ditched them long ago
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------
By the way, for people that want to know more about binary patching kernels, read here, it is worth it
http://forum.xda-developers.com/showthread.php?p=29609295
Sent from my GT-I9100 using Tapatalk 2
Hellow guys
Here's my background, I rooted my Tab by using z4root which works fine. I flash zImage using Odin with 20% battery (I think this cause the problem D:
After it says "PASS" I immediately pull it from the pc and boot em up. In the first "Galaxy Tab" logo it has Funky rainbow lines,and on the second logo which is "Samsung'' it stops there and vibrates then it repeats all over again. When I try to boot it on recovery mode rainbow lines appear then go back to First logo screen. Download mode works fine but Odin wont recognize it .
After one week of searching on the internet, I cant find my situation. So, I was thinking to post it here on forums. Thanks in advance!
Weird. I recall reported funky rainbow lines when people who have GB bootloader, which doesn't need to be patched, but people go ahead and patch them.
But you flash zImage, not bootloader.
But since it appears in place of the logo, I would still say your bootloader is the one damaged.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Weird. I recall reported funky rainbow lines when people who have GB bootloader, which doesn't need to be patched, but people go ahead and patch them.
But you flash zImage, not bootloader.
But since it appears in place of the logo, I would still say your bootloader is the one damaged.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Umm, Yea I saw that in forums too. That's why I couldn't find my exact situation, I don't know what exactly I would do
Btw I flash it with my galaxy tab in 10-20% battery,Did it cost the problem? I also immediately pulled it from the usb cable even if not boot up completely, but the odin says PASS. What do you think?
Please give me exact detail what would I do. I appreciate your fast response,Thank you!
I assume you were on froyo?
After z4root, you should immediately check if you have a protected boot loader. And patch it if so.
Now in this state, it is unsure if you have a protected bootloader.
What were you trying to achieve by flashing a zImage?
Actually I can't think of why except to root, but you have already done that?
Anyway, best you can do is charge fully, go to download mode and flash a stock rom.
If on the off chance your bootloader is not protected, you can use overcome method which can be found at my signature.
Sent from my GT-N7100 using xda app-developers app
priyana said:
I assume you were on froyo?
After z4root, you should immediately check if you have a protected boot loader. And patch it if so.
Now in this state, it is unsure if you have a protected bootloader.
What were you trying to achieve by flashing a zImage?
Actually I can't think of why except to root, but you have already done that?
Anyway, best you can do is charge fully, go to download mode and flash a stock rom.
If on the off chance your bootloader is not protected, you can use overcome method which can be found at my signature.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes Im on froyo 2.2 (I think)
Btw, I already charge the tab and go to download mode. The odin couldn't detect my device
I always saw you saying to use overcome method, the problem is I don't know how. I only saw some download links there. I don't know what exactly to do and to download.
Do you have a guide which I could follow?
I hope my tab will fix soon. Thanks!
Well. The link is the forum thread.
The thread has all the files including PDF guide.
But all useless without Odin detecting.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Well. The link is the forum thread.
The thread has all the files including PDF guide.
But all useless without Odin detecting.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
What do you mean? Is there no chance of getting it fix?
Do I need to fully charge my device? I charge it maybe only 80-90% battery.
Do I need to wait 20 minutes till Odin will detect it? Please answer :crying:
Btw How do I know if my boot loader is protected or not?
Might be a solution
Karl Legson said:
What do you mean? Is there no chance of getting it fix?
Do I need to fully charge my device? I charge it maybe only 80-90% battery.
Do I need to wait 20 minutes till Odin will detect it? Please answer :crying:
Btw How do I know if my boot loader is protected or not?
Click to expand...
Click to collapse
Hey connect your tab for about 10 minutes or more 25 minutes max it will detect and then load odin with the stock rom files and flash! after it says pass your tab is ready. Make sure your tab has 70- 100% charge :good::good:
please help me, even i tried to update from froyo using odin and now i see rainbow lines.. when i start downloading mode, odin recognizes the tab, what to do?
rainbow lines? I thought that happens to people who upgrade to GB, then tried to patch the bootloader (unnecessarily)?
Is that what you did?