My phone recently lost its ROM, and is now stuck on the 'HTC quietly beautiful screen', i did manage to get it into clock work mode recovery and have a backup of my old rom on a usb, however, when i plug in the USB before starting the phone it doesn't show up, meaning i cannot restore. Please help! Any help or feedback is much appreciated! :good:
When you're in recovery, you have to use the command:
Code:
adb devices
for see your phone.
After use adb command like push or sideload for put a rom into the phone
Guich said:
When you're in recovery, you have to use the command:
Code:
adb devices
for see your phone.
After use adb command like push or sideload for put a rom into the phone
Click to expand...
Click to collapse
Thanks, but how would i do that on a mac?
That's why I have parallels!
I had this problem the other day and I fixed it by going to data/media in recovery and installing an old Rom that was downloaded. I could then restore afterwards.
Sent from the one and only HTC One
Shadow Samurai said:
That's why I have parallels!
I had this problem the other day and I fixed it by going to data/media in recovery and installing an old Rom that was downloaded. I could then restore afterwards.
Sent from the one and only HTC One
Click to expand...
Click to collapse
Yes, but i cannot copy anything to my device, and when i attempt to use adb, it says "error: device not found"
Check the thread in my signature
Sent from my HTC One using xda app-developers app
MacHackz said:
Check the thread in my signature
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i have tried following your help, but when i type ./adb devices it says
"adb server is out of date. killing...
* daemon started successfully *
List of devices attached
"
it doesn't show the serial code
g4slyness said:
i have tried following your help, but when i type ./adb devices it says
"adb server is out of date. killing...
* daemon started successfully *
List of devices attached
"
it doesn't show the serial code
Click to expand...
Click to collapse
Is it turned on booted into Android, or in recovery?
MacHackz said:
Is it turned on booted into Android, or in recovery?
Click to expand...
Click to collapse
Yes
You have the latest adb binaries installed??
Sent from One with Tapa4 Beta
Guich said:
You have the latest adb binaries installed??
Sent from One with Tapa4 Beta
Click to expand...
Click to collapse
I am not sure what a binary is (HTC One is my first android phone so I'm new) but if it is the recovery mode, i only installed it about a week ago
Do you have the folder containing the adb and fastboot files on your Desktop? And do you have HTC Sync installed? It will load the proper drivers, even though I heard it may not be necessary anyway.
This method worked for me on my Mac. It is very simple using Terminal.
You don't actually have to download the whole SDK, just download the file attached in the threat, which is this http://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941
Place it on your Desktop, and follow the instructions. After ADB successfully lists your device, move the ROM file to your android folder and use the following command: adb sideload rom.zip of course replacing 'rom.zip' with whatever your rom's name is. You can also use adb push if you want to move your Nandroid backup to your device, but I am not sure where it will be located on the device itself afterwards.
Oh and you should be in TWRP > Advanced > ADB Sideload mode if you want to sideload the ROM. I am not sure how it works on CWM but it should be the same way.
TarekElsakka said:
Do you have the folder containing the adb and fastboot files on your Desktop? And do you have HTC Sync installed? It will load the proper drivers, even though I heard it may not be necessary anyway.
This method worked for me on my Mac. It is very simple using Terminal.
You don't actually have to download the whole SDK, just download the file attached in the threat, which is this http://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941
Place it on your Desktop, and follow the instructions. After ADB successfully lists your device, move the ROM file to your android folder and use the following command: adb sideload rom.zip of course replacing 'rom.zip' with whatever your rom's name is. You can also use adb push if you want to move your Nandroid backup to your device, but I am not sure where it will be located on the device itself afterwards.
Oh and you should be in TWRP > Advanced > ADB Sideload mode if you want to sideload the ROM. I am not sure how it works on CWM but it should be the same way.
Click to expand...
Click to collapse
Thanks, i have tried this method already and am in Clockworkmod recovery, i don't have TWRP
Related
So I managed to screw up by wiping both my data and my system, so now I have no os installed and no way to flash an OS from .zip files. Is there anyway for me to add a file to my storage and then flash it via recovery?
jason27131 said:
So I managed to screw up by wiping both my data and my system, so now I have no os installed and no way to flash an OS from .zip files. Is there anyway for me to add a file to my storage and then flash it via recovery?
Click to expand...
Click to collapse
Download a rom and put it in your adb folder
hold in shift and right click on your adb folder - 'open folder in terminal' or similar (not at my computer atm) should be there
Type
adb push name_of_rom.zip /sdcard/
Or
adb sideload name_of_rom.zip
both must be done in recovery. If you do the sideload method, choose the sideload option in recovery - once it transfers it will begin to install automatically. 'adb push' will put the file onto your sdcard then install it yourself in recovery.
Sent from my HTC One using xda premium
Awesome i'll try that. Thanks!
redbull123 said:
Download a rom and put it in your adb folder
hold in shift and right click on your adb folder - 'open folder in terminal' or similar (not at my computer atm) should be there
Type
adb push name_of_rom.zip /sdcard/
Or
adb sideload name_of_rom.zip
both must be done in recovery. If you do the sideload method, choose the sideload option in recovery - once it transfers it will begin to install automatically. 'adb push' will put the file onto your sdcard then install it yourself in recovery.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It says device not found.
What about if you go into fastboot in the bootloader screen and type
fastboot devices
Maybe you need to reinstall your adb files...
Sent from my HTC One using xda premium
then you need to install HTC drivers for your phone. If configured correctly you can do adb devices and it will show up.
If you have drivers installed correctly under device manager the phone shows up as My HTC. Make sure you aren't using a USB 3 port if your computer has one.
Reboot your computer. That worked for me. I did the same thing
Also download HTC all in one tool kit. Its a lifesaver.
Sent from my HTC One using xda app-developers app
fastboot does work. Can i use the adb command in bootloader screen?
jason27131 said:
So I managed to screw up by wiping both my data and my system, so now I have no os installed and no way to flash an OS from .zip files. Is there anyway for me to add a file to my storage and then flash it via recovery?
Click to expand...
Click to collapse
I had same problem nothing was working .i used twrp and from there mount storage as otg as that was only working and put a rom in external pendrive and flash your rom
Sent from my HTC One aka M7
jason27131 said:
fastboot does work. Can i use the adb command in bootloader screen?
Click to expand...
Click to collapse
no only fastboot commands.
So then where do i do the adb commands? In the recovery? I don't get why adb devices isn't giving me anything when fastboot is.
jason27131 said:
fastboot does work. Can i use the adb command in bootloader screen?
Click to expand...
Click to collapse
No, adb must be done in recovery.
Go into recovery and try
adb devices
If nothing shows up you need to re-install/update your adb files and HTC drivers.
If your devices shows up this time then do what I said earlier...
Sent from my HTC One using xda premium
You can either reboot the computer or stop and restart the adb service from the windows management console. The driver for fastboot and adb are the same so I suspect it's something with adb server acting up
I'm guessing you update adb files via sdk manager?
redbull123 said:
Download a rom and put it in your adb folder
hold in shift and right click on your adb folder - 'open folder in terminal' or similar (not at my computer atm) should be there
Type
adb push name_of_rom.zip /sdcard/
Or
adb sideload name_of_rom.zip
both must be done in recovery. If you do the sideload method, choose the sideload option in recovery - once it transfers it will begin to install automatically. 'adb push' will put the file onto your sdcard then install it yourself in recovery.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
gunnyman said:
You can either reboot the computer or stop and restart the adb service from the windows management console. The driver for fastboot and adb are the same so I suspect it's something with adb server acting up
Click to expand...
Click to collapse
I stopped and restarted the adb services and it stil lcan't find the phone. is there any thing specific I have to do in recovery? This is confusing me so much.
jason27131 said:
I stopped and restarted the adb services and it stil lcan't find the phone. is there any thing specific I have to do in recovery? This is confusing me so much.
Click to expand...
Click to collapse
How hard is to flash via external flash drive using micro usb otg in recovery menu
Sent from my HTC One aka M7
Remove and reinstall the driver
zinder33 said:
How hard is to flash via external flash drive using micro usb otg in recovery menu
Sent from my HTC One aka M7
Click to expand...
Click to collapse
Reasonably hard if he doesn't have a USB OTG cable atm...
Sent from my HTC One using xda premium
zinder33 said:
How hard is to flash via external flash drive using micro usb otg in recovery menu
Sent from my HTC One aka M7
Click to expand...
Click to collapse
Very, since clicking on the micro-otg doesn't do anything. I managed to get sideload working I believe. It's at 40%, hopefully it is sideloading the file.
jason27131 said:
Very, since clicking on the micro-otg doesn't do anything. I managed to get sideload working I believe. It's at 40%, hopefully it is sideloading the file.
Click to expand...
Click to collapse
Should be good to go
If it freezes in Aroma just force reboot and try again.
Sent from my HTC One using xda premium
I stupidly showed my teenage son how to use ROM Manager and CWM on my phone.
He has now completely deleted (and I feel formatted) ALL Data etc on the phone.
So, as I cannot use any software on my MAC to transfer ROMs to the phone CAN Someone please advise how to get a ROM on the phone?
I can still access CWM Recovery. I have Android SDK installed, including Eclipse.
Please remember I am using a MAC, when you helpfully pass on ideas or solutions
Go to adb and fastboot folder, boot into recovery and use the command from terminal:
Code:
adb push name-of-rom.zip /sdcard/
.
Remember to put the rom into adb/fastboot folder
Hey, thank you.
I will try that soon
Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc
aussie_boi said:
Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc
Click to expand...
Click to collapse
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium
redbull123 said:
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
This is what I typed - /Users/Greg/Downloads/Android/sdk/platform-tools/adb push AR10.1.zip /sdcard/ for the push, and
I typed this for the adb devices command - /Users/Greg/Downloads/Android/sdk/platform-tools/adb devices
aussie_boi said:
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
Click to expand...
Click to collapse
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium
redbull123 said:
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007 fastboot
aussie_boi said:
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007fastboot
Click to expand...
Click to collapse
Now try recovery again
adb devices
Sent from my HTC One using xda premium
redbull123 said:
Now try recovery again
adb devices
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$
aussie_boi said:
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$
Click to expand...
Click to collapse
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium
redbull123 said:
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have already done that. I copied the "adb and fastboot" files from the sdk and added the "ROM.zip" file there also.
In recovery, I still get no devices listed with "adb devices"
I have opened a terminal window from within the case folder ... etc etc
I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium
rizzxx7 said:
I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.
MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
I will try this once again when I get home, I've got a nandroid file from a stock tmobile Rom that I will try to install
Sent from my HTC VLE_U using xda premium
MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
When I do this, I still get the error: device not found
This is what I did when in the directory using Terminal within that directory. I was in Fastboot USB for the ADB push
home:Android Greg$ ./adb push ar10.1.zip /data/media/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
And when I do Fastboot Devices and ADB Devices, I get this in Fastboot USB mode
home:Android Greg$ ./fastboot devices
HT34LW912007 fastboot
home:Android Greg$ ./adb devices
List of devices attached
home:Android Greg$
This has really got me puzzled
shinobix37 said:
I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.
Click to expand...
Click to collapse
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange
aussie_boi said:
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange
Click to expand...
Click to collapse
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium
Android The Greek said:
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks. I had been in CWM earlier, and the same as just now, when I try ./adb devices ... while in CWM, terminal returns no listing of devices.
It seems to me that ADB does work, as it identifies the "daemon is out of date" and restarts it successfully.
It is just that ADB does not recognise the HTC One, whilst "Fastboot devices" does, while not in fast boot usb.
I am still lost. CWM works. ADB cannot connect ...
Help
Hi, guys I followed all instructions after bricking my phone, it only goes into twrp recovery, i don't have an os and i cant put the rom in device via usb since it wont recognize it, But I tried to push the rom via adb and using terminal like this:
/Users/BARKIN/desktop/Android/adb push slimbean.zip /sdcard/
etc, but it wont work, i try listing devices, it says no device found..
I USE a mac btw, help me out?
Since you have twrp find adb sideload and do it that way. If you need more info Google adb side load twrp.
Sent from my Nexus 7 using XDA Premium HD app
well, I have no file on the phone, i wiped system and everything only recovery is in place.. i cant push rom through adb on mac.
there is hasoons tool which you can make use off. there are actually two out there.. in orignal android section. find the one with mac support.
There is no mac toolkit
barkmarkin said:
well, I have no file on the phone, i wiped system and everything only recovery is in place.. i cant push rom through adb on mac.
Click to expand...
Click to collapse
With adb sideload it does not matter it will work as long as you can use adb commands
Sent from my HTC One using xda premium
So, step by step:
-Boot phone into TWRP
-Select Advanced, then ADB Sideload, swipe to start it
-Connect USB to Mac
-Launch command prompt on Mac
-"adb devices" should detect the phone.
-"adb sideload slimbean.zip" should flash the zip
Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!
See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:
ioakimakos93 said:
Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!
Click to expand...
Click to collapse
Danny201281 said:
See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:
Click to expand...
Click to collapse
Ok I read your post again and think I misunderstood your problem. Your drivers are working as adb see's the device so what exactly is the problem? The sideload does not complete?
You should uninstall HTC Sync for starters it will do you no favours while using adb/fastboot commands it has the potential to cause hangs. if
Code:
adb sideload name-of-zip
is not working for you.
Try adb push instead with the one on the TWRP home screen (Not in Sideload mode)
Code:
adb push name-of-zip.zip /sdcard
The command window will appear unresponsive until the push completes. (several minutes) When it's done select Install from the TWRP menu and select the rom zip file.
If you still get problems copy and paste the error from your command window here :good:
Or flash TWRP 2.8.5.0 it has the ability to use MTP in recovery so you can see your phones Internal Storage while in recovery and just drag and drop the rom to your phone :good:
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
neo_lithic3K said:
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
Click to expand...
Click to collapse
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
bignu77 said:
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
Click to expand...
Click to collapse
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
dragynbane222 said:
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
Click to expand...
Click to collapse
My bad, I worded that wrong it only happens once in the custom recovery and try to ADB sideload the rom, i get that error.
Fastboot boot.img via bootloader works fine.
My trouble starts one in custom recovery and it shows "emulator-5554". Please see attachment.
Thanks
bignu77 said:
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
Click to expand...
Click to collapse
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for clearing that up.
The only other thing connected it the cordless mouse reciever.
I also did update sdk platform. as shown in the attached. Yes i am trying to apply update from adb and then sideload command I also tried typing the specific file name instead of the whole path.
It only happens in adb mode. Flashing via fastboot works fine with no emulator error.
Ive been flashing for months using the standard adb method with no hiccups. Now im getting this error
SOLVED
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
bignu77 said:
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
Click to expand...
Click to collapse
Figured it something related to that, I'm happy you fixed it though, enjoy the ROM.:good: