Database Users

[Q] Flashing new bootloader (afterota and blackthund3r) both stuck at uploading.

Alright, i've gone over the instructions for the past month... finally decided to try and do this.
However, in both HC (0.03.01-HC) and now ICS (0.03.12-ICS), this tool has always stopped at stage 2:
Flashing Bootloader (EBT) stage two - uploading image...
In the dos window...
Nvflash started
[resume mode]
i presume AfterOTA stops at this location too as it stops at 3/5 Flashing.
I know i have the right SBK because i've used OTA (both times) and this has given me the SBK (which was the same after i upgraded to the locked ICS).
I've updated all the drivers on my windows 7 computer...
I've also now done this on two computers.
The only way i've been able to get out of it is to unplug and shutdown the tab.
Anyone have ANY clue why this is happening?
FYI, here is my current build.
Android Build : Acer_AV041_A500_1.031.00_WW_GEN1
Bootloader : 0.03.12-ICS
(Yes i have an a501, however i haven't been able to get past the bootloader update at all).
Thanks to anyone who can help.
Sent from my A500 using Tapatalk 2

Got it. New v4 of blackthund3r's tool worked.
Sent from my GT-P1000 using Tapatalk 2

same problem
Im experiencing the same exact problem you posted, so I thought I'd just add to it rather than start another. Ive tried so many times. Ive tried AfterOTA and the APX Flash method but I keep getting stuck on 'stage two: uploading image'. Not sure what to do at this point. Ive reinstalled the drivers. Can anyone give me a hand with this?

500tab said:
Im experiencing the same exact problem you posted, so I thought I'd just add to it rather than start another. Ive tried so many times. Ive tried AfterOTA and the APX Flash method but I keep getting stuck on 'stage two: uploading image'. Not sure what to do at this point. Ive reinstalled the drivers. Can anyone give me a hand with this?
Click to expand...
Click to collapse
Well what I did was run the newest apxflash (v4) and the only difference was the new option about bcl and I ran the patch for it.
Good luck. I'm at the point where I don't have a cwm anymore and can't install any Roms. ack!!!
Sent from my A500 using Tapatalk 2

ordio said:
Well what I did was run the newest apxflash (v4) and the only difference was the new option about bcl and I ran the patch for it.
Good luck. I'm at the point where I don't have a cwm anymore and can't install any Roms. ack!!!
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I've seen posts about this, but no answers (or i haven't found them yet).
I found i had to install "1.031.00-Patched-BL-CWM-Kernel.a500apx" first (via blackthund3r's tool)... Once that was installed, CWM was installed in the recovery.
Whew.. back to my a501, alexandra v.

Jeez what did you guys do I didn't really read xda instructions I just plugged the tablet in after a couple fails of it setting it..it worked.. If you don't get cwm from the tools and you have the newest bootloader try installing Acer recovery app from google play then installing the older recovery then download the new recovery from another source I can't mention.that is what I did and it worked.
Pm me if you need some extra guide to what I said or maybe someone will go into another install guide
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2

dincdoes.me said:
Jeez what did you guys do I didn't really read xda instructions
Click to expand...
Click to collapse
Uhm, yes i did... for the past 4 months i've been watching and waiting.. reading everything i can before i decide to do it..
dincdoes.me said:
I just plugged the tablet in after a couple fails of it setting it..it worked..
Click to expand...
Click to collapse
Its all YMMV (your mileage may vary)... mine took a while to get to where i wanted to go.
I read NOTHING.. and i mean NOTHING about BLT being the cause of why i couldn't upgrade. I didn't know that was the issue as i didn't find any posts about it... believe me i read every single post in that 65 page one about upgrading... many times.. nothing about BLT.
dincdoes.me said:
If you don't get cwm from the tools and you have the newest bootloader try installing Acer recovery app from google play then installing the older recovery then download the new recovery from another source I can't mention.that is what I did and it worked.
Click to expand...
Click to collapse
Well, when i installed the new boot loader, there was nothing saying i shouldn't already have the CWM that i installed via the apx tool. However i kept trying (tried about 7 different updates on my bootloader, and none did it).. however its possible it could have been a downloading issue (as the files were being saved as .zip and not .a500apx). So it was difficult to install a new recovery when i didn't have CWM in the first place.
Once i installed the one i mentioned in the post above, i ended up with CWM so i was able to continue.
I've got an SGS 1 and a SGT, and i know how to follow instructions to the letter... its funny though that i've been able to figure most of the issues out on my own in the end. Usually technical and not an instruction.
I'm hoping this post will help anyone who happens to have the same issues i was having (as the 2nd poster was). I read in the upgrade to ics bootloader post that someone had the exact same issue i did (no cwm after install), and there was NO answer to it.

I was not trying to put any one down if I came of that way.. I didn't know about cwm that is why I stated what I said that I just did what I thought would work and it did.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2

dincdoes.me said:
I was not trying to put any one down if I came of that way.. I didn't know about cwm that is why I stated what I said that I just did what I thought would work and it did.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Its no problem, all good. I'm just happy I finally have ics on my a501.
Cheers!
Sent from my GT-I9000 using Tapatalk 2

Took me days to do this.. Generic Google drivers finally got the apxtool to work.

adrock74 said:
Took me days to do this.. Generic Google drivers finally got the apxtool to work.
Click to expand...
Click to collapse
Generic google Drivers? You mean the basic ADB drivers? Can you provide link because this is driving me insane.

i have got the same problem....can anyone help me with this one please?
apxflash keeps stuck here: Flashing Bootloader (EBT) stage two - uploading image...
afterOTA keeps stuck at 3/5 stages
no idea, what to do.
thanks!
had to fix my partition tables first...Moscow Desire on this forum had an idea and it worked!
thank you!

get to A501_HC_bootloader.a500apx
get to A501_HC_bootloader.a500apx

U8800-51 Black screen, no boot! PLEASE HELP

I have a Huawei u8800-51 that I tried to install the official 2.2.2 ROM from Huawei, File name "U8800V100R001C00B138SP04CUSTESTC205D001 (Estonia Elisa)". I double checked that it wasn't the pro file.
It went through both steps fine, and said upgrade complete Rebooting. When it "Reboot", it vibrated slightly, but went no further, only a black screen. I left it alone for about 10 minutes, in case it was part of the upgrade process, but it never powered back on. I tried to reboot manually, with the same results, just a short vibration, and black screen. I have searched high and low, to no avail. I have tried putting the same dload file from the file on the SD card, pull the battery and plug to computer ( one of the possible fixes that I found ), but again, same results.
Is the phone officially bricked now, or can it be recovered? ANY help would be greatly appreciated.
Thanks.

You installed u8800 rom to u8800-51???
Sent from my U8800 using Tapatalk 2

From the links I followed for the 8800-51, that was the ROM to use.
Sent from my Galaxy Nexus using xda premium

Can you still get to pink screen?
Sent from my locked MB865 on Ice Cream Sandwich.

thenewguy821 said:
I have a Huawei u8800-51 that I tried to install the official 2.2.2 ROM from Huawei, File name "U8800V100R001C00B138SP04CUSTESTC205D001 (Estonia Elisa)". I double checked that it wasn't the pro file.
It went through both steps fine, and said upgrade complete Rebooting. When it "Reboot", it vibrated slightly, but went no further, only a black screen. I left it alone for about 10 minutes, in case it was part of the upgrade process, but it never powered back on. I tried to reboot manually, with the same results, just a short vibration, and black screen. I have searched high and low, to no avail. I have tried putting the same dload file from the file on the SD card, pull the battery and plug to computer ( one of the possible fixes that I found ), but again, same results.
Is the phone officially bricked now, or can it be recovered? ANY help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Try connecting USB cable from PC to your phone with out battery....

krish_nank said:
Try connecting USB cable from PC to your phone with out battery....
Click to expand...
Click to collapse
Tried that as well
Sent from my Transformer TF101 using xda premium

Disk image
thenewguy821 said:
Tried that as well
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
You didn't make a disk image?
Can you give me a link to the rom/guide you followed?

Somcom3X said:
You didn't make a disk image?
Can you give me a link to the rom/guide you followed?
Click to expand...
Click to collapse
I was jumping back and forth between here, rootzwiki and another site, hard to follow the trail. I did do a backup in CWM Recovery, but I couldn't get into recovery to try to restore.
Ended up taking the phone into AT&T, told them the hone wouldn't boot after an update. They replaced the phone, no charge.
Sent from my Transformer TF101 using xda premium

thenewguy821 said:
I was jumping back and forth between here, rootzwiki and another site, hard to follow the trail. I did do a backup in CWM Recovery, but I couldn't get into recovery to try to restore.
Ended up taking the phone into AT&T, told them the hone wouldn't boot after an update. They replaced the phone, no charge.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I have the same problem. No one know how to fix this??

Let me try making a disk Img for you
Sent from my GT-I9300 using xda premium

u8800-51 black screen, not booting at all. no pink/blue or even recovery. a little vibration and that's it..
any help is appreciated, thanks.

Somcom3X said:
Let me try making a disk Img for you
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
How can the disk image help if we cannot load without getting to a pink/blue screen?

when you took your phone to att
did you have service with them at the time?

http://forum.xda-developers.com/showthread.php?t=2000509
I have same problem after update ... any solution

Can't help due to it screwing up your process to motherboard connection

Somewhere in the sticky section of this forum should be "Back the kcuf up!" with links to image backup instructions. I have started doing it routinely. I bricked my phone this morning with a mundane font manager (who'd a thunk?). An hour later it was working just fine.

eyeconic said:
Somewhere in the sticky section of this forum should be "Back the kcuf up!" with links to image backup instructions. I have started doing it routinely. I bricked my phone this morning with a mundane font manager (who'd a thunk?). An hour later it was working just fine.
Click to expand...
Click to collapse
Its a pinkscreen backup no? I use it rarely, more likely for Official roms such as froyo, ging.

Somcom3X said:
Its a pinkscreen backup no? I use it rarely, more likely for Official roms such as froyo, ging.
Click to expand...
Click to collapse
Absolutely. I made one paperweight that CWM refused to restore from a blue screen. I have two scripts:
#!/bin/bash
dd if=/dev/sdb of=u8800.img bs=512
#!/bin/bash
dd if=u8800.img of=/dev/sdb bs=512
I'm sure that there is a WinDoze equivalent. Before installing any app that needs root, I do a complete BU.

CM10 killed my P7510. I'm sad.

After searching hard for a solution, I have come to the conclusion that CM10 fried my tab's kernel memory.
What initially happened was just a random freeze while I was using the tablet, running the CM10 preview build. Keep in mind this was a couple weeks ago or so.
I hard reset the tablet, and it randomly boots into download mode. Okay... nothing weird. Reboot again.
Back into download mode. Inspection reveals the message "Reason: No Kernel" at the top of the command line.
I've been at work all day (thankfully a slow day) and I've tried just about everything from rebooting the tablet into recovery mode - which the device no longer has, either - to Odin, to ADB. A final google search directs me to this thread, where it appears the same thing happened to a non-rooted user and he had his mainboard replaced (assuming for free) due to hardware malfunction.
So I guess I'm just here looking for insight, perhaps closure. Is it really dead? If so, how can I make the best of this? Anything that I can salvage through a teardown? Perhaps a gadget I can build with it?
Any input at all is highly welcomed - even wanted. Please, give your thoughts on my loss of this tablet.

If your able to get into download mode, your tab is not dead. (Hopefully you can still get into download mode)
I had a similar problem recent too. I had to ODIN a couple times to fix whatever my problem was.
Download an ODIN stock ICS version for your device (assuming its US wifi only based off the model number in the title). You can get it here http://www.sammobile.com/.

nakedninja42 said:
If your able to get into download mode, your tab is not dead. (Hopefully you can still get into download mode)
I had a similar problem recent too. I had to ODIN a couple times to fix whatever my problem was.
Download an ODIN stock ICS version for your device (assuming its US wifi only based off the model number in the title). You can get it here http://www.sammobile.com/.
Click to expand...
Click to collapse
Read before you post. I clearly stated that I had tried just about everything to restore it.
Sent from my SPH-L710 using Tapatalk 2

kehlan said:
Read before you post. I clearly stated that I had tried just about everything to restore it.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I guess any input was not welcome... :what:
Sent from my SAMSUNG-SGH-I747 using xda premium

kehlan said:
Any input at all is highly welcomed - even wanted.
Click to expand...
Click to collapse
kehlan said:
Read before you post. I clearly stated that I had tried just about everything to restore it.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Take your own advice and reread your post before acting like an ungrateful douche. You never said whether you tried Odin multiple times either. Not a great way to get anyone to go out of their way to respond.
Sent from my GT-P7510 using xda premium

If you can't flash to a stock ROM with Odin, with the "Re-Partition" option checked (select the correct pit file, get it from samfirmware/flashing tools), it's pretty safe to say it's a hardware fault.

Brick while on safe kernel

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

Does not boot (Only on Download mode)

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?