Hi, I've recently rooted my phone and I'm quite happily running InsertCoin ICS ROM. Although I don't have any problems I'm curious to know why when I reboot into the bootloader and select the BOOTLOADER option from the menu is get numerous errors/warnings saying can't find PG58DIAG.zip, PG58DIAG.nbh and a number of other files. Why is this happening, is it merely the bootloader looking for these files so it can update the firmware? I recall having to drop a pg58diag.zip file (I think it was called that anyway) as part of the rooting process.
Finally what do these files update, I understand it's firmware but is it specifically the radio firmware as I've seen various references to updating radio firmware specifically and other references to just firmware as if it applies to more than just the radio.
Sorry if these questions have been asked before but I want to be very clear on what files relate to what when upgrading and also the differences in process to simply flash a new ROM which so far seems dead easy - simply pick a zip file from the SD card within 4ext Recovery and follow the installation instructions. It's only when there are dependencies on other files (such as firmware/radio) that things get more piecemeal and slightly confusing.
Sent from the future three weeks ago.
Good afternoon, XDA community, I've been searching the heck out of Google for an answer to what I'm trying to do, and haven't gotten anywhere.
I have a Motorola Backflip running the latest AT&T firmware, and I'd like to downgrade it back to Android 1.5.
Now, I learned early on the Radio/Bootloader cannot be downgraded. After some digging I've found a thread on ModMyMobile that instructs you on loading the Radio image from the newer firmware into an SBF containing the older Android version. This can then be flashed from RSD Lite, and it'll keep the new radio and bootloader while loading the system partition of old.
However, an update released after that was post was made put the kibosh on that approach. It now refuses anything that isn't an official, signed SBF.
Here's three ideas I think might work, and I'd like your feedback on them:
1.) I have the MBN files extracted from the Android 1.5 SBF sitting on my hard drive. Is it possible to extract the contents of the systemsec.mbn file, load it into a flash-able ZIP; and then flash it via the custom recovery I have on the phone?
2.) If someone out there were to provide me with a backup of the old firmware, created with jr00ds recovery, could it then be modified to remove everything but the system partition, and then simply restore the modified backup to my device?
3.) This is one I know will do the trick: if someone on these forums has an old, battered Backflip that still has Android 1.5 sitting on its ROM, I could just transplant the motherboard to my pristine unit. If any of you have one you're willing to sell cheaply, please let me know!
Before anyone asks the obvious "Why so much effort for an outdated device/version of Android?", it's purely for nostalgia. This was my first Android device, and part of me would like to relive it. Because, frankly, the 2.1 update was just plain terrible.
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 !
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!
Hi,
I have a Rockchip tablet RK312x Android version 4.4. I also have the stock image for it.
What I want to do? Update the android version to at least 5.0.
What I have done so far?
Tried to understand how AOSP works, how building ROMs work. Downloaded AOSP 5.1.1. Completed a test build for one of the nexus devices just to be sure the process completes 100%.
Extracted the stock image to get .img files for boot, kernel, misc, recovery, resource, system and uboot.
My question: Is it possible to upgrade the tablet without going the entire creating .mk files and building from scratch route?
Are there any complete step by step guides on this? I tried searching and did find many but not one of them was complete, covering the process that I want to do in a simple manner.
So many of you had a look at this thread and no replies yet. I am all new to this. So sorry if my questions don't make sense. But if you have any experience in building roms, I need your help.
Still, any help would be highly appreciated.
There is no simple manner to this. As your device was not officially upgrade you will have to do alot of work to hack the kernel to work with the new OS. Then you will have to heck all the drivers to work and even then it might not work at all. I would start by finding out if the oem released the kernel source code for the device. Judging from the name I am betting not.