Europe HTC ONE M9 need urgent help - Android Q&A, Help & Troubleshooting

Solved

Nikolay82 said:
Hello. I am fairly new to the XDA forums and I would like to say hello to everyone.
I am looking for someone to help me with the following problem.
I flashed CID to take in any RUU. I've tried many even the USA T-mobile. It worked but had problems using mobile data. Now I use stock european one where version is:1.32.401.17
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_.exe
. I got this version through official RUU. Device is currently S-OFF rooted and has twrp on it.
But now problems are here. I am aware european models got the 5.1 OTA update and I do have it downloaded.
File Says:
OTA_HIMA_UHL_L51_SENSE70_MR_HTC_Europe_2.10.401.1-1.40.401.8_release_444119.zip
Now when I try to update OTA through twrp it doesnt let me. Says something about Err_message. That being said, sideload wont work either. Now my question is, how do I get the OTA to my device? Note; when checking for updates via settings in the phone it says no updates available, regardless of updated airing for a while now. Now i wonder if can update from :1.32.401.17 to 2.10.401.1 with OTA or do I need to update first to 1.40.401.8 (I have 1.40.401.8 flash file).
Please if someone can help me I would thankful. Thanks.
Click to expand...
Click to collapse
OTAs can only be used with the stock recovery. I don't recommend doing a stock OTA if you have modded parts of the system. Better to flash a rom through TWRP. You might need to update the firmware as well.

Are you referring to 0PJAMIG*.zip file? in that case i have them plenty and one I need that matches my phone is like missing some files in the zip. Sadly, I can't post the link yet.
Let me explain this better please:
1. I do have RUUs,; RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4
2. I do have 0PJAIMG Files as well: 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.8_Radio_01.01_U11440261_56.02.50306G_2_F_release_425571_signed_Hboot.zip
3. And I believe I have proper firmware and recoveries for said 0PJAIMG. I have every one of them downloaded for gradual update.
Problem is; I don't have the automatic RUU for version 1.32.401.8, the exe stuff. And I am having hard time installing the 0PJAIMG file on the phone because it gives errors and missing files inside from the looks.
File size of 0PJAIMG is 2gb but content withing the zip is barely 40mb but it says 2gb...
If I am able to get everything related with 1.32.401.8 I could most likely do the all process till latest update.
I am aware I can't post links but for this sake I would like to post it like this: tinyurl[dot]com/m9roms
Just replace "[dot]" with "."
moderator can remove the link however but I need urgent help. If someone can guide me what to I would appreciate it.

Related

[Q] Rogers Update?

Yesterday, there was an update that was pushed to my Rogers HTC Jetstream. Due to having the clockwork recovery that DooMLorD cooked up, the update was unsuccessful since the device tries to reboot in the stock recovery.
I'm wondering if anyone that didn't install the custom recovery is able to confirm any notable changes and if so, is there a way to have a .zip of the update so we can flash it in CWM?
I also tried looking for the 9MB download in root explorer to no avail.
Thank you.
Hi, AT+T is going to be pushing out an update in the next day or so as well. What i find interesting is, the update was on the HTC website at http://www.htc.com/us/support/jetstream-att/downloads/ and is now removed. i downloaded the 473 MB file called htc_jetstream_emr_update_1.30.502.1_us.exe . HTC claimed this file was the same as the update BUT that it would delete all my data if i manually used the file versus 'off the air' update when that is delivered.
Can you upload the file anywhere? Maybe our trustly devs could make something of it.
Someone else here has it and they said they will upload it shortly. So check back on this forum.
Please upload it!!
Presuming the .exe is a normal HTC RUU (as the past 2 Rogers updates are), this will be easy to turn into a CWM-flashable zip, which won't delete your data. You can extract a file called rom.zip from a temp folder once the RUU is running, and inside the rom.zip is all the .img's to be flashed. boot.img, system.img etc. Once we have those files, repackage them to a CWM-flashable zip and boom, you're off to the races. (Since we don't have the block device number for the boot partition, the boot.img needs to be flashed manually via fastboot.) Flashing the .img's as-is will likely cause you to lose root, but as long as you do a nandroid backup from CWM, you can always revert, or try DooM's root method, which I'm sure will still work.
Hopefully that upload will happen sooner rather than later and we can rip this joint apart.
Any one knows what the update contains? Will the ATT users could use it as well?
HTC says it has some bug fixes, HTC logger removed and a security patch.
Have downloaded the file. Am uploading it. Will share as soon as its done. Sorry end of month so slow internet..
Sent from my HTC PG09410 using XDA App
I think feherhollo has already uploaded the ruu. See his post under the Jetstream android development section. Thanks to him for doing it so quick.
Link is:
http://forum.xda-developers.com/showthread.php?t=1466231
Just ran the update on my stock Rogers Jetstream and in the details it only seems to update the built-in Twitter app. Does anyone know if anything else was updated that isn't mentioned in the description?
I'll rip the RUU apart after work tonight and try to get a CWM-flashable zip out tonight or tomorrow.
drizzo613 said:
Just ran the update on my stock Rogers Jetstream and in the details it only seems to update the built-in Twitter app. Does anyone know if anything else was updated that isn't mentioned in the description?
Click to expand...
Click to collapse
How you can ran this on rogers jetstream? Is your device s-off?? (this is for AT&T jetstream)
Sent from my HTC PG09410 using Tapatalk
feherhollo said:
How you can ran this on rogers jetstream? Is your device s-off?? (this is for AT&T jetstream)
Sent from my HTC PG09410 using Tapatalk
Click to expand...
Click to collapse
i was referring to the OP.

Is it possible to flash stock ROM on Consumer Cellular Variants ?

Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
The problem with flashing oem firmware
medwatt said:
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
Click to expand...
Click to collapse
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
mtyler7807 said:
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
Click to expand...
Click to collapse
When you say "update", do you mean clearing the OS and installing a new one from scratch ? Does that mean after the update all the consumer cellular additions will go away and there will be no trace of it ?
If updating seems difficult now for the consumer cellular versions, what will we do when they release Lollipop ?
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Assuming they release the CC version of lollipop, will there be any problem if some of the system files have been changed? For example, I've deleted some system apps that I never use and changed the boot- and flash-screen files. Will the update fail because of that ? I'm asking this because I saw a video made by one of the forum members here when he was trying to install the v148 update. He had to uninstall everything and return the system to default before updating. If that is so, then I guess no Lollipop crying::crying for me !!
Given that Lollipop is still some months away and the lack of any meaningful activity on the HAM2, why don't we prepare our HAM2 for who-knows-what. I'd like to get a grip on a my phone now instead of getting swamped by error messages when Lollipop gets released or we get custom firmware.
There's this thread [http://forum.xda-developers.com/showthread.php?t=2315547] which explains how to extract the individual image files from the huawei update app.
Do you have the CC version of HAM2 ? If so, will you be trying to flash the image files because extracting the image files seem straight-forward ? I'm actually a bit nervous doing it myself because I've always flashed my other devices when it has been confirmed to work. What I'm wary of is I'm not sure that the device software in the v148 update app is 100% compatible with the CC variant that I own ! How can one be sure of that ?
I've downloaded v148 update file and extracted the files you mentioned. Instead of taking screenshots of the contents of the image files, I've recorded a small video. I can see the boot.img and system.img but no recovery.img. There are also other files. Take a look at the video. The question now is what to do with these files and more importantly what are my chances of unbricking the phone if it bricks !!
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen the video I uploaded ? Is it the "full download"? Can I flash it ? Will the phone brick ?
I read your posts on the subject. But it seems you have changed some system apps and the camera is not working as it should. I have already downloaded the 148 file and extracted the system.img and boot.img files. Can I flash these or do I have to use the files you uploaded on google drive ?
The question is why didn't you use the v148 stock ? I already have the v148 stock. Will it brick my phone if I flash the image files ? If not, why did you have to add extra files there such that the camera is 8MP instead of 13MP. Also, why is the hotspot always enabled ? Is that the case with people with the original stock ?
Man, I'm still waiting for your reply !
medwatt said:
Man, I'm still waiting for your reply !
Click to expand...
Click to collapse
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
290 said:
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
Click to expand...
Click to collapse
"For whatever reason mtyler7807 is trying to reinvent the wheel", Ha Ha. I spent about 2 weeks working on this phone when I first got it. With this phone it has more partitions than what is included in the backup with TWRP. TWRP is made for backup and restoring the files that get changed, the other partitions don't change. So when I first started experimenting with this phone I got a full 148 backup with no data and installed it. I had problems, the custom.bin points to a different cust/us/ folder (because it is for a different carrier) , I had to rename that folder and found I have no more 4glte only H/H+, So I had to get the original cust folder from the guy and copy it to the phone. Still and only H/H+. It was okay for then because I testing. Next Viewed my system specs and saw that pretty much half half phone was 148 and the other half was 132.
I have Redone my complete back since I posted the last one with google camera with 13mp support( rather have border transparency). I made a post asking people summit backups. You have to do a little research, did my research and got help from the forum guys. If you want 148 on your CC version you will have to extract the update and fastboot img files (ex.fastboot flash system system.img). The name of the file is the partition name.
From my understanding twrp does a nand backup. Which is more like an image of nand. So restoring an image from a stock phone would also give you the stock partition table no?
It has been a while since ive played with android on such a low level. When it came time to update my HP Touchpad to JB i had to manually create the partition table manually to make it fit. Eventually a script was created that automatically made the changes to the file system. Perhaps a solution along those lines could be useful in getting the stuck firmware on the CC phones? The file system would only need to be created on initial flash to the stock firmware.
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
medwatt said:
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
Click to expand...
Click to collapse
Here is what k2thejx5 said after flashing a backup from a stock phone.
k2thejx5 said:
What's weird is when I flashed the stock file and tried to upgrade, it wouldn't work. The kernels were different so I had to go back to stock consumer rom. Also, while using the rom you posted.. I lost my toggles and had to use a different app. What also was very weird, after flashing back to the stock consumer rom, I had tethering! Don't get it lol.
Click to expand...
Click to collapse
-Do what I did makes your phone a complete oem, All that is need to be done is to flash a splash screen.
-How would I know if updates will work since 148 is the latest version for oem, can't test that tell lollipop.
-I'm not pushing anyone to install my image, I got about 30 pm's to post my recovery to enable hotspot and to get those toggles backup at the top. Alot of people messed up and lost them flashing that original twrp recovery under developer. Alot of others wanted the hotspot without the head ache of going through the research.
And for the people with problems with there phone that want 148 and updates with no problems, You should have brought a OEM and stayed away from sears or target or took it back to the store if you were not ready to take on the challenge of fabbing up your phone. Or just deal with the factory image and hope for lollipop.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Me and k2thejx5 was trying to fix the problem with the twrp recovery originally posted on this site. That one is not mine. Read the post. That firmware took our toogles away. You have to read this forum a little more.
Ok man, thanks for the reply. Two last question:
-For as long as you've been using your phone with your image files, have you been noticing problems like "unexpected crashes", trying to launch something and its unresponsive lie APN
-Is this the latest file you recommend : [https://drive.google.com/file/d/0BwnSk8BOQp3wV0JMWnJGc3RBTzQ/view]
Thanks.
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
mtyler7807 said:
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
Click to expand...
Click to collapse
All right then. Upload it when you're ready !

[Q] Questions on returning to stock XT1021

For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
1. Most likely. There have been many users reporting hard bricked devices when the did what you are telling. So you shouldn't risk it.
2. No, it is not necessary if you haven't changed the system a bit, and in such a case just unrooting would suffice. But as you were rooted and all, you may have altered it a little. So it is recommended to flash stock as it removes all chances of errors.
3. Working link:http://forum.xda-developers.com/showthread.php?p=54872420
Hope I helped!!!
Harsh862 said:
Hope I helped!!!
Click to expand...
Click to collapse
Thanks for the answers. I'll definitely have to go back to stock then if we want to upgrade. I hate losing all my settings and high scores, but if that's what has to be done, that's what we have to do.
However, the link for the firmware is for Brasil. So it won't work for me. I'm in the United States, and need the US retail global version for the XT1021. Maybe someone else has this? Thanks in advance!
Also, not sure if it makes a difference or not, but we are still on 4.4.3.
LeiraHoward said:
For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
Click to expand...
Click to collapse
Que 1&2 are basically the same.
Here is a detailed explanation for both.
To update your OS via official OTA, you need unmodified system. The OTA doesn't simply copy files to the system, it patches those files so if a single file is modified the update won't be able to patch it and your phone will soft brick.
Now, to avoid that, it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.)
So you can just flash the system partitions and stock recovery. This will not remove your data & those high scores.
To flash just extract your rom and execute these commands ONLY.
Code:
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
You will have your stock recovery and unmodified system ready for update.
neo.ank said:
it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.).
Click to expand...
Click to collapse
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
LeiraHoward said:
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
Click to expand...
Click to collapse
Stock recovery files are available on xda. Why are going to stock for lollipop upgrade. Use a lollipop flashable file which is given on this page. Don't screw up your device. Link-http://forum.xda-developers.com/moto-e/development/rom-motorola-stock-rom-t2935429
I've done some research and it looks as though the file I need is Blur_Version.21.12.34.condor_retuglb.retuglb.en.US which should be Android 4.4.3 for the XT1021 for the GSM phone in the US. But I am unable to find this rom anywhere. The only file I've been able to get is the 4.4.4 and I don't think that flashing just parts of that one to my device is a good idea. I'd still kinda like to keep my original settings... does anyone have the Blur_Version.21.12.34.condor_retuglb.retuglb.en.US file or a link to it? I have done SO many searches on this site but keep running into dead links. (Whatever happened to droid-developers anyway? ALL the links go to them and nothing works....)
Thanks!

How to: Update LG G2 D802 (FlashKDZ/Root/Recovery/Hiddenmenu/troubleshooting)(n2n)

(FlashKDZ/Root/Recovery/Hiddenmenu/troubleshooting)​ (noob2noob guide)​
Okay, this is my first thread on XDA, the reason I'm making it is there is a lots of problems with progressing to lollipop. All of this is already mentioned in the forum, but this way it is much easier since it is all at one place. If I'm doing something wrong please warn me with explanation how to resolve the issue. If I'm posting in wrong forum section please move my thread where it is supposed to be.
1. Before doing anything check if your phone is ready to get updated:
1.1 Do you have a stock Kitkat rom or at least a rom that is kitkat based, since there can be a problem with partitioning if custom lollipop rom is installed
1.2 Create a backup. Don't be lazy LG backups will not help you since they can't go from kitkat to lollipop, don't try to do it from recovery because you will lose custom recovery. Copy your files from phone including extracted contacts, and back it up online with google or some other backup providers.
1.3 Check if you have a latest touch firmware, because you might have a problems after installing lollipop and it will be hard for you to check for updates since your touch might become useless.
1.3.1 To check it go to hidden service menu by typing 3845#*802# and go under HW Device Test, then Touch Test then touch firmware version and write everything down. After that go to touch firmware upgrade and after 15 seconds compare the touch firmware version values with those you written down.
1.4 In hidden Menu you can also go to wlan test then ota setting to check if it is disabled on your phone. After that check again if there is OTA updates for your phone, and also check if there is PC suite Update.
1.5 Check your phones version if it is D802, D800 or something else, and check which rom you have installed. You can do this in settings about phone or if you are happy about hidden menu found, go there and into settings then version info. This might not be interesting or fun to do, but it will save you the trouble if something goes wrong, because you will know what to ask.
1.6 Last but not the least, before starting to flash fill up your battery, i've read some posts that say there are problems with wrong capacity shown, and a lots of battery drain problems, and only solution till now is to have a full battery on start.
2. You will need LG FlashTool and of course installed drivers for your G2 on your PC.
All of that you can get in the thread by @quangnhut123 .
2.1 Just a bit of precautions, don't forget to always copy a kdz file in to Flashtool folder and then start a tool. All should look the same as in that thread, except you should always use CSE method because with this method you will install kdz from scratch, removing everything from the phone.
2.2 You should find the kdz file which suits for your phone on site . You can check for kdz by typing in imei in check new firmware section or find the one for yourself by searching the site. v30a is lollipop open while v30d is for branded G2's.
(I've read that this site is not allowed by Xda moderators, so if I can't post it please give me info on where should we download kdz's from).
2.3 I think it's all pure logic now but lets say it one more time. You have downloaded kdz file, and put it inside LG Flashtool folder. You should now start Flashtool and get your phone into Download mode. To do this you need to hold volume up button on turned off device and connect usb cable while holding volume up. Now just cse flash.
2/3 This is troubleshooting step, if you have a problem ask and i hope this great community will help you like they did to me, and ofc I will do my best to help.
3. Now we go to rooting.
Here is the thread by @avicohh which worked for my D802.
Just follow his step by step tut and you will have a rooted phone
3.1 The only issue that might happen here is you are stuck with # and adb waiting for your phone. To resolve this just go into download mode manually.
4. Okay rooting done, now let's go to custom recovery install
It's easy as installing an app from google play by @bender_007
4.1 After installing it open the app and follow the on-screen instructions. If it fails for the first time, try it few more times, it will eventually work. (OFC. I didn't install it with only one try).
4.2 To get into custom recovery hold volume down and power button till first LG sign shows up, then release both buttons and quickly press them again. It will ask you do you want to do factory reset, press yes and yes again, and it will get you to custom recovery if you installed it.
4.2.1 If you factory reset your phone that means you didn't install recovery correctly and you will lose your data, but again that should be no problem since you have that backup from the start.
Now optional steps:
5. Install system app remover to remove bloatware from your phone. You can do it manually but this way you will have those apps backed up.
6. Next suggestion is to install a few mods if you need them. In my case I had to have a Plug and pop, since it is lost from Lollipop and I loved that feature. Here is a thread on how to install that mod by @p_a_r_s_a7
//That's all, if you have any questions feel free to ask, since there is no dumb questions, but also try to read carefully before//
Thanks to:
@quangnhut123
@avicohh
@p_a_r_s_a7
@bender_007
A lot of others whose names i can't remember. If anyone else needs to be mentioned PM me and i will add you in this section.
I will add pictures and stuff if needed
Thanks, good all-in-one thread, + easiest methods. Ill recommend it‚to others
This forum is such a mess that a thread like this is like a fresh breath of air. Every advice given on other threads references something that you should already know how it's done, or you should already have done to your phone in the past and have a certain version of it, or non-working tools that are only around for a few months until an update makes them unusable.
No wonder that most of the first-page topics, including pinned ones, have the word "brick" in the title. This should signal the forum moderators that something is wrong around here.
My phone is stock international sim-free G2, never rooted or otherwise modified and yet no one was able to offer a coherent solution of how to update to Lollipop, until your post.
So, thanks for this thread.
Thank you, that is exactly why i made the thread. Every one of those threads has everything explained, but you need to search theough 150 pages to understand how something is done. That's why i wanted to make a thread with all explanations made in a single post and to make it noob friendly since the worst thing that happens in other threads is answer like use a search you have it somewhere.
Hi,
Thanks for the thread. It really helps noobs like me, but I still have a couple of questions...
I was running Paranoid Android L rom with root, twrp and kk bootloader on My D802.
I didn't see this thread before I decided to downgrade back to 4.2.2 stock rom, and now I don't really know what steps to take.(I have kernel version 3..4.0 and build number JDQ39B)
I haven't seen an OTA available, so I was thinking of flashing new Lollipop rom kdz file. But I've been seeing stuff about using LG PC suite to upgrade via OTA so i wasn't sure.
So my main question is that do I do an OTA upgrade on my current 4.2.2 stock rom or do I download an official Lollipop rom? Can you give me a brief idea of the steps to take?
Thanks
seyio said:
Hi,
Thanks for the thread. It really helps noobs like me, but I still have a couple of questions...
I was running Paranoid Android L rom with root, twrp and kk bootloader on My D802.
I didn't see this thread before I decided to downgrade back to 4.2.2 stock rom, and now I don't really know what steps to take.(I have kernel version 3..4.0 and build number JDQ39B)
I haven't seen an OTA available, so I was thinking of flashing new Lollipop rom kdz file. But I've been seeing stuff about using LG PC suite to upgrade via OTA so i wasn't sure.
So my main question is that do I do an OTA upgrade on my current 4.2.2 stock rom or do I download an official Lollipop rom? Can you give me a brief idea of the steps to take?
Thanks
Click to expand...
Click to collapse
Updating through pc suite or ota is the best way if it is available to you. Flashing kdz is the same thing but that is doing it manually while through pc auite nad ota is pretty much automatic. Anyways which ever way you decide to use be sure to fully charge your battery and factory reset acter the update. If you need anything else feel free to ask
[email protected]$o said:
Updating through pc suite or ota is the best way if it is available to you. Flashing kdz is the same thing but that is doing it manually while through pc auite nad ota is pretty much automatic. Anyways which ever way you decide to use be sure to fully charge your battery and factory reset acter the update. If you need anything else feel free to ask
Click to expand...
Click to collapse
Do I flash KK bootloader or root before I update through ota?
seyio said:
Do I flash KK bootloader or root before I update through ota?
Click to expand...
Click to collapse
No need to flash bootloader if you didnt flash it for paranoid android. And definitely no need to root since you can root after update.
Problems with flashing KDZ
I have downloaded Spain Lolipop KDZ file for LG G2 D802.
Have backed up everything usint TWRP> ( Presently on Optimus G3 rom v 1.4.1 with dorimanx kernel and TWRP )
I have copied the KDZ file to the flash tool. When i use CSE flash .. it takes me to the next page .. in which I click on Start which then opens up the LG Mobile support tool.
Then it shows detecting ur phone .. unpacking or extracting file .. after that shows software updating .. reaches 2 % and then shows error .. asks me to retry .
Do you know what I am doing wrong ? or the cause of this prob ?
http://i58.tinypic.com/15rk2eo.png
sankeerth24 said:
I have downloaded Spain Lolipop KDZ file for LG G2 D802.
Have backed up everything usint TWRP> ( Presently on Optimus G3 rom v 1.4.1 with dorimanx kernel and TWRP )
I have copied the KDZ file to the flash tool. When i use CSE flash .. it takes me to the next page .. in which I click on Start which then opens up the LG Mobile support tool.
Then it shows detecting ur phone .. unpacking or extracting file .. after that shows software updating .. reaches 2 % and then shows error .. asks me to retry .
Do you know what I am doing wrong ? or the cause of this prob ?
http://i58.tinypic.com/15rk2eo.png
Click to expand...
Click to collapse
Had the same problem when flashing kitkat kdz. Are you sure that you have pasted kdzfile inside flashtool. If that is not the problem try other kdz. That helped me
Where are you from and more specifically whhere your phone is from so i can maybe help you with finding right kdz. And btw i think you might have a problem when trying to restore that backup so if you still can backup your phone manually or on the cloud.
[email protected]$o said:
Had the same problem when flashing kitkat kdz. Are you sure that you have pasted kdzfile inside flashtool. If that is not the problem try other kdz. That helped me
Where are you from and more specifically whhere your phone is from so i can maybe help you with finding right kdz. And btw i think you might have a problem when trying to restore that backup so if you still can backup your phone manually or on the cloud.
Click to expand...
Click to collapse
I have restored the complete back up using TWRP .... Yes i have already pasted kdz in the same folder of flash tool...still no change .. now downloading D802 20H firmware to flash stock n den again try KDZ
I have seen that some guys who had the same problem resolved it with disconnecting from network
Sent from my LG-D802 using XDA Free mobile app
sankeerth24 said:
I have restored the complete back up using TWRP .... Yes i have already pasted kdz in the same folder of flash tool...still no change .. now downloading D802 20H firmware to flash stock n den again try KDZ
Click to expand...
Click to collapse
http://www.1x1a.com/fixlg-flash-tool-stuck-at-2.html
Or maybe try this. I havent tried it so i cant promise anything but if you want you can try. Hope it helps
[email protected]$o said:
No need to flash bootloader if you didnt flash it for paranoid android. And definitely no need to root since you can root after update.
Click to expand...
Click to collapse
Hi again..
OTA update to Lollipop has failed on my D802, LG PC Suite only upgraded me from Android 4.2.2 to 4.4.2, so can anyone help me out here?
Am I missing something for OTA update? If not, then which lollipop kdz can I download for my phone so that I can flash? I live in UK and i use a 3 UK sim if that helps
but also, In the process of trying to boot into my previously installed TWRP recovery, I discovered that i have been restored to stock recovery. I have rooted the phone, but just wanted to clarify: I flash custom recovery, then bootloader/kernel then lollipop kdz?
Thanks again
seyio said:
Hi again..
OTA update to Lollipop has failed on my D802, LG PC Suite only upgraded me from Android 4.2.2 to 4.4.2, so can anyone help me out here?
Am I missing something for OTA update? If not, then which lollipop kdz can I download for my phone so that I can flash? I live in UK and i use a 3 UK sim if that helps
but also, In the process of trying to boot into my previously installed TWRP recovery, I discovered that i have been restored to stock recovery. I have rooted the phone, but just wanted to clarify: I flash custom recovery, then bootloader/kernel then lollipop kdz?
Thanks again
Click to expand...
Click to collapse
I am not sure but i think that update for the uk didnt come out yet. so you can't update to lollipop yet via pc suite or ota. and you got it all wrong. first you flash lollipop kdz but you will have to try out few of them since official for uk didn't come out yet, after that you root, and then flash custom recovery.
and as previously you will be back to stock recovery after update. you have it all explained step by step in first post. i know it is a bit long but that is the best way, since i didn't want to write stuff like "you should know that" and so on. so just follow the first post and you will be happy, or wait for official uk update over the ota you will be happy too, and i guess it should come out in a month.
[email protected]$o said:
I am not sure but i think that update for the uk didnt come out yet. so you can't update to lollipop yet via pc suite or ota. and you got it all wrong. first you flash lollipop kdz but you will have to try out few of them since official for uk didn't come out yet, after that you root, and then flash custom recovery.
and as previously you will be back to stock recovery after update. you have it all explained step by step in first post. i know it is a bit long but that is the best way, since i didn't want to write stuff like "you should know that" and so on. so just follow the first post and you will be happy, or wait for official uk update over the ota you will be happy too, and i guess it should come out in a month.
Click to expand...
Click to collapse
Thanks for the quick reply.
I'll download all the lollipop kdz's and see which one of them works for me till the UK one comes out then I'll just do a normal flash over it.
But seriously, one month for the UK ota :crying: Right now, I don't even know which is worse: Google that takes forever to release updates with so many bugs, or Apple who generally release better stable updates but make older devices laggy...
Thanks again for all the help.
seyio said:
Thanks for the quick reply.
I'll download all the lollipop kdz's and see which one of them works for me till the UK one comes out then I'll just do a normal flash over it.
But seriously, one month for the UK ota :crying: Right now, I don't even know which is worse: Google that takes forever to release updates with so many bugs, or Apple who generally release better stable updates but make older devices laggy...
Thanks again for all the help.
Click to expand...
Click to collapse
its a good update, not that buggy, and be sure to fully charge your battery before the process. you should try europe open or something like that, but there is no german or uk release yet and some guys suspect it is slowed down because they found out bugs in other versions
After CSE Flashing my d802 with a 30a, it got stock on lg logo screen, then an android screen with "erasing" on bottom, then lg screen. I let it sit for 4 hrs but nothing happened. Im back to stock kitkat atm. A little help please.
fernievidal said:
After CSE Flashing my d802 with a 30a, it got stock on lg logo screen, then an android screen with "erasing" on bottom, then lg screen. I let it sit for 4 hrs but nothing happened. Im back to stock kitkat atm. A little help please.
Click to expand...
Click to collapse
Where from is your phone? Are you sure you flashed right kdz? Did lollipop even turn off? DidCSE flashing finished sucessfully? I would like to help you, but i cant if you dont explainme what is your problem. I am not some pro who faced every error on every phoneso please explain a bit more
And i suppose that erasing screen could have been factory reset on stock recovery
[email protected]$o said:
Where from is your phone? Are you sure you flashed right kdz? Did lollipop even turn off? DidCSE flashing finished sucessfully? I would like to help you, but i cant if you dont explainme what is your problem. I am not some pro who faced every error on every phoneso please explain a bit more
And i suppose that erasing screen could have been factory reset on stock recovery
Click to expand...
Click to collapse
I believe mine is an international version. Where it came from, well, I'm from the Philippines and I got my phone from a local telecom, Globe.
The flash tool said that it was successfully upgraded, but judging from the phone's behavior I think there's something wrong. My phone never started successfully, and I got stuck in the LG logo.

[Firmware Needed] Galaxy S4 SCH-I545PP (Verizon Prepaid)

I'm in search of firmware for the S4 running 4.3 or 4.4. I haven't gotten this phone yet but verizon is selling it through Walmart on prepaid. I know the firmware isn't gonna be the same as if it was on contract verizon. I have the S3 right now and it's prepaid. Many argued that there wasn't a NF5 firmware but turns out there is and i used it many times to fix soft bricks on the S3 using Odin. So I'm pretty sure the prepaid side of the S4 will have different firmware then one on contract verizon would have. So that being said, does anyone have 4.3,4.4 or even 5.0 firmware they can share that will work with Odin? Not sure if the S4 got the 5.0 update. Just assuming it did. Any help is appreciated!
Anyone? Please?
If no one can then someone at least tell me how it direct me to where I can make a tar or md5 firmware out of adb pulls of the system an stuff?
bjf189 said:
If no one can then someone at least tell me how it direct me to where I can make a tar or md5 firmware out of adb pulls of the system an stuff?
Click to expand...
Click to collapse
OK never mind. I need 5.0.1 firmware. Not 4.3 or 4.4. Any help would be great
I can't think of any reason as to why post paid firmware would be different than prepaid. You can use the phone for either.
And you're posting jn the wrong forum, which is probably why nobody is helping you. Because you didn't bother to read the rules before posting.
Try the general section or Android development section. Click the search button and type firmware. I'm sure you'll find it faster than it took you to make all these posts. Good luck
still no help
sob372 said:
I can't think of any reason as to why post paid firmware would be different than prepaid. You can use the phone for either.
And you're posting jn the wrong forum, which is probably why nobody is helping you. Because you didn't bother to read the rules before posting.
Try the general section or Android development section. Click the search button and type firmware. I'm sure you'll find it faster than it took you to make all these posts. Good luck
Click to expand...
Click to collapse
still no help
I think what sob372 was saying is the hardware in the phone is the same as the contract so you can just follow the SCH-I545 stuff and it will work.
being that I just got this same phone S4 prepaid used I'll be playing with it to root it, install safestrap and probably downgrade it from Lollipop to Kitkat. So I'll let you know if you don't find more here by searching and I'm sure there are relevant posts if you dig around a bit.
BTW the S4 PP does have a SIM slot.
droidzer1 said:
BTW the S4 PP does have a SIM slot.
Click to expand...
Click to collapse
It just seems really sketchy to do with the contract firmware. Like I get the feeling that if I flash the firmware from contract, I'll lose any cell phone service under prepaid. I just don't want to end up with a big paper weight. The modules could be different. With the S3 I had which was prepaid also. I used safestrap and superlite rom was the best one I got to work with the prepaid version. The system always kept crashing but it would load if I put it under stock an not a rom slot. I had to get the i535pp module to fix the Wi-Fi problem but if I had no service cause of the sim issue then I didn't want it. Also I'm not sure but I think there is no safe strap for the s4 running lollipop. I believe the forum said it would cause bootloops if you tried. Just like you need to deodex for xposed cause of the changes in art
droidzer1 said:
BTW the S4 PP does have a SIM slot.
Click to expand...
Click to collapse
If you can confirm all is in working order with the contract firmware (can't remember what the build is) with the prepaid phone, I'll give it a go.
Update
A member already tried the OC1 postpaid firmware on the prepaid. They said all works but the camera and charging don't work. So that's out of the question
I been looking around on the net and best I've come up with is backing up the firmware. I tried using flash fire to get back ups of every partition. Then I used Odin package creator to try an make a firmware file to use with Odin but when I tried it out in Odin, it stopped at data so I took out my personal data then it stopped at something with number 3 at the end. Can't recall what it was. So if anyone can test more on this to have any luck. Maybe then we can get the firmware out to people in case sammobile decides not to or takes another year to release it
I've been trying a different approach to getting a copy of the OH7 firmware. I've been attempting to use Fiddler4 + the Verizon Wireless Software Upgrade Assistant tool that comes on my phone (Verizon Prepaid Galaxy S4 model SCHI-545KPP) to get a download link to the original rom file... I can't get the bloody link to download with Fiddler or an internet browser, as i get a 403 forbidden error. I'll keep trying, maybe I can find the downloaded file in my temp files while attempting to recover my phone? It will take some time but I'll keep trying.
*update* So I located where the Verizon Wireless Software Upgrade Assistant stores its files (compressed and extracted). The location is C:\Users\[username]\AppData\Roaming\Verizon_AR .
I unfortionally didn't figure this out until after I royally soft bricked my phone. Right now I have a OF1 recovery installed on the phone, and the assistant keeps trying to install the OF1 firmware (and it fails). If anyone could check that folder for the OH7 firmware, or post a backup of the OH7 recovery, you'd be doing me a huge favor. I think we'll have the OH7 firmware after this one way or another.
*edit* This is 100% confirmed now. C:\Users\[username]\AppData\Roaming\Verizon_AR\SCH-I545_I545VRUGOF1_FACTORY\decrypt produced a zip file that is 100% identical to the OF1 firmware zips out there. This decrypt subfolder didn't appear until after the file was completely downloaded, and the Software Repair Assistant had started to try and flash the rom. This data is deleted after the phone completes flashing (or fails to flash). If you select "delete" after this information is downloaded, the encypted rom file is deleted and you must start all over again.
If someone could check that folder who has used the Verizon Wireless Software Upgrade Assistant to recover their phone, using the tool on your phone again and you'll get the decrypt folder... if you zip/rar that folder, we'll finally have the backup files we can post somewhere.
the PP phone uses the same firmware as the normal one that guy that tried it
did something wrong
just flash the OF1 tar via odin and be done with it
TheXev said:
*update* So I located where the Verizon Wireless Software Upgrade Assistant stores its files (compressed and extracted). The location is C:\Users\[username]\AppData\Roaming\Verizon_AR .
I unfortionally didn't figure this out until after I royally soft bricked my phone. Right now I have a OF1 recovery installed on the phone, and the assistant keeps trying to install the OF1 firmware (and it fails). If anyone could check that folder for the OH7 firmware, or post a backup of the OH7 recovery, you'd be doing me a huge favor. I think we'll have the OH7 firmware after this one way or another.
*edit* This is 100% confirmed now. C:\Users\[username]\AppData\Roaming\Verizon_AR\SCH-I545_I545VRUGOF1_FACTORY\decrypt produced a zip file that is 100% identical to the OF1 firmware zips out there. This decrypt subfolder didn't appear until after the file was completely downloaded, and the Software Repair Assistant had started to try and flash the rom. This data is deleted after the phone completes flashing (or fails to flash). If you select "delete" after this information is downloaded, the encypted rom file is deleted and you must start all over again.
If someone could check that folder who has used the Verizon Wireless Software Upgrade Assistant to recover their phone, using the tool on your phone again and you'll get the decrypt folder... if you zip/rar that folder, we'll finally have the backup files we can post somewhere.
Click to expand...
Click to collapse
I'm trying out your idea. If i can get the file them I'll upload it. If not, I'll still be able to at least send you a back up of the oh7 recovery. Mines all still stock. Id hate to get stuck with a paperweight until the correct firmware is released. That's why I'm careful lol. The firmware is downloading right now. It says it's a enc4 file though. Maybe just cause its downloading at the moment. I'll just wait an see an I'll let you know
Legitsu said:
the PP phone uses the same firmware as the normal one that guy that tried it
did something wrong
just flash the OF1 tar via odin and be done with it
Click to expand...
Click to collapse
A few people who used of1 on the pp version had issues. Not one came out with no issues far as i know. So I'd rather be safe then sorry. Not saying your incorrect but I'm just trying to play it safe and careful. Appreciate the input though
bjf189 said:
I'm trying out your idea. If i can get the file them I'll upload it. If not, I'll still be able to at least send you a back up of the oh7 recovery. Mines all still stock. Id hate to get stuck with a paperweight until the correct firmware is released. That's why I'm careful lol. The firmware is downloading right now. It says it's a enc4 file though. Maybe just cause its downloading at the moment. I'll just wait an see an I'll let you know
Click to expand...
Click to collapse
Yes, while it is downloading it will be a .enc4 file. Even after downloading it will stay like that, but when you got to actually flash the file, it will decrypt and the encrypted version will appear in that /decrypt folder.
TheXev said:
Yes, while it is downloading it will be a .enc4 file. Even after downloading it will stay like that, but when you got to actually flash the file, it will decrypt and the encrypted version will appear in that /decrypt folder.
Click to expand...
Click to collapse
so im confused. do i need the encrypted or decrypted file for it to work with odin? i tried changing the file to zip format and open it with winrar after it downloaded in the software but it came up as an unknown archive or damaged. so im not sure what im doing wrong but ill keep trying
UPDATE: i have tried getting the file through verizons handy tool and i did get the decrypted folder along with the unzip folder during it was finishing up repairing my s4. i just copied the file from the decrypted folder and extracted it during the repair. so now im using odin 3.10.7 and testing it out now to see if it will flash successfully. if all goes well, i will make new thread with the firmware link inside it so users dont need to scroll through pages to find the link. first anyone know a good or popular upload storage i can use to upload the firmware to for others to use? i tried uploading onto here but i keep getting a connection timeout
UPDATE 2: ive got it! i made the firmware of OH7! finally. you can go ahead and head over to this thread TheXev. use it and youll be back to stock
http://forum.xda-developers.com/gal...nt/firmware-release-galaxy-s4-i545pp-t3365371
bjf189 said:
so im confused. do i need the encrypted or decrypted file for it to work with odin? i tried changing the file to zip format and open it with winrar after it downloaded in the software but it came up as an unknown archive or damaged. so im not sure what im doing wrong but ill keep trying
UPDATE: i have tried getting the file through verizons handy tool and i did get the decrypted folder along with the unzip folder during it was finishing up repairing my s4. i just copied the file from the decrypted folder and extracted it during the repair. so now im using odin 3.10.7 and testing it out now to see if it will flash successfully. if all goes well, i will make new thread with the firmware link inside it so users dont need to scroll through pages to find the link. first anyone know a good or popular upload storage i can use to upload the firmware to for others to use? i tried uploading onto here but i keep getting a connection timeout
UPDATE 2: ive got it! i made the firmware of OH7! finally. you can go ahead and head over to this thread TheXev. use it and youll be back to stock
http://forum.xda-developers.com/gal...nt/firmware-release-galaxy-s4-i545pp-t3365371
Click to expand...
Click to collapse
Thank you so much. I was close to taking this phone back and not getting another simply because I really need a phone to replace my S3 for tethering soon. But if you got the firmware, I can flash it back to working order, and hopefully get some deodexed roms (that way I can install Xposed framework). Thanks again!

Categories

Resources