With this you can update your Gigabyte G1305 from 1.6 (donut) to (2.1 Eclair).
This is a vannilla version based on GigaByte RU ROM
This ROM work's in Optimus Boston, Orange Boston, Apanda A60 , WellCom A88 and many other clones.
Pre-requisits:
android-sdk
Windows x86
firetrapMOD1.0 Final
ChangeLog:
- ROOT
- GMS adicionados
- Market adicionado
- mkyaffs2image adicionado
- busybox
- FlashPlayer Lite
- FlashPlugin
- TouchPal PT-PT
- Removed Chineses dictionaries
- settings.xml modded
- setup Wizard in first Boot
- increased HSDPA for 1.5 Mbps
- Date displayed as dd-mm-aaaa by default
- dalvick=24m
- removed GPS-Tacker
- removed fileBroswer
- added Astro File Manager
- added galery from froyo (solve pixelization problems)
- removed RSS Feeds
- added Mms.apk (from nexus/froyo) better image compression
- removed Stock.apk
- facebook app updated
- Maps updated
- added App2SD
- removed GigaByte bootAnims
- removed chinese bookmarks
- BOOT.img (kernel at 600MHZ)
- removed alarm clock
- removed original clock
- removed boot sounds
- added notification bar.
- recovery 2.1 (Nandroid by Kong)-> with and app2Sd fix
- add firetrapMOD BootAnimation (credits: djtkd)
CREDITS: Kong (DroidSans) & djtkd (androidpt.com)
Download:
www.megaupload.com/?d=75CXDZWT
Pre-Requisits:
android-sdk
Windows x86
RUT 1.2.2 -> www.megaupload.com/?d=X7R89BCX
THE RUT DOESN'T WORK ON WIN_x64
Installation:
1- turn on the phone in recovery mode (camera + VOL up + power)
2- startup RUT and follow instructions
3- Optional - After all finished if it display's some "Force Close" or some error with aplications, its advised to do an factory reset.
Update from 1.6:
1- turn on the phone in normal mode and do an factory reset
2- turn on the phone in recovery mode (camera + VOL up + power)
3- startup RUT and follow instructions
4- Optional - After all finished if it display's some "Force Close" or some error with applications, its advised to do an factory reset.
Troubleshoot: if RUT doesnt detect the phone:
1- lturn on the phone in normal mode and go to the Virtual CD-ROM is mounted in My computer.
2- open and browse the virtual CD-ROM and copy "\RUT\Drivers" to the Desktop.
3- turn on the phone in recovery mode (camera + VOL up + power)
4- Open the Windows Device Manager and check if isn't a device ("Qualcom") with an installation error.
5- Update the Drivers and broswe to the drivers you have copied above.
6- After this just continue the normal installtion.
Installation App2SD
PS: I will not be responsabiled for damaged in SD card.
Do a backup before to this procedure.
Installation
1- turn on the phone in recovery mode (Vol up + camera + power)
2- choose "partition SD card" and follow instructions
3- back to the menu and choose "enable app2SD"
4- Reboot the phone
You can follow my work on http://www.androidpt.com/index.php?option=com_kunena&Itemid=3&func=view&catid=71&id=61476
nice one Keep the good work
+1
Good job.
I to am a happy user of this ROM and can testify it works 5*.
Great work firetrap!!
Cheers,
PL
Great wrok firetrap!
Works @ 100%!
Keep up
App2sd don't work for me. I have a 2gb sd card.
The update from 1.6 will also work with branded Orange 1.6 ROM ?
How is this any different from CMLMod 1.4? Does your 600 MHz kernel also default to the performance CPU scaling governor (less battery life)?
This one has "ondemand" for the processor by default, it's faster and it simply works.
I actually doubt it has ondemand by default as the kernel is the same 600 MHz "performance" kernel that everyone has. The ROM might be set up so that it uses SetCPU to set the CPU governor to ondemand on boot-up.
Hi...
i'm having trouble trying to instal this mod.
First my Phone doesn't do the factory reset, when reboots it freezes on the andoid logo, i left it like that more than 5min. and nothing.
Hard Reset it's no problem.
second problem when i try recovery mode it look like it freezes to on the same place as it freezes doing factory reset, only diference is the small letter on the top saying entering flash mode or something like that, than neither Rut or windows can't detect the phone!
Any ideias??
oh and my phone is an Optimus Boston from Optimus v1.6 unlock from the network
yes also works on Orange Boston
yOoMuRy said:
App2sd don't work for me. I have a 2gb sd card.
Click to expand...
Click to collapse
initial post updated, try the new method
nuno_mdj said:
Hi...
i'm having trouble trying to instal this mod.
First my Phone doesn't do the factory reset, when reboots it freezes on the andoid logo, i left it like that more than 5min. and nothing.
Hard Reset it's no problem.
second problem when i try recovery mode it look like it freezes to on the same place as it freezes doing factory reset, only diference is the small letter on the top saying entering flash mode or something like that, than neither Rut or windows can't detect the phone!
Any ideias??
oh and my phone is an Optimus Boston from Optimus v1.6 unlock from the network
Click to expand...
Click to collapse
the recovery mode in 1.6 its that it's nothing saying its recovery mode, its simply the android logo, just connect to the windows and follow the next procedure
bkraptor said:
I actually doubt it has ondemand by default as the kernel is the same 600 MHz "performance" kernel that everyone has. The ROM might be set up so that it uses SetCPU to set the CPU governor to ondemand on boot-up.
Click to expand...
Click to collapse
the ROM dont have setCPU installed by default (check the changeLog), the kernel its the original from Kong
bkraptor said:
How is this any different from CMLMod 1.4? Does your 600 MHz kernel also default to the performance CPU scaling governor (less battery life)?
Click to expand...
Click to collapse
first this a diferent ROM than the CML , the instalation method it's only 4 step's with RUT its all in an nb0 file.
second its a vannila version 100 Mb of RAM free.
the CPU scaling governor will be implemented in the next version
Здравствуйте я и России
Подскажите а можно в вашем mod оставить русский язык.
Хотел поставить его себе
Спасибо
App2sd still don't work for me...
can you please implement the italian language for the OS?
firetrap said:
initial post updated, try the new method
the recovery mode in 1.6 its that it's nothing saying its recovery mode, its
simply the android logo, just connect to the windows and follow the next
procedure
Click to expand...
Click to collapse
the problem is that the windows won't detect the phone, in the device manager the phone doesn't show up, i've tried the troubleshooting that you post, the phone
only appears in the device manager when in normal mode.
When trying the recovery mode the phone seems to freeze there, only removing the battery and the same happens when trying to make a factory reset(left it for more than an hour and nothing).
Is there any other method to try to instal your mod?
Today i tried to install OMA 1.2 on my BQ Pascal 2 (Neo X7)
After booting the device there is no Touch-Screen Support and it looks like a screen with about 320 dpi.
I tried the Installation twice, with the same issue. Right now i am back on the stock software.
I followed the given steps:
- Downloaded and extracted both Archive Files
- Downloaded the NAND Fix and Pascal 2 Model Fix (copied both to the external SD)
- Shutdown Tablet
- Start the RK App on Windows as Administrator
- Connected the Tablet to USB and hold the vol down key, till it was detected
- Clicked on EraseIDB, then i ticked "Loader" and clicked on "Run"
After about 2 Minutes the Tablet reboots and starts with the Odys Loox Bootscreen, which is not displayed correctly, it looks like zoomed to the middle of the Screen.
I am not able to start CW on a regular way, but it starts after 2 min automatically. Now i installed the NAND Fix and the Pascal 2 Model Fix.
By choosing "Reboot" in CW the tablet crashed and i made a hardware reset.
The first book toot about 5 min, reboot will took at leas 3 min.
After booting i have no touchscreen support and a wrong dpi like described at the beginning of the post.
What i am doing wrong?
I purchased Howen Mobile Data Terminal for Taxi Dispatch.
Model - Hero-MDT-AT1
CPU - A10, ARM Cortex-A8 Core, Main Frequency 1.2GHz
Memory - DDR3, 512M
Flash - NAND Flash
OS - Android 4.0.4
Screen - 7" TFT-LCD
Resolution - 800 x 480
Touch Screen - Four-Line Resistance type touch screen
Android 4.0.4) last month. I need to change bootloader logo, splash screen and boot-animation, tried to change them. I got boot-animation changed, following procedures in web.
Then I tried to change splash screen logo (initlogo.rle in /dev/block/nandc <following procedures in website>)
Encounter a bootloop problem, so i tried to trace back to original state, but get stuck. I cant escape from recovery mode, I didn't install CWM.
The device has buttons (home, volume-up, volume-down, Ok) and no battery.
When I tried to get in recovery mode(volume-up + Ok), it shows " Formatting /Cache... ; Formatting /Data...; Rebooting" and restart. At that period, command 'adb' detect the device for 3 seconds, I can adb push 5Mb item
onto /sdcard/
I tried to make bootable sdcard with CWM, device not detect.
When I try (volume-down + Ok*5 times), pc detects the device
Hardware_id
--------------
USB\VID_1F3A&PID_EFE8&REV_02;3
USB\VID_1F3A&PID_EFE8
but I can't find the suitable driver (tried livesuite 1.0.9, not ok).
Please help me, how should I do, I would try everything
Hi!
I can't enter BIOS and I can't boot windows. I've got keyboard but any key don't enter to the bios. It`s stop immediately after kiano logo. Only Ctrl+Al+Delete working. When i press vol +, - and power ON, it show " Entering DnX mode. Waiting for fastboot command..." for 2 sec after that I see windows boot manager error . What can I do with it?
Kiano Intelect 8 3G
CPU: Intel Atom Z3735F Bay Trail
RAM: 1 GB DDR3
NAND: 16 GB + micro SD
OS: Windows 8.1 with bing
Hi,
This site is a development site for mobile phones. Pc support isn't really done here. But if you wish, you can ask for help here,
http://forum.xda-developers.com/general/help
Good luck!
Hi. I bought the Mercury Pro 7" prosumer tablet back in 2014. I installed a google account on it, forgot the password, beat the 10 opportunities, account (and RCA tablet) locked.
Soon after that, I tried to "hard reset" and "factory reset" this tablet, with all the things I found at the moment through forums, but everytime it came to restart, it will lock itself because I forgot my password and it will not allow me to enter nor my gmail account or any other password at all (no text dialogue).
A friend took it to some "expert android shop", but they never got to fix the small tablet (needless to say).
I remember the tablet came with Marshmallow (Android 6?).
It's 2021, and I thought to find the original ROM Image for this device. But tough luck, I haven't found one (from all the forums I've read, you either need to short-circuit or download a similar clone image for the processor and cross fingers so the wifi modem picks up the .img drivers).
In all and all, if anyone of you would be so kind to help me out with this 7+ year plead: I'd like to fix this tablet in 2021, please. Help me out.
The tablet can be switched on, but Loops itself in the "Mercury Pro" logo, after the dogs logo.
The tablet runs out of battery. I charge it up so that it can be turned "on" just 1 time and 1 time only, to access the Bootload menu by power + volume up.
The times I do this procedure, I wipe clean the dalvik cache, user cache, system cache, set the device to factory reset, and reboot after that.
Again, the 2 dog logo appears, but the tablet stops at the Mercury Pro logo in a loop.
Reset pinhole helps to enter the tablet's "hard reset" (power+volume up) boot menu. It reads:
Android Recovery v1.2
RCT6673W-V1MKC-Android6.0-v08-v1.15.0
- Reboot system now
- Reboot to bootloader
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Wipe Cache partition
- Backup user data
- Restore user data
- Root integrity check
- Mount / System
- view recovery logs
- Power off
(Supported API: 3)
In the remote case the so-called "android repair" shop installed a bad rom on this hardware, what are my chances to Factory reset - re-flash the original stock rom for this device?
The Screen works normally, this tablet doesn't have a hardware fail of any kind, it just loops-boot after the 2 dogs logo into "Mercury pro".
I've checked the tablet internally, there are no burnt connections or anything out of the ordinary. Hardware is intact.
Please help me.
Thanks.
Obviously I went for the VIEW RECOVERY LOGS:
--bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
--bionic_open_tzdata: couldn't find any tzdata when looking for GTM!
--bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery (pid 133) on Fri Jan 1 00:00:12: 2010
ro.build.product=RCT6673W23M
ro.build.version.sdk=23
ro.build.version.bases=
ro.build.version.release=6.0
ro.build.version.codename=REL
ro.build.version.incremental
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.ota.host=tablet15.gyrodock.com:2300
ro.product.name=RCT6673W23M
ro.product.board=
ro.product.brand=RCA
ro.product.model=RTC6673W23M
ro.product.device=RTC6673W23M
ro.product.locale=en-US
ro.product.version=1.15.0
ro.mediatek.version.dsk=4
ro.mediatek.version.branch=alps-mp-m0.mp8
ro.mediaversion.release=alps-mp-m0.mp8-v1.51_spyked8127.e_P16
ro.mediatek.chip_ver=S01
ro.mediatek.platform=MT8127
ro.openles.version=131072
ro.revision=0
ro.serialno=
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.suppress_d2d=true
ro.mtk_is_tablet=0
ro.mtk_bt_support=1
ro.mtk_wfd_support=1
ro.have_aee_feature_=1
///
Every time I left a space, there were a lot more lines, but I only copied these.
Is this device also known as mercury tab 7?
@viktorrios
In the linguistic world of Android users, they often use the term "hard reset" for "factory reset", which means that the device is reset to the state it was in when it was launched. In official serious usage, there is no "hard reset" for Android devices.
Your issue is that phone is stucking at boot logo. That can't get fixed doing a "Factory Reset" or even by means of ADB and/or Fastboot. IMO you've to re-flash phone's Stock ROM what can be achieved if phone is accessible by means of ADB - what requires USB debugging got enabled on phone.
Tab E said:
Is this device also known as mercury tab 7?
Click to expand...
Click to collapse
No.
Mercury Pro. 7" inch screen RCA TABLET.
jwoegerbauer said:
@viktorrios
In the linguistic world of Android users, they often use the term "hard reset" for "factory reset", which means that the device is reset to the state it was in when it was launched. In official serious usage, there is no "hard reset" for Android devices.
Your issue is that phone is stucking at boot logo. That can't get fixed doing a "Factory Reset" or even by means of ADB and/or Fastboot. IMO you've to re-flash phone's Stock ROM what can be achieved if phone is accessible by means of ADB - what requires USB debugging got enabled on phone.
Click to expand...
Click to collapse
ok. this is one step forward.
Thank you for your reply.
I found this site, but it doesn't have the stock rom:
ROMs | RCA
Be careful download your stock rom from unverified/ unofficial websites. May contain malware
What makes me wonder is; I can access the fastboot menu, I can CLEARLY read the entire log, but the OS is not reached during boot (logo loop). What makes it possible that I have a corrupted library?
Also: If I could find the stock rom and flash it from an SD card: How possible is it from the fastboot menu?
For anyone else who is reading this thread, here's another site with ROMs:
RCA Download Latest Firmware | Flash File | CFirmware - Mobile Phone Flashing, Unlocking and, Latest Firmwares Available.
www.cfirmware.com
Fastboot hasn't a menu ( GUI ) it's a CLI.
Look inside here:
How to Flash Stock Firmware via Fastboot Commands
In this comprehensive post, we will show you how to flash stock firmware of any Android device via Fastboot Commands.Sample Fastboot Command sheet included!
www.droidwin.com
I found an explanation of one of the errors:
I: no boot messages
I: Open /cache/recovery/comand fail error= no such file or directory locale is [(null)]
stage is []
fb0 reports (possibly inaccurate)
The Unable to open DRM node: No such file or directory issue seems to indicate that there is no DRM driver running on your device (or that it failed to initialize). DRM support is a prerequisite for using this tool, as you can see. Most platforms supported by cedrus should also have DRM support, so you probably need to enable it in your kernel config and/or in the board's device-tree file.
Closing since this is not an issue of the tool but a setup issue instead.
I think I need to upload the entire message Log, maybe someone could help. So far I already know the "driver" is not booting and there is no mount of the OS. Everything else is there, and ready to receive an image. It seems the tablet was so wiped off that it doesn't even have an OS.
jwoegerbauer said:
Fastboot hasn't a menu ( GUI ) it's a CLI.
Look inside here:
How to Flash Stock Firmware via Fastboot Commands
In this comprehensive post, we will show you how to flash stock firmware of any Android device via Fastboot Commands.Sample Fastboot Command sheet included!
www.droidwin.com
Click to expand...
Click to collapse
There is another log report that says: error/system/framework/arm/boot.oat check fail
E:Error:/system/framework/oat/arm/wifi-service.odex has been modified md5on Thu Jan 19 01:38:12 2017
System check: FAIL!!
I: Open /cache/recovery/command fail errno = No such file or directory
local is [(null)]
cannot find/open a drm device: No such file or directory
ro.board.platform=mt8127
ro.build.id=MRA58K
....
....
ro.build.type=user
ro.build.user=builder
ro.build.product=RCT6673W23M
ro.build.flavor=RCT6673W23M-user
This site has an RTC 668xxxx image. Will it work?
Download RCA Stock Firmware For All Models | Root My Device
Download RCA Stock Firmware and flash it in your Android device using a Flash tool to get back the native Android experience again.
rootmydevice.com
For anyone else reading, I remember I got this RCA tablet from Amazon years ago. They were out of stock. Recently they are selling the item again: https://www.amazon.com/RCA-Keyboard-Marshmallow-Charcoal-RCT6873W42KC/dp/B01M7TSY16
And guess what?
All along the ROM version my tablet had (from the so -called-experts in Android store in my story) put the wrong ROM version.
So Amazon indicated it is: RCT6873W42KC the rom.
Googling, I found: https://naijarom.com/rca-rct6873w42m
And the site looks legit. The scatter file is there and everything matches 1 to 1 to the STOCK image.
This site also has links: https://androidmtk.com/download-rca-stock-rom-for-all-models
My question now:
Whenever I plug the USB cable in my computer, (even after installing the ADB drivers), it says that windows 10 cannot recognize the USB device.
I am ready to flash using the SP Flash tool and the ROM file, but I can't -for the love of me- make contact from the PC to the tablet.
Could anyone help me with some work around suggestions, please?
Also: Why can't I just drag-drop all scatter ROM image to the microSD and Boot from recovery using "Apply update from SDCard"?
Ok so far everything was going full sail until I hit this brick road: Apparently I need a better USB cable. I've tried 3 different USB cables, but the device becomes unstable on win10 (switches on and off, and the "connected USB" sound dingles every 10 seconds.
Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
viktorrios said:
Ok so far everything was going full sail until I hit this brick road: Apparently I need a better USB cable. I've tried 3 different USB cables, but the device becomes unstable on win10 (switches on and off, and the "connected USB" sound dingles every 10 seconds.
Please help.
View attachment 5265921
Click to expand...
Click to collapse
Is the stock rom for your device?
And the reason you can't just apply update from SD card is that the scatter rom doesn't have Meta inf and updater script. So the recovery can't install that
Yes, I checked this is the CORRECT Stock Rom for the RCA 7" Tablet Mercury Pro
I've also installed the "legacy hardware drivers":
viktorrios said:
Yes, I checked this is the CORRECT Stock Rom for the RCA 7" Tablet Mercury Pro
I've also installed the "legacy hardware drivers":
View attachment 5265979
Click to expand...
Click to collapse
After you installed the drivers did you restart you Computer?
No, I didn't restart the computer. Let me do that.
I also tried the "newest" micro USB to USB cable I have...
I hope this works.
This is a driver problem. https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/ check this guide out. Don't use the drivers from the above site, just use the driver you instslled