yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
Sorry, I did not find the RUU.log file anywhere. I used MAupgrade_noID to upgrade. May be it is because of the RUU.conf? Please look at my RUU.conf and check if there is any thing wrong

[PLATFORM]=857873

[RADIO_TYPE]=2

[SECURITY_FLAG]=1

[DECODER_KEY]=1

[RADIO_FLAG]=2

[GETADDR_TYPE]=1

[JUMPCODE_TYPE]=1

[FORMAT_TYPE]=2

[SCREEN_TYPE]=2

Regards!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
The RUU.conf is alright.

RUU.log must be there on your root drive. On my computer it is on C drive.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
Yes, you are right. I thought RUU.log should be in the current directory where i ran upgrade but it actually in the root directory of drive C:

Here is my RUU.log, but i did not see anything abnormal there
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
now connect through mtty and do "task 28". Copy and paste the results here
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
OK, here is the result

==============

USB>task 28

DOCInfoTableinitHW+

Binary0 Size: 0x100000

FAT0 Size: 0x4000000

FAT1 Size: 0xA00000

FAT2 Size: 0x2C70000

All Size: 0x7770000

FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000

USB>
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
Your DOC seems fine. hmmmm...

Try removing the sim and SD card and plug the USB cable directly into your PC. Then run the upgrade again.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
yes, it looks good....

try to go to Boot Options screen, by holding "Light button" after reseting it.

Then select:

Format Storage -> YES

Clean Reg Hive -> YES

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
I then tried

USB>task 32

it returned the result:

Level = FF

Then tried

USB>task ?

The device itself exits from bootloader mode and start boot flash screen but again stucked at a grey screen.

Any action with the mtty did return the following result:

<CE-196609>

and I dont know what does it stand for!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
Hi Buzz,

I did as you recommended but now i have white screen instead of blue or grey as before. Do i need another upgrade?

Regards!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
Your device looks fine. Weird that it doesn't work.

Does any of the LEDs blink when the splash screen is loading?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
None of the LEDs blinked when the splash image is loading. But when it came to the grey screen i got the charging LED, Call and Drop Call LEDs light permanently.

I also noted that, with Qtek Radio 1.06 and Exec Radio 1.09 i got a blue screen and with Dopod Radio 1.04 i got grey screen

Regards!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
remove SD and SIM

start it in bootloader and reflash a complete ROM

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
Yes, i did it many times, without SD, without SIM card and with full ROM package etc. ROM, Radio and Extended ROM. Just have done once more and got the same result: a boot flash image and then a whole blue screen. Format Storage and Clean Reg Hive did not seem to work also.

Regards!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
hmm, that's very strange...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
This Is My File...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
in your case, there is a device CID error.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
CID error again...

hmm, what that might be... ??

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
do you see the difference??

Dahuzi is missing the whole FAT0 partition!!!

Tamagochi's values are OK.

Whole OS is stored in FAT0. No wonder, that it doesn't boot :o(

i just did task 28 as well, on my yet still working device and here are the correct values:

USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
So If It's a device CID error...

What Can I Do?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] v4victory:
Why dont you change the harddrive :wink:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] dahuzi:
I recall that I was touching the Extended ROM before resetting. I try to change the email storage setting from Storage Card back to main memory, just after the resetting, the devide died.

So I suppose the root cause if the FAT table or something else messed up and can't be recognized by the bootloader. Maybe a "low level format" can solve the problem, or it still can be saved from software site. Buzz, is my understanding correct?

BTW: I have sent my device to the seller and ask him try to repair. Properly he will replace the Flash ROM chip, I am not su sure.

Any clue is still welcome.

Thanks

Wilson
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
I'm not sure if the DiskOnChip is available as a spare part.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] dahuzi:
What's the possibility to damage the chip physically? If it's not physical damaged, I think it can be recovered by software. But I don't know the details.

Or the last solution is send it back to HTC for repairing. Is it practical even the brand is O2?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
for one, it's definitelly not a dry solder. I resolder it and the error is still the same.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] MBosch:
same problem as ady

I thing i have the same problem as ady.

I have a Vodafone V1640 and yesterday i upgraded it to the lastest version of Jasjar. Everything Ok till the hard reset. After it my Jasjar hangs on the Imate boot image. I've readen almost everything and i've tried also everything with these results:

1. Reflash the device. I've done that with lots of roms. No exit.

2. Set 14 0. Also no exit. Sometimes MaUpgradeUt_noID.exe doesn't find the devive (properly connected), sometimes it prompts a screen indicating that MaUpgradeUt_noID.exe is not te proper utility to upgrade my device.

3. Task 28. These results:

task 28

flFormatPhysicalDrive:status=23

DOC_format failed!

USB>

I've attached my ruu file.

Can anyone help me? If it is possible?

Lots of thanks.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
Another One?

I Hope There Will Be A Way To Fix This Problem Or I Will Have To Buy Another Unit...

:( :( :(
[JASJAR, XDA Exec, MDA Pro Software Upgrading] MBosch:
Me too.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamagochi:
Re: same problem as ady

Your DOC could be defected i guess. Usually, task 28 will be done with no error!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] MBosch:
So what do you suggest? Send it back to Vodafone and wait for a new one? I ve bought it three months ago.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
yeah... send it back if the warranty is valid.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] MBosch:
Ok. I will do that. Bur first i should replace Imate rom for Vodafone ones. And... I don't have Vodafones originals rooms. One problem more... Upps...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
Seince the last rom update/

more and more seem to have this problem...

i dont think this is an hardware problem.

the only thing differnet for me was that i've opened the ext rom for the first time b4 i've update the rom.

so i guess there is a connection..?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
I'm not 100% sure if it is though I agree that it could be.

since universal is a recently released device so most of the people can get a warranty.

However if enough people have this problem and no warranty than someone can try taking ripping the boatloader somehow to analyze what is actually wrong.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] MBosch:
Vodafone V1640 Rom

Can anyone provide me a backup ot the original Vodafone V1640 Rom. Mine is corrupted so i cannot upgrade back my device to its original rom in orden to send it to Vodafone.

Thanks...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] olliesshop:
Warranty repair / fix is Replacing the Main Board

I just heard from TOPP Solutions that "I-mate authorized the main board to be replaced. The ETD is two weeks. I wish there really was a better solution for this case. But they have found that by changing the main board it will be resolved."

They've been communicating with imate tech support over the last two weeks or so and have been unable to resolve the problem. I hope others can resolve it without replacing the board.

Total downtime, will be about 5 weeks, assuming I get it back in two weeks.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
Re: Vodafone V1640 Rom

I wouldn't worry too much about flashing original rom to it...

they will not be able to read the doc, same as you are not.

I flashed alpine rom to my himalaya once, which rendered it dead and they fixed it under warranty

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] MBosch:
Thanks.

Yesterday i sent my Universal to Vodafone...

Let's see what happens...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Viper®:
Hmm, mine seems to be stuck in bootscreen as well

Never had problems, flashed from Tmobile -> qtek -> imate ->qtek

and now it stopped working. Try flashing it again. Then I'm trying the mtty and the rewrite rom solutions. If those don't work, I'll send it back to Tmobile.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
I've Sent mine to orange...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] AlCapone:
Same here: (QTEK9000) - stuck at the blue splasscreen with version numbers..

-----------------

task 28

flFormatPhysicalDrive:status=23

DOC_format failed!

USB>

-----------------
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
now, after reading all of the above, i'm really worried about my next ROM flashing...

i'll better think twice, before i'll do...

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
btw, can we say, that the problem is related to anything? same brand? some operation?

i'm not gonna go through all those previous posts, but if there is someone, who has more time, maybe can summarize this problem...?

thanx

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] PReDiToR:
I just put the latest WWE ROM into my m5000, and bricked it.

I put the .100 ESN in by mistake, thought about living with Spanish and decided to put the .90 WWE in.

Flashed it, did the hard reset, got the 0/X screen, hit 0.

It said Clearing Now, Clear OK ... Then nothing. Blank screen.

I'm having trouble now because I can't get the USB connection to work at all.

I can do a hard reset, put it into BL mode (without USB plugged in it says serial, putting the USB in changes it to USB mode), and when connecting it to the PC I get the device attached beep, but not the device installed and working sound that I get when I plug in my network card for instance.

When I try to reflash it gives me an error and cannot get the information from the unit for the flash compare screen.

My USB is fine, I have my BT dongle in the same port, that still works.

Whatever I have done to the m5000 has killed it's ability to connect via USB. I don't have USB in mtty, Buzz's BL fix says it can't find a USB connection.

I think I might have to send it back to Orange. PITA. I was hoping to be able to sort this one out myself seeing as all my other flashes have gone smoothly and this one is the one that challenges me.

Anyone have an idea?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] sandrobber:
topp

topp sucks just contact imate via email and they will sen topp the part
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
can anyone else, with stucked device, please post here, how they did the hard reset?

Was it by holding down two "-" keys and then confirming by "0"?

I'm always doing hardreset bootloader way.

I mean to hold down "light" button after reset, till Boot Options screen comes and then i select "Format Storage - YES".

I don't know, but it might be, that the 0/X procedure is not doing the right job or behaves the wrong way..

THANX

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
i guess so, too. that's why i would like to know how all the guys who got their unis stuck at the splash screen reset their unis right after rom burning. was it [-]+[-]+[reset]?

qt
[JASJAR, XDA Exec, MDA Pro Software Upgrading] telemix:
I have made it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I had the same problem (stuck in the boot screen, logo Qtek with rom informations). Today I have reinstalled Disk on Chip (DOC) from another Qtek 9000 and all has earned!!!!!!!!!!!!!!!!!!!

The decision is found!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Really a problem in bad blocks or damage of Disk on Chip. :D
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
do you mean, you've replaced the chip with another one?

we knew before, that it has bad blocks. main question is, how that happens?

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] PReDiToR:
I'll tell you tomorrow if your way works, new unit within 24 hours - one more reason to go Orange!

NB I didn't tell them I was flashing ... or that it was a Qtek ROM.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] telemix:
Yes, I replaced the chip with another one. Most likely it is factory defect. But I do not know, it is a mistake itself DOC or it has taken place in DOC at work accompanying IC or a mistake at a upgrade ROM. :?:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
so the point remains, from where to get the DOC G3 1Gb chip?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] PReDiToR:
Buzz

I Flashed shipped ORUK 1.30.90 with the 1.09.00 radio in.

Used MaUpgradeUT, Left ActiveSync on but disabled USB. Turned Modem and Firewall off. Took SIM and SD out.

Reset, put Uni into bootloader (serial, v1.00), connected USB no hub.

BL changed to USB.

Ran upgrade, it didn't display currently installed versions, all three were blank.

Upgraded (how long??? =/ ), unplugged Uni, hit reset button only.

Rebooted, all worked well.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] paulojocelyn:
FRE to PORT

Please my friends, help me to fix this.

I bought a QTEK 9000 in France and i've problem to change my ROM to protuguese. Allways have a COUNTRY ERROR and i don't know how to fix it. I've changed all ready to 1.30.68 WWE Radio 1.09.00 and ExtROM 1.30.153 but it is a JASJAR. My memory looks weaker and i don't install anything yet. Can anyone help me???

Paulo.
[Omni Q&A] marc13100:
Hi

I installed omnirom 4.4 on my GN 7000

And installed gapps.

I tried make backup, but after few minutes

My phone reboot and the backup is not OK.

It don t understand , screen time out is disabled.

It s necessary to root ?

I don t know how to root and i don t find the ZIP file to root.

Thanks sorry fort my english
[Omni Q&A] mvd96:
try this

Try clockwork mod recovery ... you can google it for your device (i can't post links yet sorry)

and google"how to root GN 7000"

push thanks meter if I've helped you :)

greetings
[Omni Q&A] marc13100:
Hi

I Tried make root with supersu, but when i launch it.

It say : no binary installer. ?
[Omni Q&A] mvd96:
SuperSU is the app that manages root on your phone ... it can't just install root on it.. you need to root your phone first :)

try downloading 'superoneclick root' from the internet and than follow these instructions http://fixlife.in/23/working-guide-root-android-devices-phones-easy-way-superoneclick

(I can post links now :p)

greetings

PS: if it doesn't work you'll have to find another way on google (you can ask my help when necessary)
[Omni Q&A] Entropy512:
All of the galaxys2-common devices use a unified kernel and recovery. You can't change recovery without changing the kernel.

Seems like we might have some weird storage issues on the galaxys2-common family - TWRP backups cause a kernel crash, OpenDelta causes the sdcard fuse daemon to hang... There's already a JIRA bug open for this issue for i777 (not surprised it also applies to n7000), will take a look at it when I get home.

Even if you used CWM it would likely fail as it's a kernel issue not a CWM issue.
[Galaxy Note 3 Q&A, Help & Troubleshooting] nkldn:
Hi guys.

Need to say I looked 2 days to clarify that problem through topics but could not.

I have samsung galaxy note 3 unlocked international . SM-N9005

I rooted the phone I am able to access system folders.

So i see camera sounds stuff is located under

/system/media/audio/ui

the files I believe related to my problem are (at least I opened all others and did not find any more focus/shutter sounds) :

Auto_focus.ogg

camera_click.ogg

Camera_click_short.ogg

camera_focus.ogg

Shutter.ogg

Shutter_multiple.ogg

I changed their filenames. And -

I was able to mute shutter sound. BUT focus sound is still on !!

I tried to move that darn sound files to other folder - all in vain.

Yes I restarted and shut down the phone.

Also the app that does mute system sounds when camera is on does not work for me. When my phone is on mute that freaking camera still produces noise.

So to recap. Shutter sound turned off by changing media filenames. Focus still on.

Any ideas??
[Galaxy Note 3 Q&A, Help & Troubleshooting] tclocki:
Have you figured out how to turn off the focus sound? I was able to turn off the shutter sound by renaming those two files but I still cant find the shutter sound files >.<
[Galaxy Note 3 Q&A, Help & Troubleshooting] nkldn:
nope. so I read some more info and looks like camera sounds are hardcoded in camera.apk

Hence you may rename delete whatever you want but on this version sound still be on.

Other camera applications I have installed do not produce any sounds.
[Galaxy Note 3 Q&A, Help & Troubleshooting] antt00:
Add this to your others.xml in system/csc

<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>

Reboot and there will be a sound option in camera settings where you can just silent all sounds.
[Galaxy Note 3 Q&A, Help & Troubleshooting] tclocki:
Thanks. I tried it and it brought out the shutter sound menu. However, I am unable to click on the off setting no matter how many times I try to...
[Galaxy Note 3 Q&A, Help & Troubleshooting] hoangclick:
I still can't tick on the OFF setting sound like you.

Are you fix problem it?
[Galaxy Note 3 Q&A, Help & Troubleshooting] aizaizbhaby:
Same problem here. Crash rom 4.4.2 there's an option to turn off the sound but I cannot turn it off and it's not responding.
[Galaxy Note 3 Q&A, Help & Troubleshooting] fmpmuld:
All these problems are coming from the CSC you are using. ie XEF (France). It's a build feature in the camera APK itself to match the laws. Try changing your CSC(ie CHINA for me) if you want to be able to disable camera sound without rooting and/or changing system files. It worked for me.
[LG Optimus 4X HD] weezlerox:
I have a rooted O4X (rooting was about the first thing I did when I got the handset), and want to disable a stock app, namely "messaging" so that the original app does not duplicate everything that my current default SMS app is doing. If I go into Settings>Apps>Messaging I can Force Stop, clear the cache and data etc but the option to disable is greyed out.

How do I go about disabling it (presumably with an app?) I would rather do that than uninstall it just in case I change anything in the future (more than likely lol) and want to re-enable it.

many thanks in advance of your help and the banter which I undoubtedly deserve for being too stoopid to figure it out for myself :D
[LG Optimus 4X HD] MilkyJoePD:
Use an explorer to rename it. Put an s on the end or something (so it's *.apks) and reboot.

I don't know any free apps that freeze system apps, but I prefer doing it that way anyway.

To get it back just remove the s and reboot.
[LG Optimus 4X HD] weezlerox:
oooh it really is that simple? I recall doing something similar in the early days of DOS (now I feel rather old)...

I have ES File Explorer, where might I find the original android messaging apk? I have tried using the search function on the whole device but it didn't just find it and I don't *really* know if it appears as "messaging.apk" or something like "google.media..." something....

***UPDATE***

I have found the following:

UniMessagebin.apk (from the icon I would guess this is it but I ES won't let me rename it)
[LG Optimus 4X HD] MilkyJoePD:
In device window, /system/app. You have to enable root explorer and mount system RW.

I think it might be MMS.apk.
[LG Optimus 4X HD] weezlerox:
Properties are showing as

Readable: yes

Writeable: yes

Hidden: No

But I still can't rename it....

Any more ideas?

Any HOOOOJ thanks for your help thus far :)
[LG Optimus 4X HD] weezlerox:
How do I find the "Root Explorer" menus (second and third screenshots) I have the first and have enabled Root Explorer... do I require a reboot?
[LG Optimus 4X HD] MilkyJoePD:
Press root explorer, somewhere on the left, not the button on the right. Then Mount R/W.
[LG Optimus 4X HD] weezlerox:
I must be sooo dumb and you are sooo patient...

I have to press the "Root Explorer" tab? this just brings up a window showing me all the files etc, not another menu like you have :(
[LG Optimus 4X HD] weezlerox:
Just occurred to me to point out that my phone is currently plugged into a laptop (charge only mode) and being used as a hotspot for net access.... could this be relevant?
[LG Optimus 4X HD] MilkyJoePD:
Try clearing data for ES then start over. I don't know if it being plugged in and being used as a hotspot will affect it; it shouldn't.
[LG Optimus 4X HD] black@pirate:
This thread shouldn't be so long :D

Use https://play.google.com/store/apps/...um=organic&utm_term=freeze+system+app+android to freeze sys app and you are good to go.
[LG Optimus 4X HD] weezlerox:
Got it sorted, thanks for all your help guys :)

Being a dumb user doesn't help me lol
[General Questions and Answers] hassan_mourad:
My apologies for repeating this question as I am not sure I posted it in the right location

I was wondering if you can help me in a project I am about to start

I am sure a lot of you are aware of Osomcom projects and OsomcomBB in specific, a great project with great potential.

The only annoying thing about it is its use of legacy phone hardware that is hard to find or has a relatively high cost.

So I was wondering what prohibits the development community from porting this to other phones. I think that on the physical layer it is still the same components. So what is stopping this from happening

I am interested in doing this but have no idea where to start, I don't know if this would be OS related or processor related or phone related. and I don't know how to write or modify the baseband and where the baseband resides (Firmware, ROM, OS), What programming language should/could this be written with.

Can any one point me to the right direction

Regards,

Hassan