This is a short post theres not much to say since all these are stock roms. I just extracted the P4P MM rom from poland to make a TWRP flashable zip.
Main advantage is that we can keep recovery at the same time we run this MM rom so we can root by simply flashing supersu.
So here it is:
Polish v20b rom
###########################THIS IS OLD AND AT THE DATE WE KNOW IT'S CAUSED BY THE ABOOT, SEE BELOW FOR SOLUTION###########################
############################################KEPT IN CASE SOMEBODY WANTS v10i##############################################
In my case I experienced signal problems that were solved by flashing a v10i rom as base instead of the proposed v10f from where we got our aboot flashed, device didn't break. I think this is important for south american users because of different basebands, so I also uploaded that one here:
v10i ROM
For similar situation don't do any wipe and flash over that v10i the polish v20b rom.
#################################################################################################################
For Argentina/Some latin american countries, you should use the Argentinian Aboot provided by pvineeth97 there, for latin american countries where you experience issues with 3g/LTE you can also try using this aboot in order to get that working, keep in mind argentinian bands are:
2G (EDGE, GSM/GPRS): Bandas 850 / 1900 MHz
3G (HSPA+, UMTS/WCDMA): Bandas 850 / 1900 MHz
4G (LTE): Bandas 4 (AWS o 1700) / 7 (2600) / 28 (APT o 700*)
Click to expand...
Click to collapse
source
So you should google the bands your country/carrier is using and see if there's a match with the bands above, keep in mind LTE band 7 has been recently added so probably I wouldn't count that one.
I also leave here the rom template I modified from lg g2 in case someone finds it useful
https://drive.google.com/open?id=0B2yRgOWuE8rJZmlUaWF5aFg4Z1E
Get TWRP flashable supersu HERE
awesome dude!. Finally f*** MM can be rooted . Only one thing: Why P4P version and not the unbranded one, which is free of bloatware? Maybe you don't get it cause links broken, right? I have a v20b Poland unbranded kdz, if you want.
walterfuster said:
awesome dude!. Finally f*** MM can be rooted . Only one thing: Why P4P version and not the unbranded one, which is free of bloatware? Maybe you don't get it cause links broken, right? I have a v20b Poland unbranded kdz, if you want.
Click to expand...
Click to collapse
Because p4p has spanish and it doesn't pop the cust error at booting, if yours do so please upload it!
Not sure if the BAL one has spanish, but it definitely has no bloat or cust error.
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW574L07522NA3V41E0EL94/H440n20b_00_1025.kdz
Thank you very much!
jonixas said:
Not sure if the BAL one has spanish, but it definitely has no bloat or cust error.
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW574L07522NA3V41E0EL94/H440n20b_00_1025.kdz
Click to expand...
Click to collapse
Hmm, link seems to be down
Korelev said:
This is a short post theres not much to say since all these are stock roms. I just extracted the P4P MM rom from poland to make a TWRP flashable zip.
Main advantage is that we can keep recovery at the same time we run this MM rom so we can root by simply flashing supersu.
So here it is:
Polish v20b rom
In my case I experienced signal problems that were solved by flashing a v10i rom as base instead of the proposed v10f from where we got our aboot flashed, device didn't break. I think this is important for south american users because of different basebands, so I also uploaded that one here:
v10i ROM
For similar situation don't do any wipe and flash over that v10i the polish v20b rom.
I also leave here the rom template I modified from lg g2 in case someone finds it useful
https://drive.google.com/open?id=0B2yRgOWuE8rJZmlUaWF5aFg4Z1E
Get TWRP flashable supersu HERE
Click to expand...
Click to collapse
No network after installing mm, it says service disabled.
mayankjet said:
No network after installing mm, it says service disabled.
Click to expand...
Click to collapse
This is because your device is a dual sim version... this afternoon I'll make a flashable .zip file with the modem partition required for your device.
I mean... I don't guarantee it'll work but at least we'll try
Korelev said:
This is because your device is a dual sim version... this afternoon I'll make a flashable .zip file with the modem partition required for your device.
I mean... I don't guarantee it'll work but at least we'll try
Click to expand...
Click to collapse
Thanks
mayankjet said:
Thanks
Click to expand...
Click to collapse
Well, here it is so try it, as said before, I CANNOT guarantee it'll work. Even more, I couldn't get any h442 v20 rom so I used a LP modem image.
DOWNLOAD HERE
Just boot into TWRP and flash it
Korelev said:
Hmm, link seems to be down
Click to expand...
Click to collapse
Interesting, its straight from my csmg, and its the lastest one. Wget might work.
Korelev said:
Well, here it is so try it, as said before, I CANNOT guarantee it'll work. Even more, I couldn't get any h442 v20 rom so I used a LP modem image.
DOWNLOAD HERE
Just boot into TWRP and flash it
Click to expand...
Click to collapse
Didn't work. Thanks anyway. Guess i'll have to wait for a custom build.
jonixas said:
Interesting, its straight from my csmg, and its the lastest one. Wget might work.
Click to expand...
Click to collapse
Replace http://csmgdl.lgmobile.com/ with http://pkg02.xcdn.gdms.lge.com/ Tested,working.
FireMaid said:
Replace http://csmgdl.lgmobile.com/ with http://pkg02.xcdn.gdms.lge.com/ Tested,working.
Click to expand...
Click to collapse
Thanks, I guess thats sorta new.
I've been observing into the flashable zip, and see there's an aboot. bin which is from MM ROM I want to flash.
So, how is after flashing the bootloader is still unlocked??
walterfuster said:
I've been observing into the flashable zip, and see there's an aboot. bin which is from MM ROM I want to flash.
So, how is after flashing the bootloader is still unlocked??
Click to expand...
Click to collapse
It isn't from MM ROM, I replaced it with the modified one in order to TWRP wich is also included in the rom to pass signature verification.
Korelev said:
It isn't from MM ROM, I replaced it with the modified one in order to TWRP wich is also included in the rom to pass signature verification.
Click to expand...
Click to collapse
Sorry @Korelev, if I ask you so much, but I'm downloading Baltic kdz proposed here, and I'm gonna create a flashable zip with it.
Please, tell me if the steps I think to follow are correct or there's some of error with them:
Run WindowsLgFirmwareExtractor and do this:
Extract dz file from kdz. Discard the .dll ones.
Extract all files from dz file.
Do merge system-bin.
After that, in the folder where files were extracted, delete dz file, BackupGPT_xxxxxxxx.bin and all others that start with "system_xxxxxxx.bin".
Delete the character "_" and numbers in the name of each file.
So, between them, there'll be an aboot.bin file, which should be replaced with the patched one (?!).
Get system.img from merge_output folder, and put it with the other files. Delete that folder.
Download the template provided by you, extract it, get META-INF folder and add it to the other files.
Repack all this in a zip file and voilá. I got my TWRP flashable ROM.
walterfuster said:
Sorry @Korelev, if I ask you so much, but I'm downloading Baltic kdz proposed here, and I'm gonna create a flashable zip with it.
Please, tell me if the steps I think to follow are correct or there's some of error with them:
Run WindowsLgFirmwareExtractor and do this:
Extract dz file from kdz. Discard the .dll ones.
Extract all files from dz file.
Do merge system-bin.
After that, in the folder where files were extracted, delete dz file, BackupGPT_xxxxxxxx.bin and all others that start with "system_xxxxxxx.bin".
Delete the character "_" and numbers in the name of each file.
So, between them, there'll be an aboot.bin file, which should be replaced with the patched one (?!).
Get system.img from merge_output folder, and put it with the other files. Delete that folder.
Download the template provided by you, extract it, get META-INF folder and add it to the other files.
Repack all this in a zip file and voilá. I got my TWRP flashable ROM.
Click to expand...
Click to collapse
Almost exactly that, except for the extract part, you should paste all your files into the zip because it's signed, if you extract META-INF and create a new zip TWRP won't be able to process it, also you have to replace aboot with the one provided by our k10 friends and I also replaced recovery.bin with Fobos twrp one (honestly I wasn't so sure about that last one but I added it anyway to the script so you must delete the one you'll get on the extraction process or add that one in order to be able to boot with custom recovery after the flashing)
Korelev said:
Almost exactly that, except for the extract part, you should paste all your files into the zip because it's signed, if you extract META-INF and create a new zip TWRP won't be able to process it, also you have to replace aboot with the one provided by our k10 friends and I also replaced recovery.bin with Fobos twrp one (honestly I wasn't so sure about that last one but I added it anyway to the script so you must delete the one you'll get on the extraction process or add that one in order to be able to boot with custom recovery after the flashing)
Click to expand...
Click to collapse
Ok. One more thing: how you convert twrp.img to recovery.bin? cause if @Fobos531 makes an TWRP update, I wanna able to put it into the zip.
P.S.: TWRP Baltic MM flashable zip is ready
walterfuster said:
Ok. One more thing: how you convert twrp.img to recovery.bin? cause if @Fobos531 makes an TWRP update, I wanna able to put it into the zip.
P.S.: TWRP Baltic MM flashable zip is ready
Click to expand...
Click to collapse
You just rename it
Related
First things first, I hold no responsibility for bricked phones, you flash, you break, you fix.
This is the korean kk release just slightly modified by me to install without the need to freegee after installation so you should maintain your current recovery.
To get camera working I compiled the lg source release which was a pain in the ass because someone at LG doesn't know how to zip a file properly.
I trimmed it down by removing the Korean Olleh branding apps and boot/shutdown animations. Forgot, I deleted the LG Music app because it stinks. Doesn't do gapless mp3's which I have a lot of.
I replaced it with AOSP music app with gpu acceleration enabled so it scrolls smoothly and plays gapless mp3's.
No modem is flashed either, just make sure you are running the jb modem.
Only other thing I removed was the root checker daemon because it was spamming logcat (rctd: similar to this: http://forum.xda-developers.com/show....php?t=2267909)
Don't expect a lot of support for this, its not my work, I'm just sharing it because I feel that all our north american providers are going to screw us OG owners out of kitkat.
New rom is pre-rooted, flash super su if you want, but its not required.
Furthermore, new (June 4th) rom does not include busybox, just install from play store.
For all variants flash the main rom zip, boot it up, set up the phone:
Full Canadian E971/E973 Rom
You're done.
After some work from gourab4u, myself and Level99 testing we have sdcard support for you E970 folks.
Level99 built these flashable zip files for E970 AT&T people, credit to him for these zips.
This zip has all E970 patches from below applied, no need to flash any fixes:
Full E970 Rom
If you flashed the Canadian zip and want E970 specific fixes use these:
E970 External SD Fix: This flashes boot.img, framework-res.apk, and platform.xml to allow external sd to be seen on the E970.
AT&T Build.prop mod: This flashes modified build.prop to change phone to identify as US AT&T.
Both zips above combined into 1: This flashes the above two fixes and incorporates NFC fix if NFC is not working for you. Seems most people are saying NFC works as is from the main rom zip.
Install this to get the Accuweather widget to work:
Weather Theme
Enjoy.
Just a couple screenshots from On Screen Phone to show you guys whats coming...oh ya, I LOVE QSLIDE!
Paulicat said:
First things first, I hold no responsibility for bricked phones, you flash, you break, you fix.
This is the korean kk release just slightly modified by me to install without the need to freegee after installation so you should maintain your current recovery.
...
Enjoy.
Click to expand...
Click to collapse
You, sir, kick some serious ass. Looking forward to trying this out as soon as work is over today!
I'm already downloading. Will see how this behaves.. I'll post my feedback in around 2~3 hours.
Thanks for the hardwork Paulicat!
Paulicat said:
First things first, I hold no responsibility for bricked phones, you flash, you break, you fix.
This is the korean kk release just slightly modified by me to install without the need to freegee after installation so you should maintain your current recovery.
To get camera working I compiled the lg source release which was a pain in the ass because someone at LG doesn't know how to zip a file properly.
I trimmed it down by removing the Korean Olleh branding apps and boot/shutdown animations. Forgot, I deleted the LG Music app because it stinks. Doesn't do gapless mp3's which I have a lot of.
I replaced it with AOSP music app with gpu acceleration enabled so it scrolls smoothly and plays gapless mp3's.
No modem is flashed either, just make sure you are running the jb modem.
Only other thing I removed was the root checker daemon because it was spamming logcat (rctd: similar to this: http://forum.xda-developers.com/show....php?t=2267909)
Don't expect a lot of support for this, its not my work, I'm just sharing it because I feel that all our north american providers are going to screw us OG owners out of kitkat.
For E970 owners, I have no idea how your phones will react to the sdcard and red only led as this is the Korean rom...if someone who has an E970 can test/fix great but I can't help much in that regard.
There's a couple different ways to accomplish this so here goes easy way first:
2 Steps to follow:
flash this large rom zip, flash supersu.zip, boot it up, set up the phone:
http://www.androidfilehost.com/?fid=23487008491966757
Grab boot img from here (my kernel build for our cameras): http://www.androidfilehost.com/?fid=23501681358541637
Then reboot to bootloader and "fastboot flash boot boot.img"
You're done.
Alternative is to download the large rom, download the boot.img and replace the boot.img in the large rom with my boot.img from link above.
I have no computer at home so I can't do the boot.img swap and re-upload for the time being.
Large rom zip mirror provided by Liindberg in the international forum:
http://goo.gl/iRuRAI
Enjoy.
Click to expand...
Click to collapse
I have E970 AT&T I let you know. Downloading.
There will be a new boot.img soon, our north american kernel defconfigs have not been updated fully for kitkat changes.
Currently there is some logcat spam that will be gone soon.
Will also try doing a E970 specific kernel build, if someone can edit the storage_list.xml for you E970 peeps would help, I don't know anything about that part...
Thanks Pauli for the rom and kernel. I will be flashing your boot.img and see. While I was trying to port the kernel from Korean release, I have edited the storage_list.xml. I can help in editing the storage_list.xml for e970 for your rom, if you/someone can upload the framework-res.apk from your rom, as I do not have the connection to download GBs.Will report after flashing your compiled boot image.
Stuck at LG boot logo after reboot from bootloader.
Edit:
Come from CM11 nightly. TWRP 2.7.0.0.
After reboot to recovery and format cache/dalvik then reboot, the recovery said there is no OS installed
Stuck at LG boot logo after reboot from bootloader.
E970 ROM
RECOVERY TWRP KITKAT
external SD not working. camera working perfectly.
I have checked the ramdisk and saw many lines needs to be modified for external SD(probably) the fstab ones do have a "#" to comment out the sdcard1 mount code. after some changes in init.device.rc, I got a directory called sdcard1 created in media_rw how ever sdcard is not mounting. In settings, in the sd card section, there is an option called "mount sd card", however it is functionless. Can anyone of you please indicate what am I missing?
romeo_coi said:
Stuck at LG boot logo after reboot from bootloader.
Click to expand...
Click to collapse
Which recovery do you use?
I use CWM...
Paulicat said:
Which recovery do you use?
I use CWM...
Click to expand...
Click to collapse
I use TWRP. I'll switch to CWM and try again.
ChummyDays said:
The reason you guys are stuck on the lg logo is probably the same reason the people on e975 forums were. Your system partion is 1.5 gb and the Rom needs 2 gb to flash so it isn't flashing the entire thing . There is no easy fix yet. We'll have to wait
Click to expand...
Click to collapse
Good point. I thought E970's were closer to our canadian phones than that.
ChummyDays said:
The reason you guys are stuck on the lg logo is probably the same reason the people on e975 forums were. Your system partion is 1.5 gb and the Rom needs 2 gb to flash so it isn't flashing the entire thing . There is no easy fix yet. We'll have to wait
Click to expand...
Click to collapse
Attempting to build a regular flashable zip from philz recovery instead of the img files. This should get around the img file being 2gb.
Will upload later tonight.
[edit]It didnt build the zip correctly, failed to flash on my phone. Will have to look at alternatives.[/edit]
Paulicat said:
Attempting to build a regular flashable zip from philz recovery instead of the img files. This should get around the img file being 2gb.
Will upload later tonight.
[edit]It didnt build the zip correctly, failed to flash on my phone. Will have to look at alternatives.[/edit]
Click to expand...
Click to collapse
My Stop on LG Logo.
LG E970
Paulicat said:
[edit]It didnt build the zip correctly, failed to flash on my phone. Will have to look at alternatives.[/edit]
Click to expand...
Click to collapse
What if you try to unpack the system.img and from there build a flashable zip?
http://forum.xda-developers.com/showthread.php?t=2294909
jimbo77 said:
What if you try to unpack the system.img and from there build a flashable zip?
http://forum.xda-developers.com/showthread.php?t=2294909
Click to expand...
Click to collapse
Trying, symlinks are a pain in the ass...
Just the fact that this was even brought over to our devices from the Korean source is enough. I thought the geeb was on its last legs, this is a fantastic shot in the arm! Flashing shortly.
Paulicat said:
Trying, symlinks are a pain in the ass...
Click to expand...
Click to collapse
You could try my meta-inf folder here below which i use to got the Optimus g rom extracting.
https://drive.google.com/file/d/0B1u3mnq0nstfcVRDN3V3XzJBblE/
Also flashable boot.img without the need of fastboot.
https://drive.google.com/file/d/0B1u3mnq0nstfUU9RSDBpVzBKdVU/
I dont know or all the symlinks are really good correct but i think so cause i could flash my optimus g port build without any symlink error. i based my optimusgrom port on yours paulicat so it shouldnt be a problem at all lol goodluck further i hope that these files could help you guys further here also. I extracted the img file using ext2explore on windows.
I also got the boothang on the LG icon, system shows 1.5gb in CWM.
I have a working zip (regular zip not img based) now. I am taking an extra day to tweak it a bit more.
I'll also compile e970 specific kernel and release that as a separate boot.img.
LG still uses the nfc firmware file which is OK for Canadian phones but I don't know yet for e970.
Default kernel in the rom will be the Canadian kernel.
I'll upload it tomorrow night.
Bare with me as I don't have a working computer at home, bad luck killed my imac.
Sent from my SGP312 using XDA Free mobile app
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 !
Hi everyone,
I'm just here announcing for anyone who doesn't know and have the A2017U (USA Axon 7), The Nougat B15 update (SDCard Full Zip) is available online for those who need factory image base on Nougat B15.
Where to Download? :
* ZTE Axon 7 B15 (Nougat)
* Click / Tap " Software Updates "
Things to know about this Nougat B15 SDCard update zip :
FOR LOCK BOOTLOADER USERS :
1- This update.zip will perform a FDR / Factory Reset
NOTE : save everything to your SDCard or PC before proceeding with B15 update.zip installation
FOR UNLOCK BOOTLOADER USERS :
1- Same as Lock bootloader users. (READ ABOVE)
2- This zip file will replace current recovery for the stock B15 recovery.
3- Your bootloader will remain unlock, BUT you no longer will be able to execute fastboot commands.
I just want to Thank ( BIG THANK YOU ) to our hero @SShasan from Z-Community for this update / factory images file, WE wouldn't have this file if wasn't for him.
Always good to have another image.
@DrakenFX, I saw the update when I checked a few days ago. Too busy to make a post about it.
In any event, looks like they're including a fastboot.img again. Have you had a chance to compare this against previous fastboot.img's? My guess is it's similar/identical to b29.
For those that want to preserve fastboot commands and twrp (this too should be flashable in twrp as b29 was), just edit the update script to remove the lines for fastboot, recovery. Probably a good idea to leave the format user data if you're switching between roms.
These lines specifically in update-script.
Code:
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
gpz1100 said:
@DrakenFX, I saw the update when I checked a few days ago. Too busy to make a post about it.
In any event, looks like they're including a fastboot.img again. Have you had a chance to compare this against previous fastboot.img's? My guess is it's similar/identical to b29.
For those that want to preserve fastboot commands and twrp (this too should be flashable in twrp as b29 was), just edit the update script to remove the lines for fastboot, recovery. Probably a good idea to leave the format user data if you're switching between roms.
These lines specifically in update-script.
Code:
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
Click to expand...
Click to collapse
What is the process for deleting these lines? Last time I tried it wouldn't flash.
No need to quote an entire post when your reply immediately follows.
I use notepad++ to edit. Regular notepad does something to end of line indicators. Use 7zip to extract and update the script file.
gpz1100 said:
@DrakenFX, I saw the update when I checked a few days ago. Too busy to make a post about it.
In any event, looks like they're including a fastboot.img again. Have you had a chance to compare this against previous fastboot.img's? My guess is it's similar/identical to b29.
For those that want to preserve fastboot commands and twrp (this too should be flashable in twrp as b29 was), just edit the update script to remove the lines for fastboot, recovery. Probably a good idea to leave the format user data if you're switching between roms.
These lines specifically in update-script.
Code:
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
Click to expand...
Click to collapse
Those 2 lines and the last line : Wipe Data
Well if you want to keep data if not , just leave it there
I thought not formatting data could lead to decryption issues when switching between rom bases. For example LOS --> Stock.
gpz1100 said:
I thought not formatting data could lead to decryption issues when switching between rom bases. For example LOS --> Stock.
Click to expand...
Click to collapse
If you switching from NON-Stock ROM to LOS base Roms, so yeah DATA needs to be wipe. Otherwise you can remove that line...Is not like TWRP doesn't have the ability to wipe data hehehe :silly:
Is it possible to downgrade back to b29 if nougat goes haywire on me?
DrakenFX said:
If you switching from NON-Stock ROM to LOS base Roms, so yeah DATA needs to be wipe. Otherwise you can remove that line...Is not like TWRP doesn't have the ability to wipe data hehehe :silly:
Click to expand...
Click to collapse
Is modifying the update script will remove zte signed certif to flash in Stock recovery, correct?
If you Modify the file only way of flashing isTwrp.
Sent from my ZTE A2017U using Tapatalk
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
XBlackChaosX said:
Is it possible to downgrade back to b29 if nougat goes haywire on me?
Click to expand...
Click to collapse
Yes you can go back using draken b29 modded zip or flashing Zte b29 firmware..
Sent from my ZTE A2017U using Tapatalk
DrakenFX said:
Hi everyone,
I'm just here announcing for anyone who doesn't know and have the A2017U (USA Axon 7), The Nougat B15 update (SDCard Full Zip) is available online for those who need factory image base on Nougat B15.
Where to Download? :
* ZTE Axon 7 B15 (Nougat)
* Click / Tap " Software Updates "
Things to know about this Nougat B15 SDCard update zip :
FOR LOCK BOOTLOADER USERS :
1- This update.zip will perform a FDR / Factory Reset
NOTE : save everything to your SDCard or PC before proceeding with B15 update.zip installation
FOR UNLOCK BOOTLOADER USERS :
1- Same as Lock bootloader users. (READ ABOVE)
2- This zip file will replace current recovery for the stock B15 recovery.
3- Your bootloader will remain unlock, BUT you no longer will be able to execute fastboot commands.
I just want to Thank ( BIG THANK YOU ) to our hero @SShasan from Z-Community for this update / factory images file, WE wouldn't have this file if wasn't for him.
Click to expand...
Click to collapse
How can I get back fastboot commands?
@DrakenFX
On B29 I was able to add the modified update-script file using 7-zip without any issues. On B15 it's rejecting it with a 'not implemented error' from 7-zip. Is there a different tool to use to manipulate these archive files?
Thanks!
Edit: B15, not B19
sinekm1 said:
How can I get back fastboot commands?
Click to expand...
Click to collapse
Check edl thread.
I just updated to 7.1.1 and would like roll back to 7.1.0. Will downloading the .zip on the SD card of the phone and running it re-install 7.1.0 on my phone?
Thanks
Itsmejayson said:
I just updated to 7.1.1 and would like roll back to 7.1.0. Will downloading the .zip on the SD card of the phone and running it re-install 7.1.0 on my phone?
Thanks
Click to expand...
Click to collapse
There is no 7.1.0, just 7.0. What issue are you having with 7.1.1?
Yes, flashing the full firmware image from the zte site will downgrade it to 7.0.
gpz1100 said:
There is no 7.1.0, just 7.0. What issue are you having with 7.1.1?
Yes, flashing the full firmware image from the zte site will downgrade it to 7.0.
Click to expand...
Click to collapse
Thanks for your reply. Some apps I was using does not work with the March security patch.
It seems like the mirror for the download is down. Does anyone has another link?
Thanks
Itsmejayson said:
Thanks for your reply. Some apps I was using does not work with the March security patch.
It seems like the mirror for the download is down. Does anyone has another link?
Thanks
Click to expand...
Click to collapse
Indeed, looks like they pulled it. I wonder if this means the B19 firmware package will be available shortly.
Here's another mirror on afh
https://www.androidfilehost.com/?fid=673368273298940518
gpz1100 said:
There is no 7.1.0, just 7.0. What issue are you having with 7.1.1?
Yes, flashing the full firmware image from the zte site will downgrade it to 7.0.
Click to expand...
Click to collapse
bro u can help me
im on 7.1.1 without root and lock bootloader
i want back to 6.0. for unlock the bootloader u have idea how i can back
really im tired
mr.mgmg said:
bro u can help me
im on 7.1.1 without root and lock bootloader
i want back to 6.0. for unlock the bootloader u have idea how i can back
really im tired
Click to expand...
Click to collapse
Go to zte and download b29, put on sd and go to settings/updates.
lafester said:
Go to zte and download b29, put on sd and go to settings/updates.
Click to expand...
Click to collapse
Zte pulled the image for B29 when they posted B15. Looks like in the last week or so they pulled the B15 image too.
Hey guys.
I'm trying to update my F1 but since it's rooted, OTA is not happening (it caused my phone to TWRP bootloop) and other's have reported that they had a better working version flashing the update via the SP Flash Tool. So last time I tried using the Flash Tool was a mess getting it to work (because drives and all) so I was hoping someone might have an image of this update that I could flash via TWRP or is there's a way to convert the extracted RAR folder. Thanks for any help.
David C.
mantarkus said:
Hey guys.
I'm trying to update my F1 but since it's rooted, OTA is not happening (it caused my phone to TWRP bootloop) and other's have reported that they had a better working version flashing the update via the SP Flash Tool. So last time I tried using the Flash Tool was a mess getting it to work (because drives and all) so I was hoping someone might have an image of this update that I could flash via TWRP or is there's a way to convert the extracted RAR folder. Thanks for any help.
David C.
Click to expand...
Click to collapse
The OTA update may be used in Twrp, with some edits, depending on what all has been changed on phone .
I do not have time this weekend to look at it. But can in few days
***UPDATE***
This can update from version 20190316 only
If you open the update.zip you have from the OTA and replace the 'updater-script' with the one attached here. It should perform the update. Remove the ".txt" from the file name first
I say should , because if you have done significant modifications then that may effect its effectiveness.
@mantarkus
I put together an OTA style zip, that has the same images as sp flash install, with only exception being the preloader. The preloader from stock OTA update is different format to the preloader used in flash tool. ( Assume it has to do with the way it gets intalled ) So I have the preloader from OTA in the zip.
I have not uploaded the zip, or tested it out. Before i use the data to upload it. Let me know if you are interested.
mrmazak said:
@mantarkus
I put together an OTA style zip, that has the same images as sp flash install, with only exception being the preloader. The preloader from stock OTA update is different format to the preloader used in flash tool. ( Assume it has to do with the way it gets intalled ) So I have the preloader from OTA in the zip.
I have not uploaded the zip, or tested it out. Before i use the data to upload it. Let me know if you are interested.
Click to expand...
Click to collapse
Hey, thanks a lot. Yes, I am interested. Is this flashable via TWRP?
David C.
mantarkus said:
Hey, thanks a lot. Yes, I am interested. Is this flashable via TWRP?
David C.
Click to expand...
Click to collapse
It should be. Have not tested it. So busy lately.
Best option is to use the flash tool, but after I test this, I will uploaded it. But who knows , rumor us, there had been updated every 2 months so far. Maybe new update is out soon anyway
Anyone know if this is working on the normal F1 (Non-play) version? With the minimal differences including same SoC shouldnt it work? Anyone tested?
wtf rip, i refreshed and i landed here somehow (by my own fault probably). Mean't for: https://forum.xda-developers.com/android/development/twrp-twrp-3-3-0-0-umidigi-f1-play-t3933829
flashing this recovery on my non-play if anyone knows. Soz '
Nexus Radical said:
Anyone know if this is working on the normal F1 (Non-play) version? With the minimal differences including same SoC shouldnt it work? Anyone tested?
wtf rip, i refreshed and i landed here somehow (by my own fault probably). Mean't for: https://forum.xda-developers.com/android/development/twrp-twrp-3-3-0-0-umidigi-f1-play-t3933829
flashing this recovery on my non-play if anyone knows. Soz '
Click to expand...
Click to collapse
Yes, I have been told it does work for both play and not play. I am using the ported version of that official build , done by "ghost"
Oh right. I did a bit of searching before asking for a link but I did find this
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Will this work fine? I know it's a test version. As long as flashing works properly, decryption and mtp works I guess that's all I need?
Otherwise what would you say is the best available twrp version right now? ?
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Jonas336ts said:
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Click to expand...
Click to collapse
i would like to hear more about this
Can you make a video?
I too would love to hear more about this and exactly what to do
Yap please tutorial post how to do this
Used that method on p20 pro Indeed...but seemed that it did not work anymore since Android 9.0 or 9.1
deltaman83 said:
Used that method on p20 pro Indeed...but seemed that it did not work anymore since Android 9.0 or 9.1
Click to expand...
Click to collapse
Will Work, if you have a pc and Micro sdcard in phone.
Tabs78 said:
Can you make a video?
Click to expand...
Click to collapse
I make a video. Video will Come on Friday this month. I send link.
Have anybody tried this method? Any success?
Jonas336ts said:
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Click to expand...
Click to collapse
Interesting. I think you should provide more details:
1. Emui Version
2. Apps or tools used to unpacked repacked update app.
3. If there needs sign some files and tools used for that
4. other infos.
Jonas336ts said:
Will Work, if you have a pc and Micro sdcard in phone.
I make a video. Video will Come on Friday this month. I send link.
Click to expand...
Click to collapse
Where is the video link?
Jonas336ts said:
I know I need to have an unlocked bootloader to root Huawei phones. But I have found a new solution where there is no need to unlock the bootloader. Now I want to explain it. Huawei has a feature called sdcard update which flashes phone from sdcard. It made me think if I unpacked update.app and patched ramdisk_recovery by magic manager, I also replaced the real img with the patched img. Now I flashed it, result success. I magically checked the app and magically it was successfully installed. I have root access now.
Sorry for my poor English, I used Google translate.
Click to expand...
Click to collapse
As it successfull rooted as you say that so next we must go to work to cook some custom ROM
Josh said:
As it successfull rooted as you say that so next we must go to work to cook some custom ROM
Click to expand...
Click to collapse
You can't make a custom rom without sources. Besides, we still haven't got any tutorial regarding how to do this method.
Please, can you make a tutorial and show us a video @Jonas336ts
Too many pictures on first post.
Ok so I think I understand how he did it. Magisk has an option to manually patch a file. So basically, we use this guide to patch ramdisk_recovery.img : https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Now here comes another question : How do we get ramdisk_recovery.img? Simple. Find your ROM's update.zip file. Then, open update.app (or whatever it is called) using 7-zip and extract ramdisk_recovery from within. Then patch it with Magisk and then put it inside the update.app. Put update.app in your sdcard/flash drive and flash it using *#*#2846579#*#* method. Does it sound simple? Not really. There are a few issues with this and it sounds pretty strange that it works.
1.You need to sign the update.app file using Huawei keys. How did OP get these keys?
2.You can't simply replace files inside the update.app, unless you unpack and pack it, but again check reason 1 (unless the method has changed/I knew it wrong all this time)
3.It's impossible for the ROM to boot after doing this method. How can you still have root access when your bootloader is locked?
4.Doesn't EMUI know the update.app file was tempered? If it was that simple to flash stuff then we would have had a root guide like this a while ago.
Either way, this is my 2 cents. I am waiting for OP's video. But judging he/she's been inactive for a week, I doubt it.
EDIT
This method is impossible to be done. Reason being : There is absolutely no WAY you can get the update.app file for your rom MANUALLY. Unless you find a way to get Firmware Finder back, don't get your hope so high. I am sorry.
Another update : Ramdisk_recovery is not the type of IMG that Magisk patches. You need ramdisk.img. So basically this seems very fake. Still no tutorial.
AnotyClaws said:
Another update : Ramdisk_recovery is not the type of IMG that Magisk patches. You need ramdisk.img. So basically this seems very fake. Still no tutorial.
Click to expand...
Click to collapse
Try to find his other posts or topics. Pay attention to the date.
badmania98 said:
Try to find his other posts or topics. Pay attention to the date.
Click to expand...
Click to collapse
I did. Still nothing
I am trying my own method of rooting however I might risk bricking my phone. idk how I will sign the update.app or how to flash the img file with a locked bootloader...
In theory you should modify a dload firmware that can be written. But I suggest you to stay away.