Database Users

[Q] Root Help

I've been trying to root my vibrant via the directions I received on this site. It said to install the update.zip to the INTERNAL memory but that didn't seem to work. I then put the update.zip on the external memory and when I went to start it up holding the volume rocker while depressing the power button my phone displayed a green triangle image with a little android robot with a shovel in his hand. Below the image is says "Downloading....." and then at the bottom of the screen is says "?Do not turn off Target!!!" I'm going to leave it alone for a bit but doesn't anyone know what it is downloading, has anyone else come across this during an attempted root? I would appreciate any help, thanks.

sublimeNaz said:
I've been trying to root my vibrant via the directions I received on this site. It said to install the update.zip to the INTERNAL memory but that didn't seem to work. I then put the update.zip on the external memory and when I went to start it up holding the volume rocker while depressing the power button my phone displayed a green triangle image with a little android robot with a shovel in his hand. Below the image is says "Downloading....." and then at the bottom of the screen is says "?Do not turn off Target!!!" I'm going to leave it alone for a bit but doesn't anyone know what it is downloading, has anyone else come across this during an attempted root? I would appreciate any help, thanks.
Click to expand...
Click to collapse
un plug it from the PC and just make sure its on the internal memory not the 2gb SD card the phone comes with

rshemeld said:
un plug it from the PC and just make sure its on the internal memory not the 2gb SD card the phone comes with
Click to expand...
Click to collapse
I did initially place the update.zip on the internal memory but then when I went to reboot it said it could not find it and it seemed like it was looking in the ext memory card.

When I do it how it is suggested on here I get the message in the recovery screen: "E:Can't open/sdcard/update.zip (No such file or directory) Installation aborted."

try this then http://forum.xda-developers.com/showthread.php?t=746129

sublimeNaz said:
When I do it how it is suggested on here I get the message in the recovery screen: "E:Can't open/sdcard/update.zip (No such file or directory) Installation aborted."
Click to expand...
Click to collapse
This may seem like an obvious suggestion, but if you hide file extesions of known file types the file might actually be named update.zip.zip
Either turn on the file extensions and rename it or rename it update instead of update.zip

When I rooted my phone, I put update.zip onto "/sdcard". I was confused at first too, but that directory is your phone's internal storage. The external memory card is mounted to "/sdcard/sd". I don't know if it can find the update.zip if it's in "/". Good luck.

Shane_pcs said:
This may seem like an obvious suggestion, but if you hide file extesions of known file types the file might actually be named update.zip.zip
Either turn on the file extensions and rename it or rename it update instead of update.zip
Click to expand...
Click to collapse
Hmm.....didn't even think about that. Ok, I just redid it, only naming the file "update" no .zip. Trying it now..............................damn it....yes, that seems to be the reason as to why it was not working, now I feel like an idiot. lol
Thanks for your help.

Can not root with Classical Method!!

This question may have been answered before but I just cant find it here.
I tried rooting my vibrant with the classic method described here.
http://forum.xda-developers.com/showthread.php?t=723479&highlight=issues+rooting+vibrant
It didn’t work and I got the following message:
E: can’t open /sd card/update.zip
(no such file or directory)
Installation aborted
I copied the update.zip file in DCIM of internal memory card and was still getting the same message.
I copied the update.zip file into my sd card and still got the same message.
I followed the steps exactly as they have been described in the rooting thread.
I haven't tried the one click root method yet.
Would anyone know what seems to be the problem.
Thanks.

You have to replace the update.zip file and flash it with recovery.
Sent from my SGH-T959 using Tapatalk

Are you saying I have to replace with a new update.zip file and repeat the method again?
I was doing it in recovery mode.

Use the one click method. You can find all the info on unlockr.com in the--how to -- (they have a nice video) If it doesn't work then you will need to flash back the T959UVJFD stock through Odin. Look in the bible or search in this website.

Why is your update.zip in DCIM? Download that one from the forum post, rename it to update.zip, and copy it to the root directory of your sd card.

Yea replace the update.zip with a modified one that gives you root access. Its should be on the bible(stickie post) and Recovery mode is correct.
Sent from my SGH-T959 using Tapatalk

Sdobron said:
Why is your update.zip in DCIM? Download that one from the forum post, rename it to update.zip, and copy it to the root directory of your sd card.
Click to expand...
Click to collapse
Can you explain what is the root directory of internal sd card where I need to place the update.zip file?
Yea replace the update.zip with a modified one that gives you root access. Its should be on the bible(stickie post) and Recovery mode is correct.
Click to expand...
Click to collapse
Now my computer isn't recognizing the phone when I mount the sd card. It tries to install drivers for the phone and can not.

Ok, by root directory they just mean the internal 16gb memory.
Ok look, download update.zip. Rename it to "update" without the quotation marks. If you are running windows 7 you dont have to add ".zip" windows knows it is a .zip file, so again just name it update and windows and your phone will automatically know it is update.zip. maybe the problem is you are naming it "update.zip" and your phone is reading it as "update.zip.zip"
Anyways, I don't know why your drivers don't work, but once you get your computer to recognize your phone. Mount your phone to your computer.
Then go to your internal memory, the 16gb one, not the external sd card.
Now, DON'T GO INTO any folders, the root is just the internal memory, again don't go into any folders. Place the "update" file into the internal memory, don't place it into any folder.
Reboot your phone into recovery mode, and then reinstall packages.
good luck.

SamsungVibrant said:
Ok, by root directory they just mean the internal 16gb memory.
Ok look, download update.zip. Rename it to "update" without the quotation marks. If you are running windows 7 you dont have to add ".zip" windows knows it is a .zip file, so again just name it update and windows and your phone will automatically know it is update.zip. maybe the problem is you are naming it "update.zip" and your phone is reading it as "update.zip.zip"
Anyways, I don't know why your drivers don't work, but once you get your computer to recognize your phone. Mount your phone to your computer.
Then go to your internal memory, the 16gb one, not the external sd card.
Now, DON'T GO INTO any folders, the root is just the internal memory, again don't go into any folders. Place the "update" file into the internal memory, don't place it into any folder.
Reboot your phone into recovery mode, and then reinstall packages.
good luck.
Click to expand...
Click to collapse
Nevermind. But thanks alot for your response and help. After looking around to find some alternative ways to root..I finally was able to root my vibrant using the method described
HERE
In the end, rooting was as easy as installing a simple app.
Now im going to do some research on ROMs and hopefully flash before doing titanium backup.

sLiKK said:
Nevermind. But thanks alot for your response and help. After looking around to find some alternative ways to root..I finally was able to root my vibrant using the method described
HERE
In the end, rooting was as easy as installing a simple app.
Now im going to do some research on ROMs and hopefully flash before doing titanium backup.
Click to expand...
Click to collapse
Ok, make sure you do lots of research. Read the bible, every last word of it.
Don't ever try to downgrade from 2.2 to 2.1 without having the proper 2.1 kernal, becareful with lagfix such as voodoo, and learn odin.
good luck

I have run into another issue. I can not mount my phone to computer.
With USB Debugging off... I dont even get a notification in the slide down menu asking me to either mount/unmount.
With USB Debugging on... I do get the option in slidedown menu to mount my phone. At the same time the computer shows a pop up message asking me to install driver software for Samsung_Android. In the meantime , I press mount sd card which by the way is still not recognized by the computer.
I dont have the driver for samsung_android to install on the computer.
Does anyone know a potential fix for this situation.
Thanks.

Finally got my Evo 4G Fixed!

I had a problem with my EVO, here is what happened and how I fixed it.
I rooted my HTC EVO 4g using Unrevoked, it worked fine, then I decided to flash a new rom, followed all the steps and I backed up my stock and wipe data/factory reset and Davik, now my phone doesn't read the sd card, is not even connecting throw usb, not even for charging.
Took the sd card out and did a FAT32 format (4 times already), downloaded the new zip to it and still not reading.
Can't do a restore because I re-formated the sd card and is not reading anyways.
I have another SD card and same thing happens.
As soon as I check install zip from card it reads
ClockworkMod Recovery v2.5.0.1
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(No such file or directory)
E:Can't mount /sdcard
Besides that my computer wasn't reading my phone and my phone wasn't reading my SD card.
I asked and got no answers and thats why I decided on posting this.
Here is how I fixed my EVO, that doesn't mean that is going to fix yours, but is a start.
Also I am not responsible for whatever you do with or to your phone.
For everything I put on SD card I used SD card reader
A) I went to http://forum.xda-developers.com/showthread.php?t=695243
followed instructions for only SD card fix, because I couldn't use ADB.
B) Downloaded the most current RUU here http://goo-inside.me/evo/stock/RUU/ to my computer, then to SD card, went to bootloader, flashed PC36IMG, now my phone is back to stock with out USB connection, doesn't even charge with phone turned on but at least I was able to restart into a ROM. (If you have the same problem that I had, turn phone off and charge it, you don't want to run out of battery in the mids of all this scramble.
C) Download Astro, terminal emulator and root explorer from Market.
D) Download Z4root.apk from here http://forum.xda-developers.com/showthread.php?t=833953 and put it on SD Card
E) Go to http://forum.xda-developers.com/showthread.php?t=829045 and download hboot_2.xx_soff-VX.zip to computer, open it with 7zip then I put the files from step 4 on sd card, if you ignore the part that says adb push, the next is the location of the file on the zip you just opened, got to pay attention to rename the zip with correct name. The last part that says flash_image /data/local/ has to be done manually, just make sure flash_image is on the SD card.
F) Put SD card and battery back, turn phone on as normal, it will boot into rom, open Astro and search for Z4root.apk, long press on it and select application installer, install and don't open.
G)Go to Root explorer, press Mount R/W, select SD card, search for flash_image,
long press, select move, arrow back, select data, then select local and paste image there.
H)On step 6 I couldn't get Terminal to do the first part of backup but got the second part "busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key"
I) After step 7 is done, pull battery and reboot into bootloader, and install PC36IMG as described and at this time I had S-OFF so I rebooted into ROM not to recovery and plug USB cable to computer, USB worked fine so at this point I have many options to finish job.
J) I used after last reboot universal auto root from here http://forum.xda-developers.com/showthread.php?t=838448&highlight=xHausx, run it and done, now I keep flashing different roms.
Hope this help you as it helped me, I take no credit for work done buy any of the OP's of the threads mention above, I just put together all the resources in one place for you to find.
If you feel like donating, donate to them the OP's and if there is any extra I don't mind a pack of mints.

[Q] Instaling zip Rom

after instaling recovery to my phone and copying the Zip rom to the root of my SD card then going to AD recovery instal from Zip the zip file is not shown even after using a card reader, realy stumped has to what is wrong any ideas please

If you have alot of files on your sd card, sometimes it is difficult to find the .zip by scrolling down to it. I have had this happen where using the volume buttons to scroll downward to it wouldn't show the file, but then using the volume buttons to scroll upwards, which loops you up to the bottom, has worked to show the file. I don't know if this is a bug with CWM or what, but it has happened to me 2 or 3 times out of hundreds of .zip installs, and scrolling upwards has always worked for me, maybe will for you too.
If that doesn't work, maybe the .zip is corrupted. Never use MAGLDR's USB Mass Storage option to transfer the file ( surely you know this since you said you used a card reader). Maybe then try re-downloading the rom, transferring with your card reader or mounting the card to the pc using CWM's mounts menu, and try finding it again.
Sent from my T-Mobile myTouch 3G Slide

thanks for the reply i shall give that a go and see if it resolves my problem

[Q] A500 Boot into Recover will not flash update.zip

I have a new A500 that I purchased yesterday from a large national retailer. The A500 was the last one in the store (i.e. the display model).
I have not been able to flash a new ROM to replace the existing by using a microSD card. I have tried different versions of the update.zip file on different microSD cards to no avail.
The tablet will boot into recovery (PWR and VOL-) and starts the process (I get the "opening package" screen with the green robot) but quickly that turns into the "Triangle-Exclamation" screen, and the existing ROM is unchanged. I can just reboot back into the existing rom.
I have been able to use an executable EUUS file to replace the "DEMO" system using a USB cable from my PC, but the sdcard version of the update will not work.
My suspicion is that the bootloader is somehow different on the Demo models, but I don't know for sure.
Any thoughts or ideas?

i know this happened to me when my sdcard wasnt in the right format i had to use ubuntu and format it top a fat. not fat32 just fat and worked fine afterwords

Thanks for the tip, I'll try that. I think you may be on to something because I get the exact same process if I try to boot into recovery with no sdcard at all, so it's like the tablet isn't seeing the sdcard when it is present.

anon2k2 said:
Thanks for the tip, I'll try that. I think you may be on to something because I get the exact same process if I try to boot into recovery with no sdcard at all, so it's like the tablet isn't seeing the sdcard when it is present.
Click to expand...
Click to collapse
If formatting the sd card in linux/ or another Android phone does not work. Try a different sd card. This has been a issue from the beginning of the iconia with some sd cards. and its random.

or if you are as daft as I. When you rename the zip file just rename it as update not update.zip. Then right click - properties - details and you will see it named as update.zip.
When I renames it first time as update.zip then under the details it was named as update.zip.zip

ethan21 said:
or if you are as daft as I. When you rename the zip file just rename it as update not update.zip. Then right click - properties - details and you will see it named as update.zip.
When I renames it first time as update.zip then under the details it was named as update.zip.zip
Click to expand...
Click to collapse
HA! That's happened on about every known device thread at one time or another. You can fix this by changing the Explorer folder options to "display known file types".
(been there, did that)