Related
It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service.
EDIT: problem solved, i was trying this whole time to flash another recovery inside recovery, i actually left the phone on and pushed the recovery lol no more ghanja.
see the # symbol when you enter teh shell? that means you have root already and su isn't necessary. Also try unplugging then plugging back in, the phone from the usb. The file not found error probably means that the sd card is mounted. do an ls from /sdcard to make sure
Also try "adb mount" over "mount -a".
DISABLE usb debugging.
i know, its the little things we overlook. i just did this last night and forgot to disable it.
i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck
i kept getting these errors what i did and found easiest with no errors is save the recovery in the sd card. download terminal emulator then in terminal emulator su then enter
then type flash_image recovery /sdcard/nameofimage.img
someone please make sure my prompts are right as i hadn't done it in awhile.
I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?
Maitiu said:
I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?
Click to expand...
Click to collapse
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)
Demoyo23 said:
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)
Click to expand...
Click to collapse
you try using the terminal emulator method directly on the phone? only way i can get to work and works everytime.
I'm working on that now, but I tried that a few days ago and got different errors, I'll post what the specific error was when I get there in a few minutes. For some reason Superuser Permissions is force closing right now.
Yeah even from the terminal emulator, I get a "not found" error.
I just updated today from RA1.5.2 to RA1.6.2. I used the Recovery Flasher to update to the newer version as that is what I had originally used to get 1.5.2 installed.
These were original instructions from theunlockr .com:
7. Save both the Recovery-RA-HEROC-v1.5.2.img and the FlashRec.apk to your computer, then copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
8. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
9. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it. It should automatically install the apk.
10. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
11. Once done, click on the empty text box in the FlashRec program and type (again remember we have replaced the recovery image from the one in the video so type what is written here, NOT what is written in the video!):
/sdcard/recovery-RA-heroc-v1.5.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.
Just barely.
That's still not working flashrec won't back up it keeps saying failed. And it won't flash a custom img. This refurb is cursed I had no problem doing it all on my original.
-------------------------------------
Sent via the XDA Tapatalk App
Demoyo23 said:
It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service..
Click to expand...
Click to collapse
Type 'adb devices' in... Whenever I see the '/' before the '#' it means that it isn't recognizing my phone.
Just do it through adb. I did mine through adb the 1st, 2nd and 3rd time. After looking at the dirwctiona, I think it might be easier and should work.
-------------------------------------
Sent via the XDA Tapatalk App
Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.
liquidtenmillion said:
Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.
Click to expand...
Click to collapse
it keeps telling me permission denied lol
Type in
"adb shell" then
"ls /sdcard"
Without the quotes exactly as I typed them one at a time and paste the results.
dirkydirk23 said:
i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck
Click to expand...
Click to collapse
did you try fastboot boot recovery [dir on your computer]
Do a search for adb shell recovery. It should tell you how to do it. You are going to have to mount the system before doing anything else...and also change the recovery image to something Like recovery.ing as it is easier to type and less likely to be mis-typed
-------------------------------------
Sent via the XDA Tapatalk App
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
I9000 drivers
I9000 drivers
This solution is is not working for me. The problem is that the Update.zip says:
E: Signature verfication failed
Installation aborted
Any advice? How to install that update.zip package?
cellularhut said:
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
Click to expand...
Click to collapse
Fantastic find if it works, my phone is unlocked so I can't test it but thanks a lot for sharing!!! Priceless
N.B. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
tyxerakias said:
fantastic find if it works, my phone is unlocked so i can't test it but thanks a lot for sharing!!! Priceless
n.b. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
Click to expand...
Click to collapse
1000000000000000% working tested before post here !!!!!
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
erreterr said:
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
Click to expand...
Click to collapse
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Tyxerakias said:
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
Click to expand...
Click to collapse
No idea. Have you rooted your phone already? Have you installed any mods or firmwares?
No need to root
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
knkartha said:
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
Click to expand...
Click to collapse
Huh. Interesting. I would have thought /efs is a protected folder.
I have a Bell one, i asked their staff when i bought my phone if i still on WARRANTY when i unlock the phone by Bell, they said yes.
Anybody know if i will lose my phone WARRANTY after i unlock the phone? Or can i lock it back if my phone have any problem in the future?
Thanks
could somebody point out which value in the address 00181460 says the unlock code?
erreterr said:
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Click to expand...
Click to collapse
you should put the update.zip file on your internal sd card directory.
i encountered the same error when i put the update.zip file in the external sd card
erreterr said:
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
Click to expand...
Click to collapse
which of the values in the said address gives the unlock code?
Hi,
I have a NSPRO box and read the unlock code, but as I insert it, it doesn't unlock the phone.
As this didn't work, I tried your method, and the code that showes up is the same as read by NSPRO box, and... it still doesn't work.
Attached is the printscreen of the HEX area where the code is. I've noticed it says "18146D" and not "181460" as your indicated. Could this be the reason why the code doesn't work?
Please help...
Samsung Vibrant SGH-T959 Recovery Mode
I've tried all sorts of button combinations to get the Samsung Vibrant T959 into recovery mode. I think since this device is a T-Mobile phone, the firmware has been modified for VolUp+VolDn+Pwr recovery mode.
As of now, the only way I know how to get the phone into recovery mode is by using the Android SDK and sending off a command: adb reboot recovery
I've been putting together an Android SDK & Rooting tutorial as well as other Samsung Vibrant T959 findings here: jordanpeterson.me/content/t-mobile-samsung-vibrant-sgh-t959
Sorry.. the external references aren't working.. Good spam rules on new users.
Thanks
Jordan
It worked great, althoug the address on my I9000 was 00181462. My suggestion is try to find closest address to the given by the tuturial....
Thanks for everything
Don't need to root the device. Download terminal emulater from Market. Went straight to step 10. Works like a charm. Thanks for the instructions.
Sent from my GT-I9000M using XDA App
I did exactly what was written in the Development Section and more but unfortunately i couldn't manage to root it
First of all do i have to say i am no expert in these matters. Well i am not.
Somethings are missing in the guide for people who are not familiar with these things. For example it doesn't mention about how to create platform-tools folder in android-sdk-windows. I thought maybe i could do it from software and updated&installed bunch of things. Than voila i got the platform-tools folder.
In the "Setting up adb on the nook touch:" section we were told that write noogie to sd boot it and eject it away. And are we done with the sd card in the next sections ? Anyway i assumed as i don't need the card anymore and put it away.
When i came to "Setting up root acces on NST through adb and installing busybox:"
do the steps and entered the commands to Command Prompt(CMD). Everything seems fine but Nook didn't boot. I think maybe i can go to next step and enter those commands. I did it but it didn't boot either. So i manually booted the device and entered first line of commands again right after that finally Nook booted!
So i thought i only did the first command line set in the "Settin up root access on NST thorugh...." section so that i entered the second command set again but it didn't booted. And than i have proceeded to the next steps for the chance that if it went fine but directions made me thought it didn't. But when i came to Launcher and gapss part , it didn't boot so i figured that somethings was not right.
I don't know wtf is wrong but i thought maybe i should format and plug the sd card or just plug with noogie right after i thought we were done with sd card. So i did all those steps with the sd card formated and with noogie sd... It was all same.
Sorry for my unpleasant english. Please help me. For the "please help me lord" line i am sharing this song with you youtu.be/kLCCEipgmJQ
xisini said:
In the "Setting up adb on the nook touch:" section we were told that write noogie to sd boot it and eject it away. And are we done with the sd card in the next sections ? Anyway i assumed as i don't need the card anymore and put it away.
When i came to "Setting up root acces on NST through adb and installing busybox:"
do the steps and entered the commands to Command Prompt(CMD). Everything seems fine but Nook didn't boot. I think maybe i can go to next step and enter those commands. I did it but it didn't boot either. So i manually booted the device and entered first line of commands again right after that finally Nook booted!
So i thought i only did the first command line set in the "Settin up root access on NST thorugh...." section so that i entered the second command set again but it didn't booted. And than i have proceeded to the next steps for the chance that if it went fine but directions made me thought it didn't. But when i came to Launcher and gapss part , it didn't boot so i figured that somethings was not right.
Click to expand...
Click to collapse
Download noogie, and burn it into an sd-card (http://www.multiupload.com/OFI609MP8V) use Win32DiskImage.exe.
Shut down the Nook Touch completely your NST http://www.multiupload.com/CJ981FWPJG
Insert the sdcard into your Nook, connect it to the pc and turn it on.
When the nook ends booting (you should see a rooted forever spash screen on it) wait 20 seconds, you should see a new drive named boot, if not, go to MiniTool Partition Wizard Home Edition look for a parition named boot and asign it a letter.
Open boot, and replace the uramdisk, with this one http://www.multiupload.com/CJ981FWPJG.
Eject the nook from the pc and reboot without the noogie sdcard.
Download java JKD http://www.oracle.com/technetwork/ja...ads/index.html
Download the android sdk (I recommend zipped) and extract it on C so that it looks like C:/android-sdk-windows
I will add an step next, that is open the sdk, and update it.
And for the second comand line...... its adb connect yourNSTip where yourNSTip means... your Nook Single Touch IP address, so find that out and right it instead.
Read carefully, if you dont know what you are doing, you are better off using the touchnooter method, wich is simple and just works as intended and you wont mess things up so easily.
I don't know why you enlarged reboot part which i did correctly. And there is nothing wrong about ip adress part. If you would read carefully! I wrote that it is just didn't reboot automaticly as it is in the command line.
Btw if i would know what am i doing i would not need a guide so did you open that topic for just to proove that you did this. What kind of behavior is this ? Reread what i wrote or just don't try to help me with your blindfold and arrogance. I suppose there will be polite person in XDA who can help me out.
I posted the topic to help someone in particular and of course anyone who wants to use it, and myself to remember.
I couldnt understand halve of what you wrote, and I know you appologised for it so I didn't mention it.
As it says, this is a first draft, there may be typos, next time just say where you got stuck clearly, it'll be easier............
Now, I know you got stuck on the reboot at rooting, you shouldn't but I'll change the code a bit.
I also didnt intend to be rude, maybe you read me wrong, maybe you are the one being arrogant here as you got mad because I enlarged reboot, allthough I was trying to help you even if I was wrong.
If you have 0 adb experience I recomend you try touchnooter, its easier and faster, if you intend to learn adb, my guide is self explainatory, and just copying one by one the commands on cmd is enough, learn to follow instructions.
Don't worry I wont help you again
This becoming a pissing contest and i don't want to talk about it anymore.
So here is the thing. I have tried this method
mobileread.com/forums/showthread.php?t=156539 "i couldn't make it a link because i had few posts"
And it worked out well until pushing Vending.apk
Here are the things i did to make it work
1- Opened up and turn on Adb wireless widget
2- Located the Vending.apk to c:/android-sdk-windows/platform-tools/system/app
3- And then wrote these commands
cd C:/android-sdk-windows/platform-tools
adb connect 192.168.2.20:5555
mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push vending.apk /system/app
C:\android-sdk-windows\platform-tool>adb push Vending.apk /system/app
182 kb/sn (2123059bytes in 11.380s)
Click to expand...
Click to collapse
It seems okay but when i try to search from market i see that it is not.
This has whooped my a$$ all evening and I've finally found some sort of a work-around for it, thought I'd share.
When I flash a ROM, I really like to nuke everything. Problem with nuking everything is you often cannot mount the phone to the computer to copy over the shiny new Rom
So here's the scenerio:
You're in recovery, you can't mount an SD, you've accidentally (or otherwise) deleted everything off of the INTERNAL card (including your new rom). Clockwork for some reason or another hates you and won't let you mount USB to transfer the ROM over for install. So you're officially dead in the water with no hope in sight.
three magic letters come in to play on this one. ADB.
http://forum.xda-developers.com/showthread.php?t=502010
Moving on now to the point of Post-ADB-Installation...
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory (mine was installed on the C: drive, but yours is wherever you installed it)
Open a CMD.exe window (start, cmd, enter)
navigate yourself to the ANDROID-SDK/PLATFORM-TOOLS/ directory
type this command:
adb push shiny.new.rom-name.zip /sdcard/
now go back to the phone, back into recovery, install from sd, laugh all the way until the next time you think you've destroyed your $600 smart phone.
Hope this works for you!
skipster99 said:
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory
Click to expand...
Click to collapse
Or you could add PLATFORM-TOOLS to your PATH environment variable like most people do.
Also, try Droid Explorer.
skipster99 said:
This has whooped my a$$ all evening and I've finally found some sort of a work-around for it, thought I'd share.
When I flash a ROM, I really like to nuke everything. Problem with nuking everything is you often cannot mount the phone to the computer to copy over the shiny new Rom
So here's the scenerio:
You're in recovery, you can't mount an SD, you've accidentally (or otherwise) deleted everything off of the INTERNAL card (including your new rom). Clockwork for some reason or another hates you and won't let you mount USB to transfer the ROM over for install. So you're officially dead in the water with no hope in sight.
three magic letters come in to play on this one. ADB.
http://forum.xda-developers.com/showthread.php?t=502010
Moving on now to the point of Post-ADB-Installation...
Find your shiny new ROM, and copy it to the ANDROID-SDK/PLATFORM-TOOLS/ directory (mine was installed on the C: drive, but yours is wherever you installed it)
Open a CMD.exe window (start, cmd, enter)
navigate yourself to the ANDROID-SDK/PLATFORM-TOOLS/ directory
type this command:
adb push shiny.new.rom-name.zip /sdcard/
now go back to the phone, back into recovery, install from sd, laugh all the way until the next time you think you've destroyed your $600 smart phone.
Hope this works for you!
Click to expand...
Click to collapse
All well and good but my simple method after a wipe is to flash a stock rom then CWM root and copy file over .No need to bother with all that Linux stuff and probably easier for noobs and nearnoobs .
jje
I'll check out droid explorer - Thanks
As far as "all that linux stuff" I think one ADB PUSH command from WINDOWS is easier and faster than loading another rom on to the phone. Do what you wanna do, was just something I stumbled upon to help other noobs stuck in the same situation.
skipster99 said:
I'll check out droid explorer - Thanks
As far as "all that linux stuff" I think one ADB PUSH command from WINDOWS is easier and faster than loading another rom on to the phone. Do what you wanna do, was just something I stumbled upon to help other noobs stuck in the same situation.
Click to expand...
Click to collapse
So now they have two methods pity they will never look or search .
jje
+1 for all that linux stuff -- I love it! Droid Explorer is nice too but I feel like a wuss when I use that program because all its doing is executin linuxy stuff.
Hey, WHY are you nuking your sdcard? Thats overkill!!! but whatever floats your boat!
Good morning,
I'm trying to downgrade and root my device but I'm always stopped:
1- when i reboot my device on bootloader it scan the PD15IMG.zip and nothing(wrong zipped file) .
2- I can't proceed to recovey that dont work .
I want to root my HTC mytouch 4g and have the ability to explore it's capacities.
I'm so sorry for any mistakes in my english thats my first speech.
Have I a chance to root my device?
Thank's
with greeting
snayfer
snayfer said:
Good morning,
I'm trying to downgrade and root my device but I'm always stopped:
1- when i reboot my device on bootloader it scan the PD15IMG.zip and nothing(wrong zipped file) .
2- I can't proceed to recovey that dont work .
I want to root my HTC mytouch 4g and have the ability to explore it's capacities.
I'm so sorry for any mistakes in my english thats my first speech.
Have I a chance to root my device?
Thank's
with greeting
snayfer
Click to expand...
Click to collapse
Go to cyanogen glacier wiki you will find a the info and links you need to download
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
SAME THING HAPPEN TO ME FOR SOME REASON SOME HTC MYTOUCH 4gs WONT LET YOU MANUALLY DOWNGRADE don't know why. I have rooted over 3 mytouch 4gs and never had this happend.. Will I found a solution to finally root mine.
use this guide
http://forum.xda-developers.com/showthread.php?t=1178912
**Make sure you do the Fast boot Method INSTEAD OF MANUEL DOWNGRADE if you are having the problem where you can't downgrade MAKE SURE YOU READ EVERYTHING CAREFULLY
Sent from my Glacier using xda premium
That seems way harder than just grabbing the stock rom, renaming it PD15IMG.zip, holding volume down + pwr button on boot and flashing it. Why all those extra steps with adb and whatever?
Search this forum for a new zip file if the one you have is wrong.
willshep said:
That seems way harder than just grabbing the stock rom, renaming it PD15IMG.zip, holding volume down + pwr button on boot and flashing it. Why all those extra steps with adb and whatever?
Search this forum for a new zip file if the one you have is wrong.
Click to expand...
Click to collapse
Why? Because for newer ROMs it doesn't work this way, and they're not rootable. That's why it's called "downgrading".
Jack_R1 said:
Why? Because for newer ROMs it doesn't work this way, and they're not rootable. That's why it's called "downgrading".
Click to expand...
Click to collapse
Oh, I didn't realize that. I figured the hboot process would replace the system with the one from PD15IMG.zip. I guess we learn something new everyday
HBOOT only does it when it "thinks" the PD15IMG.ZIP contains something newer than what actually is on the phone. Thus the need to "hack" the /misc partition to make the HBOOT "think" it's older than it is.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I had this problem as well. Luckily there is a solution.
Plug in your phone, and open up My Computer and click on your Removable Disk icon so that it's highlighted (do not double click).
On the bottom, does it say File System: FAT32?
If the file system is not FAT32, you will receive that error.
There is a way to convert your SD card to FAT32, but this will clear all data on your SD card. Hence, I recommend making a backup. The process is quite simple, it took me about two minutes.
Open up command prompt (cmd in the search)
Now type in the following command at the prompt, replacing the X with the letter of your external hard drive of your SD card (For example, if plugging in your phone makes a Removable Disk (G appear, then replace the X with a G):
format /FS:FAT32 X:
This will format your SD card to a FAT32 file system. Once this is done, try flashing again and please tell me if it works.
Good luck