Develop Bugs

UMTS900, GPS and HTC Desire 2.2!

My GPS doesnt get any satellite when umts 900 is in use. Can anybody confirm this?

helo,
same thing is happening to me. so far you are the first with same problem.
i still havent found solution , i hope someone will.
also i had same problem with 2.1

i also asked HTC support about this problem, their answer was:
Dear *****,
Dear Mr. ****, Thank you for contacting us, We apologize for the delay in answering your email, Kindly be ifnormed that this is not a common issue with the HTC desire, kindly follow the steps below to try and solve this issue: 1) Please make sure there is enough free memory on the “Phone memory”, to check the available memory kindly go to Home>Menu>Settings>SD card & Phone storage, make sure that there is at least 5.0 free MBs on the phone memory, if not kindly delete some applications to free memory. 2) Kindly check if you will have this same issue when using the Google maps application or not. 3) Please turn off the handset and restart it again while pressing and holding the "Menu" button to open the handset in safe mode, and check if the issue persists or not. 4) If you can access the handset on Safe mode, then the issue will be a result of a 3rd party application, kindly uninstall any 3rd party application that you have on the device and has any relevance to the GPS, or Connectivity, to check the permissions of the applications kindly go to Home>Menu>Applications>Manage applications>Permissions, to remove 3rd party applications please open the device in “Safe Mode” and delete the applications. 5) If the issue is still not solved you can kindly try to perform a soft reset to the device by turning the device off, removing the battery and putting it back in again then turning on. 6) If the last step didn't solve the issue, kindly backup all the information on your handset either by synchronizing to a PC/laptop or by using a data backup software to back the information up on the memory card of the handset then perform a Hard Reset to your handset, kindly follow the steps below to perform the Hard Reset: Go To Home>Menu>Settings>Security>Factory data reset, Tap "Reset Phone" then tap "Erase everything" Kindly be informed that this process will erase all the information on the phone memory of your handset. Please note that you can contact us via support line.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number **************.
Sincerely,
Amr
HTC
none of this things work

great. this means no support from them and neither a fix. Another nail in htcs coffin for me.

you wouldnt have tusmobil, would you?

yes maybe this could be our problem

right lol. Now tell me if you are from Maribor or close by also?
Poltergeist:
http://www.alter.si/tabla/showflat.php?Cat=&Number=998774&page=0&sb=&o=&vc=1&PHPSESSID=#Post998774
Poltergeist, iii:
http://www.alter.si/tabla/showflat.php?Cat=0&Board=Telefonija&Number=917942&page=0&fpart=31
Pesimist, Onlyx :
http://slo-tech.com/forum/t411453/1549

Hi, i answered you in private msg...

Nexus 6 with Android N stops booting after entering start pin - bricked?

Scenario:
- I have a Nexus 6 (shamu) with Android preview: the version of the OTA is NPD90G. (Android beta)
- Yesterday it crashed right after it lost radio signal (this used to be a common problem for me but when it crashed it came back again fine for me)
- Now when it boots it asked for my personal pin, then the animation makes its first round and at the end of the second round it stops and it reboots.
-- This is what it looks like for a moment: www andreaundstefanhoehn de / nexusboothang.jpg (cannot post urls at the moment)
-- Removing the simcard has no effect
-- I wiped the cache partion
- Of course I do not have a backup of my data
- Of course the device is locked
- The last message in the log_kmsg is "SELinux: initialized...
What I did:
- I tried the famous "Fix Dead Android in Recovery Mode" but it doesn't help
- After many tries I understood I can update my device with "adb sideload"
-- after searching around a lot I even found the firmware NPD90G and I was successfully to reinstall the firmware.
-- For those who are desperately looking for that version as it seems not to be listed anywhere, here is the still working link: storage.googleapis.com /androiddevelopers/shareables/preview/ota/ shamu-ota-npd90g-06f5d23d.zip (cannot post urls at the moment)
-- Unfortunately even after reinstalling the firmware, it still stops at the same point
-- I tried to unlock the device with "fastboot oem unlock" but it tells me to check "allow oem unlock" in Dev Options which 100% likelyhood is not checked
- Run graphics test results quickly "error", then in a dead android image, then saying "erasing" and then saying "installing system update" but it doesn't fix the problem
Questions
- Does anyone know what the actual issue is that the device stops?
- Is there any newer OTA for shamu I could use? Is there maybe a final Android N for shamu somewhere available?
- Given the above situation, is there any chance I can access files on my device?
- Any other option I have, except factory reset (and wiping my data)?
I really put a lot of effort in it (and learned a lot) but I only got that far. I wished there are other options?
Thanks in advance for helping,
Stefan

I "reposted" the question to the forum here. Not sure how to move delete it in the the other forum. Sorry.

Mod Edit
Duplicate post
Thread Closed.
jackeagle
Forum Moderator

Nexus 7 (2013) multiple "Unfortunately..." after motherboard swap / image reflash

Nexus 7 (2013) multiple "Unfortunately..." after motherboard swap / image reflash
Hello all - I'm hoping someone can provide some assistance / suggestions...
A few months ago, my son's tablet went for a quick swim (dropped into the toilet ) Unfortunately, I wasn't at home (on a business trip) to immediately power it down and pull the battery. I'm not sure if it was turned off / back on / off again or what, but it was quickly put into a bag of rice to try and minimize the damage until I came home to review.
Inspection of the tablet confirmed it was dead - no response to either buttons or plugging in the charger. Found the ifixit how-to, and after obtaining some tools I popped the back case off to see what was what. Disassembly revealed an nice scorch mark on the underside of the motherboard, right where the main chip was, so it was pretty obvious what the failure was.
I decided that I'd give repairing it a go, and bought a replacement motherboard from ebay a couple of weeks ago. Swapping the board over was no problem, and I was happy to see that after letting it charge fully, it booted up and went into the 'Setup' routine.
However, this is where the problems started - as it was working through the setup (language / wifi / copy apps/data from other device etc) there were numerous "Unfortunately, xxx has stopped" messages. I kept 'ok'ing them, and the tablet made it to the point where it was starting to download the saved apps etc from the playstore before it rebooted.
When it powered back up, the 'Unfortunately" pop ups were worse than before, so after doing some searching I decided to try flash a factory image (razor-mob30x) , as per the link on the Nexus help forum. The flash seemed to work (no errors in fastboot mode, laptop was communicating with the tablet) but the pop ups were still as plentiful as before. I have tried the flash multiple times, even going back to lollipop, but with no real improvement. The last thing I tried tonight was to start the recommended flash process from step 1, re-downloading and installing all the required programs, but without success.
I'm not sure what else to try, as the factory image reflash should erase all the installed files.
My only thought is maybe trying to sideload the correct gapps / play services / etc in fastboot mode?
Any suggestions appreciated,
Roadie73

Update..
So, because I'm a glutton for punishment, I've been playing with the N7 again this evening...
Grabbed my old laptop, and went through the complete routine again - loading adb and fastboot onto the laptop, then the N7 factory image - and ended up with basically the same result - the tablet will look like the files have taken, but almost immediately after restarting and loading to the blue set up screen, the "Unfortunately..." messages start again.
I was able to get all the way through the set up, and have it copy and start to download the files off the tablet I was using previously, but the pop ups persisted, and it gets to a point where it is looking for a google play services update, and the process comes to a screeching halt.
I found another 'How To" and tried sideloading a rescue OTA update, which might be a little better, but the messages persist....
I'm almost wondering if it's worth reflashing the factory image back to whatever the N7 shipped with, and then trying updates from there, as it seems to be the play services / store / apps that is the issue.
The other strange thing is that when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Still trying...

Roadie73 said:
it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Click to expand...
Click to collapse
Interesting, please post the output of the 2 commands...
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run:
fastboot getvar all
fastboot oem gpt-info​
If you can, also attach logs...
download get-logs.zip to a FAT32 flash drive
connect the flash drive to your N7 with OTG adapter
download TWRP to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run: fastboot boot twrp-3.1.0-0-flo.img
when TWRP is up, go: install/select-storage/usb-otg/get-logs.zip/flash
logs.tgz will be saved on the flash drive
attach logs.tgz here
It's simpler if you have TWRP already installed. You can also use get-logs.zip from internal storage.

Hi k23m,
I ran the two commands you suggested (getvar all and oem gpt-info) , and grabbed the outputs of both as screen captures and dumped them into a ppt file (which I can't seem to attach - there is no 'manage attachments' option I can see )
I installed TWRP on the N7, but was unsuccessful in creating / grabbing logs.tgz file - which might have to do with the USB connector on the N7 being flaky - if the otg cable wasn't held in exactly the right way it wouldn't recognize the flash drive.
If I can figure out how to add the attachment I will in a separate post, or I can always email it to you direct.
Thanks,
Roadie

Hello k23m,
Finally ad a couple of minutes to play with the N7 again - copied the get-logs file over to the tablet (that was behaving for once).
Unfortunately, despite copying the file off the N7 onto the laptop, a *.tgz file can't be attached. So I did the next best thing and copied the screen caps into an excel doc, which is one of the valid extension.
Please see the attached file - I had a look at the output, but it means nothing to me...
Thanks,
Roadie

added 'logs.tgz' file run previously - please rename from *.xls
Hopefully it might provide some insights into why the N7 is mis-behaving.
Thanks,
Roadie

The logs are OK.
Roadie73 said:
when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013
Click to expand...
Click to collapse
If you have followed the factory image installation instructions and you see the error messages before setup's initial sign in, then your hardware is faulty.
If it happens after sign in, then perhaps Google has corrupt account data ("it shows as a Nexus 7 2012"). Try a new account. Try a custom ROM with Gapps.

Ok, thanks.
Just tried a factory reflash as per the link, but fastbooted the individual files (boot / recovery / system / userdata / cache) separately as from what I have read using the 'flash-all' batch file has intermittent results.
Looked like the files loaded in successfully, but I'm still getting the "Unfortunately.." messages popping up on the initial sign in screen for set-up
So, based on k23m's assessment above, it sounds like it's a hardware problem
As far as I know the touch screen is ok (it's responsive in all areas, as far as I can tell). The daughterboard is not the original (that took a swim) - it was swapped out of another N7 when the charging port started to spread (and that tablet was issue free) So it looks as if the issue is in the replacement motherboard.
I guess I could try removing and reinstalling it, on the off chance it's a flaky connection somewhere.
I will also check to see if there was any sort of gaurentee / replacement policy for the replacement mobo, but it sounds like I'm out of luck
Any other suggestions / checks I can perform to see if I can narrow down where the issue lies?
Thank you,
Roadie

Corrupted Device after downgrade attempt from 9.1 to 8.1

Hi, first time posting so I hope this is the right place to request help on this.
My device had some issues before attempting the downgrade, mainly it wasn't charging with the included cable/charger tried factory reset I could charge it with a Type A - Type C cable but super slowly, even from another charger (with the device still locked) 2 times but the issue wasn't solved. Figured it could be an issue with Android Pie saw reports of people with the same issue (and even the same solution - Type A cabe) so I decided the try a downgrade.
My bootloader version initially was TMZ20k, when I saw google's factory images page saying the unlock_critical was only needed for versions TMZ20a or bellow I skipped that version (didn't know there was downgrade protection for Pie), after many attempts I finally managed to get to the developer options to enable the OEM unlocking so then:
fastboot flashing unlock
downloaded the latest 8.1 (July) and unzipped the contents of the folder within into /platform-tools
flash-all
Problem is, don't know if this happened the first time also or just the last time I tried this (already tried multiple times at this point) but when it starts flashing the vendor.img the following occurs:
'Sending vendor_b' - 'FAILED (Write to device failed in SendBuffer() (unknown error))'
All other steps work normally
I also tried:
Flashing each image individually
Using another 8.1 Image
Use Recovery from bootloader after flashing the image
I could not:
Use another cable or port: Could only get my computer to recognize the device using the original cable and the single type C port I have on my computer
The result is the Corrupted Device screen is prompted and then it gets stuck on the G logo screen.
What should I try? Did I do anything wrong?
The only thing I can think of at this point would perhaps try to run this from another computer. Would that be recommended/required?
Sorry for the long post, just wanted to be as descriptive as I can

gfernandes92 said:
Hi, first time posting so I hope this is the right place to request help on this....
What should I try? Did I do anything wrong? The only thing I can think of at this point would perhaps try to run this from another computer. Would that be recommended/required?
Sorry for the long post, just wanted to be as descriptive as I can
Click to expand...
Click to collapse
I'll try to address a few points. One is that a downgrade is not going to solve your problem and Pie doesn't have a known charging problem. Some (read: a small number) have developed issues with the USB-C port. The issue manifests itself as not recognizing cables, transmission errors, or charging issues. Sometimes it just needs to be cleaned, and other times the port is bad. Inspect the port and clean if required. Second, you should have used BOTH unlock commands separately before starting. This forum is riddled with issues of half-unlocked phones. Everyone has a reason they don't want to unlock critical, but it is always that group that have issues. I suggest you try to get the phone fully unlocked and then flash the latest full (Pie) Google image and continue your diagnosis. Be very careful cleaning the port and inspect your cables. If you cannot flash completely through the full image with zero errors, yes you should try another computer. Lastly confirm your PC is using the latest (28.0.1 (September 2018) fastboot/adb binaries. If after wiping and installing a full image successfully you still have the original problem, it may end up being a hardware issue with the port which is repairable. Best of luck.

v12xke said:
I'll try to address a few points. One is that a downgrade is not going to solve your problem and Pie doesn't have a known charging problem. Some (read: a small number) have developed issues with the USB-C port. The issue manifests itself as not recognizing cables, transmission errors, or charging issues. Sometimes it just needs to be cleaned, and other times the port is bad. Inspect the port and clean if required. Second, you should have used BOTH unlock commands separately before starting. This forum is riddled with issues of half-unlocked phones. Everyone has a reason they don't want to unlock critical, but it is always that group that have issues. I suggest you try to get the phone fully unlocked and then flash the latest full (Pie) Google image and continue your diagnosis. Be very careful cleaning the port and inspect your cables. If you cannot flash completely through the full image with zero errors, yes you should try another computer. Lastly confirm your PC is using the latest (28.0.1 (September 2018) fastboot/adb binaries. If after wiping and installing a full image successfully you still have the original problem, it may end up being a hardware issue with the port which is repairable. Best of luck.
Click to expand...
Click to collapse
This post is golden!!

use Deuces script and flash the required factory image, solve most of the issues

[Help] Stock S9 stuck in bootloop

SOLVED - Update below.
Hey guys,
I have an S9 (SM-G960F) which appears to have auto-updated during the night and as a result will now not boot. I am making an assumption it was an update of some sort as when I checked the time on it at 1am it was fine, when I woke around 8.30am the phone was off and when powering it on I ran into the issue. To summarise, I power the device on, get the Samsung loading screen, then the black swipe pattern screen to decrypt the phone, followed by the padlock unlocking loading screen, then the phone reboots. Sometimes however, the device gets past the padlock loading screen and says it is optimising apps, which is then followed by a reboot, briefly says it is installing system update before landing me at the Android Recovery screen.
What I've tried:
- Soft reset
- Booting in safe mode (same result as booting normally)
- Clearing cache partition
- Clearing app data
- Lacking storage booting (the device was quite low on storage last time I checked)
Some other (maybe) useful info:
I haven't updated the phone for months, could be why it did an auto update.
I'm on EE in the UK but IIRC the phone is not locked to EE.
Android Recovery has the following info when I load into it
Code:
samsung/starltexx/starlte
9/PPR1.180610.011/G960FXXU2CSB9
(options to try again, erase app data, power off, view rescue log)
#Reboot Recovery Cause is [system_server:12259 RecoverySystemRescueParty]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
Viewing the rescue log presents me with a stacktrace , the top of which is
Code:
*** FATAL EXCEPTION IN SYSTEM PROCESS: main
java.lang.RuntimeException: Failed to create service com.android.server.job.JobSchedulerService: service constructor threw an exception
(followed by the rest of the stacktrace I can get a picture of if necessary)
My goal here is to recover the photos on the internal storage as they don't appear to be backed up to Google photos, nor Samsung's alternative - which is particularly painful cause I'm the one usually preaching backups.
Is there anyway to recover the OS to retrieve data, or pull the data off the device without wiping it? I'm open to any suggestions on how to do this, the main goal here is saving my photos, hence why I have avoided a factory reset from the Android Recovery menu.
Hope I've been clear enough, but let me know if I need to clarify anything. I would greatly appreciate any suggestions!
Thanks,
Matt

Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt

Which version of Odin did you use?

majormatt said:
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Click to expand...
Click to collapse
I would really appreciate it if you post a YouTube tutorial on how to fix this. Because we are facing the same problem right now but I have no idea what solution you prescribed. Thank you and God bless.