i have a tmobile g2 and used visionary to root and it did not work right but my s-off and i can not root any way i try,if i have stock rom what do i have to do to reinstall the stom rom and will this make my g2 go back to s-on?
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
renn9420 said:
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
iv tried that and nothing works at all,i was told i needed s-on again because s-off is what i have and no matter what i try i can not root this **** phone!!!!!!im ready to throw it out the window.
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
steviewevie said:
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
Click to expand...
Click to collapse
im about to try it
hightechlive said:
im about to try it
Click to expand...
Click to collapse
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
hightechlive said:
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
Click to expand...
Click to collapse
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
steviewevie said:
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
Click to expand...
Click to collapse
yes i did get forked xxx children message,but i this is different for me
init_module 'wpthis-OTA.ko' failed
i get this
local/tmp/init_module 'wpthis-OTA.ko' failed
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
fastludeh22 said:
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
Click to expand...
Click to collapse
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
hightechlive said:
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
Click to expand...
Click to collapse
*Following instructions in that post includes a wipe. This will delete settings, 3rd party apps, mms etc. Be sure to backup what's needed.
These directions are for windows computers:
Do not unzip the file. It should be clockwork recovery 2.x.x.x.img. just rename it recovery.img. The root of c just means not in any folders. So after naming it recovery.img put it on c. It will then be c:\recovery.img
Then when you open up cmd window, goto sdk folder like when you use adb. With your phone booted into hboot with usb connected. You type this into cmd window: "fastboot flash recovery recovery.img" without the quotes. Then finish following pervious link.
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
i type in command window but it says can not load recovery img
hightechlive said:
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
Click to expand...
Click to collapse
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
fastludeh22 said:
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
Click to expand...
Click to collapse
i type in command window but it says can not load recovery img
im doing everything you said?
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
fastludeh22 said:
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
Click to expand...
Click to collapse
i did that,this i what i did i download and change the name and put the zip file in the c root,open command and went to the tolls folder after the other things to get there in command and this is what it says
says can not load recovery img
What zip file? The recovery should be an img file.
fastludeh22 said:
What zip file? The recovery should be an img file.
Click to expand...
Click to collapse
that what im saying when i down load the file if is zip up and when i unzip it says i can not open it?
when i download it this is the name of the file
recovery-clockwork-2.5.1.2-vision (1)
I went to clockwork thread and clicked link. It dl's as .img file for me. This is the direct link I'm talking about. http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
If your using that, check this. In an open window/folder in windows. Click tools, then folder options. Select view tab. Uncheck "hide extensions of known file types". Then the file extensions should show at the end of every file. Make sure its named right now.
Related
HTC Desire USB Bricked Without Root
Hey guys, got a really tricky one for you here...
Some people may have seen a thread I posted the other day about problems that had arisen with my HTC Desire, well I have managed to find out that these problems are being caused by a USB Brick.
As of now I have managed to restore SD Functions however my phone will still not connect to the computer, and the phone won't recieve a network signal from Orange.
I read through this tutorial here and also this one here. My problem is, all the requirements of the fix, my device does not meet. My phone is not rooted, it is running the latest software and has the latest HBoot.
I also found this that looked very promising, however when I tried to log into my Google account on my phone, everytime it said it couldn't make a connection, I left it for a few hours and the same thing, I can't help but think this is due to the USB brick?
I just really need some help, is there anything I can do to restore USB functionality? The phone is being sent to HTC tomorrow, however I can cancel at any point. Please, I know there are so many amazing people on XDA that can help me. Thankyou
*UPDATE* - After using the Fastboot code to enable the SD Card, my Sim Card is now working. I have been able to log into my G-Mail account and download the terminal emulator which is an apparent fix in one of the posts I linked above, however this doesn't work. Please can someone help me
hy did you try to reinstal the software ???? the original os or an upgrade??
en_mih said:
hy did you try to reinstal the software ???? the original os or an upgrade??
Click to expand...
Click to collapse
I have done a factory reset, re-installed the PB99IMG and also flashed an RRU. All the problems persist
Really need help with this guys! E-Mail - [email protected]
jaaystott said:
Really need help with this guys! E-Mail - [email protected]
Click to expand...
Click to collapse
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
leinad said:
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
Click to expand...
Click to collapse
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
HQRaja said:
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
Click to expand...
Click to collapse
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
jaaystott said:
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
Click to expand...
Click to collapse
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
leinad said:
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
Click to expand...
Click to collapse
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
jaaystott said:
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
Click to expand...
Click to collapse
:-( (10 characters)
leinad said:
:-( (10 characters)
Click to expand...
Click to collapse
I really appreciate the help you gave me mate, even if I asn't able to fix my device, thankyou for the time.
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
moley10 said:
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
Click to expand...
Click to collapse
I found a way around this, as I was having the same problem. Try This ->
cat /sdcard/rageagainstthecage-arm5.bin > data/data/rageagainstthecage-arm5.bin
Do that for the two other commands that follow that, then follow the instructions as given, that should work.
HQRaja said:
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
Click to expand...
Click to collapse
Link to your blog? =)
ok, so i did that, no longer got errors.. seemed to work but after reboot still the same, doesnt connect to my pc, and device manager it is still being shown as 'qualcomm cdma technologies msm' in other devices!
is the purpose of those commands to moved the files to certain directory? i can get temp root with visionary to perhaps just move the files in root explorer?
thanks for all the help. its much appreciated!
Hello,
I've got a similar problem but this solutions doesn't work for me, because I cannot create a CID.
Any ideas?
Thanks in advance
hi,
i managed to create files etc and still am stuck with the same problem... searched hi and low for days,
hopefully someone will be able to find us a solution..
You mean creating the mtd from that site? Thats because you need to type the Build Number not the kernel version.
Hi I have followed this guide exactly (http://forum.xda-developers.com/showthread.php?t=905003) and when i open command prompt and navigate to the downgrade folder i get stuck on the command:
"adb shell chmod 777 /data/local/tmp/GingerBreak"
I get the following error message "adb shell chmod 777 /data/local/tmp/GingerBreak: permission denied"
I have looked around for solutions but still cant find any way to fix it, help is very much appreciated!
Usually that would only happen to me if gingerbreak was already pushed to phone. Have you tried rebooting your phone and starting over?
Sent from my HTC Desire HD using XDA Premium App
hi, yes i have restarted my phone and now i get stuck on the command:
"adb push GingerBreak /data/local/tmp"
and get the error message "cannot open 'GingerBreak' : no such file or directory'
But when I go into my downgrade folder it is definetly there...
What software version are you currently using, is it one that can actually be downgraded at this time?
If GingerBreak is transfered try running it.
adb shell
./data/local/tmp/GingerBreak
what happens then?
alternatively try this guide instead, it helped me: http://forum.xda-developers.com/showthread.php?t=1152233
Hi thanks for the reply, when i do the command "adb shell /data/local/tmp/GingerBreak" i get the message "ermission denied"
hope this helps, will look at the link you posted
also my version of software is 2.36.405.8
Yeah follow the guide given above (http://forum.xda-developers.com/showthread.php?t=1152233)
also re-download the downgrade tools. If you running windows 7 make sure you dont extract them directly to the c drive. first extract to some d drive or so and then copy paste to c drive or directly given the d drive path in the cmd.
Also make sure you are logged in as admin in the system. and run the cmd after right clicking and selecting run as administrator .
and also you are deleting the older PD98IMG zip file and doing all the cmd stuff after downloading the stock PD98IMG zip file and putting it in the sd card.
Make sure you check the md5sum of the file you downloaded so that its integrity is intact.
See if it works after all this. Do post your results.
All the best
Cheers!
abhisahara said:
Make sure you check the md5sum of the file you downloaded so that its integrity is intact.
All the best
Cheers!
Click to expand...
Click to collapse
Hi how do you do this please ?
Thank you
Stephen
sbsshadow said:
Hi how do you do this please ?
Click to expand...
Click to collapse
Total Commander can do it under Windows. Else see http://www.google.com/search?hl=en&...=Google+Search&aq=f&aqi=g10&aql=&oq=&gs_rfai=
Hi thanks for the help, when i go to extract the downgrade folder into my D drive i get the following message:
"You need permission from the computers administrator to make changes to this file"
and underneath that it has displays the GingerBreak file and its details. The downgrade folder appears in the D drive but without the GingerBreak, misc version or psneuter file.
Your help is very much appreciated!
Lanky09 said:
also my version of software is 2.36.405.8
Click to expand...
Click to collapse
http://driphter.com/index.php?topic=3867.0
Start at step 2.
bump - still need help on downgrading!
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Its simple if u have a backup. I have not heard of anyway of getting to build.prop thru recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
You need to restore from backup (nandroid) or start over if you don't have a backup..
Did you copy the original file to ur sd card then back over?
Chances are you did.. I did the same thing lol.. And when u do that it doesn't save original permissions of the file.
The reason the wallet post says to use root explorer is because it saves the file in the same folder permissions and all and you can just rename it back.
Sorry dude u are sol.. Restore from back up or flash a new rom and start over.
Sent from my SAMSUNG-SGH-I747 using xda premium
Get into recovery, do a factory reset.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
Any resolution. I have the same problem.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
I don't think that would work, as far as I know a factory reset only wipes data and cache. The build.prop is part of the system, so it will not change.
Sent from my SPH-D710 using xda premium
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Side note--> twrp recovery has a built in terminal and the ability to copy/paste files from internal and external SD cards. Not so sure about changing permissions easily....but through the built in terminal....might be able to load what you need (plus twrp flashable found in android dev forum) on external SD card with an adapter on a computer. Flash twrp and transfer files or use built in terminal to change perms. Good luck....
I know editing build props with es file explorer will cause That.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed it!
Thanks everyone for your help, i feel like an idiot for not replying to anyone i didnt have it set up to notify me of replies, i figured out it was the build prop that was messed up, im not sure how this worked but i figured i would try to root again and flash the root files using the simple root steps using odin and it actually fixed the file and booted up fine! i appreciate everyones help and hope this thread helps other people because i know many people screw this up the same way i did. (i will never do anything like this without doing a nandroid backup again). THANKS AGAIN!
thanks but..
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
prior to running that command, type su then hit enter
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
stratatak7 said:
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
Click to expand...
Click to collapse
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
lyrictenor1 said:
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
Click to expand...
Click to collapse
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
crammer04 said:
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________
If you got no back up give us your phone information one of us can send you one I have aTT D2att you
?
Its all in my sig get mobile odin bellow, get the tar for which ever recovery you got. I got all three. CWM, CWM Touch and TWRP for d2att (only) if different phone then use other ones.
Thats my build prop im D2att SG3 ok so just make sure. But you can grab mobile odin bellow and fix it.
_________________________________________
Just get mobile odin HERE
and flash your reocvery there CWM, TWRP, CWM TOUCH... all of them latest all in my sig bro
Here is all drop box to get any of the recoverys --------------------> Recoverys Drop Box
Get mobile odin Here along with the s3 kernal extension its all in here -----------------------> Mobile Odin
If you get hardware id missing error install these old samsung dricers this is a bonus, don't update it ----------------> Hardware ID samsung driver fix
__________________________________________________________
S3 build prop here --------------> here
Mobile odin is simple if download zip in my drop box just install it (or get it form market) download the driver you need (in my drop box) or go mobile odin thread and find it if your on a different phone. Rest is simple just load what your going to flash click the OPEN FILE option in mobile odin click tar and run it.
_________________________________________________________
Get android comander. You can mod build prop easy with it its nice GUI for installing programs or uninstalling or backups or moving files around. awesome try out here --------------------------------> ANDROID COMANDER
need anything else?
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
lyrictenor1 said:
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
Click to expand...
Click to collapse
Tiy need to remount system Read Write i don't think its a SU problem it could be but normaly you already got su i forget comand in adv its mount system -r i beleive. I dunno I run a script that mounts it for me let me check it out real fast
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
crammer04 said:
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
Click to expand...
Click to collapse
Just so you no a common problem when doing commands you forget to do it just trying help didn't know fixed
#!/system/bin/sh
busybox mount -o remount,rw /system
My build.prop got messed up while trying to install Google Wallet on my rooted sg3 and my phone became soft bricked. I had to reinstall the stock jellybean ROM with root that I had been running before this happened, through Odin. Solved my problem. Never got wallet to work though.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Would this work on S3 T-Mobile T-999?
stratatak7 said:
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
Click to expand...
Click to collapse
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Boosoth1st said:
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1746682
Try downloading the toolkit from there. It should contain the necessary T-Mobile files. If you are having an issue, please PM me. Make sure you flash the right one! Be careful and read the whole thread.
I created the pathways needed to open files in command prompt and set the pathways to C:\Android-sdk\tools and C:\Android-sdk\platform-tools. I have unzipped and installed everything and placed the files in the platform-tools folder, but i cannot access the files through prompt. it tells me C:\android-sdk\platform-tools is not recognized as and internal or external command. Please someone help... i havent worked with DOS since i was in high school 14+yrs ago.
So you changed your PATH environment variable to include 'C:\Android-sdk\tools' and platform-tools?
That just lets cmd run exe's from those folders regardless of where it is pointed, it will not let you access other files from those folders.
You still need to either change where cmd is pointed (using the 'cd' command) or you can move the files to where cmd is currently pointed (probably C:\Users\Username>')
-Nipqer
Still need some assistance, when starting to downgrade from gingerbread its telling me that i dont have a device detected. I have USB debugging on, so i dont know what i should do; any ideas
PvtJoker said:
Still need some assistance, when starting to downgrade from gingerbread its telling me that i dont have a device detected. I have USB debugging on, so i dont know what i should do; any ideas
Click to expand...
Click to collapse
Hello noob.
Did you install the USB drivers ( HTC Sync software )?
shared_ptr said:
Hello noob.
Did you install the USB drivers ( HTC Sync software )?
Click to expand...
Click to collapse
Im not sure if i installed the USB drivers. I installed everything that the wiki guide said to. I am gonna try again once i get home.
PvtJoker said:
Im not sure if i installed the USB drivers. I installed everything that the wiki guide said to. I am gonna try again once i get home.
Click to expand...
Click to collapse
I faced the same problem. My Windows PC didn't recognize the attached Android-device (Check Windows Device Manager).
After following the instructions as described in the following thread it suddenly worked and I could successfully root my device:
[Tutorial] Adb Driver Android 1.0 Install
Cheers
pemphix
Please help
Well i got the USB driver installed and ran adb Devices.... it picked up my phone but now when im running adb push fre3vo /data/local/tmp i get the message "cannot stat "fre3vo" no such file or directory". Am i suppose to be in C:\users\name\Android-sdk\platform-tools\ to run the adb push?
If so, need some help with command prompt. Im running windows 7,
need to either edit the path in environmental variables or make sure all the files needed and adb.exe are in the same folder and change directories to there, i have a guide to setup fastboot (and adb is the same setup for the most part) HERE
Ok, Well i got Command prompt to start working. i remembered how to path in dos but my first go round with commands didnt work so i have to try another line to exploit.. wish me luck:fingers-crossed:
I will keep that in mind.. right now im trying to get the exploit to work.. i have gone through 1 thru 3 and got nothing yet...
so you successfully downgraded to 2.2 and are now trying to temp root? maybe like the guide you are using so we know what steps 1 through 3 are and explain what isnt working if you have issues
xda wiki, cyanogen wiki and strawmetals pdf guide are simple easy and trust worthy. i hope one of these is the guide you are using
In process of downgrading
demkantor said:
so you successfully downgraded to 2.2 and are now trying to temp root? maybe like the guide you are using so we know what steps 1 through 3 are and explain what isnt working if you have issues
xda wiki, cyanogen wiki and strawmetals pdf guide are simple easy and trust worthy. i hope one of these is the guide you are using
Click to expand...
Click to collapse
I have gotten as far as "# dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10 1.00.000.010+0 records in 10+0 records out 10 bytes transferred in 0.001 secs (10000 bytes/sec)". Now the next step is to downgrade. the command line is:
> adb push su /data/local/tmp/
> adb push busybox /data/local/tmp/
> adb push fixsu.sh /data/local/tmp/
> adb install SuperUser.apk
> adb shell chmod 755 /data/local/tmp/fixsu.sh
> adb shell /data/local/tmp/fixsu.sh
but my command prompt is still # what do i do to
skip that, thats just for temp root which is pretty unnecessary. just downgrade and move on
I know i sound really stupid, but where is the Root of my SD card??? Please dont tell me its just the card itself...
yup, dont put files in a folder is what that means
Ok, now im in Hboot, but i dont understand what im suppose to do next. How do i work bootloader to downgrade. Once in bootloader i see; fastboot, recovery, factory reset, simlock and image crc
if the PC10IMG.zip is on the root of sd card and is named properly it will do it for you, just boot into hboot and let it do its thing.
if you want to do it the fastboot way (my preference but both work fine) then follow setherios guide to do it that way
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
oh and always check md5sums when flashing firmware, its a good habit to have
Now here is an important question. If i had to turn off my phone before the Hboot took, do i have to go thru the entire process again? or can i just do the reboot bootloader?
well i just tried to fastboot flash zip StockRom.zip and it said cannot load StockRom.zip any ideas how to get it to work??
are you using window? if so know that it may be hiding the file extentions, so pc10img.zip should be named pc10img
etc, this may be your issue other than that you will have to copy and paste your issues so I can see what you are doing and why its failing
Sent from my HTC Vision using xda premium
So, my problem is that I have recently unlocked the bootloader on my HTC One X using my Mac and the very helpful guide provided on this YouTube link
http://youtu.be/8Y3VbFJIwWU
No problems with the process in that video and I've gotten to the end with the phone bootloader definitely.
My problem is that I've then attempted to install a custom ROM from the SD card. Again, this seems to work fine, but upon reboot I'm immediately hit with a continual pop-up 'unfortunately, the process com.android.phone has stopped' with the only option to press ok. It loops continuously.
I suspect I may have to reinstall the ROM onto the SD card, but this is my problem. I cannot get my phone's USB access to work on my Mac as I am stuck with the above pop-up preventing me. I can't seem to access it via Recovery either.
Can I use fastboot to 'flash' over the *.img or *.zip of a new ROM to get it onto the SD card? Stuck with a phone I can't use otherwise. :crying:
Thanks.
Mount usb storage from the recovery.
Sent from my HTC One X using xda app-developers app
or while in recovery type
Code:
adb push rom.zip sdcard/
Thanks for that, athulele . :good:
I have tried that. On a Mac, for USB access requires that I use software called 'Android File Transfer' rather than the way Windows would do it. That software doesn't kick in via Recovery mounting. So, I'm going to need a different approach.
Since I have Windows installed via Bootcamp, I think I'll try to connect the phone up via Windows and see whether I can access the SD card via USB using that route.
Any other help is most welcome.
you do not need that file, just boot into recovery and type the command above... it's the easiest way
matt95 said:
you do not need that file, just boot into recovery and type the command above... it's the easiest way
Click to expand...
Click to collapse
Having booted into recovery, using Terminal on my Mac and typing
adb push sentinelrom_v4_30_endeavoru.zip sdcard/
gives the following message:
-bash: adb: command not found
Am I doing something wrong here?
well, have you got the sdk installed on your mac?
matt95 said:
well, have you got the sdk installed on your mac?
Click to expand...
Click to collapse
I've now downloaded the sdk for mac. It's a adt bundle folder with many files inside. I've installed 'Eclipse' but I'm still getting the same message as before from the Terminal. What else do I need to do here?
Im not into macs .... but don't you need to enter sudo commands before the adb/fastboot commands ?
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
matt95 said:
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
Click to expand...
Click to collapse
Hi matt95
I'm grateful for the help you are giving me here. I've found the adb file within the following downloaded directory path:
act-bundle-mac-x86_64-20130219 - sdk - platform-tools - adb
When I changed directory in Terminal to this path and ensured the specific rom.zip was also in that path, Terminal is still giving me this:
./adb push sentinelrom_v4_30_endeavoru.zip sdcard/
-bash: ./adb: No such file or directory
I must be doing something not right. Please help further.
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
matt95 said:
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
Click to expand...
Click to collapse
Folder contents as described.
Thanks.
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
matt95 said:
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
Click to expand...
Click to collapse
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
and
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools/sentinelrom_v4_30_endeavoru
Thanks.
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
matt95 said:
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
Click to expand...
Click to collapse
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
fingerbob said:
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
Click to expand...
Click to collapse
Flash a newer recovery.
Mr Hofs said:
Flash a newer recovery.
Click to expand...
Click to collapse
I managed to find a copy of ClockworkMod Recovery v5.8.4.0 and flashed this as advised. This has somehow enabled the USB facility on my phone to start working again and I can replace the ROM I've downloaded onto it.
I just tried reinstalling the ROM I had again, but once again got the original message stated in my first post. I'm about to now try a different ROM to see if that makes any difference.
:good: