yashsingh1/xdaforums huggingface dataset:
[Advantage X7500, MDA Ameo General] silviu.h:
Hi,

Don't worry about using SirfDemo anymore - I swear I'll never touch this piece of sh*i again (provided I get my GPS back to life).

I tried hard resetting, the problem is still the same. I will try removing the battery and letting the PDA lose its current. I read this *might* put the GPS receiver back into its initial state.

I also tried to contact the guy who made SirfTech, and try to understand what the error messages mean.

Silviu
[Advantage X7500, MDA Ameo General] silviu.h:
OK, I removed the battery for a night and now the GPS receiver came back to life... Problem solved :D

Something tells me I won't try any soon to change anything in the receiver :)

Regards,

Silviu
[Advantage X7500, MDA Ameo General] neo_strut:
i did the same: removed battery for overnight

but GPS still not fixing
[Advantage X7500, MDA Ameo General] apd:
Try the solutions in my post (above - #2)
[Advantage X7500, MDA Ameo General] silviu.h:
Hi,

What exactly is the problem: the GPS can't get a fix, or your programs (Tomtom etc.) cannont connect to the GPS?

In my case the problem was that the programs couldn't access the GPS anymore.

If your programs see the GPS but can't get a fix, it's a different problem.

Hope this helps,

Silviu
[Advantage X7500, MDA Ameo General] neo_strut:
GPS can't fix

hi, thanks for reply...

the GPS can't fix at all after 20 minutes....of course outdoor under clear sky

I'm using M700 Glofiish with built in GPS SiRF Star III chipset

I also tried using GPStuner as recommended above...still can't fix, not sure if it's software or hardware problem

one thing, i used SiRFtech...

1. there are signals from "Find Port & Baud"

2. Protocol: NMEA

3. Baudrate NMEA 0 Effective 0

4. Errors FE=0 PE=0 OE=0 QOE=0

???

any idea?

Thanks so much
[Advantage X7500, MDA Ameo General] Pyrofer:
Try the free GPSView program, that is the best for getting a FIX I find.

Make sure you use QuickGPS to download the data first as well.

Hold it up above your head and wave it at the sky?
[Advantage X7500, MDA Ameo General] silviu.h:
I think there might be a problem with your unit, there are several people on the Eten forum who had this problem and had their M700 replaced. See http://eten-users.eu/index.php?showtopic=6586 and generally speaking http://eten-users.eu/index.php?showforum=42

Silviu
[Advantage X7500, MDA Ameo General] Olipro:
try reflashing the radio on the device, GPS firmware is all controlled by that, so flash it and cross your fingers
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] cenkberk58:
Back returns from s4 4.4.2 Mini How ?

I had to try to install 4.4.2 , but did not return it back did not return 4.2.2 ?

Phone Model: i9190

Android Version: 4.4.2

Country: Turkey

Baseband version: XXUBNA1

::confused::confused::confused:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] danio.78:
edit
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
Not sure about the i9190 as I own i9195 but check your bootloader to see which knox software version you are running. Don't think you can down grade certain bootloaders. You may be stuck on 4.4.2 ...maybe
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] cenkberk58:
4.2.2'y the custom in return there, but the stock kernel, not the stock kernel is going flashing phone brick and he did, but custom kernel have installed works as 4.2.2, but sarranty bit kernel, enter the opening did not go my liked required to load the stock kernel to fix it
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
Sorry buddy I didn't quite understand that? ? Try using Google translate to convert your text.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] cenkberk58:
How can I return to my 4.2.2'y I mean my device: i9190
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] czary01:
My teacher does not care for the way we can't find kernel return a BF at this rate, what this samsung yapmıssa kramıcek u this rate no one kernel in knox
[Xperia Z3 Q&A, Help & Troubleshooting] endela:
Good afternoon,

My z3 has coverage problems since he repaired the screen, which was broken.

Since then coverage is not working properly, reaching in some areas remain without network service areas that have no coverage constancy.

The technical service has done tests and says it is correct, but it is not.

Not wanting to send it back I have reinstalled the rom flashtool 23.0.1.A.5.77 but still with problems.

I can do?

Greetings and thanks.
[Xperia Z3 Q&A, Help & Troubleshooting] nedooo:
Insist on repair...
[Xperia Z3 Q&A, Help & Troubleshooting] endela:
The technical service says that passes the test , but the problem comes when you move and that does not prove the technical service.
[Dell Venue] xBIGREDDx:
Dell has updated their open source site with the developer files for the Lollipop update for the Venue 8 7840:

http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/

This includes the kernel source, a guide Doc, and a "blankphone" image which will re-partition the device and leave it in the fastboot interface OS and wait for a system image to be flashed. It does not erase or provision a system image or boot image. The documentation mentions a separate "fastboot" image paired with the "blankphone" image, and traditionally (based on files posted by other OEMs) the "fastboot" zip is what contains the OS images. So hopefully (maybe?) they will be posting that at some point. We should be able to get images pulled off working devices for people to flash.

This "blankphone" zip should function as an "unbrick" and put a mis-flashed device back into a functioning (flashable) state, but you may end up without an OS. (This is why I called it "partial" unbrick, because you won't have a brick but you won't necessarily have a booting-to-Android device either.)

ALSO A WARNING: This should be all fine and good but proceed with caution.

I have flashed the IFWI-only.xml and successfully booted back to Android.

The zip file can be flashed with Phone Flash Tool Lite, available here from Intel for Windows and Linux.

There is a "Flash file" selector in Phone Flash Tool.

To unbrick and format, use the file: flash-DDO_BB.xml

[IMG="unbrick"]http://i.imgur.com/V6xrLcS.png[/IMG]

To just flash the unlocked bootloader firmware, use the file: flash-IFWI-only.xml

[IMG="firmware only"]http://i.imgur.com/DdYvzUp.png[/IMG]

DO NOT use the EraseFactory xml; I'm not certain but I think there are DRM keys in the /factory partition, and you could permanently break things like Netflix if you erase it.
[Dell Venue] anggusss:
Since mine is currently useless, I may as well try this. Will the image you uploaded here work?

Don't have access to the tablet at the moment but I'll try when I get in (couple of hours).

I know [MENTION=339557]wirebook[/MENTION] tried on the older bootloader and failed but not harm in trying with this new stuff I suppose...
[Dell Venue] xBIGREDDx:
That system.img doesn't flash I think... Though it sounds like it's just an issue of repacking it somehow.
[Dell Venue] wonglynn2004:
This is great news!

If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
[Dell Venue] xBIGREDDx:
Windows is unlikely, as it would require additional drivers and a custom bootloader OS to be created, among other issues. Linux may be possible though.
[Dell Venue] anggusss:
I've managed to unbrick my device, but I'm honestly not sure how.

So using the intel flash tool, I used the option flash-DDO_BB.xml, understanding that it would wipe the device (erase system, repartion, etc). I then had access to fastboot. From fastboot I attempted to flash the system.img [MENTION=4026388]xBIGREDDx[/MENTION] uploaded, obviously that failed with the sparse image header issue.

Next I converted the system.dat.new in the OTA to a system.img, attempted to flash that from fastboot, no go.

I decided it might be a good idea to flash the boot.img from the OTA, so I did that. Ended up on the original Dell/Intel boot animation (progress?). This seemed to infinitely bootloop (however maybe I was just impatient?).

I then booted CWM using the temp. recovery method (T4), wasn't able to do much at all, most directories were empty and nothing was mountable. Rebooted the tablet once more, went to get a drink and it's booted into Lollipop!?

I'm both confused and pleased... Can anyone shed any light?
[Dell Venue] xBIGREDDx:
Hahaha not sure, maybe the reboot caused it to process the update again? The OTA may have been in the cache still.
[Dell Venue] xBIGREDDx:
Update: I have looked at the xml files and it turns out they are not erasing the boot or system partitions after all. That has been the standard procedure in the past so I didn't think to check. They are, however, wiping the data partition, and they wipe the cache twice. Maybe they've been reading XDA too much? :D
[Dell Venue] anggusss:
Ah I see. So if my system was never wiped, I assume flashing the new boot.img from fastboot is what kicked it into life.
[Dell Venue] wirebook:
I probably should have posted somewhere that I wrote a second query to Dell and heard back from someone in Legal six days ago stating that they were going to go bug the team and get the images posted online. They promised to follow up- never did- but looks like the rest of you were a lot more diligent in checking out the open source repository. ;)

Anyway, the tablet I was working on belonged to a family member now living in a different city. Seems like we've figured out more or less how to unbrick this thing, so that's fantastic! :) I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
[Dell Venue] wonglynn2004:
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
[Dell Venue] anggusss:
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
[Dell Venue] xBIGREDDx:
Yes, it was the developer unlock firmware that broke the OTA, not rooting. With the new Lollipop boot firmware, I think even if it's the unlocked firmware we should be good moving forward.

If you still want to unroot, there should be a menu option in SuperSU, it's like "cleanup" or something.
[Dell Venue] xBIGREDDx:
1) Install Phone Flash Tool Lite from Intel.

2) Download the blankphone zip from Dell's open source site.

3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"

4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.

5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.

6) Click "Start to flash" and wait.

7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.

If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
[Dell Venue] wirebook:
Thank you so much for posting that! I'll attempt to walk my father through the process this weekend. :)
[Dell Venue] anggusss:
Stuff wasn't quite working right for me, the screen was turning on randomly, reboots took a ridiculously long time, and a few other things. Decided that it may be better to start with a fresh system partition.

Tried converting both the system.img from [MENTION=4026388]xBIGREDDx[/MENTION] and the one from the lollipop OTA to sparse imgs and flashing, however I'm getting

FAILED (remote: flash_cmds error!

When I try to flash system, during the write stage. I'd like to think they're correct sparse images since fastboot reads and sends them to the device.

If I look at the tablet screen during the flash, it complains of an "Unknown chunk type" before failing.

I can get to the default recovery and fastboot, I just don't seem to be able to flash something to my now empty system partition from fastboot...

EDIT: Managed to flash system through the tethered recovery, but I'm still met with a black screen on regular boot.

EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.

Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
[Dell Venue] wirebook:
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
[Dell Venue] anggusss:
Sorry, I could have been clearer.

The steps I performed:

First, booted to fastboot

Trigger the tethered recovery (T4)

Once in the recovery, I then formatted /system using the graphical menu. (Probably not necessary since we're DDing the img directly?)

I had a microsd card in the device which was EXT4 formatted, so I pushed the system.img to that after mounting it by hand.

mount -t ext4 /external_sd /dev/block/mmcblk1p1

Then from the PC side

adb push system /external_sd/system.img

You could probably push to the data partition if you can get it mounted in the event you don't have a microsd.

Once you have the system.img on the device, you can dd it onto the system partition

Make sure /system is unmounted

umount /system
dd if=/external_sd/system.img of=/dev/block/by-name/system

NOTE: /dev/block/by-name/system may be wrong, I'm going from memory. I'll correct it when I get in from work.

After flashing system, reboot to fastboot again

adb reboot fastboot

And finally flash the boot.img from the OTA zip I uploaded

fastboot flash boot boot.img

Perform a normal boot, and it should be working. First boot takes a while, 3-4 minutes.
[Dell Venue] xBIGREDDx:
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:

fastboot flash fastboot droidboot.img

There is a droidboot.img in the update.zip from the OTA.
[Dell Venue] anggusss:
I did try that quite a few times but no luck. I just seem completely unable to boot straight into fastboot. I either have to reboot to it using ADB or use the flashtool. Not necessarily a problem, just an inconvenience.
[Dell Venue] Noswal:
Thanks for this.
[Dell Venue] wirebook:
Had no luck coaching someone else through the process. Apparently they couldn't get anything to mount and thus were unable to flash anything. I also caught them loading the ZIP file (and not the IMG inside) onto the MicroSD card so who really knows what's wrong at this point. I'll probably just have them mail me the tablet and then I'll do it myself.

Unless anyone has some suggestions. Thanks again for all the wonderful help!
[Dell Venue] Noswal:
I found it easier to put the system.img onto the sd card using a card reader than through shell. From there, I went straight into unmounting /system and DD. Unmounting or mounting will give you an error if it is already unmounted or mounted, respectively. Everything went smoothly except when I tried to update to 5.1. I had to install the update.zip through recovery.
[Dell Venue] bobbyhawaii:
So I got myself in a bind last night trying to root my 5.1 update. For some reason it bootlooped at the "Intel Inside" screen. Couldn't get anything to go through. I followed the instructions posted within this thread to try and get root to the letter. Not sure what happened, so I quickly flashed the flash-DDO_BB.xml to get myself out of the bootloop. I am currently in Fastboot and I can get into the tethered recovery but for the life of me can't get any of the steps done that anggusss posted. I put the system.img file on my SD card but cant get adb to to push the file to the system directory. I can't even get adb to do the dd command for some reason. ADB shell isn't showing up but ADB does show my device listed. Could someone help me with this please? If need be, I can let you do a teamviewer session on my computer if that's easier. Thanks again everyone.
[Dell Venue] jet23jay:
I copied the system.img to my sd card like you said, but when tried to DD it i got "dd: /external_sd/system.img: No such file or directory. Any help would be greatly appreciate
[Dell Venue] jet23jay:
Thank you for your guide. I copied the system.img file to my sd card so i skip to umount system (it said " /system/ not currently mounted") When i tried to DD to the system partition, it said that there was no directory or file for /external_sd/system.img. Im not sure why it could not see the system.img ???
[Dell Venue] jet23jay:
Got it working now. I used a new sd card, DD system.img to system and install boot.img, and the device is now working again.

Thank you
[Dell Venue] enzymeyllw:
No luck for me, after i type "umount /system" , the answer is "Operation not permitted", do you know what' wrong with it, thank a lot！

---------- Post added at 07:30 AM ---------- Previous post was at 07:24 AM ----------

No luck for me, after i type "umount /system" , the answer is "Operation not permitted", do you know what' wrong with it, thank a lot！ and my sd card is fat32 formatted, i did not find the ext4 formatted. Is that mean i should change a sd card?
[Dell Venue] enzymeyllw:
Is sdcard must be ext4? Can fat32 work? Please give me a hand
[Dell Venue] minnaing:
I try many time , finally end up in the fastboot OS. What should i do to boot into OS.
[Dell Venue] xBIGREDDx:
Try following these steps.
[Dell Venue] minnaing:
Thanks a lot man, now working back...:good:
[Dell Venue] minnaing:
Finally android 5.0.2 developer version is working now.

I receiving OTA for 5.1 and I tried to update.

Tablet reboot into fastboot and showing waiting fastboot cmd....

Can't get into stock recovery.
[Dell Venue] sangsanh:
Anyone able to resolve this issue? Currently having the same issue
[Dell Venue] wilbur4321:
Yes!

Strangely enough, following the steps to root it fixed it. Specifically, flashing step 1 from the droidboots zip file, and the using the T4 mode booted into TWRP (or is that CWM?) recovery. Here, it magically ran an update script, and then rebooted, and all was golden.

--randy
[Dell Venue] minnaing:
which update script do run. Can u give me link?:confused:
[Dell Venue] jet23jay:
So after multiple attempted to update to 5.1 i got it working.

So after unbricked you dell venue 7840 you will be on 5.0.2 then launch update to start downliading 5.1 once it finish it will ask to reboot. Reboot your device, and you will be stuck at fastboot. Now you need to launch temporary recovery ( T4 mode) but ****you need to use this version" IntelAndroid-FBRL-06-03-2015-PTR2" which use TWRP recovery; it will run update-script like wilbur4321 said *** If you use older verions which use CWM recovery the update will failed.
[Dell Venue] minnaing:
Thanks a lot for information, Now updated to 5.1 and rooted.:fingers-crossed:
[Dell Venue] vikasnewports:
what if my device not detected on PC
[Dell Venue] lamoid:
flash-DDO_BB.xml fails with "Flash Failed" No reason is given.

My Venue 8 7840 boots into fastboot mode only. I've tried everything I could find on xda but cannot recover. I can use Intel Fastboot Tethered Temporary Recovery Session Launcher (IntelAndroid-FBRL-07-24-2015) to get into CWM recovery but it does nothing. I've tried using Intel platform flash tool lite 5.5.2.0 to flash flash-DDO_BB.xml from Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397 but that fails.

Upon Opening flash-DDO_BB.xml I get this:

11/21/16 21:19:45.220 WARNING: Bootloader DnX file not specified in flash configuration ("os_dnx" key)

If I start the flash procedure I get

11/21/16 21:20:02.001 ERROR : Automatic reboot is not supported on this device, please reboot the device manually

It fails at 3% with

11/21/16 21:20:43.095 ERROR : [Port 2/8] Command `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\xfstkFlashTool.exe" "-1" "F:\packages\Android\Dell\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\dnx_fwr_blackburn_qs_rd_opensource.bin" "F:\packages\Android\Dell\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\ifwi_blackburn_qs_rd_opensource.bin" "" "F:\packages\Android\Dell\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` failed

11/21/16 21:20:43.096 ERROR : [Port 2/8] Flash failed (Command type: Ifwi)

"fastboot devices" executed from my windows 7 PC returns the devices serial number but the device does not recognize any of the fastboot commands. The device was unlocked before it failed for reasons unknown, but it does not show that now on the fastboot screen. I've attached a picture of the text on the fastboot screen.

Anybody have any ideas what is going on or how to fix it?
[Android Apps and Games] hanrian:
NOW available in Google Play Store

App in Google Play : https://play.google.com/store/apps/details?id=com.handev.angelup

Angle Up is new addicting android games, Angel Up game is not easy.

Help angel flying up by passing a circle without hitting the circle.

And most of all, stay calm :cool:

★ ★Please don't angry if you play this game, Angel Up game is not easy.★ ★

★ ★★ ★[HOW TO PLAY]★ ★★ ★

• Tap to up the angel into the circle.

• Angel don't hit the circle.

Enjoy the game!

★ ★ Please rate Angel Up game if you like :) ★ ★

App in Google Play : https://play.google.com/store/apps/details?id=com.handev.angelup
[G3 Accessories] pikachukaki:
I purchase this power bank for a webstore in my country so no ebay no Chinese site is involved... I get it it look legit but it can't charge my phone... Any help?
[G3 Accessories] tunichi01:
You got a fake one :(
[G3 Accessories] pikachukaki:
how can you tell?

Pass-Through Charging

Genuine: The original Mi Power bank supports pass-through charging. What it means that the power bank will also charge a mobile phone connected to it while it itself is being charged. Only necessity is that the input charger must supply enough power and as such, charging via a PC’s USB Port will not help.

Fake: The fake power bank does not have this capability and it will just charge itself and won’t pass on any current to the mobile phone connected to it. It will only charge the mobile when you disconnect the charger from the power bank.

The power-bank its connected with the charger and my phone with the powerbank and my phone didn't charge...MADAF***ERS
[G3 Accessories] tunichi01:
Originally, the print on the bottom would be a lighter gray color but maybe it's just because your pic is taken with low light. Or maybe you got a Class S clone? I also have one but I have no problems charging my phone with it whatsoever.

Why not ask for a replacement from the seller?
[G3 Accessories] pikachukaki:
As i said the original have to charge the phone while charge the bank...mine didnt do it so its fake...of course i contact the seller and ask for refund they said they can give me my money back or i should choose a remoss bank as well...i'll see thanks for your answer!
[G3 Accessories] oledetech:
Identification of the true and false xiaomi power bank:

1, The usb connector of the real xiaomi power bank is a little bit yellow, the false one is white.

2, The logo of the real xiaomi power bank is delicate, looks darker.

3, The imprint of the letters on the power back is clear and light. The false one is not clear and looks dark.

4, The usb cable of the real one is a little bit gray as apple cable. The USB end has black rubber core

Hope it can help
[Micromax A116] Abhinav_Rocks:
Heyyyaa everyone.. Can anybody give me solution how to do odex to deodex stock rom of a116i.. Can anybody help me plzzz..