Related
I just recently acquired a HTC Touch Dual and really like it but am having a few issues with it. First, I get tskschedule, repllog, and clocknot notification errors. I've noticed a few threads regarding this issue but haven't yet found a solution so any suggestions would be most appreciated. The second problem is that my battery indicator doesn't seem to be working properly, it stays at 90% and doesn't change regardless of how long I use it for. This caused the phone to die on me in the middle of a conversation. So if anyone has an idea on how to fix either of these two issues, that'd be great.
Hard-Reset or flash another ROM (for example Original HTC Shipped 6.1 or one of the custom ROMs which where offered here in your language).
I bought the device used and unlocked off of eBay, will hard-resetting it keep it unlocked? Also, I'm very much a noob to phones and don't have any clue about flashing roms, what are they exactly and how do I do it? Thanks for the quick reply.
Hard-reset = Original state of the installed ROM
For flashing there are lots of tutorials here (I don't know which is your native language, so I can't post links to some ROMs - I have nearly tested all of them ;-)). Best you try flashing first original HTC ROM. Very easy (you said it's already unlocked), just connect the phone to pc via USB and start the flashingtool. After flashing hard-reset to be sure that all settings and files were restored to original state. That's all.
Don't forget to backup contacts, emails and so on before hard-resetting/flashing! Files on storage-card will be ignored, you don't need to backup them!
im from the us, so my native language is english. do you have any suggestions or links for the better flashing tools? after flashing to my original rom, my phone will stay unlocked right? because it doesn't it'll create more problems for me then i am having right now. thanks again
My native lang is German, so don't worry about my English ;-)
Unlocking is easy, just use hardspl and uspl. I have unlocked my phone only once a time and never had problems after or while flashing (done 15 times or more!). Once I killed my phone with a bad Rom (endless boot-sequence), but you can go into bootloader by pressing "Power-Button + Camera-Button + Reset", so you're always able to flash another Rom and/or could unlock the phone again. Nevertheless I can give no guarantee.
First you could try to download from HTC website. You need the serial-no. which can be found after removing the battery. If you have a look at niki upgrading/flashing forum you'll find also links to the original ROMs.
You can also try the latest WWE/english ROMs offered in this forum at the first 1-2 pages. I tried Gullum's TF3D and Lilly's ROM, both are great and have Manilla included (if you don't like it, the old HTC Home plugin is included in HTC Rom), but I prefer german ROMs. The Niki Project Rom didn't work for me (bugs in Outlook and Office Mobile).
All Roms include the flashing tool, it's really easy to use.
thanks buddy, i'll give it a shot and let you know how it goes
do i have to use a sspl before a hardspl? i have a neon and havent yet found a sspl for it yet. how dangerous is it to use a hardspl? im very new at this so thats why i have so many questions. thanks again
For me everything worked without problems. So I can't say how "dangerous" it is. Most users don't have any problems. To be sure get latest ROM from HTC or your provider, so if any problems occur, you're able to flash the original ROM back via bootloader.
As far as I know you only need to hardspl, but I did sspl first and then hardspl.
I think we need to clear up a couple of things and kind of slow down before you brick your phone
Generally, there are 3 types of locking for these phones.
First, there is SIM locking that everyone is familiar with and locks your phone for use on only one network.
Secondly, we have CID locking - which locks the software\firmware on your phone to that supplied by a particular carrier (for example, if your phone is CID locked to AT&T, you can only flash a ROM from AT&T and not HTC or a custom ROM).
Lastly, and least to be concerned about, is Application locking. I've not heard of any of the touch duals being app locked so we can safely ignore this.
I'm guessing that you meant your phone is sim unlocked in which case, I'm 99.9% sure that none of the ROMs that you can flash will change that.
If yours still has the carrier ROM on it, it is most likely still CID locked so you need to get that off first.
Once that's done, you need to HARD SPL installed (the SPL is the bootloader bit, SSPL is just a "software" version of it that can run but doesn't install anything) If you put HARD SPL on, then it is almost impossible to brick and ruin your phone - but until that is on, don't try flashing custom ROMs or radios etc. as you're asking for trouble.
Also, until you have HARD SPL on, be careful about flashing anything - make sure you don't run apps while it's going and shutdown anything that could interfere. Take basic precautions and you should be fine.
But TBH, if you're new to these phones anyway, and the ROM is right for your carrier, I'd leave it as standard - I personally always find something wrong with the cooked ROMs - missing T9 dictionaries \ SMS not working \ MMS not working \ some other detail that was missed, and I always end up going back to either my stock ROM (T-Mob UK WM6) or the HTC Update (WM6.1) but I don't notice the difference if I'm honest.
People say that whatever ROM they have on is the fastest they've ever tried but in my experience (and I'm on my fifth or sixth generation of WM phone) the difference is marginal at best and certainly not worth the trade off of broken features and multiple reboots.
So, my advice is, by all means, have a mess with other ROMs but be careful, get HARD SPL and make sure you have a ROM to go back to.
Oh, and try a hard reset (or Clear Storage from control panel) after syncing everything up to try and fix your current problems
Cheers,
Smiffy.
i was thinking about trying a hard reset prior to flashing a rom. i cant download a rom from htc and am unable to find one from att (my carrier) so as of now, i dont have a rom to fall back on. i bought the phone used and unlocked, so will a hard reset keep it that way (basically, what will a hard reset do exactly)? i am referring to a sim-unlocked state. the centennial wireless splash screen still shows up so im guessing it is still cid locked? do i need to unlock the cid before hard-resetting it? thanks for the help
The hard reset basically wipes and user-related info and returns it to a factory-fresh state - if one ever starts playing up, this is what should be done before you flash a new ROM, and yes, it will still be SIM-unlocked afterwards. It will alos go through the setup routine again as if you just took it out of the box
There are other places to get the HTC rom from - it's actually quite a good one too as it will set up all the data\MMS settings for your carrier too.
If you're not worried about any warranty, then it's good as a fallback though search on here and see what results other people have with AT&T.
CID unlocking is fairly easy if I remember - been a while since I did it and I have a different model than you. Just make sure anything you use is listed as OK for a neon
HTH,
Smiffy.
so i did a hard reset, and there hasn't been a change in the battery issues. so maybe the battery is faulty? would flashing a different rom help or should i just get a new one? thanks again
If the ROM is at fault, then flashing a better ROM would help, yes. If the battery the faulty, then even a ROM that is much more energy efficient would help little, only delaying the inevitable.
how would i know if the the problem is from the rom or the battery? other than trying a new battery that is
aight, so i got the hardspl for the neon. will that cid unlock my phone cause i cant find a cid unlocker for the neon 300. what would happen if i didn't cid unlock my phone before flashing a new rom?
Nothing would happen. Either it refuses to flash on beforehand, or it'd stop at about 1% from the start not touching your existing rom.
Hardspl is indeed the way to cid unlock your phone, as far as I know.
Please Help!
new problem here, my new battery just arrived a couple of days ago. i inserted it in my phone then let it charge before turning it on. my previous problem was that with old battery, the amber light would start blinking but not remain steady and tell me that my battery was very low then eventually turn off. the new battery's amber light was solid and i left it plugged in for 10ish hours because the light never turned green. i finally turned it on, but eventually the same problem arose. i hard-spled it then flashed a new rom which helped for a little while. the light stayed steady and the battery status rose up until 100%, but the light stayed amber. then if there was any shift in pressure on the chord, the light would start blinking and the battery would immediately read 5%. now the new battery isn't any different from the old one. does anyone have a suggestion? it would be greatly appreciated.
Anybody? Help? At the very least would anyone have suggestions of good repair sites? Thanks in advance
Hello,
few days ago i made a shot and flashed Argentinian SBF to my German motorola. Now i have very bad signal and my phone loosing signal very often, even if it's full (yup sometimes it's full but it's rare to see it) so i have around 70% signal, and after few seconds its lost. I don't know how can i change it or flash something different. I tried a lot of sbf's after argentinian, none of them was succesful, even flashing different kernels with backups. Always something - very ofter bootloader errors.
Now i want to ask if there is ANY way to bring back my phone function to normal? i tried a lot of tricks, hacks and none of them was succesful - like modify .prop files. I saw that argentinian sbf updates bootmgr. But is there a chance to revert those changes? For example to flash from recovery boot.img from froyo backup or any other freak changes?
Well off the topic i can say that german XT610 is unbrickable. I saw a lot of posts that people bricked they devices (well maybe with verizon model is different) but i never experienced that. If bootloader launches - device is not bricked.
Up. Bootmgr can be reverted using JTAG or something like that?
Hi all.
I've asked this question in numerous threads so, to be fair to all the others whose questions I'm getting in the way of, I thought I'd post it here and wait with baited breath for a potential solution.
I very recently bought an XT1684 (3GB/32GB) UK G5 Plus. I installed all the official OTAs and got myself up to firmware version NPNS25.137-33-11. All was well, amazing battery life, but needed root for some apps. The steps I followed are roughly as follows:
1. Unlocked bootloader: I did this the usual way, got my code, chucked it into fastboot etc voila, job done.
2. BOOTED Twrp: I did this so I could attempt to back everything up without modifying, for purpose of returning to stock. It didn't work, I could not back anything up nor could I install magisk or a custom kernel. My Twrp would not read the internal storage and said something about formatting data. I ended up formatting data, which actually formatted the whole damn thing, losing my stock ROM completely.
3. FLASHED Twrp: By this point I had to, as I had limited access to the internet outside of my phone so put a lineage ROM on my phone and some gapps and flashed it.
4. Installed magisk 15.3
5. Installed Alize kernel: I did this because I was looking for improved battery life over the lineageos kernel. It hasn't been better.
So that's where I am. I have two main reasons I need to return to stock:
1. The battery life was better on my stock firmware.
2. Whenever I use lineage, I find my signal not to be as strong, and it seems to randomly lose all signal for a few seconds several times an hour, usually affecting my data more than voice calls. This is absolutely not something that happened on stock. I dunno if it's related to baseband or something, but it happens and I don't like it.
My main issue is I have seen several retUS versions of the firmware above, and lots about many other XT16xx models but nothing about my XT1684 and no fastboot images for retGB. I'm comfortable flashing pretty much anything via Twrp as I have a full backup of all partitions including OEM, system image etc but these were taken after installing lineage. I'm just totally not comfortable fastboot flashing anything except the exact correct firmware, as I've had this phone literally a week.
If anyone can help me locate the right firmware, or advise me how I could possibly return totally to stock, that would be amazing. I can provide any logs or other information required, but may need walking through more obscure commands as I am only technically proficient enough to do a basic fastboot flash, Twrp, etc.
Many thanks for reading and my apologies to all of those whose threads I've muscled in on up to this point.
Filmware is here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
And there is a tool that automates flashing in the development section here..
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
Firmware - https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
How to flash - https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
?hope it helps.
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it.
Could someone confirm that these are safe to flash for me? Thanks for the replies, though.
Your filmware is there yes? Having said that mine is a xt1685 the same filmware number as yours but mine is euret dual SIM. Sold by Amazon UK
My confusion is that I thought they were for US models.
Well US version has no NFC but had a compass.
Has yours?
Mine has NFC and no compass lol!
darkglobe87 said:
Mine has NFC and no compass lol!
Click to expand...
Click to collapse
Seems to be typical for EU G5+ devices, NFC but no compass.
The retail firmwares don't appear to have region restrictions, hence no labelling for retEU/retGB/retUS etc. However, as you may have noticed, flashing the incorrect build for your region causes all sorts of headaches, including loss of SIM network.
That being said, you know what firmware you need (NPNS25.137-33-11) and that particular firmware was only released for EU/UK devices to the best of my knowledge. India/Brazil, US and other territories had different firmware builds released.
So, you should be okay with flashing that particular firmware - but please verify you have the correct firmware downloaded and the correct flashing instructions, and take your time in flashing.
Also, if you choose to re-lock your bootloader, re-locking your bootloader will unfortunately not restore your warranty with Motorola (which is 2 years now for EU/UK users at least). However, UK consumer laws may cover you in the eventuality of hardware repairs, just be careful. Also, re-locking will erase your device and requires firmware of the same build or newer than what is currently on your device.
Good luck whatever you decide.
I have the UK version and have gone back to stock a few times, I used this thread, and the linked firmware is the same as UK one. The guide is for bootloader locking, but ignore that part if you only wish to return to stock.
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
Hope someone can help with some ideas, im really lost how to fix this now.
I have my S4 on the latest stock 5.0.1 Lollipop which is rooted with CFAutoRoot.
I9505XXUHQK1 (edit: Samsung international update 2017 - only installed in a hope to cure the problem in Feb 2018 but made no difference)
Since about last October I have a problem booting about once every 6 weeks, basically it runs great then something starts acting up like you get with all phone, so I do a restart to get things running smoothly again.
It goes through the splash screen no problem, I get the music and it stats booting with the colourful samsung logo with fireworks behind but it just sticks there forever and won't finish a boot, I notice when I get a good boot there is a vibration as it finishes, this vibration never comes when it fails.
The first time, I put changed the recovery to (twrp-3.2.1-0-jfltexx) thinking next time it would be easy wipe the cache and dalvik/art and get it booted, using twrp to clear the cache and dalvik/art did not help so I was forced to reset it again.
Next I noted there was an unexpected update to the S4 from Samsung, I thought applying this update might help things so went ahead and installed it giving my phone all the latest security updates etc, but again the same happened a few weeks later.
Here post 979 (Bootloader, Modem & kernel): https://forum.xda-developers.com/ga...rom-untouched-stock-rom-t3419034/post75164948
I then decided after another painful reset I would keep a weekly Nandroid backup so I could at least get it up and running again quickly.
Last week it failed again, this time I the data icon light would not turn off without clicking through and unticking the checkbox, even then with the data off the green light was on in notification, so a restart and as expected a freeze....
This time I had my Nandroid backup and I had a fresh(ish) Titanium Backup and has backed up my texts and call lists via Samsung so after an hour it was all backup and normal and this time only lost a few days texts and call logs.
Really i'm in a situation where all I can be is spend my life being prepared to restore my phone with good backups but completely unable to prevent it.
My only thought is there must be an app that is playing up during boot, but how do I identify it, the symptoms are never the same (except the boot freeze), no apps are showing high battery use and my battery usage is great, I have hardly used today but it's been off charge since 9am (its now 3.20pm) with 82% left and estimating 27 hours more usage.
Does anyone have any ideas what could be causing this or any tips on how to identify the problem, I would rather spend time fixing it that spend my time preparing for an inevitable recovery.
Thanks in advance for any thoughts.
Edit: Just for info, I regularly reboot it to do a Nandroid backup and it restarts just fine, just fails about once every 6 weeks or so.
I9505XXUHQK1 is meant for branded Greek and German networks only, if your device is unlocked international you will experience problems, especially at boot as it looks to load the branded stuff. Eventually it will give up and just boot.
Although this last update looks all sexy, it's almost identical to XXUHKP2 just a newer security patch and a few minor changes, really not worth the hassle of getting it (or the problems your having).
I believe the latest "MachineX" ROM is built off this firmware which has the branding stuff removed and also links to the correct XXUHQK1 boot loader. Have a look in the ROM section.
cooltt said:
I9505XXUHQK1 is meant for branded Greek and German networks only, if your device is unlocked international you will experience problems, especially at boot as it looks to load the branded stuff. Eventually it will give up and just boot.
Although this last update looks all sexy, it's almost identical to XXUHKP2 just a newer security patch and a few minor changes, really not worth the hassle of getting it (or the problems your having).
I believe the latest "MachineX" ROM is built off this firmware which has the branding stuff removed and also links to the correct XXUHQK1 boot loader. Have a look in the ROM section.
Click to expand...
Click to collapse
Thank you but the I9505XXUHQK1 update is not the issue, the problems started months before this update
I can easily revert this but it is really not the cause of the issues.
are you sure about I9505XXUHQK1? XXU is international unbranded is it not?
XXU= international
H=5.0.1
Q=2017
K=November
1=version 1
Refference:
What do the letter-codes mean?
Example: XXUHPA1 for the I9505
XXU: is the region, in this case international.
H: is the android version, in this case ‘5.0.1’
P: is the year in alphabetical order, P is the 16th letter, thus 2016
A: is the month, again in alphabetical order, thus it’s January.
1: is the revision. In this case 1st
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Also:
Samsung bootloader /modem /firmware NAMING:
GT-I9505XXU#(version)
Example: GT-I9505XXUCNE4
GT-I9505 = phone model
XXU = baseband cellular network
XXU is Global and valid almost everywhere, any country regardless of carrier
C = baseband build version
NE4 = version
Version translated
N = year = 2014 (14th letter of alphabet)
E = month of year (May in this case, 5th letter of the alphabet)
4 = build # of that month ( they start 1-9, then letters, A=10,...)
Example:
NE4 = 2014, May, Build 4
NE5 = 2014, May, Build 5
OH2 = 2015, Aug, Build 2
Click to expand...
Click to collapse
kudos1uk said:
Thank you but the I9505XXUHQK1 update is not the issue, the problems started months before this update
I can easily revert this but it is really not the cause of the issues.
are you sure about I9505XXUHQK1? XXU is international unbranded is it not?
XXU= international
H=5.0.1
Q=2017
K=November
1=version 1
Refference:
https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Click to expand...
Click to collapse
OK i'll try explain
XXU can mean international as in 2 different branded networks in different countries or regions, understand? Also In with that firmware are the csc codes for the country you;re in, detected off the SIM at start up, sometimes the correct csc codes are loaded sometimes they're not and then you get stuck on boot. This why you should only flash firmware which is device AND region specific.
Anyway, flash XXUHKP2, run it for a few weeks with frequent restarts, if no boot loops then you have your answer.
cooltt said:
OK i'll try explain
Anyway, flash XXUHKP2, run it for a few weeks with frequent restarts, if no boot loops then you have your answer.
Click to expand...
Click to collapse
Thanks but it wont make any difference, I had that for months and was on the phone when this all started, I did several resets and an odin reflash of XXUHKP2 but still had the problem, I only flashed XXUHQK1 a month ago in a last ditch hope it might cure the issue but I have had one boot problem since I installed it.
Both XXUHKP2 & XXUHQK1 behave exactly the same, they work for weeks with no issue, I can reboot as many times as I like without a problem then all of a sudden something will start playing up on the phone (start running slow or unable to turn off data etc) and the restart freezes.
cooltt said:
OK i'll try explain
XXU can mean international as in 2 different branded networks in different countries or regions, understand?
Click to expand...
Click to collapse
You don't need to explain anything XXUHKP2 and XXUHQK1 are both international and will work in almost any country that's what XXU means, not a couple of regions or countries, I don't think Samsung have this classification.
More information, had problems overnight last night.
During the night I was woken by the phone restarting, I looked at it and it was in the middle of preparing all my apps, this normally only happens after a wipe, I left the phone and went to sleep.
I woke this morning to find the phone restarted and asking for my sim pin, my happiness was soon gone as it then asked my which launcher to use and only listed the two Touchwiz, Google Now which I normally use wa not listed. I chose Touchwiz full but after a few second the phone went into a soft reboot loop (not asking for a sim pin).
I did my last nandroid 4 days ago, so I set that going but it failed right at the end with error 255, next I tried an old nandroid I have used twice before but it failed in the same way. Next I did a file system check and restore and reformat (saves personal files), still error 255. Next I reformatted the data partition as a full reformat (this TWRP method deletes personal files) and finally the latest nandroid ran without problems and I'm up and running.
There must have been something wrong with my internal personal files which TWRP was trying to preserve. I actually keep very little on my internal as everything is stored on my external sd.
All this is making me start to think my internal storage may be beginning to fail, on the other hand TWRP check and repair did not find any problems, still at a complete loss what the problem is and every time the issue is slightly different but always points at data corruption causing the bootloop.
First of all, forgive me for being cognitively impaired when it comes to things like this. I work in marketing and can't code or follow instructions very well.
Here's the deal:
I made the mistake of buying a Chinese Nokia 6 way back, and now I want to flash it with an international ROM before giving it to my niece. Which international ROM it gets doesn't really matter so long as it has Gapps. Since my niece is three years old, she won't care if the phone has Nougat, Oreo, or Pie as she's likely to be more interested in eating those pastries rather than having one as the firmware on her freebie phone.
First of all, I just updated to Android 9 before I began working on this little project. That might have been my first mistake.
Anyway.
I started by following this guide. I wasn't able to get OST LA to work so I gave up.
Then I started following this guide, as it seemed to involve less work.
I downloaded all the relevant files;
renamed them;
put them on my SD card;
went into recovery mode;
installed the update
rebooted the phone and;
installed the firmware.zip
However, after the installation, the phone never goes further than the Nokia-logo. I can reboot all I want, but it's stuck. I can't even get into recovery anymore. I believe this is a bootloop? The main issue here is that I am completely locked out of my phone, and that is really annoying.
Any tips or ideas on how to get away from this unpleasant conundrum would be greatly appreciated.
Ok, an update.
I was able to find a way to access the damn recovery menu after following the steps proposed by viennazar in this thread.
Similarly, I did a wipe as per his instructions, and rebooted the phone after that. Lo and behold, my phone was able to move past the Nokia-logo, and booted up as a TA-1003!
Now, my main issue is that I am unable to move past the initial setup as the phone is checking for updates from Google's servers. That means I am fresh out of luck since I have the great misfortune of residing in the PRC.
That's an entirely different issue though...