Related
I've flashed my Galaxy S2 with Odin several times and it has worked fine until yesterday, when I tried to flash again, and everything just froze.
I followed the normal instructions for flashing and the phone just stopped at the "downloading" screen where it says, "Do not turn of target!!".
So it has been, for several hours now. The Odin window on my computer seems to be waiting... but for what? Will it ever time out?
Is it normal that a flash session can take several hours?
Is it safe to interrupt it?
fugy56 said:
I've flashed my Galaxy S2 with Odin several times and it has worked fine until yesterday, when I tried to flash again, and everything just froze.
I followed the normal instructions for flashing and the phone just stopped at the "downloading" screen where it says, "Do not turn of target!!".
So it has been, for several hours now. The Odin window on my computer seems to be waiting... but for what? Will it ever time out?
Is it normal that a flash session can take several hours?
Is it safe to interrupt it?
Click to expand...
Click to collapse
Odin will flash, takes less than 5 minutes.
Is there any data running that you can see? I mean at the bottom left. I would suggest you turn off the phone, battery pull, wait for 5 minutes, and reflash back.
If it semi bricked, use JIG to revive it.
Either way, you can't be letting the phone there for the next few days etc right?
Did you click Start in Odin??
Although i don't have an s2(will be getting one soon) did you try to reset your pc? When i was flasing my sgsl i was stuck in this situation where odin seems to freeze everytime. I restarted my pc and poof, flashed without a problem
Edit: was flashing successful? If so maybe you should follow the instruction from the post below.
Sent from my GT-I9003 using XDA Premium App
This might sound stupid but did you have 'auto-reboot' checked? It happened to me once even though I have flashed hundreds of times. Odin was still open after flashing a kernel and never reset.
Start was clicked - yes.
Re boot was checked - yes.
I reset my computer and restarted my phone and - now it's still frozen, but with an icon on the center showing three icons in a line. First is a phone, second is a exlamation mark and third is a computer. Yiipiiiee. It doesn't boot. I can't get into recovery mode. Download mode does work however, but still the same behaviour. It freezes if I try to flash it.
Now what? Where is that reset-button which resets the phone and clears its brain down to original mode? A simple "brain wash" would be nice.
Is there anyway out of this "freeze of death" ?
Flash CWM kernel, download CM7 rom, copy it on SDCard (mount USB storage in CWM, connect to PC via USB, copy ROM), flash ROM from CWM
fugy56 said:
Start was clicked - yes.
Re boot was checked - yes.
I reset my computer and restarted my phone and - now it's still frozen, but with an icon on the center showing three icons in a line. First is a phone, second is a exlamation mark and third is a computer. Yiipiiiee. It doesn't boot. I can't get into recovery mode. Download mode does work however, but still the same behaviour. It freezes if I try to flash it.
Now what? Where is that reset-button which resets the phone and clears its brain down to original mode? A simple "brain wash" would be nice.
Is there anyway out of this "freeze of death" ?
Click to expand...
Click to collapse
Try to go into recovery mode and factory reset and clear cache and try flashing again (make sure you are on download mode)
Sent from my GT-I9003 using XDA Premium App
Hold power button to off it (hold a lil longer for this).
Then Go into recovery mode (power, home button and volume up at same time). Try do wipe all data, cache and even dalvik. Reboot and see if that works.
Alternatively, at the same place, go into restore backup.
The man said: "I can't go into recovery mode"
...
Recovery mode doesn't work - nope. But thanks anyway. It's nice to see that people at least try to help. Big hugs to you all.
If I try to flash CWM, I come into the same freeze again. Mindbending stuff ala Samsung, huh. They clearly don't make idiot-safe products. I'm stuck. My next phone might be a StarTAC...
Has happened to me before. KIES was opened. I closed all KIES files and the flashing fun started again~
Good point, make sure Kies isn't running when using Odin!
Also, now that you've flashed CWM, can't you boot on it?
Kies is not running and whatever I flash - it freezes. The green progress bar in Odin reaches maybe 1 cm, but no blue progress bar is visible on the phone as usually happens when flashing. It just says, "Downloading... Don't turn off target!!"
Am I slowly heading towards the brutal-axe-method?
Sounds like the NAND is damaged to me, but I'm no expert...
"NAND" means? Why does it sound like it's damaged? How can it get repaired?
NAND is the flash chip (internal sdcard). Seems that its damaged because you're unable to fully flash it.
I don't think you can have that repaired (if the NAND is truly damaged, like I said I'm no expert), you'd have to get the phone replaced.
With all respect, let's hope you aren't an expert, but better. But has anyone else interrupted a flash process and went though a "freeze"?
I'm looking for a way to reset the phone to use only what was burnt into ROM from first delivery. I just can't accept that it is so easy to mess up a phone, and I doubt Samsung would be so crazy not to build it with a rescue kinda last savior. Am I totally naive? Is my baby dead? :'(
lol I hope for you that I'm wrong also!
fugy56 said:
With all respect, let's hope you aren't an expert, but better. But has anyone else interrupted a flash process and went though a "freeze"?
I'm looking for a way to reset the phone to use only what was burnt into ROM from first delivery. I just can't accept that it is so easy to mess up a phone, and I doubt Samsung would be so crazy not to build it with a rescue kinda last savior. Am I totally naive? Is my baby dead? :'(
Click to expand...
Click to collapse
Something similar had happened with me too. The phone was stuck b/w flashing with odin. And the startscreen was showing those 3 icons. It was soft bricked.
But I then finally fixed it by flashing CF and then a ROM
This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium
Pretty much have the same exact problem on my thread :S http://forum.xda-developers.com/showthread.php?t=1725027
Take to sprint store and they willgive you a new one
sent from my EVO LTE
cant wait
ddeecc said:
This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Hopefully one day someone will figure this out with out actual casualties. Thanks all for your help. I'm getting a new one tomorrow.
I wanted to know if you found a solution because im dealing with a similar problem. I can cant access my phone manually or through fastboot
Linux will help you with download mode. There's threads on how to use ubuntu to unbrick. I'd find the thread for you, but am not in a position to do so.
Sent from my EVO using xda app-developers app
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
First off are you rooted? Do you have a custom recovery installed? Are you running a custom ROM or kernel? If you you have a custom recovery did you make a backup? If you can provide some more details I can try to help you out.
Sent from my SCH-I535 using xda premium
Alcatel OT5020t - Mediatek BOOTLOOP SOLVED!!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Pop c7 7041x
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
I have 7041x stuck in boot loop. Flashing a rom by CVM doesnt even help. Could you please tell us how you fixed yours.?
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
nabil_rachak said:
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
Click to expand...
Click to collapse
It's been so long since i messed with these Alcatel phones. But if i recall, you can take the rom zip or update zip, and you have to rename it to some special name. Then you put it on sd card and it'll install to phone.
But in your case, if you flashed wrong. There might be something else.
But either way. Since you can boot into recovery or bootloader you should be able to push stock firmware to device. You need to make sure you get the correct files for your device.
This is most i can tell you. I've been using samsung devices for past years and forgot alot about flashing devices such as this through adb.
All i can say is, at least it doesn't seem like your hard bricked. As long as you can get into bootloader mode or recovery, you should have a way to fix. Search and Google around! Good luck!
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
Whenever learning to mess with phones and roms with adb and fast boot. As a lot of devices are different, but some simple key facts to follow are as follows.
Find out your devices partition layout (which partition is boot, system, recovery)
Don't mess with any other partition but them.
Always, always make a backup of all partitions with 'dd' command. And keep safe.
Need build prop
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
Where would I find the build prop bro? Thx
At first, I apologize if i didn't see this kind of thread. I was looking for solution for a couple of weeks and didn't find anything that would help...
My Rezound is S-OFFed with 2.27 hboot and CWM recovery (the one befor CMW6.*****).
I dodn't know what made me try flashing CMW 6.*** but i did. Right after i flashed CMW 6, i went to "advanced" and rebooted recovery.
This is where weird thing happend: My phone just turend off. I tried to turn it on but i doesn't do anything.
While in Windows, if i connect my phone it shows up as QHSUSB_DLOAD
I tried:
pulling out/in the battery - didnt help
Connecting charger and turning the phone on without battery and holding vol - - didn't help
I also tried " [UNBRICK]Wanna unbrick your Rezound? (9/8, Episode VI, Return of The Zip)" and ended up with something like " device isn't found". I tried it in Urbundu 12.04
Ivanov4912 said:
At first, I apologize if i didn't see this kind of thread. I was looking for solution for a couple of weeks and didn't find anything that would help...
My Rezound is S-OFFed with 2.27 hboot and CWM recovery (the one befor CMW6.*****).
I dodn't know what made me try flashing CMW 6.*** but i did. Right after i flashed CMW 6, i went to "advanced" and rebooted recovery.
This is where weird thing happend: My phone just turend off. I tried to turn it on but i doesn't do anything.
While in Windows, if i connect my phone it shows up as QHSUSB_DLOAD
I tried:
pulling out/in the battery - didnt help
Connecting charger and turning the phone on without battery and holding vol - - didn't help
I also tried " [UNBRICK]Wanna unbrick your Rezound? (9/8, Episode VI, Return of The Zip)" and ended up with something like " device isn't found". I tried it in Urbundu 12.04
Click to expand...
Click to collapse
Can you boot into bootloader? Pull battery and put it back in and hold down power+vol down. If so cant you just flash a new recovery?
It sounds like your phone is stuck in Download Mode, that is used by the older RUU EXE files... you run it from your PC and just walk through the steps to install the firmware. Perhaps trying one of those, they can be downloaded here: http://mobile-overload.com/topic/53-ruu-htc-rezound-ruu-roundup/ but I think the newest EXE version you will get is 2.1.605.11 which is Gingerbread. It will return your phone to bone stock Gingerbread, S-ON, stock recovery, and all that good stuff, but it might work and get you running again.
It's the glitch that you get when you install cwm on a rezound, you can't charge your battery. Look it up on xda they have a solution.
That's the thing. It doesn't work at all.
Sent from my SCH-I535 using xda premium
Here's the link to save your ass.
http://forum.xda-developers.com/showthread.php?t=1711408
If you need to buy another I can sell you mine 230 + shipping obo
mforminio7 said:
Can you boot into bootloader? Pull battery and put it back in and hold down power+vol down. If so cant you just flash a new recovery?
Click to expand...
Click to collapse
The phone doesn't work at all. It doesn't even turn on.
I know there has been other treads about this before but none of the suggestions seemed to work for me. I searched and searched and I'm just not finding a fix. I hate to do these posts when an easy answer is right there but I just can't figure it out and it's killing me. So here it is:
I just got this Verizon Galaxy Tab that would not come on - only showed the battery charging icon. I just charged it over night and it came on once. However, processes kept shutting down. For instance, when I went into settings and tried to connect to my wifi network, the whole process would just close down. So I let it get to about 40% and reboot it to download mode (there was no recovery). I found the correct .tar file for it and flashed it with ODIN3 v1.85. It completed successfully but now it won't boot past the Samsung splash screen. Once the splash screen comes up, it will just go back to the large battery charging icon in the middle of the screen.
Then I tried the other option where you get into recovery and nothing happens at all. The screen is backlit black (you can just see light around the edges of the screen) and nothing ever happens.
So now, it's just charging but it seems to charge very slowly. I was wondering if this is a battery issue or some strange sequence that needs to be done. It seems to be at about 40% again. Any other suggestions would be appreciated.
These are other things I've tried:
hold the power button down for 30 seconds
Hold the power button down while touching the screen
More suggestions would be appreciated.
Now the tablet is fully charged but it still gets stuck on the splash screen when trying to boot up. Still have no recovery. Also, I'm not able to find a PIT file to re-partition. Can someone tell me how to get the stock recovery back at least? I've been looking but I can't find a file to flash for the recovery.
Same problem
Hi, I have the same issue basically. I have the Galaxy Tab SGH i957D 8.9 (TELUS) and flashed it to root last night, now I have the same problem. Except I have CWM installed, I was able to install that AFTER I locked it up. Help from one of the GURUs here would be great. It's obviously a problem caused by flashing it.
So try flashing with CWM, at least you'll have a good recovery on it. If we work together, we may be able to come up with a solution for our dilemma. I don't believe it;s a major problem, I had the same issue with my captivate phone when trying to CWM and Cyanogenmod, and I got it working perfectly, so there is hope.
I have tried the stock rom, rooted rom, and a couple of others, but still can;t get past the splash screens. Left it overnight trying to boot, and all it did was kill the battery. I can;t even turn it off, it just reboots every time I try shutting down. I CAN get to download and recovery mode though, and flash it all I want with Odin 3.7 and 1.83, just never boots past the splash screens.
DermagraFX said:
Hi, I have the same issue basically. I have the Galaxy Tab SGH i957D 8.9 (TELUS) and flashed it to root last night, now I have the same problem. Except I have CWM installed, I was able to install that AFTER I locked it up. Help from one of the GURUs here would be great. It's obviously a problem caused by flashing it.
So try flashing with CWM, at least you'll have a good recovery on it. If we work together, we may be able to come up with a solution for our dilemma. I don't believe it;s a major problem, I had the same issue with my captivate phone when trying to CWM and Cyanogenmod, and I got it working perfectly, so there is hope.
I have tried the stock rom, rooted rom, and a couple of others, but still can;t get past the splash screens. Left it overnight trying to boot, and all it did was kill the battery. I can;t even turn it off, it just reboots every time I try shutting down. I CAN get to download and recovery mode though, and flash it all I want with Odin 3.7 and 1.83, just never boots past the splash screens.
Click to expand...
Click to collapse
Thanx for the reply. As you can see, I've been around these forums for a long time and usually I'm able to work it out but this one has got me stumped. Just wanted to ask you if you have tried to flash a custom ROM in Clockwork? Also, did you go through unlocking the boot loader befor you flashed it? I did not because I received the tablet in this condition. I tried to flash clockwork mod but I get an "invalid file" error in Odin. Once I flashed the stock recovery and it worked fine. But after reflashing the stock rom, the stock recovery is gone now. Do you have a link to the files you used? I'm thinking that the stock recovery is messed up but I can only find that one file.
no I haven't tried flashing through CWM, as I wasn't trying to flash originally, I was just rooting and going easy on it, then it wouldn't boot, so I wasn't prepared and now can't add files to my SD drive.
I didn't unlock the boot, as none of the instructions I read mentioned it (rooting was all I was trying to do).
I don't even have a stock recovery either, all I have is CWM and TWRP.
I'm going to try mounting it in Linux and see if that makes any difference to put roms on my SD drive, as windows doesn't like it anymore, except through Odin, where luckily it seems to work fine... For now.. lol
Fixed!!!
shawndh said:
Thanx for the reply. As you can see, I've been around these forums for a long time and usually I'm able to work it out but this one has got me stumped. Just wanted to ask you if you have tried to flash a custom ROM in Clockwork? Also, did you go through unlocking the boot loader befor you flashed it? I did not because I received the tablet in this condition. I tried to flash clockwork mod but I get an "invalid file" error in Odin. Once I flashed the stock recovery and it worked fine. But after reflashing the stock rom, the stock recovery is gone now. Do you have a link to the files you used? I'm thinking that the stock recovery is messed up but I can only find that one file.
Click to expand...
Click to collapse
ok.. I have mine fixed and running again.
http://samsung-updates.com/device/?id=SGH-I957D
This is the stock flash/rom for Telus on the SGH i957D LTE 4G 8.9 model. Try samsung-updates.com and search for your exact model and carrier.
-Download correct stock image for your tablet.
-Unpack the file you downloaded
-Put your device in DOWNLOAD mode
-Connect it to Computer
-Start ODIN and wait for the COMM status to show as connected
-In PDA box navigate to your file and add it to the box.
-Press start
-Sit back and relax.
-Enjoy the fireworks as your tablet comes back to life..
-YEAH!!!
Life is good again...
DermagraFX said:
ok.. I have mine fixed and running again.
http://samsung-updates.com/device/?id=SGH-I957D
This is the stock flash/rom for Telus on the SGH i957D LTE 4G 8.9 model. Try samsung-updates.com and search for your exact model and carrier.
-Download correct stock image for your tablet.
-Unpack the file you downloaded
-Put your device in DOWNLOAD mode
-Connect it to Computer
-Start ODIN and wait for the COMM status to show as connected
-In PDA box navigate to your file and add it to the box.
-Press start
-Sit back and relax.
-Enjoy the fireworks as your tablet comes back to life..
-YEAH!!!
Life is good again...
Click to expand...
Click to collapse
I'm glad you got the right firmware and fixed your tab! But this site does not list a firmware for the SCH–i905 anywhere. Unless the Verizon Galaxy tab has an alternate model# there is no firmware on the site for my device. Oh well, at least one of us got tablets fixed. Congrats!
Download mode issue.
What recommendations do you guys have for a tablet that will not recognize in download mode?
I accidently flashed a bootloader and had auto reboot on - couldnt flash kernel and modem in time.
My tablet fully boots up, (rom manager says cwm is installed) as well as when i boot into recovery its completely black.
My main concern is that download mode is not recognized. it was previously working prior to installing the bootloader.
What can i do to fix this issue?
younggunner said:
What recommendations do you guys have for a tablet that will not recognize in download mode?
I accidently flashed a bootloader and had auto reboot on - couldnt flash kernel and modem in time.
My tablet fully boots up, (rom manager says cwm is installed) as well as when i boot into recovery its completely black.
My main concern is that download mode is not recognized. it was previously working prior to installing the bootloader.
What can i do to fix this issue?
Click to expand...
Click to collapse
Can you start by giving as much info as possible about your tab, make model# etc.
can you actually get into download mode? Power button and Volume down button till it boots then release pwr.
you may have bad drivers on your pc. I had this problem with my phone when I installed CM.
get into DL mode and then start Odin and hopefully you will see the Com port attached.
then in PDA load the stock rom for your tab.
hopefully at this point youll be all set.
if your tab is fully functional, then try just flashing CWM or TWPR to your tab. I found with mine that CWM works best. I like TWP better for looks and the touchscreen functionality, but I found it gets a bit flaky after a few flashes, where CWM seems more stable.
SHAWNDH...
give me all your info for your tab, make, model.. carrier etc. as much as you can, and I will see if I can find any stock roms while doing my searches. 2 sets of eyes are better than one...
So i have a sch-i905, 4.0.4 - I CAN boot into normal android
I flashed a bootloader last night and had auto reboot ticked. was not able to install the modem or the kernel.
I can get into download mode without any issues,but now download mode says "waiting for cable" and is not recognized by pc as it once was prior to the flash.
I can also get into recovery but its completely black ( assuming due to no kernel flashed )
I can get into android normally, but cant fix firmware through download mode, and recovery.
Please help :X
side note: rom manager says twmp and cwm is installed, though i get no display in recovery only blackness
if i can get download mode to work again or get cwm to show up i can fix it, but dont know where to go from here.
younggunner said:
So i have a sch-i905, 4.0.4 - I CAN boot into normal android
I flashed a bootloader last night and had auto reboot ticked. was not able to install the modem or the kernel.
I can get into download mode without any issues,but now download mode says "waiting for cable" and is not recognized by pc as it once was prior to the flash.
I can also get into recovery but its completely black ( assuming due to no kernel flashed )
I can get into android normally, but cant fix firmware through download mode, and recovery.
Please help :X
side note: rom manager says twmp and cwm is installed, though i get no display in recovery only blackness
if i can get download mode to work again or get cwm to show up i can fix it, but dont know where to go from here.
Click to expand...
Click to collapse
I don't get it. First, you can't flash a kernel using Odin. Second, your tab won't even be able to boot without the kernel.
Sent from my GT-P7500 using Tapatalk HD
younggunner said:
So i have a sch-i905, 4.0.4 - I CAN boot into normal android
I flashed a bootloader last night and had auto reboot ticked. was not able to install the modem or the kernel.
I can get into download mode without any issues,but now download mode says "waiting for cable" and is not recognized by pc as it once was prior to the flash.
I can also get into recovery but its completely black ( assuming due to no kernel flashed )
I can get into android normally, but cant fix firmware through download mode, and recovery.
Please help :X
side note: rom manager says twmp and cwm is installed, though i get no display in recovery only blackness
if i can get download mode to work again or get cwm to show up i can fix it, but dont know where to go from here.
Click to expand...
Click to collapse
If you can get into DL mode, then its probably just an issue of drivers on your pc. Download the samsung drivers and reinstall.
Then put your tab in dl mode. Then connect to the pc with cable, try a different usb port than before.
Then start odin, if you get the Com port showing up in the status box, then flash CWM recovery to the tab. Then start over with what you are trying to do. But I can almost garantee its an issue with drivers on your pc. I had the exact same problem with my phone when I did it,
and fixing drivers was the issue. I wss stumped for a long time on that issue. If that doesnt work, look into Heimdall flash utility or Kies and go from there.
Hope this helps. Or at least gets you on the right track.
update
DermagraFX said:
If you can get into DL mode, then its probably just an issue of drivers on your pc. Download the samsung drivers and reinstall.
Then put your tab in dl mode. Then connect to the pc with cable, try a different usb port than before.
Then start odin, if you get the Com port showing up in the status box, then flash CWM recovery to the tab. Then start over with what you are trying to do. But I can almost garantee its an issue with drivers on your pc. I had the exact same problem with my phone when I did it,
and fixing drivers was the issue. I wss stumped for a long time on that issue. If that doesnt work, look into Heimdall flash utility or Kies and go from there.
Hope this helps. Or at least gets you on the right track.
Click to expand...
Click to collapse
dont think its a driver issue.
it was working fine in download mode prior to me flashing a bootloader.bin, and yes you can flash a kernel.bin through odin, as well as a modem.bin.
I was in the process of installing cwm this way when it happened.
I can get into the os, i can get adb working fine, recovery is just a black screen though it goes into it. and i can get into download mode still, just stuck at "waiting for cable" no interaction with device manager
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
younggunner said:
dont think its a driver issue.
it was working fine in download mode prior to me flashing a bootloader.bin, and yes you can flash a kernel.bin through odin, as well as a modem.bin.
I was in the process of installing cwm this way when it happened.
I can get into the os, i can get adb working fine, recovery is just a black screen though it goes into it. and i can get into download mode still, just stuck at "waiting for cable" no interaction with device manager
Click to expand...
Click to collapse
Ive tried another pc as well. I dont believe its a driver issue as there is 0 interaction in download mode with device manager. but prior it easily was detected in odin no issues.
younggunner said:
dont think its a driver issue.
it was working fine in download mode prior to me flashing a bootloader.bin, and yes you can flash a kernel.bin through odin, as well as a modem.bin.
I was in the process of installing cwm this way when it happened.
I can get into the os, i can get adb working fine, recovery is just a black screen though it goes into it. and i can get into download mode still, just stuck at "waiting for cable" no interaction with device manager
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
Ive tried another pc as well. I dont believe its a driver issue as there is 0 interaction in download mode with device manager. but prior it easily was detected in odin no issues.
Click to expand...
Click to collapse
Ok... Im getting confused here... You Can still flash with Odin? Then you can install a new recovery on it. If device manager on the pc is not working, then you probably have a corrupt install, or the wrong rom file for your particular tab, and the usb drivers arent correct for your tablet.
Personally, I would start by downloading a stock rom file and return the tab to factory before starting anything, so you have it working as it should before continuing further.
If you DO HAVE a stock rom, maybe you could pass it along, i believe shawndh who started this thread is in need of one for the same tablet.
confusion fixed
DermagraFX said:
Ok... Im getting confused here... You Can still flash with Odin? Then you can install a new recovery on it. If device manager on the pc is not working, then you probably have a corrupt install, or the wrong rom file for your particular tab, and the usb drivers arent correct for your tablet.
Personally, I would start by downloading a stock rom file and return the tab to factory before starting anything, so you have it working as it should before continuing further.
Click to expand...
Click to collapse
I cannot currently get download mode to recognize anything. just keeps saying "waiting for cable" thats why i cant do anything in download mode. It was currently working prior to flashing the bootloader through odin with the "auto reboot" accidentally clicked.
younggunner said:
I cannot currently get download mode to recognize anything. just keeps saying "waiting for cable" thats why i cant do anything in download mode. It was currently working prior to flashing the bootloader through odin with the "auto reboot" accidentally clicked.
Click to expand...
Click to collapse
Oh... Well then it is beyond the scope of any problem I have encountered, or seen a solution to. I thought you could still connect in download mode.
Can you change usb debugging mode in tablet settings, that may enable you to connect? If not I dont think I personally can help, as your posts read like you could still use Odin.
On my phone, (galaxy S) nothing would connect after I messed up, but could do things with Heimdalls utility. See if you can connect with that. Worth a try, it does the same as Odin, but connects differently somehow.
DermagraFX said:
Oh... Well then it is beyond the scope of any problem I have encountered, or seen a solution to. I thought you could still connect in download mode.
Can you change usb debugging mode in tablet settings, that may enable you to connect? If not I dont think I personally can help, as your posts read like you could still use Odin.
On my phone, (galaxy S) nothing would connect after I messed up, but could do things with Heimdalls utility. See if you can connect with that. Worth a try, it does the same as Odin, but connects differently somehow.
Click to expand...
Click to collapse
i even went as far as getting a brand new cable to see if it was my cable still same thing. No response in download mode for either pc's ive tried.
little stumped....
possible clues: when tablet boots up, it boots up to a bright black screen, only once it completely boots up am i able to see my display properly.
DermagraFX said:
Can you start by giving as much info as possible about your tab, make model# etc.
can you actually get into download mode? Power button and Volume down button till it boots then release pwr.
you may have bad drivers on your pc. I had this problem with my phone when I installed CM.
get into DL mode and then start Odin and hopefully you will see the Com port attached.
then in PDA load the stock rom for your tab.
hopefully at this point youll be all set.
if your tab is fully functional, then try just flashing CWM or TWPR to your tab. I found with mine that CWM works best. I like TWP better for looks and the touchscreen functionality, but I found it gets a bit flaky after a few flashes, where CWM seems more stable.
SHAWNDH...
give me all your info for your tab, make, model.. carrier etc. as much as you can, and I will see if I can find any stock roms while doing my searches. 2 sets of eyes are better than one...
Click to expand...
Click to collapse
Thanx for the reply. I have the SCH-i905 32gb Galaxy 10.1 tab. The carrier is Verizon. I've spent days looking for another download source but I can only find one - there's a link from this site. Others have posted that it did restore their devices so I'm thinking that there are some bad clusters that need to be quarantined but I can't even find a tool for the Galaxy Tab that will do or check for that. I'd appreciate it if you could take a look though. Thanx.
younggunner said:
I cannot currently get download mode to recognize anything. just keeps saying "waiting for cable" thats why i cant do anything in download mode. It was currently working prior to flashing the bootloader through odin with the "auto reboot" accidentally clicked.
Click to expand...
Click to collapse
Are you connecting to a USB port that is on the motherboard of your computer? Mine will only recognize my tablet with one port. The other ports are not recognized at all by ODIN.
shawndh said:
Thanx for the reply. I have the SCH-i905 32gb Galaxy 10.1 tab. The carrier is Verizon. I've spent days looking another download source but I can only find one - there's a link from this site. Others have posted that it did restore their devices so I'm thinking that there are some bad clusters that need to be quarantined but I can't even find a tool for the Galaxy Tab that will do or check for that. I'd appreciate it if you could take a look though. Thanx.
Click to expand...
Click to collapse
I don't think its a cluster issue, just a bad flash previously. But you'll see from the link, yours is also known as the P4vzw. Well check the link and make sure that's your tab that I found. Then have a look at ALL the files for that tab.
Have you seen/tried this one... here's the thread STOCK ROM FOR YOUR TAB...
forum.xda-developers.com/showthread.php?t=1342995
Here's just the file.
http://goo.gl/XPMXv
Try flashing CWM recovery to your tab, and try a file from cyanogenmod
http://wiki.cyanogenmod.org/w/P4vzw_Info
Or just try the CM ROM first maybe and see what happens. I don't remember what you have for recovery. There are a bunch on there, but all nightly that I saw, but even that would be better than nothing for now if it works.
I'm still looking, but I know what you're saying about few and far between. I think they all are for the tabs. Let you know if I find anything else.
Another mod ROM. http://www.teamandroid.com/2012/08/...tab-101-sch-i905-android-411-aosp-jelly-bean/