Database Info

"Need updated Rom Utility"

Does anyone else get this when they try and update their phone?
For some reason everytime i try to flash a new rom i keep getting this error.

icewhitenewyear said:
Does anyone else get this when they try and update their phone?
For some reason everytime i try to flash a new rom i keep getting this error.
Click to expand...
Click to collapse
I'm not sure on this error. Is it from the KaiserCustomRUU Application?
I;ve attached the one I use, just incase you need a different version.
If you still having problems, a little more info on what your doing at the time (and what you've done so far, Hard SPL, etc).
Thanks
Dave

I had this for a while and i thought it was a rom issue but all my older roms did it also.
you need to repair or reinstall active sync to fix it
icewhitenewyear said:
Does anyone else get this when they try and update their phone?
For some reason everytime i try to flash a new rom i keep getting this error.
Click to expand...
Click to collapse

I am having the same problem...I have the HardSPL flashed but when I try (and yes I tried the one that is attached to this post) and flash the ROM with the KaiserCustomerRUU exe. file it comes back "The update utility can not open the requested file. Please check your Update Utility".
How do I repair the active sync as it runs fine right now?

Do you have "Enable USB connections" checked?

Yep it's enabled and connected

volleykinginnc said:
I am having the same problem...I have the HardSPL flashed but when I try (and yes I tried the one that is attached to this post) and flash the ROM with the KaiserCustomerRUU exe. file it comes back "The update utility can not open the requested file. Please check your Update Utility".
How do I repair the active sync as it runs fine right now?
Click to expand...
Click to collapse
did you try just putting your phone into bootloader (hold down the camera button while soft resetting with the stylus) and flashing while in bootloader?

In Windows Task Manager, check and see if rapimgr.exe and wcescomm.exe is running. If either one of those are not running, then you will need to reboot the PC. Also, you can try another USB slot on the PC. Everytime this has happened to me, a reboot of the PC always fixed the issue.

P1Tater said:
In Windows Task Manager, check and see if rapimgr.exe and wcescomm.exe is running. If either one of those are not running, then you will need to reboot the PC. Also, you can try another USB slot on the PC. Everytime this has happened to me, a reboot of the PC always fixed the issue.
Click to expand...
Click to collapse
What is this "reboot" of which you speak, is that like power cycling...no wait that's just riding your bike really fast...

P1Tater said:
In Windows Task Manager, check and see if rapimgr.exe and wcescomm.exe is running. If either one of those are not running, then you will need to reboot the PC. Also, you can try another USB slot on the PC. Everytime this has happened to me, a reboot of the PC always fixed the issue.
Click to expand...
Click to collapse
Or in P1Tater's case your PC and phone might need a little oil.
{
"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"
}

AllTheWay said:
Or in P1Tater's case your PC and phone might need a little oil.
Click to expand...
Click to collapse
OOOOOHHHHH, It's on now.

Tried many "fixes" and still in boot loop.

I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"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"
}
Any ideas?

Repartition 2048 and 0.

Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.

Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?

No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.

Congrats, man. I think you're the first to truly brick his gtab.

tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.

Thanks KJ, I will try those when I get home this evening.

[Q] Bricked TF

Disclaimer: Searching for this brings up far too many results to be useful.
Just attempted a Root of 3.2 using http://forum.xda-developers.com/showthread.php?t=1185104
I'd post this there, but don't have access rights.
Anyways, process went well, rebooted, but once the initial splash screen has cleared, this happens:
{
"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"
}
I've tried using the same tool to restore to stock, but nothing doing at the moment. Help would be appreciated.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.

How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra

i had the same thing happening to mine when i first rooted to 1.4 prime. however now ive upgraded the rom to 1.6 and so far no artifacts

I had the same problem. I found it was able to fix it by downloading the latest version of the batch script root method zip file and using it to flash my tablet. You need to MAKE SURE you are using the latest version v5 beta5 because the older version had a problem flashing HC3.2 and gave me that error.
here's the link to the forum entry
http://forum.xda-developers.com/showthread.php?t=1185104
here's the link to v5 beta5
http://www.mediafire.com/?59rzqn61jl445lh

Speedstra said:
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
Click to expand...
Click to collapse
I had actually attempted to flash the 3.1 image instead of the 3.2 image. Thus the reason for edit on the original post.
The latest version of the tool should restore it.

EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
Click to expand...
Click to collapse
Please stop using the incorrect term for 'brick.' IT IS NOT A BRICK when your device turns on. Just stop, please.

Just had this same issue, got the same screen - blood pressure went through the roof, had to go water the plants to calm down
I was following this procedure: http://forum.xda-developers.com/showthread.php?p=14760983#post14760983
My mistake was not replacing the boot.img in the root folder with the newer 8659 .img file (linked at the top of the post, but not called out in the otherwise very detailed instructions).
HOWEVER: I did have an issue in that after flashing the wrong .img and getting the "oh sh!t" screen, I could not get adb to list a connected device, which kind of threw me. I could get it into APX mode by holding down the vol-up and power keys (and paying close attention to the "usb connected" notification sound - hold them down for about 10 seconds, hear the "disconnected" sound, then almost immediately hear the "connected" sound and let them go. The screen should stay dark instead of going to the boot logo) and I could see the driver being used, but "adb devices" returned nothing.
So I just ran root.bat again, as I had nothing to lose - and BOOM! Success!
Followed the rest of the procedure with no issues. Hope this helps someone!
Cheers
PatMan

[Q] Bricked SGS4G

Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"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"
}

What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide

Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.

Major kudos to diego930 for such a nicely detailed description of his problem!

Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.

Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!

When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.

ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.

Going back to stock ROM

Hi everyone. Could someone please direct me to a guide for going back to the stock firmware? I have been looking everywhere with no luck at all.
Thanks!

Jonny_Bandana said:
Hi everyone. Could someone please direct me to a guide for going back to the stock firmware? I have been looking everywhere with no luck at all.
Thanks!
Click to expand...
Click to collapse
https://c.mi.com/oc/miuidownload/detail?guide=2
This page doesn't like playing with mobile browsers, so if you've got a blank page change the browser to desktop mode.
All required downloads are in the guide.
The Mi Flash Tool will lock the bootloader, by default, after flashing. If you don't want to do this, then change the option at the bottom of the tool before flashing (step 5)
If you wish to lock the bootloader, you must make sure the ROM region matches the phone, i.e. global ROM on a global phone.

Robbo.5000 said:
https://c.mi.com/oc/miuidownload/detail?guide=2
This page doesn't like playing with mobile browsers, so if you've got a blank page change the browser to desktop mode.
All required downloads are in the guide.
The Mi Flash Tool will lock the bootloader, by default, after flashing. If you don't want to do this, then change the option at the bottom of the tool before flashing (step 5)
If you wish to lock the bootloader, you must make sure the ROM region matches the phone, i.e. global ROM on a global phone.
Click to expand...
Click to collapse
Thanks!
However, I'm having a lot of trouble with the tool. It will not recognize my phone. I connect it, and the computer detects the phone. Then I click on "refresh" on the tool, and automatically the USB device is disconnected from the computer and the tool will not recognize it.
I have installed the Qualcomm and ADB drivers, rebooted and nothing changes.
{
"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"
}
Then, after hitting refresh (device still connected on Fastboot):
Any ideas?
Thanks again

Sounds like a dodgy USB connection.
Try using the best USB cable you can find. If that doesn't work, try using a different computer. Fastboot and adb are very sensitive to the quality of the USB connection.
My old laptop will happily connect normally to my phone and I can transfer files with no issues, but from about a year ago I can no longer use adb and fastboot, with similar problems you are seeing. Using the same phone and cable I have no issues with my wife's laptop.

Robbo.5000 said:
Sounds like a dodgy USB connection.
Try using the best USB cable you can find. If that doesn't work, try using a different computer. Fastboot and adb are very sensitive to the quality of the USB connection.
My old laptop will happily connect normally to my phone and I can transfer files with no issues, but from about a year ago I can no longer use adb and fastboot, with similar problems you are seeing. Using the same phone and cable I have no issues with my wife's laptop.
Click to expand...
Click to collapse
That actually worked. Phone is flashed. Thanks a lot friend.