Related
i have my phone updated to 2.1 and rooted. Want to overclock it now but not sure what im supposed to do with the kernel-overclock-update-v3.zip. I have the original PB00IMG.zip i updated and rooted my phone with, am i supposed to use it somehow?? New to this would appreciate any help.
Just use this, Flash it and it will make ur life easyier.
http://forum.xda-developers.com/showthread.php?t=685581
so phone will be stock again right? have to re dload apps and sync contacts and **** again right?
hmm... or u can try to flash the kernel-overclock-update-v3.zip to the one you have
be sure to nand backup first
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
did you flash recovery?
duckingzebra said:
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
Click to expand...
Click to collapse
Hey man,
When you rooted did you flash the Amon-Ra recovery image? If so put the update zip on the root of your sd. Power down your handset. hold the volume UP and the power on will bring you to the recovery menu. Here you have options for back up,flash from zip etc...once there you can select whatever rom/update you want to flash. Remember nandroid is your friend always back up. Also as far as apps etc...check out Titanium back up or one of the other free back up apps in market. I hope this helps you out.
volume up + end button = Recovery
ok, im following the steps to III: Flashing a Custom Recovery. and when i get to the step :adb push recovery.img /sdcard it says :cannot start recovery.img: No such file or directory...is the recovery.img also supposed to gon on the root of my sd card? or just the tools folder, cause its there?
yes its suppose to be on the root of the sdcard too
still says cannot stat 'recovery.img': no such fire or directory
am i supposed to replace /sdcard with /J (which is what my phone comes up as in my computer) -tried that still didn't work...
can u link me to the tut u are using?
http://forum.xda-developers.com/showthread.php?t=647707
QUOTE=TopazAaron]
duckingzebra said:
did you see the tutorial i linked? still cant figure it out.
Click to expand...
Click to collapse
ok
put the Recovery image in the tools/ in the sdk
after that plug ur phone into the comp
now being there in cmd navigate to the /tools/ folder
then type or copy and paste
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
---
now if you still have issues, let me know, sorry i didnt reply, i got busy with other things.
thanks for ur pm tho[/QUOTE]
ok now instead of saying :cannot start recovery.img: No such file or directory
it says error: device not found, when i open my computer my sdcard in my phone shows up and i can open it...
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
TopazAaron said:
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sorry newser here, irc??
Is your phone actually rooted? To check, turn on your phone, then turn on USB debugging through Settings/Applications/Development/USB debugging. Plug your phone into the computer via the USB cable.
In the run box of your computer, type cmd, then enter.
When the command window shows up, changed you your SDK tools directory. On my system it would be:
cd c:\android-sdk-windows\tools
Then run the following command
adb shell
You're rooted if it comes back with
#
If it comes back with
$
try the typing
SU
if it does not change from $ to # then you might want to try rooting again, and be sure to install the Amon_RA recovery
typing exit multiple times will back you out of adb, and the cmd window.
Hope that helps.
Edit: Of course that works for 2.1 leak 3 users as well.
Easier way for you tho, if you boot to hboot with the send and end buttons, you should see hboot with S off if you're rooted. If it's S On you're not.
Hi guys, so I've done tons of searching & I still can't seem to get this work.. I'm running CM7 #21 & I'm trying to install adfree using the tutorial here.. For some reason I just can't seem to get ADB shell commands working.. I can put my phone into recovery via ADB, no problem, but that's about it.. When I try running recovery-windows.bat I get "directory not found" errors, from what I can see it's looking for a "files" folder, which I don't have, & I've downloaded the SDK 3 times! Initially I didn't even have a recovery-windows.bat file, I found it somewhere & modified it.. Anyway, I've attached pics of the steps I've done, could someone tell me what I'm doing wrong, or guide me in the right direction...? thanks in advance...
Using fakeflash will get you to recovery more easily. Look in the roll up sticky for that Once in recovery the adb push syntax is thus:
adb push [file on PC] [location on phone]
For pushing a directory, c:\foo to the phone's data partition you'll want this:
adb push C:\foo /data/
Or you could use wildcards:
adb push C:\foo\* /data/foo/
The latter option is probably easier
EDIT:
I notice that this was your first post. Welcome!
Thanks for the help & welcome! What I didn't realize all this time was that I had to reboot in ClockworkMod recovery & not normal recovery, but by you directing me to the fakeflash post I figured it out.. Btw, the download link at modaco.com for the update.zip file is dead...
Rename to update.zip: http://dl.dropbox.com/u/3382637/recovery-update.zip
Hay, my name's Nick, been reading the posts for a while, decided to join. Iv'e been wanting to root my T-mobile vibrant so i can get a more streamlined ROM will less features to make the ones i use go smoother and faster and get the full potential out of the device. I rooted it no problem with one click root, installed clockwork rom manager, and titanium backup, installed clockwork recovery (i love the clockwork orange icons by the way) put the latest "insanity 0.6.7.zip" in the root of the internal SD, and hit the "install rom" option on the rom manager and selected the .zip, and it made my phone go into the standard recovery mode, no option to install any .zip files. So i opened the rom manager and manually put it into CWM recovery so i could manually install the rom. It looked like it was going to work, but then it sent my phone back to the recovery screen with white text that said "install update.zip" so i did what it said, and it sent my phone into a boot loop. I can get into recovery mode, but when ever i try to recover my backup or access any files it says "no files found, operation canceled" or something like that. It also fails to mount via USB. I can get it to go to download mode but have not tried odin yet, because im on a mac (working on getting bootcamp working now to run windows)
Odin seems like my only option now right? anyone have any idea ware I went wrong? it must have been the incorrect update.zip file right?
I dont think u flashed a vibrant rom
Just mount your internal sd from clockwork and copy over a vibrant rom, and flash
Sent from my SGH-T959 using XDA Premium App
have any idea why it wont let me mount my sd card? that makes me worried it wont connect to a Pc in download mode but i haven't had the opportunity to try that yet.
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
when it booted up it went to my normal "vibrant" screen, then to an unfamiliar "galaxy s 19000" screen. Im assuming there is a difference between galaxy s and vibrant right?
jRi0T68 said:
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
Click to expand...
Click to collapse
tried that, when i try to to install zip from sdcard it says "no files found"
i assume it's looking for files on the internal and not the external right? so i tried mounting the external sd card from the mounts and storage menu, and i got an error message that said "E:INFO is WRONError mounting SDEXT !"
In recovery, do you see any folders when you click install from zip, or is that when you get an error message?
If you see folders, can you navigate to external_sd?
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
amandadam said:
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
Click to expand...
Click to collapse
That's useful for me as well.!
shreddintyres said:
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
Click to expand...
Click to collapse
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
niik000 said:
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
Click to expand...
Click to collapse
Never rename rom zips to update.zip leave it at bionix.zip and flash through clockwork mod recovery.
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
niik000 said:
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
Click to expand...
Click to collapse
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
i ran the SDK and AVd manager and installed the rest of the SDK packages, then found the ADB file and drug it into the terminal, that gave me the list of commands. I plugged in the phone and tried "adb devices" and it said "command not found" tried quitting and restarting terminal a few times and still nothing
shreddintyres said:
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
Click to expand...
Click to collapse
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
niik000 said:
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
Click to expand...
Click to collapse
thats a security feature within linux it wont show what you are typing but rest assured its registering keystrokes, and you dont drag and drop to terminal
assuming the androidsdk is in your home directory you would type
cd /home/username/android-sdk/platform-tools
then ./adb devices (this is just a check to make sure your phone is being recognized)
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
niik000 said:
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
Click to expand...
Click to collapse
ok so you are doing this from mac then? i apologize as i have no experience messing with android using a mac, id imagine itd be much like linux although terminal commands may be different. If i were you id google using adb commands in mac os and see what you can find, personally i use windows normally and am only just learning how to work linux
Looking for anyone with a new NS4G to dump a copy of the radio. I messed up and flashed a rom that had a gsm radio attached. rendering my phone useless as far as phones go.
root
post a good root method and how to do the dump. I can have it hotlinked in 1 hour
i used http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
worked just fine.
Once you're rooted, do
Code:
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
Then upload that ns-cdma-radio.img somewhere ;D
?
ok thanks, i will link it when finished
the dumped file will be in my phone memory, correct?
ryandoubleu said:
ok thanks, i will link it when finished
the dumped file will be in my phone memory, correct?
Click to expand...
Click to collapse
It will be on your internal storage that you can mount as a drive on your pc, yes.
may take...
may take longer than an hour as I am doing the SDK install
ryandoubleu said:
may take longer than an hour as I am doing the SDK install
Click to expand...
Click to collapse
You don't need the platform api, just the SDK tools/platform-tools , that'll save you a lot of download time.
yes i should have mentioned that. i didn't install the SDK either just the tools.
just like http://forum.xda-developers.com/showthread.php?t=878786
hmm
fastboot command wont work? troubleshooting as we speak
ryandoubleu said:
fastboot command wont work?
Click to expand...
Click to collapse
instal drivers?
look to the 2nd rooting method i posted. the 2nd file you download are the drivers. you would install it when your phone is in fastboot mode then go to device manager and upgrade the driver
unzip the rar file and make sure to select x86 or x64 driver for your pc.
you should be able to type "fastboot devices" hit enter and it will return your phone if you have the drivers installed
Also the simplest method to get the drivers might be to put phone into fastboot mode, plug USB to computer, then install PDA Net (which automatically installs the phone drivers). I personally could not get the drivers to install manually on Windows 7, had to use the PDA Net method.
CMD is giving my a Permission Denied with this command
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
ryandoubleu said:
CMD is giving my a Permission Denied with this command
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
Click to expand...
Click to collapse
Try this: (I am assuming you've already finished rooting and installed superuser)
run adb shell
that should give you a "$" prompt in your command window (you've just shelled into your phone)
then type "su" (without the quotes)
On your phone, a superuser request should pop up on the screen, hit Allow
Your command prompt should change to a #
then type
dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
*EDIT: made a typo in the original writeup of this post and left out the count parameter*
(no adb shell required before the dd command this time since you're already shelled into the phone)
here it is
http://www.megaupload.com/?d=H3Z7RQLZ radio image for you
Also, from the first root method I cant find this file and move forward
4. Tap on the gray box that says Mount R/W
5. Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
6. Once renamed, download and install the app called ROM Manager from Android Market
7. Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
ryandoubleu said:
http://www.megaupload.com/?d=H3Z7RQLZ radio image for you
Also, from the first root method I cant find this file and move forward
4. Tap on the gray box that says Mount R/W
5. Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
6. Once renamed, download and install the app called ROM Manager from Android Market
7. Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
joebags said:
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
Click to expand...
Click to collapse
Actually the point of renaming that script is to prevent clockwork from being overwritten by the stock recovery.
The default stock rom is set up to re-flash the stock recovery from cache on bootup if it detects that it's been changed (which is very annoying if you *want* clockwork recovery).
thank you very much for uploading that for me
now correct me if i'm wrong netarchy but i would use fastboot to flash the img file?
I just want to double check before i mess up once again. i'm pretty smart and a quick learner but not a pro like yourself
worked?
joebags said:
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
Click to expand...
Click to collapse
the radio.img got you working?
Hello everyone.... i really think i bricked my device and i would love for someone to help me... i Have been searching the forum since yesterday morning and i cant seem to find anything that works... well first off i am rooted (s-off) i used the gfree method because setting up adb wasnt going to well for some reason... but im stuck in bootloop mode or whatever and when i hold down power and the vol down button it recognizes the pd15dimg.zip file but when i do the update i get an error check out the first pic below... then when i put it in recovery mode i get another error check out 2nd pic... then when i to to load the pd15dimg.zip manually from the choose zip file directly from the root of the sd card i get another error check out third pic... as u can see im on cwm 3.0.2.4 and the rom i was originally using i dont remember the name but it was gingerbread...can someone plz help?? any help will be appreciated. thnx
I had this same issue 3 weeks ago. But I wasnt getting those partition errors with the PD15dimg.zip. I would first suggest downloading another one to make sure the one you got wasnt corrupted. But before I figured out to do the pd15dimg trick, the nice fellas over on Cyanogenmods Shoutbox were helping me out with a different method. You have the engineering bootloader, which is great news for you. I did not. Do you have a nandroid backup on your SD that you can copy over to your computer?
i didnt do a nandroid back up but i did a back up threw the rom manager i had... is that useful?
curlz187 said:
i didnt do a nandroid back up but i did a back up threw the rom manager i had... is that useful?
Click to expand...
Click to collapse
Hmm. Maybe, I'm not sure what that backs up, do you know what folder that went into? Find it and post whats in there
the folder is on the root of my sd card... its call clockworkmod... i click that then i see two folders one of which is named back ups. i click that and it has tsome some files in it such as android_secure.img boot.img cache.img data.img nandroid.md5 recovery.img and system.img
curlz187 said:
the folder is on the root of my sd card... its call clockworkmod... i click that then i see two folders one of which is named back ups. i click that and it has tsome some files in it such as android_secure.img boot.img cache.img data.img nandroid.md5 recovery.img and system.img
Click to expand...
Click to collapse
Perfect! Alright, PM now and I'll help you with the rest alright?
Ok just did it
does anyone else have any insight on this subject?
Once you get fail-pu you can't do anything as you need to send it back they have to replace the motherboard. Fail PU means failed partition update at this point once its corrupted you can't reformat it since we are using SLC-EUDA low level format which is 1 time.
TmpUsr said:
Once you get fail-pu you can't do anything as you need to send it back they have to replace the motherboard. Fail PU means failed partition update at this point once its corrupted you can't reformat it since we are using SLC-EUDA low level format which is 1 time.
Click to expand...
Click to collapse
the original file i used was corruted JDV28 sent me another file and it starts the update but idk how long its suppose to take because its been updating for bout 15 mins now
Well PD15IMG.zip can be corrupted and even if you get a good radio/rom image and verify it the problem you will run in to is when you try to write to the partition. Fail PU means failed partition update where you can't write radio, recovery and system. I was leaning on to gfree but I need another phone to fully hack it as I was massing with the emmc block last time but atm I don't have any other phones. Best solution is soon as you see the errors on recovery you should push and manually flash recovery partition and replace it.
TmpUsr said:
Well PD15IMG.zip can be corrupted and even if you get a good radio/rom image and verify it the problem you will run in to is when you try to write to the partition. Fail PU means failed partition update where you can't write radio, recovery and system. I was leaning on to gfree but I need another phone to fully hack it as I was massing with the emmc block last time but atm I don't have any other phones. Best solution is soon as you see the errors on recovery you should push and manually flash recovery partition and replace it.
Click to expand...
Click to collapse
how do i do that?
Terminal said:
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
flash_image recovery /sdcard/recovery.img [hit enter]
Click to expand...
Click to collapse
adb said:
adb devices [hit enter]
adb push boot.img /data/local/boot.img [hit enter]
adb shell [hit enter]
su [hit enter]
flash_image boot /data/local/boot.img [hit enter]
rm rm /data/local/boot.img [hit enter]
Click to expand...
Click to collapse
Like I said depends on how deep the issue is you can't revert it. But try it anyways. You will need image which you can get from dev section.
im not connected threw adb had problems setting it up b4... but after i did the update now my screen only turns black? idk what happened it was updating i leave for a min now it seems unusable
I had the same issue, couldn't recover it so I sent it back.
Sent from my HTC Glacier using XDA Premium App
partitioning issues most likely = game over unless your running the engineering boot. thats the bottom line i think with everyone thats running into these issues..