I bought a Samsung Galaxy S a week ago and now it seems bricked. Here is what happened:
1. I got it rooted yesterday using "SuperOneClick".
2. Then I installed "Basic with a Twist SGS4G KJ6 Kernel" on it. Since SGH 4G Wiki recommeded having the stock Gingerbread ROM flashed at least once prior to flashing any other Gingerbread ROMs, I downloaded " bhundven's Back to Stock Heimdall One-Click" and installed the latest Java and Visual c++ runtime.
3. According to "lumin30's Heimdall One-Click for Dummies", I downloaded "usbdeview-x64.zip" and tried to uninstall anything that has Samsung and Android related. However, some of them cannot be uninstalled by it and I had to move on. I put my phone in Download Mode and installed the "SAMSUNG USB Composite Device" drivers using Zadig. I got it flashed successfully and booted into the Gingerbread ROM.
4. Bad things happened when I tried to flash the bootloaders. It stuck at certain step for at least half an hour and I decided to pull the USB cable out.
5. I tried to flashed it again using the same approachdescribed above. I got into the download mode and flashed hte device. But during the reboot, it stuck on the System Recovery Screen, saying
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter: OK Key, Select: Vol UP / Vol Down
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
# Manual Mode#
6. I tried 2 different computers and all USB ports, and still it would eventually stick on the System Recovery Screen.
I am definitely a noob, and I don't see many posts discussing what I described above (one post suggested using Odin, but I am not sure where to find the right download link). I wonder whether there is a way to get my phone back working (simply jump out of the System Recovery Screen?) using Heimdall One-Click. Or I should try Odin instead?
Thanks!
Try it again with a different USB port, cable, computer, etc. Get into download mode by holding vol up and vol down while the phone is completely off and plugging in the USB cable. Then flash once without bootloaders, then when the phone begins to reboot (after the update completes in recovery mode), pull the battery, get back into download mode, then flash with bootloaders.
Sent from my SGH-T959V using xda app-developers app
Thank for the suggestions. I have tried 2 computers and 5 different USB ports so far.
I can always get into download mode and flash without bootloaders. After that the phone will reboot and stick on the System Recovery Screen I described above. I can never reach the next step--flash with bootloaders.
I wonder whether there is anything missing during the reboot process?
cpkelley94 said:
Try it again with a different USB port, cable, computer, etc. Get into download mode by holding vol up and vol down while the phone is completely off and plugging in the USB cable. Then flash once without bootloaders, then when the phone begins to reboot (after the update completes in recovery mode), pull the battery, get back into download mode, then flash with bootloaders.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
rockyhigh said:
Thank for the suggestions. I have tried 2 computers and 5 different USB ports so far.
I can always get into download mode and flash without bootloaders. After that the phone will reboot and stick on the System Recovery Screen I described above. I can never reach the next step--flash with bootloaders.
I wonder whether there is anything missing during the reboot process?
Click to expand...
Click to collapse
What happens when you try to flash bootloaders? It hangs?
Sent from my SGH-T959V using xda app-developers app
Yes, in the very beginning I successfully flashed the ROM and after reboot I got a fresh working phone. Then the device hung there when I try to flash bootloaders.
Now I can still flash the ROM but after reboot, it will stick at system recovery screen and won't work anymore.
cpkelley94 said:
What happens when you try to flash bootloaders? It hangs?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Have you tried flashing bootloaders again? Pull the battery and get back into download mode.
Sent from my SGH-T959V using xda app-developers app
Stop. Remove the heimdall drivers using the usbreview. Reboot your computer.
Goto this guide and follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1223765
umlaaat had a similar issue and what is happening is your usb ports are not playing nicely with heimdall.
cpkelley94 and eollie,
Thank you very much for the help. Now it is working again.
What I did was:
1. Uninstall all the Samsung related drivers using [usbdeview-x32.zip] according to lumin's step by step guide.
2. reinstall "SAMSUNG USB Composite Device" driver using Zadig according to lumin's step by step guide.
3. Flash with Bootloaders. However, I want to point out that in my previous tries, I couldn't select "Flash Bootloaders" without doing step 1 and 2.
It is so great that I can try some custom ROMS tonight.
eollie said:
Stop. Remove the heimdall drivers using the usbreview. Reboot your computer.
Goto this guide and follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1223765
umlaaat had a similar issue and what is happening is your usb ports are not playing nicely with heimdall.
Click to expand...
Click to collapse
Related
hey guys! so i'm stuck in android system recovery and i can't really do anything.
i tried applying the update.zip but it said "signature verification failed".
problems im having.
-im NOT rooted
-everytime i reboot the phone it always goes back to system recovery
-i cant flash an update
-my computer wont even recognize the phone
-i cant go into download mode
please help. ive searched everywhere and there doesnt seem to be a clean answer.
anything helps. thanks.
You are getting that because you didn't properly push the recovery file to system/bin....BECAUSE YOU ARE NOT ROOTED. try to wipe cache and factory reset the phone from recovery to get back your android stock. Try to get into download mode using one if the methods in the download guide in the bible. Odin to kc1 with the final cwm from krylon that fbis posted. You will have root.
Please read the bible, especially the opening threads. Also, do not apply update.zip.
Sent from my SGH-T959V using XDA Premium App
Try outing in recovery using adb
Sent from my SGH-T959V using XDA App
jager555 said:
You are getting that because you didn't properly push the recovery file to system/bin....BECAUSE YOU ARE NOT ROOTED. try to wipe cache and factory reset the phone from recovery to get back your android stock. Try to get into download mode using one if the methods in the download guide in the bible. Odin to kc1 with the final cwm from krylon that fbis posted. You will have root.
Please read the bible, especially the opening threads. Also, do not apply update.zip.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
so i dont know how i can connect to odin if my pc cant read the phone.
reinstall the drivers using the files in the bible useful files section. (http://forum.xda-developers.com/showthread.php?t=1117554)
restart the computer.
plug one end of the usb to a different port than what you had it before.
take out your sd card and your sim card and put the battery back in.
press the up+down volume keys and connect the usb cable to the phone
xXpatisXx said:
so i dont know how i can connect to odin if my pc cant read the phone.
Click to expand...
Click to collapse
oh i also have tried to get into download mode.
i tried:
- the 3 button method
- adb
none of those dont work.
please help =/
what exactly did you do to get into this?
jager555 said:
what exactly did you do to get into this?
Click to expand...
Click to collapse
a friend of mine gave me his phone and it was fully functional. but then some certain apps werent working so i tried to reset all the data through the privacy settings. and i had no luck. so i tried going into download mode but instead it took me to the recovery menu. i wiped all cache and user data and i tried to reinstall packages. its been stuck ever since.
ill show you a video of what im going through in just a sec...
also since im in recovery mode. does that mean my phone isnt bricked?
http://www.youtube.com/watch?v=eBo3630sNu0
jager555 said:
what exactly did you do to get into this?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=eBo3630sNu0
download the usb drivers from the bible for your windows machine.. Once installed reboot the pc
once rebooted download odin 1.85 from xda or u can snag it out of my kc1 downlaod i packed it in there
oppen up odin you may have to run as admin...
with your phone powered off
press and hold
vol up and down
then insert usb
once you see the screen with a android yellow box says download your fine if you dont see that screen but odin has a light com port dont fret your ok
download dr honks kb 5 odin off the bible and flash that
it wont have the hacked signature verificaton we will get to that
once you flash the rom via odin and its up and running
go here
http://forum.xda-developers.com/showthread.php?t=1099374
download cwm final and recovery record
then download root explorer or equilvent off the market
push the reocery record to the system bin folder
you will prob have to set the system bin folder to read write then change it back to read only after
once u do that reboot phone boot cwm hit reinstall packages enjoy
RaverX3X said:
download the usb drivers from the bible for your windows machine.. Once installed reboot the pc
once rebooted download odin 1.85 from xda or u can snag it out of my kc1 downlaod i packed it in there
oppen up odin you may have to run as admin...
with your phone powered off
press and hold
vol up and down
then insert usb
once you see the screen with a android yellow box says download your fine if you dont see that screen but odin has a light com port dont fret your ok
download dr honks kb 5 odin off the bible and flash that
it wont have the hacked signature verificaton we will get to that
once you flash the rom via odin and its up and running
go here
http://forum.xda-developers.com/showthread.php?t=1099374
download cwm final and recovery record
then download root explorer or equilvent off the market
push the reocery record to the system bin folder
you will prob have to set the system bin folder to read write then change it back to read only after
once u do that reboot phone boot cwm hit reinstall packages enjoy
Click to expand...
Click to collapse
thanks but i downloaded the drivers and the phone still isnt recognized by the pc or odin. please help!
Can someone please help =[
xXpatisXx said:
Can someone please help =[
Click to expand...
Click to collapse
Did you try a different usb port?
Sent from my SGH-T959V using XDA Premium App
cnote74 said:
Did you try a different usb port?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
yes i tried all 3 on my laptop. i just resorted to buying a usb jig. that works right?
"IV. Flash the Recovery Image
1. Remove the battery from your device (if you put it back in).
2. Plug the phone in via USB cable to your computer.
3. Right click OneClickRecoveryFlasher.exe inside the NvFlasher folder inside the file you extracted in section II and select Run As Administrator (if such an option doesn’t exist, just select Open).
4. Once it is done, unplug the device from the USB cable.
5. Now, hold Volume Up and Volume Down (and keep holding them through the next couple of steps).
6. Plug the phone in via USB Cable (with the volume up and volume down still being held).
7. While still holding the volume up and volume down buttons, click on Flash ClockworkMod 3.0.2.7 on your computer.
8. Once it says “S/W Upgrade – Please wait while upgrading…”, you can let go of the volume up and volume down and just wait for it to finish flashing in the command prompt.
9. Once it is done, it’ll say press any key to continue in the command prompt window on the computer. That means it is done, press enter then unplug your device from the computer.
10. Put your battery back in.
11. To boot into recovery mode in the future, simply turn off the phone then turn it back on by holding down Volume Down and Power and keep holding it until you see the word Android in Orange letters.
V. (Optional) Flash a Custom ROM
1. Head to our How To Flash a Custom ROM procedure to begin flashing custom ROMs (like Gingerbread ROMS etc.).
VI. (Optional) Flash Back to Normal Recovery
1. You can follow section IV but click Flash Stock instead of Flash ClockworkMod to get back to a stock recovery image."
this is the way i flashed my phone, i tired different roms but in my opinion the g2x is not really worth rooting, so i want to go back to stock. i did a back up before flashing any new roms,
so my question is if i restore the original back up,follow step IV but then go to "flash stock" instead of Flash ClockworkMod ,will that unroot my phone completely stock? (tmobile wont know that it was ever rooted?)
thanks for the help, i read other unroot methods but not sure if this will do.
I believe that just puts back the default recovery and removers CWM. Looking at the steps you took, you never rooted your phone in the first place. Do you remember using SuperOneClick or another rooting tool? Flashing Recovery!= rooting.
Jufjufjuf said:
I believe that just puts back the default recovery and removers CWM. Looking at the steps you took, you never rooted your phone in the first place. Do you remember using SuperOneClick or another rooting tool? Flashing Recovery!= rooting.
Click to expand...
Click to collapse
all i did was this steps
http://theunlockr.com/2011/05/03/how-to-flash-a-custom-recovery-image-on-the-t-mobile-g2x/
but i am rooted, i flashed three different roms to try them out, i used different rooting apps. but I dont think its worth flashing (IMO)
g2uzer said:
all i did was this steps
http://theunlockr.com/2011/05/03/how-to-flash-a-custom-recovery-image-on-the-t-mobile-g2x/
but i am rooted, i flashed three different roms to try them out, i used different rooting apps. but I dont think its worth flashing (IMO)
Click to expand...
Click to collapse
After installing CWM did you immediately make a backup? If so you weren't rooted. The ROMS you installed were but the backup isn't. Just try to install an app that requires root privileges and see if it works. If it does, just download SuperOneClick and click Un-Root.
Jufjufjuf said:
After installing CWM did you immediately make a backup? If so you weren't rooted. The ROMS you installed were but the backup isn't. Just try to install an app that requires root privileges and see if it works. If it does, just download SuperOneClick and click Un-Root.
Click to expand...
Click to collapse
Sorry, I'm new at rooting and this is first phone I rooted, but yea your right, it won't let me use rooted apps on the first back up I did (stock one) it only let me on the other Roms I installed, so how I get back to completely stock? If I hold power and down volume it takes me to recovery, Thanks for all the help
Sent from my LG-P999 using XDA App
Download the stock nandroid in dev thread place it in /sdcard/clockwork/backup. Then restore!
Sent from my LG-P999 using xda premium
Then after you reflash the stock nandroid use Nvflash to flash the stock recovery back onto the phone.
Thanks for all te help
Sent from my LG-P999 using XDA App
First, I'm on SGS4G on T-mobile.
For a while, I was running the Bionix Frost ROM (here), but it started giving me random reboots and crashes and I wanted to get Gingerbread on there anyway, so I used CWM to flash Valhalla Black Edition (here), which works fine, except that I get rainbow screens during boot (this isn't the problem, they only last for a bit), and when I boot into recovery it won't display properly and all I get is rainbow screen. Because of this, I decided to try ODIN-flashing the Official GB 2.3.6 (here).
I downloaded ODIN 1.85, and I have the SGS USB drivers installed, but for some reason ODIN will only detect my phone if it isn't in download mode. When I plug it in regularly, ODIN displays "<ID:0/003> Added!!". But when the phone is in download mode (even though it's displaying the triangle and everything), ODIN does nothing.
Also, pressing both volume buttons and plugging in the USB cable does nothing. I have to boot into download mode from the options screen you get by pressing and holding the power button in Valhalla Black.
So booting into recovery gives me a rainbow screen, and ODIN won't detect my phone in download mode. Any suggestions on how to get a different ROM to flash?
New Rom
Will your phone go into recovery mode, if yes then just place NEW rom .zip file on the root of your SD card and flash through recovery.
Try flashing another froyo rom, download quickboot and then reboot to download mode that way, then try flashing the official gb rom with Odin.
anoymonos said:
Will your phone go into recovery mode, if yes then just place NEW rom .zip file on the root of your SD card and flash through recovery.
Click to expand...
Click to collapse
Like I mentioned, when I boot into recovery all I get is a rainbow screen, which is why I'm trying to flash through ODIN.
FBis251 said:
Try flashing another froyo rom, download quickboot and then reboot to download mode that way, then try flashing the official gb rom with Odin.
Click to expand...
Click to collapse
I downloaded quickboot, but it doesn't give me an option for booting to download mode, just to recovery. The options it gives me are "Reboot", "Recovery" (which still gives me rainbow screen), "Bootloader", and "Power Off".
edit: I've also tried to use ODIN 1.7 flash back to the Froyo Stock+Root here, but ODIN 1.7 is giving me the same issue as ODIN 1.85 (won't detect in download mode).
I am a noob but it seems you went from Bionix Frost rom - looks to be a froyo rom - straight to Valhalla Black Edition - a GB rom. The rainbow screen sound like it may be a bootloader issue. You need the GB bootloaders which it seems you skipped that step.
Try using Heimdall One-Click Collection from bhundven which will give you UVKJ6 with all the bootloaders then try flashing Valhalla Black Edition again.
Click here for Heimdall One-Click Collection
Here is a very detailed tutorial using Heimdall courtesy of Bassmanjames in case you are unfamiliar with it - Click Here
Try the bootloader option in quickboot, if not find a guide on how to get set up using adb. Open adb on your computer and type in
adb reboot download.
lumin30 said:
I am a noob but it seems you went from Bionix Frost rom - looks to be a froyo rom - straight to Valhalla Black Edition - a GB rom. The rainbow screen sound like it may be a bootloader issue. You need the GB bootloaders which it seems you skipped that step.
Try using Heimdall One-Click Collection from bhundven which will give you UVKJ6 with all the bootloaders then try flashing Valhalla Black Edition again.
Click here for Heimdall One-Click Collection
Here is a very detailed tutorial using Heimdall courtesy of Bassmanjames in case you are unfamiliar with it - Click Here
Click to expand...
Click to collapse
I had some similar issues with getting back to stock. What did it for me was to use a Jig to get into download mode, Reinstall the Samsung USB drivers, and then go back to T595VUKF1 package that uses the Pit, PDA, CSC and Phone files. Got a very clean stock image, Used Odin to install a CWM then installed Valhalla 1.5 and then the New Valhalla Black, Which BTW is one of the coolest ROMs out there.
One thing to try is installing Heimdall and the related drivers, which are different then the Samsung drivers, then reinstall the Samsung drivers. In my case that seemed to clean things up.
With all due respect to
some of the answers you guys posted. It seems as if he can get into dl mode fine. its that his PC won't see the phone in which case make sure debugging mode is on for the USB wootimus
Sent from my SGH-T959V using XDA APP
goddi2010 said:
With all due respect to
some of the answers you guys posted. It seems as if he can get into dl mode fine. its that his PC won't see the phone in which case make sure debugging mode is on for the USB wootimus
Sent from my SGH-T959V using XDA APP
Click to expand...
Click to collapse
His real issue was the rainbow screen.
And difficulties with ODIN.
Which is why Heimdall was $uggested as a way to get gb bootloaders. He went straight from Froyo to flashing Valhalla Black.
I agree but also if debugging was off Odin wouldn't see the phone
Sent from my SGH-T959V using XDA App
I know it's been about 6 months (I ended up buying a different phone from a friend so it became a moot point), but I recently had to flash this back to stock in order to sell it to a friend of mine and the above method using Heimdall worked like a charm. Thanks!
- I am running Android 2.3.6. I flashed the UCLB3 via Heimdall. I have GB bootloaders from Heimdall
- I have the bootloaders from Samsung Kies Mini
- I have USB Debugging on, but when I connect to the computer it says “USB Connected” rather than “USB debugging connected.”
- I try rooting through Odin using jscott's tar.md5 files in the PDA window, but the window does not turn yellow (indicating the phone is not recognized) and after the process the Gingerbread setup greets me, but I do not have Superuser.
- SuperOneClick just freezes up when I try to root.
- I've tried to use the modified 3e recovery via replacing the “recovery” file in /system/bin but there is no recovery file there and the paste “fails” due to lack of superuser access, I presume.
- Basically, I'm stuck and unable to root or flash anything that has SuperUser unless I can either get Odin to recognize my device or find another way that does.
When I first got the phone it was on froyo. I stupidly tried to flash an ICS ROM (Dark Knight) because I assumed it was on GB. I successfully rooted using SuperOneClick and flashed CWM recovery, but got the rainbow distortion from lack of GB bootloaders. I then proceeded to flash the UCLB3 via Heimdall and got my phone working again, but with ranbow distortion on boot and in recovery mode (rendering the CWM recovery useless as it would not respond with the rainbow distortion. I then re-flashed UCLB3 using Heimdall and checked the “GB bootloaders” box this time, which got rid of the distortion. But now I'm stuck and unable to root or flash anything because Odin won't recognize my device (it says it's there but the window does not turn yellow) and no other methods give me SuperUser. Kies Mini recognizes my device and says there are no updates, so it's not the cord. However, Kies regular does not. I think it's something to do with USB debugging not working properly and allowing Odin to recognize the phone so it can root it.
JoeyofBladez said:
- I am running Android 2.3.6. I flashed the UCLB3 via Heimdall. I have GB bootloaders from Heimdall
- I have the bootloaders from Samsung Kies Mini
- I have USB Debugging on, but when I connect to the computer it says “USB Connected” rather than “USB debugging connected.”
- I try rooting through Odin using jscott's tar.md5 files in the PDA window, but the window does not turn yellow (indicating the phone is not recognized) and after the process the Gingerbread setup greets me, but I do not have Superuser.
- SuperOneClick just freezes up when I try to root.
- I've tried to use the modified 3e recovery via replacing the “recovery” file in /system/bin but there is no recovery file there and the paste “fails” due to lack of superuser access, I presume.
- Basically, I'm stuck and unable to root or flash anything that has SuperUser unless I can either get Odin to recognize my device or find another way that does.
When I first got the phone it was on froyo. I stupidly tried to flash an ICS ROM (Dark Knight) because I assumed it was on GB. I successfully rooted using SuperOneClick and flashed CWM recovery, but got the rainbow distortion from lack of GB bootloaders. I then proceeded to flash the UCLB3 via Heimdall and got my phone working again, but with ranbow distortion on boot and in recovery mode (rendering the CWM recovery useless as it would not respond with the rainbow distortion. I then re-flashed UCLB3 using Heimdall and checked the “GB bootloaders” box this time, which got rid of the distortion. But now I'm stuck and unable to root or flash anything because Odin won't recognize my device (it says it's there but the window does not turn yellow) and no other methods give me SuperUser. Kies Mini recognizes my device and says there are no updates, so it's not the cord. However, Kies regular does not. I think it's something to do with USB debugging not working properly and allowing Odin to recognize the phone so it can root it.
Click to expand...
Click to collapse
download mode:
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
profit
Thanks for quick reply and it worked!
I flashed a rom (Dark Knight) but every time I reboot, it goes straight to recovery. Do I need to change some settings or what? No matter how many times I flash it, the phone boots straight to CWM Recovery. What did I do wrong? What should I do now? I think I'm just stuck in a boot loop but I don't want to restore to stock and try again because I'll probably just keep making the same mistake. Instead I'd rather wait for someone to tell me why that flash didn't work and what I should do to make it work. Ive done work on a few other (newer) phones and I've never had this happen.
JoeyofBladez said:
I flashed a rom (Dark Knight) but every time I reboot, it goes straight to recovery. Do I need to change some settings or what? No matter how many times I flash it, the phone boots straight to CWM Recovery. What did I do wrong? What should I do now? I think I'm just stuck in a boot loop but I don't want to restore to stock and try again because I'll probably just keep making the same mistake. Instead I'd rather wait for someone to tell me why that flash didn't work and what I should do to make it work. Ive done work on a few other (newer) phones and I've never had this happen.
Click to expand...
Click to collapse
Read the OPs.
You need to flash CM9 twice, with a wipe in between.
If you accidentally did a reboot to recovery and suck in a loop, use the GB kernel flash in heimdall, wipe. Download mode, flash the Jt kernel and try again
qkster said:
Read the OPs.
You need to flash CM9 twice, with a wipe in between.
If you accidentally did a reboot to recovery and suck in a loop, use the GB kernel flash in heimdall, wipe. Download mode, flash the Jt kernel and try again
Click to expand...
Click to collapse
I read the instructions and i didn't see it say to wipe in between flashes, just to reboot recovery. I do follow directions you know but can't follow directions that aren't written in the spot I'm reading them and assuming them to be right. But thank you for telling me what I should havedone. So once I have jt kernel, I just flash, wipe, reboot recovery,and flash again?
I did the UCLB3 Repartition One Click and then wiped everything. Then I flashed JT's kernel and flashed the ROM. Before I could do anything else, it started on its own and everything is fine now. THanks for your help, I'm still a little confused but you pointed me in the right direction. Thanks will be given.
JoeyofBladez said:
I did the UCLB3 Repartition One Click and then wiped everything. Then I flashed JT's kernel and flashed the ROM. Before I could do anything else, it started on its own and everything is fine now. THanks for your help, I'm still a little confused but you pointed me in the right direction. Thanks will be given.
Click to expand...
Click to collapse
Glad it worked for you.
While in cwm recovery, re-boot into recovery means powering off and then turn back on with 3 finger salute.
Selecting "Reboot Recovery" may not work and may send a user into a loop recovery image.
I've found from experience that flashing a different kernel with different cwm version may erase that loop and let you start over.
As you have discovered what I've been saying along and if you read the ops on the heimdall thread, you will understand that rooting the official firmware is pointless if you are planning on flashing a custom firmware.
Root it only to run it with root permissions.
Flashing in download mode does not require root. Just flash the kernel with cwm recovery.
have fun
ok so ive had my tf101 rooted since i got the thing over a year and a half ago, i was running the megatron rom which was cm9 based and everything was good. today i tried to flash Eos4 and i got F%$ked out the a$$. so i did my standard procedure which was put the rom and gapps package on my device and then i wiped everything (after making a nandroid) and flash the rom along with its gapps. then i went to reboot it then i got shot back into recovery...so i was like wtf. i then found a way where if i hold the power and volume down for about 10 seconds i could cold boot android and once booted fix this problem with my recovery. unfortunately when i go to boot into android my device just bootloops on the boot animation ( ive left for about ten mins just to make sure) then i was like oh well ill just restore my nandroid, but for some reason clockwork mod touch wont let me use my microsd card, and its also not letting me restore from the backup i made earlier, it says files not found. i tried to connect it to my pc so i could just factory reflash it but unfortunately it will not be picked up by my pc through adb or apx.
so here is my main issue,
i just need to boot into android one time successfully so i can change the location of some ROM files and fix this stupid recovery bull****.
or if i could some how factory reset the tablet completely then that would be fine too
or or i could flash a different recovery that actually worked (currently on CWM 5.8.3.4 installed from rom manager which i realize now to be a huge mistake)
and i've tried ever tool on this forum as well and nothing works because it cannot pick up my device.
*** one other side note i am running windows 8 pro 32bit through Vmware (if this can be problematic)
thanks for any help in advance
To fix this, you will need to get your tablet recognized by your computer via ADB (in recovery) or APX mode.
You could have a bad cable, or it could be the VM causing the detection issues.
Is there a way you can connect it to a computer running Windows natively?
Does your computer make the new hardware sound when connecting?
Once you get it detected via one method or the other, here are my suggestions:
APX - Use the Naked Driver 0.72 and replace whatever driver is being used. Then use EasyFlasher to install TWRP 2.2.1.4 (it blows CWM away, and can read internal AND external memory)
ADB - use the Naked Driver 0.72 and replace whatever driver is being used. Then download the TWRP 2.3.2.3 blob from the TWRP project: http://techerrata.com/browse/twrp2/tf101
Call the downloaded file TWRP.blob.
Then run the following from your computer via ADB:
Code:
adb push TWRP.blob /sdcard/
adb shell
su
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Make sure it is a normal reboot to complete the recovery. Then reboot to recovery and you should be able to see the external card (so long as it is formatted for FAT32).
Thanks for the quick response and it probably is because I am using vmware... Unfortunately I don't have access to a windows machine right now. But I will definitely try to find one
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok so now it looks like this... All i did was flash some random ass jb rom I found in my cwm folder... It has been like this for about 15 mins
Sent from my SAMSUNG-SGH-I747 using xda premium
** edit I'm assuming it got stuck boot the apps because now a my directories seem F&#cked up too... It now goes sdcard/0/0/0/(everthing else)
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Lethe6 said:
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Click to expand...
Click to collapse
But my problem is I can't flash another recovery... I can't access the memory on my micro sd card... So like idk what to do
Sent from my SAMSUNG-SGH-I747 using xda premium
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
frederuco said:
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
Click to expand...
Click to collapse
I can't get into the os that's the problem... I just clean installed Windows via boot camp on my mac... Gunna try a few tools now... Hopefully I can get it back to stock... I'll update in a little bit
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok so my computer can sort of detect it... I installed the drivers via brks root kit but when I plug it in in apx mode it says unknown device... Tried all my programs and they all failed...
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok so I've tried to to reinstall the drivers... Tried to flash everything in apx and adb but it's not being properly detected By the PC... So I have no idea what to do at this point... If I could somehow either boot into android or flash TWRP
Sent from my SAMSUNG-SGH-I747 using xda premium
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
frederuco said:
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
Click to expand...
Click to collapse
Not to sound like a complete noob at this point but idk how to install these naked drivers
Sent from my SAMSUNG-SGH-I747 using xda premium
I think I installed the drivers right but idk can someone please like teamviwer or Google + hangout with me
Sent from my SAMSUNG-SGH-I747 using xda premium
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Lethe6 said:
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Click to expand...
Click to collapse
Not working... :/ I swear it's not me
Sent from my SAMSUNG-SGH-I747 using xda premium