[Q] Update fails to install - HTC Desire 510

Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?

mzqaddicted said:
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
Click to expand...
Click to collapse
I flashed stock recovery and update installed successfully, you can give me update file?

Uploaded the file
https://drive.google.com/file/d/0B_bbXjxfqWaeMEFjUmE1ZlhFMmM/view?usp=sharing
can you please share your stock boot & recovery files ?

mzqaddicted said:
Uploaded the file
https://drive.google.com/file/d/0B_bbXjxfqWaeMEFjUmE1ZlhFMmM/view?usp=sharing
can you please share your stock boot & recovery files ?
Click to expand...
Click to collapse
With this recovery I flashed update.
https://drive.google.com/open?id=0B3-NJk0QRfxXaG5sWDc1NG5tbzg&authuser=0
EDIT: Try this recovery, is extracted from update.
https://drive.google.com/file/d/0B3-NJk0QRfxXNzBZbFFiRk5HclE/view?usp=sharing

tried both of them and i have the same issue.
https://drive.google.com/file/d/0B_bbXjxfqWaeVXJqZFBIaTZySGc/view?usp=sharing

mzqaddicted said:
tried both of them and i have the same issue.
https://drive.google.com/file/d/0B_bbXjxfqWaeVXJqZFBIaTZySGc/view?usp=sharing
Click to expand...
Click to collapse
Lock bootloader => run this RUU => update

lucyr03 said:
Lock bootloader => run this RUU => update
Click to expand...
Click to collapse
the RUU installer doesn't work.. somehow.. after i accept the licence agreement nothing happens and the installation shield application disappears.
Thried on 2 dif computer, both W7 x64, latest drivers via HTC sync manager
updated Visual C++ Redistributable for Visual Studio 2012 Update 4

mzqaddicted said:
the RUU installer doesn't work.. somehow.. after i accept the licence agreement nothing happens and the installation shield application disappears.
Thried on 2 dif computer, both W7 x64, latest drivers via HTC sync manager
updated Visual C++ Redistributable for Visual Studio 2012 Update 4
Click to expand...
Click to collapse
Work for me, but take more time to open and you have to wait after accept license...

How i can lock bootloader? I am looking instruction and i can't find :/
Ok i find command "fastboot oem lock" lock bootloader. Now I install RUU from link on post lucyr03 but this version is Europe_1.51.401 .1. Today my phone first time find new update to version Europe_1.51.401 .2-1.51.401.2. What is a diffrent of this version?

Misarus said:
How i can lock bootloader? I am looking instruction and i can't find :/
Ok i find command "fastboot oem lock" lock bootloader. Now I install RUU from link on post lucyr03 but this version is Europe_1.51.401 .1. Today my phone first time find new update to version Europe_1.51.401 .2-1.51.401.2. What is a diffrent of this version?
Click to expand...
Click to collapse
Install RUU from my post and update with OTA.

mzqaddicted said:
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
Click to expand...
Click to collapse
I forgot you posted this already. I just received a 30MB update from Boost Mobile on the 32 bit version and it fails the same exact way yours does. I contacted HTC and Boost Mobile and it seems if it doesn't update properly we have to wait for HTC to release it in the form of a RUU, which I believe they will just wait for Lollipop and bundle this little fix in with the Lollipop update. I searched on their site to see if there was anyway we could manually update and it doesn't exist. There are only old ROMs. I tried some tricks to manually update and it failed every time. I am completely stock on the Boost Mobile RUU and I totally deleted everything before the install so there aren't any problems on my end. There is simply a problem with the way they are attempting to update our phones.

Pretty sure you cant update if unlocked and rooted. Has to be like out of the box running. I couldnt but I did update on my wifes locked/unrooted phone no problem. Took 10 minutes. Checking it out, couldnt really see much, if any, difference. 30mb is pretty small.

CSP III said:
Pretty sure you cant update if unlocked and rooted. Has to be like out of the box running. I couldnt but I did update on my wifes locked/unrooted phone no problem. Took 10 minutes. Checking it out, couldnt really see much, if any, difference. 30mb is pretty small.
Click to expand...
Click to collapse
I am on the Boost Mobile stock RUU, locked, and unrooted.
I just noticed the error message in the stock recovery:
htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/373881.1:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/373881.2:user/release-keys"
Installation aborted.
Write host_mode:0 done
I did
adb shell
getprop ro.build.fingerprint on my phone and I got:
htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/433600.1:user/release-keys
This is on the stock Boost RUU, locked, and unrooted.
There are some other items in build.prop that are different than what the update is looking for.
I am going to change them to what is in my phone and try again.
I don't expect it to work, but it can't hurt.
If it doesn't work, I'll try a stock Rom backup from this site, then try the update again.

Sounds good man. Check back in with the results, I'd like to see how it turns out for you. IMO though, I really think the update isn't worth all the hassle but I totally get it if you are/want to just get it to work. I'd probably do the same. good luck.

CSP III said:
Sounds good man. Check back in with the results, I'd like to see how it turns out for you. IMO though, I really think the update isn't worth all the hassle but I totally get it if you are/want to just get it to work. I'd probably do the same. good luck.
Click to expand...
Click to collapse
Thanks. I know it's not really worth the hassle, but I'm learning a lot by messing with it. It's not working, still. I may be wrong but I think they made a mistake with the build.prop when sending the updates to some of our phones. I think some of us just have to wait for Lollipop.

Related

[Q] Online Update for SEA Region failed

Greetings.
Very recently, there was an official/OTA update for P7-L10. And I subsequently downloaded and tried to update it as soon as it finishes downloading.
But, when it tried to update, it keeps failing. Is the update wrong? or is there something missing that I am not clearly seeing it?
My current version, out of the box - P7-L10V100R001C00B133SP01
and the update (online update) is (as mentioned) : P7-L10_SouthPacific_C00B620.
Please advise me on what might have went wrong?
Thank you.
piring said:
Greetings.
Very recently, there was an official/OTA update for P7-L10. And I subsequently downloaded and tried to update it as soon as it finishes downloading.
But, when it tried to update, it keeps failing. Is the update wrong? or is there something missing that I am not clearly seeing it?
My current version, out of the box - P7-L10V100R001C00B133SP01
and the update (online update) is (as mentioned) : P7-L10_SouthPacific_C00B620.
Please advise me on what might have went wrong?
Thank you.
Click to expand...
Click to collapse
Do you have custom recovery?
ibeqa said:
Do you have custom recovery?
Click to expand...
Click to collapse
Hey there, thank you for the reply.
I'm not sure, how to check. But I have never rooted this phone yet.
piring said:
Hey there, thank you for the reply.
I'm not sure, how to check. But I have never rooted this phone yet.
Click to expand...
Click to collapse
Do you have TWRP or CWM installed? Was your phone brand new or pre-owned? Do you have custom rom or stock rom?
ibeqa said:
Do you have TWRP or CWM installed? Was your phone brand new or pre-owned? Do you have custom rom or stock rom?
Click to expand...
Click to collapse
Nope, I do not have those installed. This is a brand new phone running stock rom.
Ok, I guess your phone is not branded (vodafone, orange, etc.), so get the b609 update and install it.
If you had firmware 133, how come you got SAE update? Where did you buy your phone?
ibeqa said:
Ok, I guess your phone is not branded (vodafone, orange, etc.), so get the b609 update and install it.
If you had firmware 133, how come you got SAE update? Where did you buy your phone?
Click to expand...
Click to collapse
Yep, it's not. Hmm. I am unsure as to how or where I can get the B609 update, because ever since I first laid my hands on this phone, it has been running B133 out of the box. And, since, in between then and now, I have been going to the system update to look for any update prior to this one that I am currently having a problem to update, and there was no new update (until, again, now )
Also, previously I did went online on my PC to find an update B609, and downloaded it and tried to do a local update. and unfortunately for me, it caused my phone to be soft-bricked, and back then, I have not turned on my USB debugging or did any major changes to my phone, thus, requiring me to send my phone to the service centre. So, I'm kinda weary about downloading an update online from my PC, as of now.
Well, I am not sure what SAE is, and to answer that question, again, I do not know how I may have gotten the update. I bought my phone from where I am currently living, Malaysia.
Can you make a print screen of your SAE update problem?
sorry, but um, can you please enlighten me as to what is SAE? I am truly sorry for not knowing this.
piring said:
sorry, but um, can you please enlighten me as to what is SAE? I am truly sorry for not knowing this.
Click to expand...
Click to collapse
SEA is the code Southeastern Asia
Ohhh. haha. Sorry, was wondering what SAE was. Will update as soon as possible.
ibeqa said:
Can you make a print screen of your SAE update problem?
Click to expand...
Click to collapse
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
piring said:
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
Click to expand...
Click to collapse
So OTA fails., what's the code of error (why it fails)?
Also, you can try manual update or the "3 button update" (it is described in the forum).
But the most important thing is to know why it fails.
P.S. You can take print screens from the Hisuite during update or when it fails
piring said:
Hey there, I couldn't really printscreen it, as it was in the updating process (the one with the Android bot and the black screen behind) anyway, it just it failed. That's all.
Here's however, a printscreen of the update.
Click to expand...
Click to collapse
Hi piring, I've encounter the same issue with updating from B133SP01 to B620, my set is a"SOUTH PACIFIC" model.
I even brough my set to the huawei service centre to see if the technician over there can solve the issue but unfortunately, they are just as clueless as I am..... They did a factory reset of my set and tried to install the update again but the update still fail to install. There is no error code but only "fail" word appearing. They claim it's because my set was rooted but when I have unroot my phone, it still.can't update.
So if you managed to successfully updated your set, can you share with me how to go about it? Thanks.
[email protected] said:
Hi piring, I've encounter the same issue with updating from B133SP01 to B620, my set is a"SOUTH PACIFIC" model.
I even brough my set to the huawei service centre to see if the technician over there can solve the issue but unfortunately, they are just as clueless as I am..... They did a factory reset of my set and tried to install the update again but the update still fail to install. There is no error code but only "fail" word appearing. They claim it's because my set was rooted but when I have unroot my phone, it still.can't update.
So if you managed to successfully updated your set, can you share with me how to go about it? Thanks.
Click to expand...
Click to collapse
Oh. well, to be honest, I kinda given up hopes on how to update it. And with that, I am still clueless as to how to update it. I have tried using HiSuite, but to my surprise, HiSuite mentioned that my phone is already up to date. So, I am honestly puzzled as to how my phone is pushing for an OTA, but HiSuite insists that my phone model is of current and latest update.
Sorry I am unable to help you.
piring said:
Oh. well, to be honest, I kinda given up hopes on how to update it. And with that, I am still clueless as to how to update it. I have tried using HiSuite, but to my surprise, HiSuite mentioned that my phone is already up to date. So, I am honestly puzzled as to how my phone is pushing for an OTA, but HiSuite insists that my phone model is of current and latest update.
Sorry I am unable to help you.
Click to expand...
Click to collapse
Hi piring, same thing goes for my HiSuite as well. It's kinda of sucks that the update is available but can't update. It's even more worse that Huawei service centre cannot do anything about it and just tell me forget about the update and ignore the notification. Now i have a phone with a permanent notification mark that i cannot get rid of.
P7-L10 is a good phone but the support i'm getting from Huawei service centre is really unprofessional and disappointing.
But anyway, thanks for your reply.

Moto X mobile data not working.. i messed up

Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
azerouz said:
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
Click to expand...
Click to collapse
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Bhargav4591 said:
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Click to expand...
Click to collapse
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
azerouz said:
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
Click to expand...
Click to collapse
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Bhargav4591 said:
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Click to expand...
Click to collapse
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
azerouz said:
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
Click to expand...
Click to collapse
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Xanthales said:
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Click to expand...
Click to collapse
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
azerouz said:
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
Click to expand...
Click to collapse
No problem, im glad to hear, that I could help you!
Maybe you can help me here?: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
This would be awesome, if you got a retail device!

Stuck On Google Logo and didnt Check Unlock OEM

Hi All,
So I have been searching the interwebs for the last four hours with no luck.
I have a Nexus 6 and I was trying to update the OTA developer preview from google that I signed up to test.
Problem is that I ended up on a bootloop. I am able to get into Fastboot but I am unable to make any commands work since the device is locked. All commands end with a Failed (command write failed error).
I am able to go into recovery to access ADB but that is also not very useful because it seems i am unable to push anything to the phone. The only thing which seems to want to work is when I try and load an OTA image.
This loads until 100% and I get an error which says the image I have is to new and it requires a specic image.
I am currently on 6.0.1/MMB29V/2554798.
I have tried factory reset but no help there.
Also when I try select update from SD Card it says it Couldnt mount/sdcard.... Unknow volume for path
Any help?
qbzee007 said:
Hi All,
So I have been searching the interwebs for the last four hours with no luck.
I have a Nexus 6 and I was trying to update the OTA developer preview from google that I signed up to test.
Problem is that I ended up on a bootloop. I am able to get into Fastboot but I am unable to make any commands work since the device is locked. All commands end with a Failed (command write failed error).
I am able to go into recovery to access ADB but that is also not very useful because it seems i am unable to push anything to the phone. The only thing which seems to want to work is when I try and load an OTA image.
This loads until 100% and I get an error which says the image I have is to new and it requires a specic image.
I am currently on 6.0.1/MMB29V/2554798.
I have tried factory reset but no help there.
Also when I try select update from SD Card it says it Couldnt mount/sdcard.... Unknow volume for path
Any help?
Click to expand...
Click to collapse
Very difficult. Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=3053783
NLBeev said:
Very difficult. Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=3053783
Click to expand...
Click to collapse
Tried it and it seems I have no other option but to return.
Problem is that i am in South Africa and have no idea how to go about.
Bought off Amazon
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
qbzee007 said:
.....Problem is that i am in South Africa and have no idea how to go about.
Bought off Amazon
Click to expand...
Click to collapse
your n6 is bricked and you could try all the options from XDA.
There is a thread about the Nexus Root Toolkit of Wugfresh. This kit runs on a Windows PC and has a menu with option for bricked phones.
When you can start in recovery mode (long press start button + volume down) you could give it a try. http://forum.xda-developers.com/showthread.php?t=2947452
When there is no result, you could send it to Amazon for repair. But check the costs.
The total costs of mail, assurance and repair are probably more than $ 100,=.
I have seen some posts that the of a new N6 is every month lower.
TriguyRN said:
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Click to expand...
Click to collapse
I was going to suggest this too. The link posted leads to this link that has instructions on installing.
alryder said:
I was going to suggest this too. The link posted leads to this link that has instructions on installing.
Click to expand...
Click to collapse
Thank you very much.
This worked.
Booting as I type this. Best Easter Monday gift.
Thanks Again

MIUI Global 7.2.4.0.0 uses A LOT of RAM. (?)

Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.
i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..
7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working

Can't update my ROG Phone II

Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!
HyphenZzX said:
Hello, recently just bought a ROG Phone 2 Tencent Edition from Ebay, when the device came everything was great. However i noticed that online it said that an update had come out which allows support for airtrigger sliding functions. Mine however did not have this. I went to the settings in order to try and update it, but it said that there was no update. So i then went ahead and downloaded an update form asus's website in an attemp to manually update it. But for whatever reason it said that the update was unsuccsessfull or something like that, and that it failed. I checked online and it said my finger print was still on CN however using device hw info it says im on "WW" fingerprint. My software version is 198.12. Please help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293
reg66 said:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Follow this guide to change fingerprint and update to 1910.33, from there download the raw 1910.44 and run flashall_AFT.cmd to update to latest version...
https://forum.xda-developers.com/rog-phone-2/how-to/raw-ww-1910-44-download-t4009293
Click to expand...
Click to collapse
but i don't understand i am already on ww fingerprint???
HyphenZzX said:
but i don't understand i am already on ww fingerprint???
Click to expand...
Click to collapse
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
hi thank you for the response when i open flash thing it just opens the cmd and closes again? what do i do?
edit never mind its doing it now thanks!
reg66 said:
Ah sorry, misread your post. Just download the 1910.44 raw rom from the second link and extract to the root of C drive, remove the original zip file from the folder you extracted and then run flashall_AFT.cmd with the phone in fastboot mode (hold volume up and power together until you set a menu, that's fastboot mode) . It will take about 5 to 10 minutes to complete then the phone will restart. You will not lose any data... Good luck
Click to expand...
Click to collapse
thank you so much it works now quick question can i do manual updates now and get the latest firmware?
HyphenZzX said:
thank you so much it works now quick question can i do manual updates now and get the latest firmware?
Click to expand...
Click to collapse
Well, up until 1910.44, we were able to just download the updates from asus and put them in the root of internal storage... But this changed for many users with the .44 update, so I'm not sure... We'll have to see how the next update goes, but yeah, it'll either be through download of ota or by flashing raw rom... Either way it'll be posted here by someone. Won't be long to wait as China versions already have update .52 update, WW comes shortly after
Hi there I am in a similar situation with a tencent rog 2 purchased on ebay that is on android 9 WW version. Is it possible to flash WW_ZS660KL_17.0240.2107.100_M3.23.44.20-ASUS_1.1.232_Phone-user.raw to get to android 10 immediately? I have attempted it just now but it appears the flashall_AFT.cmd is stuck and i have waited around 20 minutes.
edit: I waited an hour and nothing seemed to happen. so I restarted the phone and it seems like nothing happened at all. Any ideas?
edit: accidental double post

Categories

Resources