Database Info

Brand new WM 6.0 phone won't turn on :(

I am about to burst out in tears
Oh yeah, Hi, my name is sitnet, I just registered.
Today I bought a HKC Mova 305 windows mobile 6.0 phone. You won't know the make, it is a local service provider make. It doesn't have any warranty, it was on promotion for very VERY cheap.
This is the problem:
When I turn it on it just shows the logo of the service provider (a splash screen) and then the screen goes dark (logo still visible in sunlight), but it doesn't do anything from there on. So then I did a soft reset (with a small reset button) but still the same thing.
Then I started experimenting, the phone has a load of buttons, there is a wheel on the side with a button below it and then also a camera button. I held in the button under the wheel and the power button together then this menu came up:
Code:
PB Update!
Connecting ...
INFO: Trying to initialize USB RNDIS...
HostMiniInit:: !!
Rndis:: initialization: with addr-0
Rndis:: initialization!
Rndis:: PDDInit success!
Rndis:: Get MAC address 4500,5634,9A78
Rndis:: initialization: Fail!
ERROR: Failed to initialize Bulverde Rndis USB Ethernet controller.
ERROR: Failed to detect and initialize Ethernet controller
Then I removed and reinsterted the battery and pressed the wheel button in while pressing the power button and got this menu:
Code:
------------------------
Xloader Version:
Eboot Version: Eboot-1.02-02
1(W): Update with SD Card
2(T): Boot from IPL KITL disable
3(B): Doc Update
4(L): Format Partition
5(R): Test Memory
-----from oallog--------
Enter your selection:
The buttons associated with the selections do not do anything though, BUT I experimented that I can select any of the options (except nr.4) with other buttons.
Ok and lastly when I press the Camera button and the power button together it says "KITL enable" and then only shows the splash screen again but forever.
This is my very first Windows mobile phone. I have no clue what to do
I have read that there is a way to reinstall the rom or something. I will do anything to get the phone working.
Here is the phone: ucables.com/ref/TELKOM-MOVA-305-PDA-P-R105795
Please, please I beg of anyone to help me, I will be so grateful it can't even be described in words.
EDIT: OK I found out that when pressing the "red dot" button (it changes between numbers and letter while typing) and the power on button it says waiting for USB connection and then I plugged it in and it installed as a "pocketPC" and now it says "Updating" on the screen. I'm just going to wait...
THANX so much guys!!!

Did you manage to get the phone booting. I`ve got the same problem with a phone I got today.
Kind regards

Got a link that might help. Haven`t tried it yet: expansys.jp/ft.aspx?k=119230
PS: Another name for the mova 305 is UBiQUiO 503G

ive got the same problem with mine...let me know if there's any changes

I found a link that will help. My phone is loading into windows mobile now. Not hanging on splash screen.
Good luck
expansys.jp/ft.aspx?k=119230
just add www to the front of the url. Wasnt able to post full link.

Thanx for the reply, i tried that method and could actually install that rom on the phone through the "super rom update" utility.However, when the phone restarts it still does the same thing...It just shows the telkom logo for 4 seconds then the phone switch off.
Any suggestions?
Thanx

So, somebody is trying to sell this phone again! And with the same useless initial rom in it as I can see!
The same support site has a new version of the rom that is 3.05 instead of the 2.2 here
Originally they were selling this phone with an extra special cable just for flashing the radio part of the rom but as far as I know it is no longer offered.
I think there is someone from China that posted on the same site that he's flashed WM6.5 on it but the guy disappeared! See here.
There is also more info on the Modaco website and an even a new rom! You will need to flash the 3.05 first then the 3.10 at Modaco. It is new but it is only a 6.0 rom but it addresses issues that people had with the phone. The Modaco website has more info about this phone.

[Q] lg optimus 3d dead

hi, i'm new here and why i'm here is that i'm desperate for help.
i have lg optimus 3d korean version called lg su760. it was working. i even root my phone. when i update it to gingerbread, phone became unrooted. i believe it was on v20e. some one told me to change it to v20a or something.so i download some software by googling. connect my phone via usb to laptop while holding volume up and power button. the s/w logo came up on screen. there was some process on the pc screen then its comes something like failed to update..can't remember. i disconnect my phone. it was still on s/w. then i turned off. from that time my phone won't turn on. won't show any kind of response. when i try to connect with laptop, i can here some sound like its trying to connect but can't and then the sound stops. i really want it fix. but it just dead..plz help me if some one have a clue what happned to it.

Search the forum for guide unbrick optimus 3d kdz method I think u need v20g but I am not sure with the Korean model
sent from my acidhazard thrill

this phone lg optimus 3d (lg su760) just seems dead. it won't turn on, it won't go to recovery mode, i won't show battery charging status, i won't connect to laptop. laptop does make sound like its trying to connect with then phone. but after few attempts it just gave up.
i was in uk, but right now in Pakistan. i showed it to few mobile phone technicians and they said that its BOOT ROM DAMAGED. can anyone please tell me who can i connect this phone to laptop??? i don't know much about ROM, About KDZ or anything. but i think once my phone get connected with pc then i might be able to do something with it.
what do you thinks guys? will i be able to recover my phone or its just gone now..totally dead?? please reply.

At the moment you have no way to recover it by connecting to laptop,you need a new board.

Sorry, search doesn't work right now and i found this thread via google only. Hoping someone can pull magic out of their $$$.
I have an LG Optimus 3D P925G (but using the ThiaiZ ROM for a long time). Yesterday i was going to experiment with another ROM, so i copied some files from the SD to External SD via mass storage, rebooted into recovery and did a backup (CWM), and then forgot i wanted to copy a couple more files, just to be safe. So i rebooted into the phone, connected via mass storage, copied my files and turned the phone off. A bit later, i went to turn the phone on into recovery so that i can flash a new ROM and nothing happened. Phone won't turn on, no screen, nothing!
So here is what i tried, with two separate batteries.
1. Hold down 3D, volume down and power
2. 3d, volume up, power
3. volume down, power
4. volume up, power
5. home, volume up, power
6. home volume down, power
7. Took battery out, held the power button for more than 10 seconds, but the battery back and tried above options
8. All of the above while connected to PC via USB
-Some caused my PC to connect for half a second and go into continuous loops (you hear the PC trying to connect, but half the sound it usually makes, and then again and again...)
-So PC can't see it, ultimately
9. Tried above options with battery out and then putting battery in
I got nothing left to try...any ideas? Magic?
But i am guessing an expensive brick/paperweight is what i have.
Thanks!!!

Follow this step by step.
Install driver.
Use another cable.
Open Windows device manager.
Remove battery.
Insert battery.
Hold vol+.
Insert cable.
If it gets recognized it will show you LG communication port in device manager.
Release vol +.
If you cant see that and all you get is OMAP4430 you probably flashed wrong ROM and your LG can't be repaired with the tools that are available here.
Send from my Xperia Neo V using xda-developers app.

No go. Still get the OMAP, off and on in a continuous loop. The thing is, i didn't install a new ROM yet, i was planning on it but never got there.
Fun (sarcasm).
James

Pls help - same situation
Pls help! I'm in same situation. Did anyone manage to find a solution?
I am desperate because I need my phone all the time.
I have the same symptoms, and the OMAP device in device manager does the same thing. On/Off/On/Off...and so on..
If I simply plug my phone in, It just goes on/off/on/off ....... it only vibrates shortly when it starts and I can see the LG logo, then it turns off.

Did you enter "S/W update" mode ??(by insert battery while holding vol+)??
Hit Thanks Button If I Helped
---------- Post added at 04:06 AM ---------- Previous post was at 04:03 AM ----------
This happened to me . The same .I am sure ...
I just follow this guide and the life return to my phone .
http://forum.xda-developers.com/showthread.php?t=1942836
Hit Thanks Button If I Helped

Search the threads ..
There are tools available that fix this problem

Wkpark fastboot tools make the phone almost unbrickable unless it's damaged the hardware
And it's very hard to damage the hardware

zeeshana said:
hi, i'm new here and why i'm here is that i'm desperate for help.
i have lg optimus 3d korean version called lg su760. it was working. i even root my phone. when i update it to gingerbread, phone became unrooted. i believe it was on v20e. some one told me to change it to v20a or something.so i download some software by googling. connect my phone via usb to laptop while holding volume up and power button. the s/w logo came up on screen. there was some process on the pc screen then its comes something like failed to update..can't remember. i disconnect my phone. it was still on s/w. then i turned off. from that time my phone won't turn on. won't show any kind of response. when i try to connect with laptop, i can here some sound like its trying to connect but can't and then the sound stops. i really want it fix. but it just dead..plz help me if some one have a clue what happned to it.
Click to expand...
Click to collapse
First things first. If you have tried all these, start afresh.
uninstall all LG related software, reboot laptop and start again.
search the forums for all related issues, read read read, understand and follow the steps exactly.
you will have your su760 up and running!!
schubeir

[Q] Star N9800 unresponsive touchscreen

TL;DR - Flashed a ROM designed for N3+ (which is supposed to be same phone) but touch screen is unresponsive now. Need help with SP MDT or editing uboot
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?).
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
____________________________________________________________________________________________
Hello everyone, like title says I have unresponsive touchscreen on my Star N9800 phone. It's pretty much a new phone, octa core, quad core GPU, 2GB RAM, 16GB storage, etc.
What I've done is I flashed the ROM designed for Star N3+ (which is supposed to be same phone) but my touch screen is unresponsive ever since then. I've googled and read some articles on xda about SP MDT. It's a tool which can help us choose the display driver we want the phone to run with. I actually ran into a problem when i downloaded SP MDT. I can select the database etc, but when i get to scatter file it just doesn't want to load it. Either it's incorrect name or file type. I've downloaded 3 original ROMs from needrom.com and strangely the scatters seem to be different. But none is accepted by SP MDT. I need someone of knowledge who can teach me where to find uboot and how to edit it correctly. I'm not a linux/android programmer and I really don't wanna get involved into much programming. I understand basic stuff, i can find files on the system, i can edit build prop correctly, remove or edit boot_logo, boot anim etc, but this is a bit more than that. 2
Please share some knowledge with me and please don't point me to google. There's no solution there, i've googled for 3 days now. The last resort for me is to make a post here (and hopefully don't get ignored for spamming because this isn't spam).
My email is: [email protected] - you can notify me here if I don't get automatically emailed by xda.
Thanks in advance.

BUMP

Have no solution but would like to learn as well if anyone can help us...
I had the same issue but gave up and flashed another rom instead.

Flashing another ROM didn't help my problem. Well partially it did. I've flashed 2014-1-7 original N9800 ROM and the touchscreen only needs 1 or 2 off/ons till it starts working. I'm kinda fine with it because it was completely unusable. Flashing drivers with SP MDT didn't really help. I've tried flashing RX5720TM_828A (from N3+ ROMs) and LP057APK (default in N9800 ROMs) and RX5720TM_813A (2nd in N9800 ROMs), and so far my touchscreen works only with 813A LCM driver. When i turn off the phone and then hold VOL- & POWER & OFF/ON it goes to factory mode. There i clicked version and it showed that 813A is installed as LCM driver, BUT touchscreen says (null). Could it be that my digitizer is no longer connected or what? Cuz it sometimes works correctly without turning the display off/on at all.

EDIT 15. July, 2014.
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?). It is possible that digitizer is detected but not working?
Even if i boot into recovery, screen doesn't react to touches.
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
Apparently it's the calibration which ****ed up my phone. I'm now trying to figure out how to calibrate the screen through CWM.

ever find a solution?
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.

Touch screen sometimes not react
AlexZap said:
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Click to expand...
Click to collapse
-------------------------------------------------------
I have exactly the same issue and same signes, the phone itself is working good, ring for incomming phone but the the screen is not reacting i cannot take the call, it receives emails.
Did someone have a solution please let me know... thanks
My phone is star N9800, 2Gb memory and 16 Gb storage, android 4.4.2 originaly installed and was working fine during 9 months

Touchscreen - hardware failure
Hi,
I am wondering if you may have experience and be able to help me with my Star N9008 phone which has has had its touch screen stop working while I had it in storage for about 3 months.
Very well stored, no shock, no humidity. I keep it with my laptop backpack as a spare in case my everyday phone fails.
Today I powered it up to make sure battery was good (found it good at 95%) and update applications, etc. Basically, just checking it was still good to serve as a backup should I need it.
Thing is, I found the touch screen is completely unresponsive. Connected a mouse to it and verified all was working good, did up the updates, etc.. using the mouse. Reboot and boot into service mode and restore menu. Also, no touchscreen response (I use TWRP). Thus, it must be hardware failure.
From experience, would you know what would cause this, and how to resolve?
Thank you.

So, its been a while.
So, it's been a while. I still have the phone in storage and pity it doesn't work...
I haven't bothered opening up the phone if I don't know what to really try and also risk damaging it.
Also didn't bother ordering a new digitizer to replace as it's economically unviable.... the phone is now really getting behind as new tech is further evolving, so I do unfortunately see it going in the rubbish soon (along with two brand new batteries I had purchased for it just before it died).
Has anyone been successful at finding the culprit?
In my case, it was fine and very well stored... so I don't really have an explanation other than the phone possibly having a 'countdown timer' to break it... (yeah, a bit too conspiratorial, lol)

I did not find a solution yet , phone still sits in storage

[Q] Power cycle loop, bad kernel

Started with a VS980, flashed a TMOB ROM and (here's the error) flashed a D801 kernel. All hell has broken loose. The phone loads as TMOB, which is great but it power cycles a little bit after reaching the home screen. The keyboard does not work, and there is a panel mid-screen saying "ERROR". TWRP is gone, and factory resets don't help. Tried flashing KDZ and TOT but neither have worked, LGMobile Support Tool encounters an error partway through and the FlashTool claims the versions are wrong and to check the DLL (have tried VZW and TMOB).
I keep getting kicked into the Flash to Stock threads but I can't reach that stage, and I can only get partway through ADB (when the computer recognises it, which is only part of the time) before the phone power cycles. I can get into software download mode, but that doesn't seem to help. I have been told that since I can reach the home screen and muck with settings (I have USB Debgging enabled and Developer options now) that it's not a bootloop, I just don't know where to go from here. Need a phone ASAP for business calls, have been out for almost a week and the job is pissed at me.
What do? It registers as a D801 though the computer recognises a VS980. Software/IMEI/all that good stuff is "UNKNOWN" in the About Phone section.

Recover files from bootlooping Zenfone6

Dear all,
from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots again.
As always, the backup is too old and I want to extract some data off the device. Most important are a few KBs worth of text notes. Here come some questions:
- It seems to be a hardware fault. Are there educated guesses what may give me a few last moments with the device to extract data? Heat? Freezing?
- Are there professional data recovery companies dealing with smartphones such that they can extract data from the chips without the phone working?
- As it is a Qualcomm device: Would any access via QDLoader work or would it be as unstable as the rest of the phone?
I appreciate any input. And yes, I know that I didn't backup often enough.
Thanks,
weaker

which rom are you on?

Sorry for the late reply.
I'm on stock ROM with Magisk. In the end when it became worse, I let Magisk restore the images but this definitely seems to be hardware-related. I also did no overclocking and I don't use games on the phone so I think that it is also not a thermal issue.
To keep the interested ones updated how it evolved: The situation is now as follows:
I tried to boot into recovery via fastbooting the TWRP (the one I used many times successfully for my phone) after one of the phone bootings was stable for enough seconds so have ADB contact and go to fastboot mode. I hoped to be able to interact more stabily in the recovery. However, the result was that the phone rebooted (I am unsure if the TWRP transfer was finished before that) and then the charging screen appeared and the charging screen remained constantly on, even when pulling the cable. It didn't react to any keypresses in that state.
I let it drain the battery (which was only a few hours as the screen was always on). Then, I plugged the phone in and it booted normally and was stable for 15 minutes or so, which gave me enough time to save the most important data. Phew.
This session however seemed to be the last farewell. The phone started to bootloop and I switched it off*. Now the phone has always a black off screen and doesn't respond to anything: Pressing (and holding) the power button, also in combination with Vol+ or Vol-. Also plugging a cable to charge doesn't create any reaction.
* switching it off worked the following way: The unlocked bootloader shows that one could press the power button to pause the boot. I can't think of why this might be a useful function in a normal situation. However, in my situation I could pause the boot and after some time it would switch off. That way I could at least break the bootloop.

you will have to boot into qloader to be able to recover your phone...
follow step by step exactly what is mentioned in the below link, ypu should be able to recover your phone :
Here’s how to unbrick Asus ZenFone 6 (Asus 6z) from QDLOADER 9008 mode - PiunikaWeb
Is your Asus ZenFone 6 (Asus 6z) hard-bricked? You can use still flash via QDLOADER 9008 mode to give a new life to your dead handset.
piunikaweb.com

Sorry to be the prick here, but next time post this in Q&A section. This one is for posting development (Kernels and ROMs)

OK, no offense taken. I thought that I would need to resort to some TWRP magic to get data off my device.
@MOD: Feel free to move thread where it fits best.

For the sake of completeness:
The phone is back from RMA. According to the sparse documentation they exchanged the mainboard and battery and some connector. Some firmwares are now newer than on the old mainboard (little surprise here). Bootloader unlock worked also on the new phone (some report that this would not work by default after an RMA, for me it did).
So, ASUS did a great job dealing with the issue.