i'm trying to help a friend out. he has a mesmerize, running froyo 2.2.1, and its on page plus (originally on us cellular). hes having a lot of problems with it, its very laggy and he can't install programs from the play store (package error) and the screen comes on at random times by iteself. few more problems but you get the idea. i too have a mesmerize that i've been flashing for over a year so it isn't nothing new to me. however, i can't seem to root or flash his phone for nothing. all of the versions of superoneclick hangs (not responding") on "waiting for device" step, i have samsung drivers installed and i can mount the sd card with no problem but adb cannot find device either, i've tried on three different computers. i tried un-checking usb debugging and re-enabling it, and i've put the usb settings on "ask on connection" and neither of them worked. i looked in the device manager, i don't have an "adb interface" category but my "samsung usb composite device" is listed under universal serial bus controllers category. i even tried the old z4root and it doesn't hang it just runs for about 30 seconds, vibrates twice and goes back the the app draw. no su app and busybox installer says the device is rooted but i can't install busybox. i can however browse the system files with root explorer and no superuser request pops up. i hate not being able to figure this out.
i was wondering if i can go ahead and odin cwm on it being that i can see my system files with root explorer. the last thing i wanna do is brick it being that it isn't mine.
How about starting from scratch?
Odin back to stock with this:
https://www.dropbox.com/sh/mpnagnzh1vckqqw/VuhLjOcqE7
Flash CWM for CM7
https://www.dropbox.com/s/ya0cwxp7b7k8840/cwm4_fixed_for_cm7-ODIN.tar
And this is what I flashed to gain root when I had my mez:
https://www.dropbox.com/s/ey979jdlwv4v2vg/UPDATE.zip
Related
I have downloaded the one click and samsung drivers. The program opens fine. But I have read some people getting phones messed up from rooting with this program?
Should I remove the SD card first before rooting?
Does this program work with 2.2 one click for Galaxy?
Thanks!
Hey
the version i used is 1.7 and no problem here ....
I have read somewhere that you should unmount your sd card , well i didnt and still got phone rooted..
i dont see much of problem with it ..... it will take around 5 mins so just be patient.....dont forget to install samsung drivers .... and put phone into developer mode
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
iceshark said:
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
Click to expand...
Click to collapse
Down root check fron the market. Just because Titainium is not getting root permission does not mean it's not rooted. It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. BTW this post should be in general.
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Thanks guys! Yes Rage was the issue. I followed his instructions and left in pnuueter and it worked perfectly! Now my Titanium is rooted and working.
Now if we could just get a good Apsd to let us format the SD card to ext 4 that would be a perfect world!
Thank you.
Moved to proper forum.
menacetwosociety said:
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Click to expand...
Click to collapse
^ thats what i forgot to tell him to change it lol
Rooted my SGS4G using Superoneclick.
2 things I noticed. Your AV will think that Rage is a virus. NOD32 kept quarantining it. I turned off both AV and FW.
Also, after you install the Samsung USB driver, reboot your computer. I had that "waiting for device" message until I rebooted computer. Then it flew. The driver doesn't offer to reboot, or tell you to.
Z
Okay here is the thing, I am a bit of an advanced user, and have been flashing ROM's for quite a while, so i am not a noob and I have already tried everything in the book to fix my problem.
Info:
1- Drivers installed on Windows 7 and have been working for the past 4 months.
2- USB Debugging ticked
3- Windows recognizes the Galaxy Tab 7" GSM (P1000 International)
Problem:
1-Running "adb shell" in adb results in: error: device not found
2-CWM Restore stops at android_secure.img not found and aborts.
How did it happen (Detailed):
1- Was on Overcome 2.0.1 "Hermes" and found out that there was an update on kies from someone.
2- Decided to restock
3- Flashed P1000JPJM5 (I already did that quite a few times and no problems ever occurred from that)
4- When i restocked i wanted to root, so i went into settings>Application>developement> and ticked USB Debugging
5- Plugged in USB and I opened up Super One Click Root v1.7 and hit Root, however, Nothing happened and it was "Waiting for device" forever.
6- tried Super One Click root v1.9 with the same result
7- Opened adb and typed "adb shell" and got error: device not found.
8- I downloaded Better Terminal app from the market and tried "adb shell" and i got "Adb not found" as a result
9- I wanted to root my device to use the Bootloader Batch and change my protected boot loaders
10- tried everything, Restore factory from 3e Recovery, Doing the same from Setting>Privecy, Flashing the same ROM Over and Over again with no luck
11- learned later that flashing ChainFire's Gingerbread P1000XXJMQ is safe on protected boot Loaders so i did that
12- the problem persisted and i just cant use adb
13- I had a CWM Backup done so i thought doing a restore might solve the problem, but that resulted in a failure in restore. it stops at android_secure.img not found and aborts restore.
If anyone kow's a solution or at least knows what might have gone wrong Please shed some light on how to go about this issue.
Thanks
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
pwolfamv said:
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
Click to expand...
Click to collapse
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
DistortedWisdom said:
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
Click to expand...
Click to collapse
Did you at least try what I suggested?
I can't get my galaxy tab to be seen by adb either. At least not since upgrading to Gingerbread.
I'm using the
"sprint_p100_Samung_GALAXY_Tab_USB_Drivers.msi" file from the Samsung web site.
Take away: Things do work like the developers say -IF- your device is in a stable state and instructions are followed. I also describe how I finally got Heimdall to work for me.
Windows 7 64bit Pro SP1
USB 2.0 Port
Dell laptop
Original Samsung USB cable
ATT Captivate
::My Story::
Coming from Apex 8, 10 to CM7 and now Apex 11.0 which all worked as a CWM upgrade after wiping cache/dalvik, etc and never had to go back to JF6 stock. This time there were failures installing Apex 11.0>11.1 upgrade file. It would not install using CWM Install ZIP from sdcard. I believe it may have been related to previous issues with lagfix settings and thus making the 11.0 version unstable. My Apps basically went missing and the phone was just unstable. This probably happened from a botched lagfix enable/disable and while I could take phone calls and message people things were different.
Ok, so here I am at a messed up OS and an inability to upgrade I then decided format partitions/reset to try installing the full 11.1. After a couple attempts this also fails. Formatted partitions, deleted sdcard data, further attempts at just installing an OS continue to fail. Frustration sets in, I went and made some iced tea.
Coming back I decide to follow Apex 11 web site instructions about using Heimdall to start a new and install the new kernel as the base thinking this would lead me forward. The tea tastes great by the way.
As I attempt to use Heimdall it errors, always.
I follow the instructions about plugging the phone in, locating the device using the Driver tool it comes with. I find Samsung Device and 'upgrade it' all appears to go well but whenever I attempt to install the kernel, Talon or Darkcore it fails.
I won't go through all the iterations attempting to get this to work but we can assume I tried 5 variations of madness to the nTH power.
Symptoms included:
-Unable to locate device. Drivers not working even though its a libusb device in (devmgmt.msc)
-Unable to download PIT file from device.
-Uploading failed at 19% - "did not return" or "partial file # 0"
Unable to get Heimdall to complete the installation of a Kernel and at this point the phone has a "PC screen" instead of "Download" screen, worse than when I started.
I realize the above issues were most likely related to the voodoo lagfix debocle I put the phone in earlier and that it would be best if I started fresh from JF6 stock.
While I was unable to use Heimdall using Odin worked fine. [ SEE, How I switched between the two below ]
I found some references related to Heimdall and the base USB drivers that should be used and was the turning point for this event. Tea has had more time to melt the ice and is getting better.
::Make a note, this is how I got Heimdall to work everytime.
Plug the phone in and open Device Manager, locate the Samsung USB entries and uninstall it AND select 'delete drivers' option during uninstall. Also locate something named 'Gadget Serial' and uninstall/delete it.
1) Uninstall the previous versions of Samsung USB Drivers.
2) Install Samsung Kies Mini from the Samsung web site.
http://www.samsung.com/us/support/downloads/at-t/SGH-I897ZKAATT
3) Use Kies Mini application to install the base USB drivers.
;Switching over to timeline format;
Odin 1-click to stock I897UCJF6-final-OCD-REV0
Booted to base OS, Shutdown (no setup, it's going poof anyways)
-Now following Apex 11 instructions from http://apex.merseine.us/installation/
Downloading files, deciding on BigCache or not then it gets to 'Install Heimdall' obviously Apex is not responsible for how this app works so the instructions are vague on purpose.
::My experience using using Heimdall WITH the proper Kies Mini usb drivers::
Unzip Heimdall application.
Plug the phone in let it find and install the necessary Samsung drivers.
Navigate into the Heimdall\drivers folder.
launch zadig.exe (accept the warning)
-Options > List All Devices
In this list you should see Samsung USB Driver
Select Samsung USB and click the Install Driver button, accepting all prompts for 'unsigned drivers' allowing the installation.
--If you have Device Manager open at the time you should see the Samsung device disappear and a new libusb category pop up.
Close Zadig
Unplug the phone, wait a few seconds and plug it back in, libusb should show back up in device manager.
::
Launch Heimdall and follow the remaining instructions from Apex installer.
These instructions worked perfectly after culpirate was wrong USB drivers.
::How I switched from Heimdall drivers to Samsung drivers(Odin friendly)::
Once the Samsung drivers were converted to libusb using Heimdall removing them was just as easy.
1) Go into Device Manager (devmgmt.msc) and find the libusb device.
2) Right-Click, uninstall. This prompts to uninstall and an option to delete the drivers at the same time.
3) Check the box to delete the drivers and the device. OK
4) Launch Kies Mini and use the Install Drivers function of this tool.
After installation completes, plug the phone in again.
3 things...
Wow ! What a post !
I hope the tea was sweet tea.
Sent by XDA Premium App
Good info. Thx
Sent from my SGH-I897 using Tapatalk
Apex
Love the ROM! Came from Cognition and haven't looked back. Good work.
Apex is my favr rom
Hello everyone and thanks in advance for anyone replying to my dumb question.
Today I was preparing to use the Aroma Toolkit to restore my phone to a basic stock. I placed it in a folder called ".rom" on the internal sdcard so it would appear at the top. (can you believe it?) I have CWM Red and it doesn't see ".rom" as it is now hidden. (I guess) Unfortunately, I already wiped AND formatted "system" so I can't boot the phone up to change the folder to something more sensible. I cannot restore from Odin OR Heimdall because my phone won't show up on ANY PC and it only shows "Unknown USB Device." I've been up and down with that one too. Also, I tried to put the toolkit on the external sdcard both as is and as update.zip but it says there are no files. I think my only way(s) out of this would be to Odin or Heimdall, if I can get either working again, or if there is a way to get the CWM Red to see that hidden ".rom" folder.
ANY help at all would be greatly appreciated.
Thanks for reading this.
folders and files that begin with a dot are hidden in linux systems like android. you are seeing an unknown device because you dont have samsung drivers installed. you should be able to go into mounts and storage and select usb mass storage or something like that and it will mount as a mass storage device where you can rename the file in windows where that doesnt show as a hidden file.
if you wiped system, if you turn off your device, you might not be able to get back into recovery and youll have to use odin or heimdall. you can download the samsung drivers from http://d-h.st/xEG and when you are in recovery mode, go to device manager and select from the list of device and choose samsung composite device or something like that i dont remember.
next time you want a folder to show at the top of the list, i think you can start it with an underscore. i could be wrong about that though. you can try it out and see.
I don't recall if red CWM has the mount as usb storage option. If not...
Next step is getting the drivers on your PC. Easiest option from there is Odin or Heimdall - unless you want to download the android SDK and use adb shell to rename the directory.
Underscore should work for sorting...
fwiw I use exclamation points.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
well, if youre not going to download mode to run odin, and you cant do usb mass storage in red cwm, and you want to do it from recovery, you need to choose samsung adb device in device manager. then you need adb and can do adb shell and run "mv /sdcard/.rom /sdcard/_rom"
mrpectate said:
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
Click to expand...
Click to collapse
sd_ext in red recovery does not refer to the external sd card (even though you would think it does from the name)
For compatible drivers, remove all Samsung phone related drivers from your system and install the first driver package located here (not the mini-kies one):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
Some things that may help:
http://forum.xda-developers.com/showthread.php?t=1982306&page=2
Also, turn off auto driver install in Windows 7 - could be your PC is deciding what is best for you before you can install working drivers:
Go to Control Panel > System > Advanced System Settings > Hardware > Device Installation Settings > "No / Never"
Then install the driver, then connect your phone. Once the driver and devices are fully installed you can change the above setting back to what it was or to "No / Install" (that's where I usually leave it)
Good luck
Well I sincerely appreciate all the help from you guys, and Zen Arcade, thanks for the toolkit that brought me back from disaster quite a few times. I tried all of your suggestions, but it seems like I might have a hardware failure which occured before all this. I was able to connect to USB fine and out of nowhere it just wouldn't anymore. That was OK. I still rom-hopped along with straight to phone rom aquisition, but then I made a mistake. One I have learned from. I'm not able to get the phone to show up AT ALL. I even tried a clean install of WinXP then the drivers from Zen's post, and Nicky's Win7 laptop. I also tried several versions of Linux. Only Mint's Gparted could see it as /sdb/ with a corrupted partition. I even gave Haiku's Drive Probe a shot. Jack of Clubs, I tried the SDK shell but it just scans and sees nothing. I just think that the USB thing is roadblocking any hope of saving this heap. Recovery is there, download mode is there, but the connection required to utilize either of those is gone.
Again, I truly appreciate the help.
Well I've been trying to get CWM to see the Infuse Toolkit (and various roms) on external_sd but it keeps saying:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard
I've tried 4 different microSD's formatted as FAT, FAT32, and I used SDFormatter (I saw someone recommend that somewhere). I really see this as the very last ember of hope for this phone before I let it go.
Any ideas?
BTW, my CWM is v2.5.1.3 - Voodoo lagfix
Thanks again and in advance.
Infuse GB recovery menu will not see external SD card.
If you can get adb working - connection to your PC - you have some options. From adb there are commands that will allow copying files from PC to phone ... also from external to internal sd card depending on which kernel you are running. You could also rename your hidden folder too.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks again for your continued help Zen. I just can't get it recognized (in a constructive way) by anything. I tried Santoku linux today and nothing. I've just been beating my head with this thing. Well here it is: CWM is accessible, as is download mode, and it charges fine, but no PC connection. When it was given to me, the glass was cracked, but it always worked fine for me. It's in a Ballistic case. If your interested in it, I'll be happy to send it to you, even if it's just for parts. I loved this phone, and had a lot of fun with it. (thanks to this community and all of its' contributors) I think it's time to move on.
I'm gonna start looking at a phone with a good selection of custom roms cuz I just love flashin' 'em
Let me know if your interested in this phone Zen.
I was messing with my galaxy core prime (android 4.4.4) using a app to remove system apps that you can't with the stock app manager.. (no reason for crap like smartcard manager, bluetooth, wifi sharing..etc to be running when i haven't authorized such things, seems like security risk imo)
Was also editing the autorun list and messing with Norton applock and phone encryption settings to try to further secure it.
Welp, I f'ed things up because phone crashed and now can't do anything.. can't access home screen, settings, call/txt, nothing. So I booted into the stock bootloader and tried formatting the entire thing including cache..
Didn't fix the problem, can't finish the setup wizard without it crashing, get message saying setup, hangouts, and keyguard stopped working and then my phone bricks and can't do absolutely anything. No backup either.
I have been googling and googling for solutions but everything I read says to either:
-Reformat from bootloader (tried a 100 times)
-Wipe with TWRP or CWM (don't have either and can't access play store)
-Use Kies (won't detect my device since I can't enable MTP)
-ADB sideload twrp or cyanogen (cant, usb debugging probably not enabled since I formatted and no way to enable it since setup of android fails)
Odin can't detect anything either.. probably due to same reason. (Cant enable MTP or usb debugging)
So am I totally screwed? What are my options here?
I noticed the stock bootloader has a option to install from external storage.. can I put my sd card in a phone that does work and download twrp, cyanogenmod, (or ANYTHING else to fix this) to that, then put it back in my bricked phone and re flash it that way? That way I wouldn't need mtp or usb debugging... or won't that work?
Wasted so much time trying to fix this guys, googling and even formatted my pc removing Linux and reinstalling Windows hoping suddenly my pc would detect it.. atleast on linux when I used "adb devices" command it detected my device (trying to sideload anything didn't appear to work though, phone says error about verifying it and tries again and says completed and reboots but no sign of the rom I just supposedly sideloaded anywhere)
removing Linux and installing Window seems to have been a mistake because on windows using "adb devices" returns a blank list.. Tried different cords, ports, kies 2 and 3, reinstalling drivers, disabling firewall..etc but like I said even if I do get adb to detect it, what can I do from there without mtp or debugging?
Sorry for wall of txt, just want to be descriptive as possible so I don't get all replies telling me to try stuff that I've tried 100 times or just flat out won't work for my particular problem because of the above reasons..
will be sincerely grateful to anyone that took the time to read this and try to help me.