Related
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
Can you still boot into your main ROM or not? IF so, just reinstall recovery - Clockwork Mod 0.8 works, I don't know about later versions or ROM Manager, I don't trust them, based on what I see on the forums.
If you can't boot into recovery OR boot normally, then you have to use APX mode and nvflash to reflash your G Tablet. That completely wipes and rewrites everything on the tablet.
EDIT: If indeed it sounds like clockwork isn't installed and stock recovery is still working, see the instructions in the next post to install clockwork mod 0.8. No need to resort to nvflash.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
You could become a professional gadget breaker with all the broken stuff you have
Clockwork never got installed if you are seeing the ! and then it reboots. I would not fool with rom manager, or any of the other stuff. Your tablet is NOT a Vega. The vega rom is used as a base to build stuff for the G tablet but it is not the same.
Get clockwork installed. You need to find Clockwork.8 ... You will have an update.zip file, and a recovery folder with a command file inside it. You can install it from the internal sdcard, or an external. You just need to look at the command file with a text editor like notepad and see if it lists sdcard, or sdcard2. If you want to install from internal, sdcard.. From external, sdcard2. The command file does not have an extension. If you do not have one in your clockwork package then download one of the other roms. Most of them will have it. Or even the stock rom package. They are all the same.
Go to SDX and we'll help you with the Intercept. Follow the info hear and the G will be rockin.
webosb said:
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
Click to expand...
Click to collapse
I'm pretty sure I wrote that... I don't care that your reposting it...just link where you got it from next time.
Anywho, keep in mind that it's nearly impossible to completely brick these things. Follow this guide, step by step, from start to finish. You will need a microSD card with a way to get files onto it (microSD slot on computer/SD slot with microSD -> SD adapter)
http://forum.xda-developers.com/showthread.php?t=865245
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
If you really have managed to mess up recovery.. You can use Nvflash to get all the way back to stock. Just use caution.. The only 2 tablets I know of that may have actually been completely bricked have been from folks that ran the incorrect batch file in Nvflash... It is really simple to use though... Guide is here...
http://forum.xda-developers.com/showthread.php?t=861950&highlight=nvflash
scsione889 said:
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
Click to expand...
Click to collapse
Yeah, I got it to recognize it, I didn't take recovery and update.zip out of the cwrecovery folder so it didn't work before. I just got it to "unpackage" for a second. but the same boot cycle happened.
I have to run out now for a bit, I'll try the flash later. Thanks for the help so far.
As mentioned before you need a microSD to put the CM recovery on. It also needs to be the .8version of clockwork. AndroidPolice is alright but you really should stick to the xda forums for this kinda thing. It only took me 5 mins to flash clockwork and get the VEGAn build up and running. I wish you the best of luck with your tab. It really is a nifty device....once you're running a custom ROM lol.
Edit: you can hard reset...unfortunately viewsonic failed to make a hole in the case to be able to reach it
Sent from my VEGAn G-Tab
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
Happy New Year! I hope!
Hello,
I flashed my GTab with TNT Lite a while back, but I was going to switch to Vegan. When I try to go into recovery mode, I get the message in the corner "Recovery Key Detected" but it won't go into CWM. I've got the update.zip and Recovery folder (with command file) in the root of my sdcard. I opened the command file to check the file path, and it's to the internal sdcard, not sdcard2. I even put those files on sdcard2 just in case, but still no go.
Any ideas? CWM 0.8 worked like a charm the first time around when I flashed to TNT Lite 4.2.1, but I just can't get into recovery anymore. I redownloaded it, and erased and put new versions of the update.zip and recovery folder on the sdcard (when the existing ones didn't work), just in case, but still no go.
I can still boot into my ROM, so I also tried "Reboot into recovery mode" from CWM inside the app, but it reboots to the Viewsonic splash screen and hangs there.
Any help would really be appreciated.
Hey, so I ran into the same problem as the first post (with the recycling boot screens). I flashed TNT-Lite onto it, and it worked for a few hours before the problem happened. I NVFlashed it, and at the very least I know the recovery screen is different than after I flashed it, but the yield sign only lasts a few seconds and then the problem persists.
Does NVFlash actually unroot? If so, can I return this to viewsonic and get a replacement? If not, am I screwed?
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
To NVFlash using windows 7 shouldn't be a problem I actually used it today and I'm running windows 7 home edition maybe you need to update your PC and try a linux live CD to run linux on a PC it has more drivers available for equipment and saves someone who doesn't understand linux alot of headache as it uses the CD as your hard disk and it sets it self up just make your system boot from the CD first.
Sent from my Bottle of Smoke using XDA Premium App
TimmSpinn said:
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
Click to expand...
Click to collapse
Really it depends on your boot loader branch and its good practice to ensure that everything installs as the Rom develoer intends.
Sent from my Bottle of Smoke using XDA Premium App
While I was checking my emails i rediscovered this thread... lol
I'm a linux user, I got ubuntu 10.10 on my laptop running, again, months ago.
But now I don't touch it and use my tablet or phone 98% of the time. (this is 2% other on an XP desktop)
I also share the same recovery mode issues, but after reading the rest of this topic, I think I might feel adventurous enough to try that honeycomb... >.>
stuck cant get into cwm and is stuck on the tapntap logo
after i nvflash the tablet it wont boot. it gets stuck on the tapntap logo after a few seconds it turns the screen black. and even cant get into cwn it just get stuck on the view sonic logo. i need help
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/
Hi, I'm completely new on all this mobile/android stuff, also sorry my poor English.
Out of nothing my phone bricked and I just wanted to recover my files from the internal storage.
Why I've tried so far: to install a custom recovery using Odin. Installation process were OK, I guess, judging by Odin and phone messages (on phone download mode you can read "custom binary download: YES (3 counts)". That's 3 because I've tried twrp-2.8.6.1-i9300 (tar) twice and recovery-clockwork-touch-6.0.4.4-i9300 (tar) once.
Where I'm stuck: I cannot see the options to access these recoveries form the recovery mode, just the already existing options (reboot, apply update, ...).
Thanks you for any help!
Vinicius
First of all flash chainfire auto-root. You can download it from here: https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
Then try again to flash TWRP. If it will go ok, you can copy from recovery data from internal storage to sd card
Hi There,
I am in a similar predicament.
I have a Galaxy S3 (purchased in 2012) and a few weeks ago, the phone started to automatically switch off (when I locked it) and I would have to hold the power button for about 15-30 seconds for it to switch back on.
I checked the power button(to see if it was broken and pressing down all the time) but it seemed to be fine as whenever I pulled the battery, the phone would NOT come on unless I held the power button.
About 1 week ago when i tried to turn my phone on, with the power button, but it would get stuck on the samsung logo screen (it was frozen, not looping).
I was still able to enter both recovery and download mode. So I tried wiping the cache but it did nothing.
Then I tired flashing the ROM with ODIN and it passed but it also did nothing (tried flashing multiple times all with "PASS" as well as wiping the data cache in conjuction with the flashing but to no avail).
Tried flashing it again with BL and it also passed, but now whenever I try to enter Recovery Mode or Turn the phone ON it would display a White Scrambled Screen which probably means eMMC failure.
How do I retrieve the information on the phone ?
N.B;
- I do not care about fixing the phone, only want the information
-I cannot enter Recovery Mode, BUT I can enter download mode.
-When I connect S3 to PC it is detected (In Device Manager it states "Samsung Mobile USB CDC Composite Device")
-I did have my phone password protected before this happened using the Pattern Password (you have a 3x3 Dot grid in which you can use to draw a line(s) which will function as a password)
-My phone is an S3 GT-I9300
-Never interfered with the ROM or software on the phone before this (was running the official android software from Samsung which I believe was Android Version 4.3).
-I am not very versed with computer programming so please use simple words to help me
As previously stated. flash cf-autoroot and then flash twrp, both via odin. Then you should be able to access twrp (hold home and vol+/- (cant remember which, opposite from download mode) and press power once.
If you can get to twrp you can use its built in file manager to move your data to an sd card.
If no twrp its what is technically known as f*cked.
I wish I stole my HTC M9.
shivadow said:
As previously stated. flash cf-autoroot and then flash twrp, both via odin. Then you should be able to access twrp (hold home and vol+/- (cant remember which, opposite from download mode) and press power once.
If you can get to twrp you can use its built in file manager to move your data to an sd card.
If no twrp its what is technically known as f*cked.
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
How would I flash cf-autoroot and thenflash twrp (I have no clue what this means lol).
Also what is twrp?
bossman111 said:
Hi,
Thanks for the reply.
How would I flash cf-autoroot and thenflash twrp (I have no clue what this means lol).
Also what is twrp?
Click to expand...
Click to collapse
Short and sweet: TWRP is a popular recovery system; cf-autoroot is the preferred method for rooting some samsung devices by member Chainfire
I could lay out all that here again in detail, but it's safe to say you are better off in the long run if read up on that stuff by yourself...
Check the excellent threads I linked in my signature! Trust me, it's not as complicated as it seems.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
Hi all,
This is a brief guide on what are some things that could go wrong if you decide to flash a new ROM especially GSI as they are quite buggy at the time of writing this post. I'll try to mention as many issues as I can but if something remains, please feel free to write them in the reply.
The guide is aimed for complete beginners who were trying to flash something and are now stuck OR who just want to know what to be prepared for and not to panic. if you are experienced you might not need it but it might just help you with something.
also, as always, I AM NOT RESPONSIBLE IF SOMETHING DOES NOT WORK. YOU ARE RESPONSIBLE FOR YOUR OWN ACTIONS.
So let's start with the most common problem. Bootloops!
1 - Bootloops :
What happens? : The title is pretty self-explanatory. You know you are in a bootloop if your phone turns off automatically as soon as it turned on. This generally happens BEFORE the phone actually boots up i.e. in the booting screen but could also happen after the phone completely turned on. There are various causes for this it may be due to a bug in the ROM or missing system files.
How to fix? : If you are flashing a custom ROM then you may want to reboot back to TWRP, wipe and flash it again. It works sometimes if there was an issue with the files.
I am unable to reboot to TWRP my phone is stuck even long pressing the power button does not shut it down! :crying::crying: : well if you are stuck you don't actually need to open the back panel to remove the battery or wait for it to die those won't help. all you need to do is wait for the phone to turn off and IMMEDIATELY press and hold the VOLUME UP and POWER button that should get you into TWRP if that doesn't work then you can try pressing and holding the VOLUME UP + DOWN + POWER key as the phone is about to turn on. it might boot you into download mode. if that does not work as well then as the phone is about to turn on, press and hold VOLUME UP + DOWN and plug the phone into PC that will get you booted into download mode eventually. Once you have access to one of these you can continue doing whatever you were doing. To reset everything back to normal (stock, like a new phone) checkout the solution listed below.
2 - I was doing something and now my phone is stuck at charging mode :
What happens? : This has happened to me while flashing PHH GSI. My phone was plugged into the charger and I restarted the phone. turns out it was a fatal mistake for the bugged gsi. The phone now only showed a battery icon that was charging very similar to the one that you would see if your phone is out of battery and you put it to charge. This happens before the phone actually turns on. usually, once you unplug the charger the phone automatically restarts but in my case it didn't. It was stuck at that screen with no way out.
How to fix? : turns out it's pretty easy, it might seem like its doing NOTHING, not responding to power buttons or anything but internally it is. Surprisingly, if you press and hold the VOL UP + DOWN + plug it into the PC it would get you into the download mode.
3 - I flashed GSI and ... :
What happens? : There are MANY things that can go wrong with GSI if you are a beginner I would suggest you stay away from GSI until it supports the device better. For me, I flashed PHH gsi and it went smoothly I booted in but as soon as I was finishing the setup adding fingerprint the ROM went into bootloop. you know how to fix this now. if nothing works, just refer to the reset solution listed below.
4 - "Custom binary blocked by FRP lock" :
What happens? : This usually (at least with me) happens when you are trying to flash something but forget to flash the DmVerity thing. The phone won't turn on and going to download mode will throw you with a line saying FRP lock.
How to fix? : At this point, trying to install custom binaries with Odin probably won't help as for me it simply stated that you cant install custom binaries only Samsung official updates are allowed or something similar. There might be a better/easy solution to this but I found doing a stock reset with Odin worked great. It is given below refer to that.
5 - Phone is in "Emergency firmware recovery" Mode :
What happens? : Turning on the phone throws you into a cyan screen saying that your phone needs emergency firmware recovery which can be done using Samsung smart switch
How to fix? : I believe it is a fantasy way of Samsung saying that your phone is almost dead and nothing remains on it. Fear not, turns out that cyan screen is actually the download mode. so that's a win you don't even have to boot to download mode just connect your phone to pc odin and follow the reset to stock firmware as mentioned below.
6 - I am back in some OS but my internal memory is shortened!!!
What happens? : well you are in the os you wanted but if you check the storage it appears to be shortened. i.e. if your phone has 64gb internal memory it might appear as 30gb or 20gb.
How to fix? : This is a problem caused by missing PIT file in odin. I would not suggest you to manually download the PIT file from somewhere and flash it using odin because doing so got me stuck in the FRP LOCK (4th) situation. I would suggest that you flash the stock firmware using the method given below.
MASTER SOLUTION/RESET TO STOCK FIRMWARE: if you are new to modding I would suggest that you download the stock firmware files from here BEFORE doing anything as the files exceed more than 3GB in size and not everyone has fast internet. if anything goes wrong and you have access to download mode you can follow this and get everything back to stock. Download the stock file AFH given at the link. once you download the stock firmware you just need to extract it and put the respective files in odin and begin flash. it will RESET everything and make it a new phone. I've tried this method and it works always for me.
That concludes my guide. if anyone knows any better solutions to these problems or think I've written something wrong please feel free to correct me. I've faced all of these issues back to back when I tried flashing a GSI and was able to fix all of them so this is just my personal experience.
Lastly, don't panic if something happens wrong happens there is probably a way to fix it.
Depends on many things, but now that we have a working TWRP, life is much easier, and also we have kitchen tools which help as well.
thvardhan said:
Hi all,
This is a brief guide on what are some things that could go wrong if you decide to flash a new ROM especially GSI as they are quite buggy at the time of writing this post. I'll try to mention as many issues as I can but if something remains, please feel free to write them in the reply.
The guide is aimed for complete beginners who were trying to flash something and are now stuck OR who just want to know what to be prepared for and not to panic. if you are experienced you might not need it but it might just help you with something.
also, as always, I AM NOT RESPONSIBLE IF SOMETHING DOES NOT WORK. YOU ARE RESPONSIBLE FOR YOUR OWN ACTIONS.
So let's start with the most common problem. Bootloops!
1 - Bootloops :
What happens? : The title is pretty self-explanatory. You know you are in a bootloop if your phone turns off automatically as soon as it turned on. This generally happens BEFORE the phone actually boots up i.e. in the booting screen but could also happen after the phone completely turned on. There are various causes for this it may be due to a bug in the ROM or missing system files.
How to fix? : If you are flashing a custom ROM then you may want to reboot back to TWRP, wipe and flash it again. It works sometimes if there was an issue with the files.
I am unable to reboot to TWRP my phone is stuck even long pressing the power button does not shut it down! :crying::crying: : well if you are stuck you don't actually need to open the back panel to remove the battery or wait for it to die those won't help. all you need to do is wait for the phone to turn off and IMMEDIATELY press and hold the VOLUME UP and POWER button that should get you into TWRP if that doesn't work then you can try pressing and holding the VOLUME UP + DOWN + POWER key as the phone is about to turn on. it might boot you into download mode. if that does not work as well then as the phone is about to turn on, press and hold VOLUME UP + DOWN and plug the phone into PC that will get you booted into download mode eventually. Once you have access to one of these you can continue doing whatever you were doing. To reset everything back to normal (stock, like a new phone) checkout the solution listed below.
2 - I was doing something and now my phone is stuck at charging mode :
What happens? : This has happened to me while flashing PHH GSI. My phone was plugged into the charger and I restarted the phone. turns out it was a fatal mistake for the bugged gsi. The phone now only showed a battery icon that was charging very similar to the one that you would see if your phone is out of battery and you put it to charge. This happens before the phone actually turns on. usually, once you unplug the charger the phone automatically restarts but in my case it didn't. It was stuck at that screen with no way out.
How to fix? : turns out it's pretty easy, it might seem like its doing NOTHING, not responding to power buttons or anything but internally it is. Surprisingly, if you press and hold the VOL UP + DOWN + plug it into the PC it would get you into the download mode.
3 - I flashed GSI and ... :
What happens? : There are MANY things that can go wrong with GSI if you are a beginner I would suggest you stay away from GSI until it supports the device better. For me, I flashed PHH gsi and it went smoothly I booted in but as soon as I was finishing the setup adding fingerprint the ROM went into bootloop. you know how to fix this now. if nothing works, just refer to the reset solution listed below.
4 - "Custom binary blocked by FRP lock" :
What happens? : This usually (at least with me) happens when you are trying to flash something but forget to flash the DmVerity thing. The phone won't turn on and going to download mode will throw you with a line saying FRP lock.
How to fix? : At this point, trying to install custom binaries with Odin probably won't help as for me it simply stated that you cant install custom binaries only Samsung official updates are allowed or something similar. There might be a better/easy solution to this but I found doing a stock reset with Odin worked great. It is given below refer to that.
5 - Phone is in "Emergency firmware recovery" Mode :
What happens? : Turning on the phone throws you into a cyan screen saying that your phone needs emergency firmware recovery which can be done using Samsung smart switch
How to fix? : I believe it is a fantasy way of Samsung saying that your phone is almost dead and nothing remains on it. Fear not, turns out that cyan screen is actually the download mode. so that's a win you don't even have to boot to download mode just connect your phone to pc odin and follow the reset to stock firmware as mentioned below.
6 - I am back in some OS but my internal memory is shortened!!!
What happens? : well you are in the os you wanted but if you check the storage it appears to be shortened. i.e. if your phone has 64gb internal memory it might appear as 30gb or 20gb.
How to fix? : This is a problem caused by missing PIT file in odin. I would not suggest you to manually download the PIT file from somewhere and flash it using odin because doing so got me stuck in the FRP LOCK (4th) situation. I would suggest that you flash the stock firmware using the method given below.
MASTER SOLUTION/RESET TO STOCK FIRMWARE: if you are new to modding I would suggest that you download the stock firmware files from here BEFORE doing anything as the files exceed more than 3GB in size and not everyone has fast internet. if anything goes wrong and you have access to download mode you can follow this and get everything back to stock. Download the stock file AFH given at the link. once you download the stock firmware you just need to extract it and put the respective files in odin and begin flash. it will RESET everything and make it a new phone. I've tried this method and it works always for me.
That concludes my guide. if anyone knows any better solutions to these problems or think I've written something wrong please feel free to correct me. I've faced all of these issues back to back when I tried flashing a GSI and was able to fix all of them so this is just my personal experience.
Lastly, don't panic if something happens wrong happens there is probably a way to fix it.
Click to expand...
Click to collapse
Absolutely well written for new users who wish to get into the world of Android on their Samsung. Might I suggest a few corrections?
Akhil99 said:
Absolutely well written for new users who wish to get into the world of Android on their Samsung. Might I suggest a few corrections?
Click to expand...
Click to collapse
Sure by all means, feel free to suggest any modifications/corrections.:highfive: