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 !
Related
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
MrTip said:
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
Click to expand...
Click to collapse
Here you go - hope it's what you're looking for..
Tigerite said:
Here you go - hope it's what you're looking for..
Click to expand...
Click to collapse
No, it's not. The key element of my message is
with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
Click to expand...
Click to collapse
Thank you anyway.
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Tigerite said:
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Click to expand...
Click to collapse
That's unfortunate. Did you click on "prepare Blocks for FlashTool" after backup ? I'll try myself asap to confirm the procedure.
Yes I did, but no PMT text file in the relevant folder..
Tigerite said:
Yes I did, but no PMT text file in the relevant folder..
Click to expand...
Click to collapse
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
MrTip said:
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
Click to expand...
Click to collapse
What exactly are you trying to do?
kuronosan said:
What exactly are you trying to do?
Click to expand...
Click to collapse
Install last firmware known to be working with twrp.
Did that.
The device doesn't boot anymore.
Revert to previous backup.
Did that.
I like to see things by myself.
It's not your firmware that's the problem. I'm running twrp on the latest firmware without issue.
kuronosan said:
It's not your firmware that's the problem. I'm running twrp on 20140513 firmware without issue.
Click to expand...
Click to collapse
I can only rely on testimonies on this very forum, but I have not seen a single person succesfully installed twrp on firmware 20140513.
I have seen successfull install on previous firmware, and then OTA upgrade.
What is it for you ?
It is exactly what I told you. It's up to you to believe me or not.
kuronosan said:
It is exactly what I told you. It's up to you to believe me or not.
Click to expand...
Click to collapse
You didn't told me if its an install on 20140513 firmware or if it's an upgrade from previous firmware.
kuronosan said:
EU 1/8 users who have the new aluminum watch or who received their units after May 13th need to click here and also need to remember that recovery may not work (although it probably won't work before this anyway).
Click to expand...
Click to collapse
I understand you agree there is a problem with twrp 2.7.1.0 on newer devices.
You'll notice I did say new devices. Not new firmware.
kuronosan said:
You'll notice I did say new devices. Not new firmware.
Click to expand...
Click to collapse
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Tigerite said:
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Click to expand...
Click to collapse
That's OK. It appears that PMT can be (or not) in scatter file without any difference in the filename. (If you look in the file and see many lines per partition, like 'physical_start_addr' and 'linear_start_addr', you have PMT)
So I found what I was looking for, thank you.
MrTip said:
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Click to expand...
Click to collapse
No one is trying to win. I have a good deal of experience with MTK devices based on my researching various methods of backup/restore/flash/etc and I was offering a hand.
You can play one-person pong with yourself and claim fallacy all you want or you can get off your high horse.
Up to you. I have work to do.
TWRP Install on newest firmware + OTA
got watch on 7/26. did OTA. firmware date 5/27/2014. unable to install TWRP via any method including shell DD command. well it installs but on entry I just get on the old andy with red ! showing. It seems like a watchdog timers reboots it after a few minutes and all is back to the way it was.
Which TWRP did you use?
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!
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.
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!
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse