Just FYI, HTC released a couple of hotfixes for the Tilt 2 and the Pure
http://www.htc.com/us/support/tilt-2-att/downloads/
denco7 said:
Just FYI, HTC released a couple of hotfixes for the Tilt 2 and the Pure
http://www.htc.com/us/support/tilt-2-att/downloads/
Click to expand...
Click to collapse
Sweet, thanks for the heads-up!
oh excellent! they fixed my two issues i have with it.
Sorry for this n00b-ish question, but...
I just see the 3 PDF files from the 2nd of Oct, '09. What am I doing wrong?
Thanks!
~Eric
eknutson said:
Sorry for this n00b-ish question, but...
I just see the 3 PDF files from the 2nd of Oct, '09. What am I doing wrong?
Thanks!
~Eric
Click to expand...
Click to collapse
I had the same problem 'til I flushed my browser cache and tried again. refreshing the page didn't do it for me, I had to delete my browsing history and then click the link again.
HTH
Mike
Bingo! Thanks =)
This is NOT a ROM update and you will not lose your data. Also, these files will survive a Hard Reset so they need only to be installed once.
Click to expand...
Click to collapse
i wonder what it changes to survive the hard reset.
The Jack of Clubs said:
i wonder what it changes to survive the hard reset.
Click to expand...
Click to collapse
It actually runs kind of like a ROM update. It resets the phone then installs the hotfixes before at the AT&T World Phone splash screen with the ROM and Radio info before WM loads. Interestingly the Radio says "None" on that screen when the update program is running.
does the SMS fix helps improving the sense 2.5 SMS client running on the Tilt2?
if you flash a new rom you need to do the fixes again right? any cabs yet?
Hmmm, I wonder if this is utilizing the vastly underused Windows Mobile Image Update system. It sure sounds like it, but I can't test since I'm not on a stock ROM.
EDIT: It seems it is using Image Update! I extracted the installer and found two .cab.pku files. According to Da_G, this is what they do:
Update contains a binary delta between a package already on the device, and the updated version of that package. In this manner the limited space is conserved (i.e. if a package change was a simple registry entry - no need to replace the 5mb of .dll and .exe in that package, just alter the .rgu with the new data. These packages are also referred to as "Delta" packages. The concept is similar to the unix implementation of Diff/Patch. The file extension is .cab.pku
Click to expand...
Click to collapse
EDIT2: I've extracted both .cab.pku files, and one gave me a single .dsm, while the other gave me a .dsm, a DLL relating to EZinput, and a .rgu file containing registry entries. Not very useful information, but still nice to see that AT&T is taking the initiative to use this underused Windows Mobile feature.
Question is how to get these updates installed onto a ROM other than the stock one. It seems to do some type of validation before installation, and refuses to install on a ROM other than the stock one.
I suppose chefs will have to cook these fixes in, or someone will need to create a CAB or learn how to mess with the Image Update fixes?
Just as a caution, don't try to apply these updates to a reconstructed ATT Tilt2 ROM (in case you flashed to cooked ROMS and then went back to one that is supposed to be like retail).
The HTC hotfix installation starts as the verification passes, but then at least on my device, it was stuck in a reboot loop. I had to flash to another cooked ROM and then flash back.
It would be interesting if we can find a way to update TouchFlo to the latest release using this method. That way you can update touchFlo while keeping AT&T's stock rom and not have to flash a new one.
jh20001 said:
It would be interesting if we can find a way to update TouchFlo to the latest release using this method. That way you can update touchFlo while keeping AT&T's stock rom and not have to flash a new one.
Click to expand...
Click to collapse
Unfortunately, it's extremely unlikely that will happen with AT&T's stock ROM. Image Updates are signed, and are checked against certs that are cooked into the ROM. This ensures that only the OEM or carrier can release these updates (kinda like how ROMs are signed so only the OEM or carrier can release updates). The Image Updates will refuse to install if the certificates can't verify the update, and there's no way we're going to get AT&T's security certificates. So unless someone gets those, you're out of luck.
I installed the 2 fixes that where on the htc website but now when i go to the start menu i only get a 3 row menu, how do i change it back to a 4 row menu
Okay here's a problem, I installed the SMS fix that was on HTC's website, that went without a hitch, but when I tried to install the inconsistent Caller ID hotfix, it said it was incompatible with my device. I have the stock ATT rom. Anyone else have this issue?
Yep same here...stock AT&T ROM and getting the same error when I try to install the Caller ID HotFix....hopefully they fix it because I have this happen a lot with the CallerID not showing up on my device.
AngelDeath said:
Okay here's a problem, I installed the SMS fix that was on HTC's website, that went without a hitch, but when I tried to install the inconsistent Caller ID hotfix, it said it was incompatible with my device. I have the stock ATT rom. Anyone else have this issue?
Click to expand...
Click to collapse
kizzle07 said:
Yep same here...stock AT&T ROM and getting the same error when I try to install the Caller ID HotFix....hopefully they fix it because I have this happen a lot with the CallerID not showing up on my device.
Click to expand...
Click to collapse
How old are your devices? This fix might be for older devices. I had my original Tilt 2 replaced due to a faulty ROM or radio chip which would boot loop my device before the red version numbers would show on the AT&T logo boot screen. The version numbers on the new Tilt 2 seem to be updated. I would guess if I were to run the updates, I would be in the same boat...
mines less than a month old and the updates ran (att tilt 2)
Related
Hi Folks,
I'm looking for an Original HTC Artemis Bootscreen an how to change it.
The T-Mobile Screen is ugly.
Can Anybody help me?
Thunderhawk36
Thunderhawk36 said:
Hi Folks,
I'm looking for an Original HTC Artemis Bootscreen an how to change it.
The T-Mobile Screen is ugly.
Can Anybody help me?
Thunderhawk36
Click to expand...
Click to collapse
use this file. just copy it in windows dir and soft-reset.
ai_99 said:
use this file. just copy it in windows dir and soft-reset.
Click to expand...
Click to collapse
Sorry, but i'm looking for the screen just before the welcome screen.
The one where the Rom Version is shown.
Thanks
Thunderhawk
Hmm.. how many times do ya actually reset your phone to look at that screen?
MasK said:
Hmm.. how many times do ya actually reset your phone to look at that screen?
Click to expand...
Click to collapse
Not very much times , but the pink T-Mobile Logo is going to nerve me.
Thunderhawk
Thunderhawk36 said:
Not very much times , but the pink T-Mobile Logo is going to nerve me.
Thunderhawk
Click to expand...
Click to collapse
getting on my nerves too.. want a nice bluefish over there... have figured it out?
Yep you need to flash a new rom because as far as I know thats the only way it can be changed since its written at the same time as the ROM. Tom's B&Bv3 has just changed mine from the o2 default to the HTC logo, ask him how he did it but I'm pretty sure you need a new ROM with the logo of your choice embedded.
PS: Don't think you can do the log seperately either but I'm sure a more knowledgable person will be along shortly
markquinton said:
Yep you need to flash a new rom because as far as I know thats the only way it can be changed since its written at the same time as the ROM. Tom's B&Bv3 has just changed mine from the o2 default to the HTC logo, ask him how he did it but I'm pretty sure you need a new ROM with the logo of your choice embedded.
PS: Don't think you can do the log seperately either but I'm sure a more knowledgable person will be along shortly
Click to expand...
Click to collapse
Totally not going for me.. just upgraded to wm6 and the new activesync... maybe that's the reason?
There was a way I heard of using the RUU and replacing a file with the new image you wanted for splash...
"Perhaps you should look at this thread: http://forum.xda-developers.com/viewtopic.php?t=12898.
There is a great program on there for converting pictures to .nb files and also a CAB which, when run, will change the boot images.
This does require putting the splash1.nb and splash2.nb files into the /windows/ directory before running MDA3_bootimage_changer2.CAB,
but if you want to just run a CAB file you can just edit that CAB and place your own created splash1.nb and splash2.nb files
in it with the location set as /windows/ (I tried it with WinCE CAB Manager and this way works as well)."
http://forum.xda-developers.com/showthread.php?t=231632
eppoeh said:
Totally not going for me.. just upgraded to wm6 and the new activesync... maybe that's the reason?
Click to expand...
Click to collapse
It does depend on the rom, B&B v1 & 2 didn't update my boot screen but v3 did so maybe you've got an old version? Are you actually using the B&B rom at all? Not all rom updates change the boot screen, it depends on the chef if they include em in the first place
markquinton said:
It does depend on the rom, B&B v1 & 2 didn't update my boot screen but v3 did so maybe you've got an old version? Are you actually using the B&B rom at all? Not all rom updates change the boot screen, it depends on the chef if they include em in the first place
Click to expand...
Click to collapse
B&B? Did i miss something?
Tried two ways:
1: making the splash1 and splash2
2: tried RUU updating the splash, but fails, think it's the new activesync.
Did i mention that i'm trying this on a htc p3300?
Sorry, B&B is Black & Blue. Its the ROM that Tom Codon has been releasing and updating for the P3300\Artemis\Orbit.
Can be found here: http://forum.xda-developers.com/showthread.php?t=314568
http://www.4shared.com/file/19395089/5971579/Upgrade_HTC_First_Splash.html
dopod/HTC/O2/Orange/T-Mobile Boot Screen
LINK:http://www.aray.cn/?p=1362
zrays said:
[IMAGE]
dopod/HTC/O2/Orange/T-Mobile Boot Screen
LINK:http://www.aray.cn/?p=1362
Click to expand...
Click to collapse
Can somebody please explain the chinese over there? Or give another diescription?
Getting the message: "The image file is corrupted. Please check your Update utility"
eppoeh said:
Getting the message: "The image file is corrupted. Please check your Update utility"
Click to expand...
Click to collapse
CID lock was back? Did a hard reset, unlocked again.. now i can flash again
still no custum bootscreen though
eppoeh said:
CID lock was back? Did a hard reset, unlocked again.. now i can flash again
still no custum bootscreen though
Click to expand...
Click to collapse
still no image... bad splash.nb i guess... seeing nice colored rows now (green to black)
eppoeh said:
still no image... bad splash.nb i guess... seeing nice colored rows now (green to black)
Click to expand...
Click to collapse
WOOT, Finally, i got things running
How i did it:
search the forum for: "3-splash-screens.txt"
do step 2 (might run it in a dos box, to see errors)
search the forum for: "dutty's good NBH tool v1.1"
make the nbh file
flash it into the phone
Dudes Guys
ZRAYS give you the link on post 14.
Just download the right file depending on the logo you want.
Weblink : http://www.aray.cn/?cat=34
zip files are:
P800-logo-dopod.rar
P800-logo-HTC.rar
P800-logo-HTC-new.rar
P800-logo-O2.rar
P800-logo-Orange.rar
P800-logo-T-Mobile.rar
Shall I install it for you then...
Unzip the file go on folder etc... (backup your data, but this upgrade does destroy it) launch ROMUpdateUtility.exe
..wait and smile.
Hi,
For those who don't fear to brick their phone, you can try this custom rom (v11) I've just made
As of now, nothing special with it, I just added Pim Backup, only to test the kitchen, so really no reason to flash it except to confirm whether it works or not. If you want to test it, use the stock rom in this thread (thanks Dark9781) to extract the files into programsdata\LGMOBILEAX folder and then replace phone\GW820-V10d-OCT-27-2009+0.dz with mine (giving it the same name).
Once again, I can't insist enough on the fact that this is experimental for now (for this test rom, I did some rebuild stuff manually, I don't know if it works). Once the tools are proved to be stable, I'll release a updated kitchen for you to play (it might take a week or so to finalize the tools, maybe less).
if u can free up rom and ram i will like to test for u. i hate only having 70% free on reset opera 10 crashes on my phone
Downloading it now. I will post to let you know if it works after I flash it.
Just tried to flash the test rom, but it keeps causing the flasher program to crash before 4%.
damn i was just about to try, dark are you on windows 7 or xp?
ManelScout4Life said:
damn i was just about to try, dark are you on windows 7 or xp?
Click to expand...
Click to collapse
I ran it on windows 7. I'm going to try it on xp now and will post the results.
UPDATE: Crashes on xp too.
Thanks for the test, Dark9781.
When you say it's crashing before 4%, what does that mean exactly ? Does is start to flash anything on your phone ? Are the 1st percents only decidacted to do checks on the file ? Do you have a log file ?
Did you try to download the rom a second time to be sure it was not a bad download ? I'm downloading it myself to check if my upload was good (I remember the 1st Incite tests were failing because of errors on upload, that's why the following tests were 7z, I'll do that on the next tests).
Also did you try to extract the stock v10d with dzdecrypt and pack it with dzcreate using another version name (-vTEST_ROM) (just to be sure it's not due to the name and/or the tools).
Sorry for all these questions but it's just to narrow the search.
spocky12 said:
Thanks for the test, Dark9781.
When you say it's crashing before 4%, what does that mean exactly ? Does is start to flash anything on your phone ? Are the 1st percents only decidacted to do checks on the file ? Do you have a log file ?
Did you try to download the rom a second time to be sure it was not a bad download ? I'm downloading it myself to check if my upload was good (I remember the 1st Incite tests were failing because of errors on upload, that's why the following tests were 7z, I'll do that on the next tests).
Also did you try to extract the stock v10d with dzdecrypt and pack it with dzcreate using another version name (-vTEST_ROM) (just to be sure it's not due to the name and/or the tools).
Sorry for all these questions but it's just to narrow the search.
Click to expand...
Click to collapse
Well, the first 4% is just a check of the rom and it is failing causing the flasher program to crash. I'm going to try and download it again to see if it was the download. I didn't try dzdecrypt to take the stock rom apart and dzcreate to put it back together, but I'll try that too.
I used dzdecrypt and dzcreate to deconstruct and reconstruct the stock rom and it flashed fine. I downloaded the test rom again and again the flasher crashes. The message I get is 3GQCT_SP_STARTER MFC (a bunch of weird symbols) stopped working. The log I posted on the last post was the wrong log. It was for another install that failed on me so please ignore that. The flasher didn't create a log for the flasher crashing.
Ok, after a check, it seems that there was a problem during upload (i've found a string "n: close cache-control" in the middle of the uploaded dz file that was not on my version).
I'm reuploading it right now, let's hope it will be fine this time.
Hoping that that was the only problem. I remember that there was a problem with uploads with the Incite. I've been having some problems with uploads lately. Seems to be happening a lot with mediafire. I'll try it again once it is uploaded.
Upload finished, link in 1st post. I've embedded a md5 in the archive.
2Am here, see you in 8h from now
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Dark9781 said:
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Click to expand...
Click to collapse
EXCELLENT!
GREAT WORK GUYS!
well now i'm anxiously awaiting your step by step and what all is needed. cuz i'm ready to get down and dirty with this..
Dark9781 said:
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Click to expand...
Click to collapse
So what exactly isn't functioning correctly?
New test rom available.
Flashing your V3 now, having trouble flashing with the LG IQ Flasher so I am using my Octopusbox to flash.
Ok, phone boots up, but the screen is all black, and non of the buttons seem to work or there is a really long delay to get them to work. Start Menu doesn't work.
Just flashed test 3 and can confirm that I am getting the same results as test 2.
Test 4 gives the same results as test 2 & 3.
I9000M_JL2_JL2_JL2_JL2_UG_BMC
ro.build.date = 2010.12.21 23:29:56 KST
ro.build.fingerprint = samsung/GT-I9000M/GT-I9000M/GT-I9000M:2.2/FROYO/UGJL2:user/release-keys
http://www.multiupload.com/UTFJCCIP5H
NOTICE: I do not have this device model, nor have I tested the ROM, I'm only telling you where to find it.
anyone know if this is 2.2 or 2.2.1?
BMC? So it's a Bell Mobility Canada ROM?
what is the file SBI.bin
Looks like bell. Lets hope bell users can finally upgrade
Sent from my GT-I9000 using XDA App
Someone said it was already on Kies, but this is what I get:
JK4: "This device's version cannot be upgraded."
tjsooley said:
anyone know if this is 2.2 or 2.2.1?
Click to expand...
Click to collapse
See "fingerprint", it's 2.2.
zorxd said:
BMC? So it's a Bell Mobility Canada ROM?
Click to expand...
Click to collapse
Probably, but I'm not sure.
montrealguy said:
Someone said it was already on Kies, but this is what I get:
JK4: "This device's version cannot be upgraded."
Click to expand...
Click to collapse
look at the updated GUIDE sticky
@Chainfire Awesome, thanks very much for posting!
It's showing up for me on kies, obviously you need to do the registry hack.....i'll give it a go over lunch and let you guys know if there is anything different from JK4.....
zorxd said:
BMC? So it's a Bell Mobility Canada ROM?
Click to expand...
Click to collapse
Yes, BMC means Bell Mobility Canada, check the screen shot. I used the reg hack to spoof JG9 and also used BMC
http://flic.kr/p/93Q4dV
I'm just charging up my battery, I'll give it a shot when it's charged if no one else has.
Already loaded it. It kills the GPS. No GPS lock at all, despite different settings! It detected 1 satellite when normally it detects 10.
montrealguy said:
Already loaded it. It kills the GPS. No GPS lock at all, despite different settings! It detected 1 satellite when normally it detects 10.
Click to expand...
Click to collapse
did you notice anything else different?
mssmison said:
did you notice anything else different?
Click to expand...
Click to collapse
Yes- there are weird force closes sometimes when you restart. If you touch anything on the screen it will go completely blank. Now I wait until everything loads until I touch anything.
Seems less stable than JK4. I'm wondering whether I should revert to JH2 before my SD card crashes.
Just an update: I've tried many different GPS settings on JL2 and the GPS does not work. The best setting I got was with Auto-config + secure socket and even then it found 3 satellites and never locked on for 15 minutes.
Does anyone have another solution? Can I load a GPS kernel from another ROM? JPO had worked perfectly.
for me personally my GPS got ****tier after going from 2.1 i'm running JK4 right now and it's OK but not like it was in 2.1. i'm going to give this a shot and see how my device fairs. my hardware is an august build or earlier so might affect my device differently. not sure, will report back though
LOL....after downloading the binary Kies tries to decrypt it and I get an error that says "crypto error" that's it. so looks like i'll be running JK4 for a while longer now, not that it's a huge issue, This one is apparently only 2.2.....still waiting for the 2.2.1 with the upgraded kernel.
spectre85 said:
LOL....after downloading the binary Kies tries to decrypt it and I get an error that says "crypto error" that's it. so looks like i'll be running JK4 for a while longer now, not that it's a huge issue, This one is apparently only 2.2.....still waiting for the 2.2.1 with the upgraded kernel.
Click to expand...
Click to collapse
The crypto error is a known problem- it just means that the download got interrupted and the files were corrupted. Just keep on trying until it works. The problem is on Samsung's side, not yours.
I got the crypto error, but it worked on the second try.
Be forewarned though- this firmware has problems. See my posts above.
I'd give this a try but I've been flashing so much lately and it's just becoming a pain. I'm currently running JK3 as I've found this to be the best firmware so far. Great battery life, fast w/no lag, good GPS and stable. JH2 was good but didn't have the 2.2 features I wanted. JK4 wasn't very good, unstable at times, random wifi issues and used battery at twice the rate of JK3.
The next ROM I flash will either be the next official if it greats good feedback or CM7/AOSP Gingerbread when it's available.
I'm still curious and looking forward to hearing more reports from users running JL2.
Hello!
I'm using a HTC Desire with a the "Pre-rooted Stock Froyo" ROM by teppic74.
Today I've received an OTA update notification from HTC, which I haven't accepted yet because it would probably break my ROM (by the way, it seems like teppic didn't disable the OTA update notifications in this ROM).
The size of the update is 6.34 MB.
Has anyone else received the OTA update? Anyone knows what's updated?
EDIT: As I've read somewhere, it increases the software version number to 2.29.405.14 from 2.29.405.05
ronaldace said:
Hello!
I'm using a HTC Desire with a the "Pre-rooted Stock Froyo" ROM by teppic74.
Today I've received an OTA update notification from HTC, which I haven't accepted yet because it would probably break my ROM (by the way, it seems like teppic didn't disable the OTA update notifications in this ROM).
The size of the update is 6.34 MB.
Has anyone else received the OTA update? Anyone knows what's updated?
EDIT: As I've read somewhere, it increases the software version number to 2.29.405.14 from 2.29.405.05
Click to expand...
Click to collapse
Increases?
........
Droidzone said:
Increases?
........
Click to expand...
Click to collapse
Yes... increases... version number used to end in 05, with the update it would end in 14.
I don't know what changes in functionality this update is supposed to bring.
Hey i just received the system update actually its called "system enhancement 6.34 MB"
And i ofc clicked on yes, phone restards and then when the "package icon" aka the lets say progress bar starts it just stops and a "!" along with an android maskot appears... cant update, my phone is rooted tho...so, any suggestions or news to this update in general i would appreciate!
ps.i hope you get what i wanted to say
I've been seeing this in other forum when I googled it and looks like no one doesn't have any idea about what the update contains.. yet.
It's nice to see the good old Froyo still getting "enhancements".
Old? Sure. Good? Not by a long shot.
I only had Froyo for a couple of weeks before I rooted and flashed Gingerbread and never used Eclair sooo I'll take your word for it. Haha
If your using a custom RoM, you should never apply OTA updates.
@DroidZone: maybe citing the message just before yours isn't necessary? Just asking.
@shankly1985: you're not helping us who are dealing with this problem as I can pretty much certify we all know that: just read the original post and other comments.
I registered here to ask about this and maybe have an answer. The thing is I am NOT using a custom ROM. I am using the original HTC ROM that came with my Desire 14 months ago. BUT I have rooted the phone in anticipation of installing MIUI – I was desperately looking for a two-way recording of phone calls that never made it into MIUI. So I've installed ClockWorkMod as well as ROM Manager. I too have experienced exactly what @Drizzline describes. System update notification, phone restarting, exclamation icon that seems to be from ClockWorkMod and not from the OS.
My question is: how can I apply the system update, knowing that I have never installed a custom ROM on my device nor made any changes to the factory-installed – and subsequently updated – vendor-provided ROM?
shankly1985 said:
If your using a custom RoM, you should never apply OTA updates.
Click to expand...
Click to collapse
And if you're using a stock ROM, you shouldn't either.
I stupidly updated my Desire and
calendar stopped working properly (events disappeared; luckily, I can see from Google Calendar's web interface that they're all still there)
every now and then an error message appears:
Error: com.htc.bgp has stopped unexpectedly
Click to expand...
Click to collapse
None of the methods I found around Googling (clearing cache, factory reset) could fix this issue. Now I'm really pissed off and I don't know what to do, except waiting for another update from HTC.
"System enhancements"? Hah
@vodoomoth, Stop telling people what to do and what not to.. Who do you think you are, barging into a forum and being a pompous ass with your first post?
If telling that I think repeating a the whole post above might not be necessary when I reply with one line is telling people what to do and what not to do, then yes, I am a pompous ass. No, actually, I am a stupid arrogant pompous ass. But I didn't write the Netiquette, I just read it and it's pretty standard in forums. Sorry to be the one to remind you that there is no need to cite an entire message and reply with just one single word and a question mark!
I doubt you were talking about me telling shankly1985 that his "do not apply OTA updates on custom ROMs" was not helping. Oh yes, I am not the person who hasn't read the opening post where that concern is pretty obvious.
However, I don't see how my post is summed up as "barging into" a forum. I didn't know some behaviors were not allowed in first posts but only in later posts. Sorry for that again. I guess I should have not written a first post.
To other people, sorry for the off-topic.
desiredr said:
And if you're using a stock ROM, you shouldn't either.
I stupidly updated my Desire and
calendar stopped working properly (events disappeared; luckily, I can see from Google Calendar's web interface that they're all still there)
every now and then an error message appears:
None of the methods I found around Googling (clearing cache, factory reset) could fix this issue. Now I'm really pissed off and I don't know what to do, except waiting for another update from HTC.
"System enhancements"? Hah
Click to expand...
Click to collapse
Why don't you root and flash a custom ROM?
Won't do it until my warranty expires.
desiredr said:
Won't do it until my warranty expires.
Click to expand...
Click to collapse
it doesn't make a difference, all you need to do to restore warranty is use a RUU....
desiredr said:
Won't do it until my warranty expires.
Click to expand...
Click to collapse
You can flash an RUU of 2.29.405 and return it back to the state it was before you updated. You can do this now to fix your issue, if you dont want to go the rooted way.
bortak said:
it doesn't make a difference, all you need to do to restore warranty is use a RUU....
Click to expand...
Click to collapse
It actually does: imagine if my screen doesn't light up anymore. Then I would send my phone to repair. But I wouldn't be able to restore any RUU, since I wouldn't see anything and I couldn't be sure my phone was restored successfully or not.
Anyway, please, let's stay in topic... OTA update and its problems.
desiredr said:
And if you're using a stock ROM, you shouldn't either.
I stupidly updated my Desire and
calendar stopped working properly (events disappeared; luckily, I can see from Google Calendar's web interface that they're all still there)
every now and then an error message appears:
None of the methods I found around Googling (clearing cache, factory reset) could fix this issue. Now I'm really pissed off and I don't know what to do, except waiting for another update from HTC.
"System enhancements"? Hah
Click to expand...
Click to collapse
"If you add a new appointment, and then delete this new appointment again, the calendar re-syncs and shows all your appointments again."
Check this for the discussion about it if you haven't already.
desiredr said:
It actually does: imagine if my screen doesn't light up anymore. Then I would send my phone to repair. But I wouldn't be able to restore any RUU, since I wouldn't see anything and I couldn't be sure my phone was restored successfully or not.
Anyway, please, let's stay in topic... OTA update and its problems.
Click to expand...
Click to collapse
If you screen died, all you'd have to do is boot fastboot, and watch the RUU process and your pc screen, so you stand corrected as you would know if it's restored.
And I don't really see what all the hype is about.. I bet it doesn't even do anything.
stankyou said:
"If you add a new appointment, and then delete this new appointment again, the calendar re-syncs and shows all your appointments again."
Check ... for the discussion about it if you haven't already.
Click to expand...
Click to collapse
The Calendar problem fixed by itself. com.htc.bgp keeps crashing every time the Meteo service tries to sync.
bortak said:
If you screen died, all you'd have to do is boot fastboot, and watch the RUU process and your pc screen, so you stand corrected as you would know if it's restored.
And I don't really see what all the hype is about.. I bet it doesn't even do anything.
Click to expand...
Click to collapse
No hype at all, let's just say I want a vanilla rom if it makes you happier
Please, let's stay in topic....
Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
@BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.
Be aware, and backup before doing this or everything you're dubious about.
Cheers
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them
RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order