Hey all,
Came from the Nexus 4 forums, just recently picked up a VZW Moto X. I have a Dell Venue 8 Pro with Windows 8.1, and RSD Lite doesn't work on it. I wanted to restore to 4.2.2 and then later after rooting, back to 4.4 stock and RSD Lite wouldn't see my phone, but adb and fastboot would. I made a quick script which will restore your Moto X, after of course, downloading the correct firmware from http://sbf.droid-developers.org/ghost_rcica/list.php. This is tested working on VZW and if there is enough interest, I can make more for the T-Mobile and AT&T versions.
Instructions:
1. Download and extract the kit zip. It includes install.bat (the script), mfastboot (found on a file share site, if someone is due credit for this please let me know and I'll update) and adb. with associated files.
2. Download and extract your Moto X firmware.
3. Drop the files from the kit in the file with all the extracted Moto X firmware files.
4. Ensure your phone is backed up, if applicable.
5. Plug your phone in and make sure the drivers are loaded (install Motorola Device Manager if needed).
6. Open CMD prompt and navigate to folder with your Moto X firmware files and the files from the kit.
7. Type
install.bat
Click to expand...
Click to collapse
and wait for process to complete. Note the system install takes a bit longer than the rest, as it is a big file.
Please feel free to tweak the batch file if you need. Enjoy!
EDIT: This will not work for anything but VZW as of right now as there are some carrier specific commands in there. Anyone need this for a different carrier? I can download the firmware you need it for and make the batch.
Nice!!!!!! And as you said in the EDIT
Can you provide a file for this carrier?
ClaroChile_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-25_cid12_CFC_1FF_svc.xml.zip
Click to expand...
Click to collapse
The 4th link in this list
http://sbf.droid-developers.org/ghost/list.php
I'll be appreciated.
Thank you very much for your work.
This wont work with the Sprint Moto X, right?
Edit: Didnt see the bold text...lol. I know that KitKat is going to be pushed to the Sprint Variant next week so if you could make one then, that'd be great
I'm getting a 404 - Not Found error on the Kit download link.
Does this preserve user data?
andino said:
Does this preserve user data?
Click to expand...
Click to collapse
I'm pretty positive it doesn't. All the partitions get wiped and flashed to stock.
cvhovey said:
I'm getting a 404 - Not Found error on the Kit download link.
Click to expand...
Click to collapse
It's hosted on XDA, I don't know why that would be.
d14gvn said:
Nice!!!!!! And as you said in the EDIT
Can you provide a file for this carrier?
The 4th link in this list
http://sbf.droid-developers.org/ghost/list.php
I'll be appreciated.
Thank you very much for your work.
Click to expand...
Click to collapse
Sure, I am on a slow internet provider right now so I'll try to get it done by tomorrow. Gotta let it download tonight.
karn101 said:
I'm pretty positive it doesn't. All the partitions get wiped and flashed to stock.
Click to expand...
Click to collapse
Correct, this is a complete wipe and return to stock (or whatever version you download from the site).
Most people will not need this kit. If RSD Lite works on your machine, I would recommend using that as it is widely accepted.
Claro Chile Install added. Just drop the file inside the ZIP into the directory with the rest of the files, and run ClaroChileInstall.bat instead of the regular install.bat.
I'd be happy to have a version for my TMo DevEd phone. No big rush, but it would be great to have this on hand since I know I'll be restoring to stock at some point soon.
Thank you!
varxx said:
I'd be happy to have a version for my TMo DevEd phone. No big rush, but it would be great to have this on hand since I know I'll be restoring to stock at some point soon.
Thank you!
Click to expand...
Click to collapse
No problem! I'll try to whip something up tonight.
jlink38 said:
Hey all,
Came from the Nexus 4 forums, just recently picked up a VZW Moto X. I have a Dell Venue 8 Pro with Windows 8.1, and RSD Lite doesn't work on it. I wanted to restore to 4.2.2 and then later after rooting, back to 4.4 stock and RSD Lite wouldn't see my phone, but adb and fastboot would. I made a quick script which will restore your Moto X, after of course, downloading the correct firmware from http://sbf.droid-developers.org/ghost_rcica/list.php. This is tested working on VZW and if there is enough interest, I can make more for the T-Mobile and AT&T versions.
Instructions:
1. Download and extract the kit zip. It includes install.bat (the script), mfastboot (found on a file share site, if someone is due credit for this please let me know and I'll update) and adb. with associated files.
2. Download and extract your Moto X firmware.
3. Drop the files from the kit in the file with all the extracted Moto X firmware files.
4. Ensure your phone is backed up, if applicable.
5. Plug your phone in and make sure the drivers are loaded (install Motorola Device Manager if needed).
6. Open CMD prompt and navigate to folder with your Moto X firmware files and the files from the kit.
7. Type and wait for process to complete. Note the system install takes a bit longer than the rest, as it is a big file.
Please feel free to tweak the batch file if you need. Enjoy!
EDIT: This will not work for anything but VZW as of right now as there are some carrier specific commands in there. Anyone need this for a different carrier? I can download the firmware you need it for and make the batch.
Click to expand...
Click to collapse
Will this work on the Verizon Developer Edition Moto X? I want to unroot and relock the bootloader.
Not sure. As long as you have the proper ROM, all this does is flash it.
Sent from my XT1060 using Tapatalk
Does it work in xt1058 from AT&T?
Sent from my XT1058 using xda app-developers app
I would like to thank the OP. This worked perfectly. The exchange email part of 4.4 is broken, so I needed to downgrade so I could check email without buying a play store application. Thanks, again.
jlink38 said:
Hey all,
Came from the Nexus 4 forums, just recently picked up a VZW Moto X. I have a Dell Venue 8 Pro with Windows 8.1, and RSD Lite doesn't work on it. I wanted to restore to 4.2.2 and then later after rooting, back to 4.4 stock and RSD Lite wouldn't see my phone, but adb and fastboot would. I made a quick script which will restore your Moto X, after of course, downloading the correct firmware from http://sbf.droid-developers.org/ghost_rcica/list.php. This is tested working on VZW and if there is enough interest, I can make more for the T-Mobile and AT&T versions.
Instructions:
1. Download and extract the kit zip. It includes install.bat (the script), mfastboot (found on a file share site, if someone is due credit for this please let me know and I'll update) and adb. with associated files.
2. Download and extract your Moto X firmware.
3. Drop the files from the kit in the file with all the extracted Moto X firmware files.
4. Ensure your phone is backed up, if applicable.
5. Plug your phone in and make sure the drivers are loaded (install Motorola Device Manager if needed).
6. Open CMD prompt and navigate to folder with your Moto X firmware files and the files from the kit.
7. Type and wait for process to complete. Note the system install takes a bit longer than the rest, as it is a big file.
Please feel free to tweak the batch file if you need. Enjoy!
EDIT: This will not work for anything but VZW as of right now as there are some carrier specific commands in there. Anyone need this for a different carrier? I can download the firmware you need it for and make the batch.
Click to expand...
Click to collapse
Claro Puerto Rico
jlink38 said:
Claro Chile Install added. Just drop the file inside the ZIP into the directory with the rest of the files, and run ClaroChileInstall.bat instead of the regular install.bat.
Click to expand...
Click to collapse
Can you make it to Claro Puerto Rico?
Android 4.2.2
Blur_Version.139.12.35.ghost_row.AmericaMovil.en.PR > http://sbf.droid-developers.org/download.php?device=0&file=51
Thanks!
Updated
I use the Moto X Install Kit.zip and if works without problem in the Claro Puerto Rico firmware. Thanks a lot!!!
Can you please work on a version for the ATT MotoX? I'll try to look through what you have done and do it manually for myself... But, I've had so many issues with Win8 and have wasted so much time... I don't know if I'll be able to tackle it....
jlink38 said:
No problem! I'll try to whip something up tonight.
Click to expand...
Click to collapse
Have you had time to do this for the T-Mobile Dev Version
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hello my friends.
What is mean the commands below?
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear
Related
Hi fellows,
I contacted the Motorola support and they said that Vivo's Motorola RAZR is about to get an update to improve the cellphone performance. When it is ready, it will become available by OTA system.
Thanks,
Ronan.
Hello,
I got my phone on Vivo, and it came with version 651.73.240.XT910.Vivo.en.BR.
This version is very buggy and some bad localization, like for example the function to merge contacts was translated to "Conferência", wich means "Conference", and clearly does not have anything to do with "Merge".
I then used Motorola Software Update to download an update, and since it was failing to update the phone, I used RSD Lite to manually update it.
Now I am using 651.73.2062.XT910.Vino.en.BR, and the phone performance is much better, the localization is fixed but I still see some bugs with the camera app and 3G modem dropping data, but its still better than stock.
You say that this OTA will be appied on top of 2062, or maybe its the 2062 itself but an OTA version?
Or its a complete new OTA that can be applied on top of 2062 and 240?
casaroli said:
Hello,
I got my phone on Vivo, and it came with version 651.73.240.XT910.Vivo.en.BR.
This version is very buggy and some bad localization, like for example the function to merge contacts was translated to "Conferência", wich means "Conference", and clearly does not have anything to do with "Merge".
I then used Motorola Software Update to download an update, and since it was failing to update the phone, I used RSD Lite to manually update it.
Now I am using 651.73.2062.XT910.Vino.en.BR, and the phone performance is much better, the localization is fixed but I still see some bugs with the camera app and 3G modem dropping data, but its still better than stock.
You say that this OTA will be appied on top of 2062, or maybe its the 2062 itself but an OTA version?
Or its a complete new OTA that can be applied on top of 2062 and 240?
Click to expand...
Click to collapse
Hi fellow!
I'm pretty sure it will be 2062.
I haven't noticed that the version here on XDA is 2062. I thought it was 206 and, since mine is 240, then I hasn't updated
Can you help me to update my RAZR to 2062? I has a very big experience with Samsung devices, but to achieve it, I hard bricked my Galaxy TAB Since I really don't want to be without a cellphone and Samsung devices doesn't use fastboot, can you give some tips how can I flash this update by fastboot?
By the way, I have something that might be useful for Brazilian RAZR owners:
From Motorola support chat:
Marivaldo: A informação que temos é que será o primeiro aparelho Motorola a receber a versão 4.0 do android, até segundo semestre de 2012.
(The information available to us is that Motorola RAZR will be the first phone to receive android 4.0, which will happen until second semester 2012)
Ronan Jardim : nossa, muito bom!
Ronan Jardim : obrigado!
Ronan Jardim : então a Motorola do Brasil atualizará sim?
(Very good, thanks, so Motorola will update this device in Brazil also, won't it?)
Marivaldo: Sim, sem sobra de dúvidas.
Marivaldo: É uma atualização aguardada por todos.
(For sure, it is an update expected by everyone)
...
So, how much do you believe that?!
Ronan
Until second semester?
Oh, lord. If Moto keeps following their schedule the way they're doing now, it probably means we won't see this ICS update any time before october.
brunoerre said:
Until second semester?
Oh, lord. If Moto keeps following their schedule the way they're doing now, it probably means we won't see this ICS update any time before october.
Click to expand...
Click to collapse
Well, considering my past experience with Motorola Brazil, I'll be glad if Moto update RAZR no matter when
And also, I have lost faith in Motorola's schedules a long time ago
Nevermind
I managed to do that... very simple and straightforward...
I'm now with 2062 version that was build on Dec 6 (or 16 can't remember), the other was built on 20 Oct.
I'll post the differences I saw tomorrow.
Thanks,
Ronan
Ronis_BR said:
Nevermind
I managed to do that... very simple and straightforward...
I'm now with 2062 version that was build on Dec 6 (or 16 can't remember), the other was built on 20 Oct.
I'll post the differences I saw tomorrow.
Thanks,
Ronan
Click to expand...
Click to collapse
Would you mind to show how you managed to update? Appreciate that! Thanks!
njoismartguys said:
Would you mind to show how you managed to update? Appreciate that! Thanks!
Click to expand...
Click to collapse
Start here: ht tp: // direct.motorola.com/hellomoto/support/update/[/url]
select your country, then your carrier, or "retail" for retail version.
Download that software and *DO NOT INSTALL TO "c:\program files (x86)\motorola mobility\software update" because the file paths will get too long and you will have problems.
To avoid these long filepaths problems, install it to somewhere else shorter, like for example "c:\moto"
Run the software updater while connected to the Internet, connect your phone to the computer and follow the steps on the update.
The do not forget to root again
Good luck!
casaroli said:
Start here: ht tp: // direct.motorola.com/hellomoto/support/update/[/url]
select your country, then your carrier, or "retail" for retail version.
Download that software and *DO NOT INSTALL TO "c:\program files (x86)\motorola mobility\software update" because the file paths will get too long and you will have problems.
To avoid these long filepaths problems, install it to somewhere else shorter, like for example "c:\moto"
Run the software updater while connected to the Internet, connect your phone to the computer and follow the steps on the update.
The do not forget to root again
Good luck!
Click to expand...
Click to collapse
I wasn't able to perform the update with software update by motorola...
The only way possible was to use RSD Lite and fastboot files here.
Thanks!
Ronan
Ronis_BR said:
I haven't noticed that the version here on XDA is 2062. I thought it was 206 and, since mine is 240, then I hasn't updated
Click to expand...
Click to collapse
I was confused also when I first saw. Perhaps someone need to notify the EternityProject thread about the version number so it does not cause more confusion.
I still can't post to that thead , so maybe someone else could do it.
BTW, After the update, running Motorola Software Update does not update anymore, since we are already at the latest version.
I guess using Motorola Software Update is the safest way to upgrade and for sure it should not void your warranty.
Thanks
casaroli said:
I was confused also when I first saw. Perhaps someone need to notify the EternityProject thread about the version number so it does not cause more confusion.
I still can't post to that thead , so maybe someone else could do it.
BTW, After the update, running Motorola Software Update does not update anymore, since we are already at the latest version.
I guess using Motorola Software Update is the safest way to upgrade and for sure it should not void your warranty.
Thanks
Click to expand...
Click to collapse
Software Update will do exactly what RSD Lite and the fastboot files is doing. There isn't anyway to know which kind of method was used to update the cellphone. So, if you have a Vivo cellphone and flashed a Vivo stock ROM from here, if you don't do anything wrong, then you are "safe".
Ronis_BR said:
I wasn't able to perform the update with software update by motorola...
The only way possible was to use RSD Lite and fastboot files here.
Thanks!
Ronan
Click to expand...
Click to collapse
Did you install to the default location? Open the software update folder, find the ZIP and try to extract it, you will see that it will create an empty folder (with very long name), and will give an error to extract the file contents. Motorola Software Update just fails to install the update and does not describe the error. Using windows to extract, you should see the error.
Moving the whole software update folder to c:\moto should work, since the extraction works.
If it does not work, you can manually flash by RSD Lite, and use the downloaded zip in the software update folder.
casaroli said:
Did you install to the default location? Open the software update folder, find the ZIP and try to extract it, you will see that it will create an empty folder (with very long name), and will give an error to extract the file contents. Motorola Software Update just fails to install the update and does not describe the error. Using windows to extract, you should see the error.
Moving the whole software update folder to c:\moto should work, since the extraction works.
If it does not work, you can manually flash by RSD Lite, and use the downloaded zip in the software update folder.
Click to expand...
Click to collapse
I think that Motorola Software Upgrade doesn't need to extract update.zip. Normally, it is pushed to the phone and than extracted. If update.zip is extracted in Windows (NTFS partition) I think that it will have problems with permissions and links that must be defined in RAZR's ext3 partition.
But it is only my guess
I'm pretty sure that Software Updates (and RSD Lite) extracts the ZIP because I could see the empty folder created on the software update folder.
Also, the contents of the ZIP are not the actual files on the phone (i.e. the ext3 fs contents), they are flash images, like radio.img, filesystem image, webtop, and so on. Also, there is the file mapping so software update knows where to flash each image.
Extracting this file should not lead to any error on permissions.
I'm not at my computer right now, so I'm not able to extract the zip contents and post here. I could do it later.
casaroli said:
I'm pretty sure that Software Updates (and RSD Lite) extracts the ZIP because I could see the empty folder created on the software update folder.
Also, the contents of the ZIP are not the actual files on the phone (i.e. the ext3 fs contents), they are flash images, like radio.img, filesystem image, webtop, and so on. Also, there is the file mapping so software update knows where to flash each image.
Extracting this file should not lead to any error on permissions.
I'm not at my computer right now, so I'm not able to extract the zip contents and post here. I could do it later.
Click to expand...
Click to collapse
Yes, if it is images than you are right!
Unfortunately, I have already updated my RAZR, so we can't test it
Yes, I think you are right.
I saw the file in software upgrade's folder and it is the same file (same md5sum and name) I have flashed using RSD Lite 5.6.
Well, here the differences I saw:
- As casaroli commented, some translations were fixed.
- GPS is 100x faster. I think they really enable AGPS. I can see the option in GPS Status apk, which didn't exist before. In a cold start and using the network (AGPS), I got a satellite fix in less than 25 seconds inside my home (near a window obviously).
- The operational system is much more stable.
- I think (didn't test it) that WiFi connection is better.
- Windows Live apk is installed.
- Compass problem wasn't solved
It is a very good update, my RAZR is much more stable and I recommend to everyone who have a Vivo RAZR.
I won't explain how to use RSD Lite since you can brick your device. First, try what casaroli said and try to update by Software Upgrade by Motorola. It is the safest way always.
Now we have to see how can we flash android 2.3.6 here
casaroli said:
Start here: ht tp: // direct.motorola.com/hellomoto/support/update/[/url]
select your country, then your carrier, or "retail" for retail version.
Download that software and *DO NOT INSTALL TO "c:\program files (x86)\motorola mobility\software update" because the file paths will get too long and you will have problems.
To avoid these long filepaths problems, install it to somewhere else shorter, like for example "c:\moto"
Run the software updater while connected to the Internet, connect your phone to the computer and follow the steps on the update.
The do not forget to root again
Good luck!
Click to expand...
Click to collapse
Thanks! The ROM on the official ROM page from the development section has 2062 (as you figured already)
Ronis_BR said:
Now we have to see how can we flash android 2.3.6 here
Click to expand...
Click to collapse
Yes looking forward for this. Plainly I am so disappointed with Moto's update schedule for different regions. Thought Google acquisition would speed up the process, but doesn't seem like it.
MY I updated to 2.3.6
Update via RSD LITE
Man, can you please describe exactly what you did? Is your razr from vivo?
Thanks and great job!
Ronan
Sent from my XT910 using xda premium
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 !
Thanks to everyone over the past almost six years who helped me get to the point where I am so far. Glad to help others in what ways I can.
Thanks to @bweN diorD for his Verizon LG G3 VS985 repository. Inspired me to do this for the VK810.4G, although it took me six months of considering doing it before I was motivated enough to.
Thanks to @Papay346 for purchasing and testing the 22B_00 TOT file from a Chinese website, and for sharing it with us! His original post here http://forum.xda-developers.com/showpost.php?p=66089535&postcount=6.
I intend this as a repository for all OTA, .img, KDZ and TOT files relating to each official (and leaks if we ever find any, which will be indicated as unofficial/leak/whatever) LG release. If not noted otherwise, all files are official (unaltered from the official stock release).
The latest files will always be at the top with the oldest always at the bottom.
All downloads are available in my VK810.4G section on Android File Host in the OTA, IMG or KDZ and TOT subfolder. Below is merely a list of what's available there. If you don't know what to do with these, you don't need them.
36B_00 - Lollipop v5.0.2
KDZ: VK81036B_00-Lollipop_5.0.2_KDZ.7z
IMGs:VK81036B_00_5.0.2_system.img.7z
VK81036B_00_5.0.2_all_but_system.img.7zOTA: VK810.4G_altev_35A_08to36B_00_5.0.2_OTA.7z
35A_08 - Lollipop v5.0.2
KDZ: VK81035A_08 - Lollipop 5.0.2.KDZ - MD5 hash inside.7z
IMGs:VK81035A_08 5.0.2 system.img.7z
VK81035A_08 5.0.2 all but system.img.7zOTA: VK810.4G_altev_24A_00to35A_08_5.0.2_OTA.7z
24A_00 - KitKat 4.4.2
KDZ: VK81024A_00.KDZ - KitKat 4.4.2.7z
IMGs:Verizon LG G Pad 8.3 VK810.4G 24A system.img.7z
boot.img
modem.imgOTA: Not captured yet.
23A_04 - KitKat 4.4.2
KDZ: VK81023A_04.KDZ file with MD5 hash inside - NON-FLASHABLE - KitKat 4.4.2.zip
IMGs:VK810.4G Verizon LG G Pad 8.3 23A_04 system.img partition file.7z
VK810.4G Verizon LG G Pad 8.3 23A_04 other partition img files.7z
VK810.4G Verizon LG G Pad 8.3 23A_04 extracted from KDZ Web8064.dll - don't know if it's useful.7zOTA: Not captured yet.
22B_00 - KitKat 4.4.2 (TOT available)
TOT: VK81022B_00.TOT file with MD5 hash inside - KitKat 4.4.2.7z
DLL for TOT method: VK81022B_00-KitKat_4.4.2-Web8064.DLL_for_TOT_method.7z
KDZ: VK81022B_00.KDZ file with MD5 hash inside - KitKat 4.4.2.7z
IMGs:VK81022B_00_4.4.2_all_but_system.img_and_userdata.img.7z
VK81022B_00_4.4.2_system.img_only.7z
VK81022B_00_4.4.2_userdata.img_only-extracts_to_10.7GB.7zOTA: Not captured yet.
11A_01 - Jellybean 4.2.2
KDZ: VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside.7z
IMGs:VK81011A_01_4.2.2_all_but_system.img.7z
VK81011A_01_4.2.2_system.img_only.7z
I confirm that this works.
How is this tool used to flash VK81023A_04.kdz?
D0M1N!X said:
I confirm that this works.
Click to expand...
Click to collapse
Every time I go to thank your post I happen to not be on TapaTalk and over my 8 Thanks limit. Thanks for confirming.
gehx said:
How is this tool used to flash VK81023A_04.kdz?
Click to expand...
Click to collapse
Hi! The page I linked to for [URL=" Flash Tool 2014 - Tools Offline KDZ Flash Rom for LG[/URL] has the directions and screenshots. I know the language is in Vietnamese. Google Chrome (at least on the PC, but I believe on Android too) will translate the word directions closely enough, and for what doesn't get translated because it's text in a picture won't matter because the screenshots make it pretty clear what to do. It's pretty easy, I've done it a couple of times.
I'm not seeing the link for the KDZ file on the page. I used the translate option but maybe I'm blind. I looked around and found this:
https://www.androidfilehost.com/?fid=95864024717073362
Is this the right file?
sefirosu0522 said:
I'm not seeing the link for the KDZ file on the page. I used the translate option but maybe I'm blind. I looked around and found this:
Is this the right file?
Click to expand...
Click to collapse
Yep, that's my file as you can tell by the MD5 hashes matching those in my post. My link is at the end of the line:
Any current and future files for this and other devices will be available in my section on Android File Host.
Click to expand...
Click to collapse
I'll try to make it stand out more. Thanks!
roirraW "edor" ehT said:
Yep, that's my file as you can tell by the MD5 hashes matching those in my post. My link is at the end of the line:
I'll try to make it stand out more. Thanks!
Click to expand...
Click to collapse
Thanks. So basically just to dumb it out. What I should be doing is:
Install the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe file.
Download and install the LG Flash Tool 2014.zip file.
Which files get copied into the KDZ 2014 LG Flash Tool folder?
Connect the phone to the computer. (Are we supposed to use ethernet mode ?)
LGFlashTool2014.exe
Does that sound right? Sorry for the dumb questions. I've set my G2 back a ton of times using the Verizon only method. I've never done it with the tablet and it seems like it's done differently.
Any help would be very appreciated.
sefirosu0522 said:
Thanks. So basically just to dumb it out. What I should be doing is:
Install the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe file.
Download and install the LG Flash Tool 2014.zip file.
Which files get copied into the KDZ 2014 LG Flash Tool folder?
Connect the phone to the computer. (Are we supposed to use ethernet mode ?)
LGFlashTool2014.exe
Does that sound right? Sorry for the dumb questions. I've set my G2 back a ton of times using the Verizon only method. I've never done it with the tablet and it seems like it's done differently.
Any help would be very appreciated.
Click to expand...
Click to collapse
Just going by memory at the moment - I'm at work so I have to hurry. Yes, it all sounds right except the driver. If I remember correctly, the Verizon variant of the G3 uses a different set of drivers, I think it's mentioned on that LGFlashTool2014 page, right after it mentions the one you said. They're probably saying to copy the KDZ to the flash tool folder, but I think you can just browse to wherever you have it on the same PC from the tool anyway.
Yes, ethernet mode.
sefirosu0522 said:
Thanks. So basically just to dumb it out. What I should be doing is:
Click to expand...
Click to collapse
How'd it go?
Sent from my LG-VS985
roirraW "edor" ehT said:
How'd it go?
Sent from my LG-VS985
Click to expand...
Click to collapse
It was flawless. The only thing is that I did the CSE flash and I was able to root but I'm not sure how to get TWRP back. I tried following the thread but ran into issues. I can't remember what it was. So basically I did it twice and now I am fully stock unrooted.
sefirosu0522 said:
It was flawless. The only thing is that I did the CSE flash and I was able to root but I'm not sure how to get TWRP back. I tried following the thread but ran into issues. I can't remember what it was. So basically I did it twice and now I am fully stock unrooted.
Click to expand...
Click to collapse
That's good to hear!
To confirm that your steps of trying to root and put TWRP back on are the same as what I think:
1. Turn BOTH USB Debugging and (install from) Unknown Sources on.
2. Install and run Stump.apk (turn volume all the way down) and choose to brute force. Might take 10-20 minutes.
3. When Stump reports success, reboot when prompted, install SuperSU from the Play store, run SuperSU, install binaries and reboot again.
4. If it is or ever will be your intention for USB Debugging to stay on (for use with Titanium Backup, etc) between reboots, Stump creates a quirk where it doesn't stay selected between reboots. A known fix is to (if I remember correctly) plug the tablet into your PC, select Camera (PTP) mode, then re-select Media sync (MTP) mode. You might or might not have to already have USB Debugging re-checked during this - *shrug*.
5. While on the subject of Titanium Backup, I find that on recent versions of SuperSU (since it's been made Lollipop compatible and includes the "Mount namespace separation" option and it's checked by default), that I have to de-select "Mount namespace separation" in SuperSU's settings in order for Titanium Backup to work for restoring - perhaps backing up or other things as well. Reboot after changing that option in SuperSU.
6. Follow the directions at http://forum.xda-developers.com/showthread.php?t=2726707 to the letter, using the extracted zip of TWRP v2.7.0.1, then flashing 2.7.0.2 from 2.7.0.1 once booted into it.
Note that by "terminal", if I remember right, they mean the Terminal app on the rooted tablet - not Terminal under Linux or Command/PowerShell under Windows. Or it's the other way around, I really haven't done it quite enough times but I think I recall that it wasn't as convenient since I couldn't as easily copy and paste the necessary commands. Sorry for vagueness! Make sure USB Debugging is turned on for this, too.
roirraW "edor" ehT said:
That's good to hear!
To confirm that your steps of trying to root and put TWRP back on are the same as what I think:
6. Follow the directions at http://forum.xda-developers.com/showthread.php?t=2726707 to the letter, using the extracted zip of TWRP v2.7.0.1, then flashing 2.7.0.2 from 2.7.0.1 once booted into it.
Note that by "terminal", if I remember right, they mean the Terminal app on the rooted tablet - not Terminal under Linux or Command/PowerShell under Windows. Or it's the other way around, I really haven't done it quite enough times but I think I recall that it wasn't as convenient since I couldn't as easily copy and paste the necessary commands. Sorry for vagueness! Make sure USB Debugging is turned on for this, too.
Click to expand...
Click to collapse
Thank you. You've been extremely helpful with this. For step 6, are you talking about the instructions over at this thread?
http://forum.xda-developers.com/showthread.php?t=2726707
I thought that was only for 4.2.2.
sefirosu0522 said:
Thank you. You've been extremely helpful with this. For step 6, are you talking about the instructions over at this thread?
I thought that was only for 4.2.2.
Click to expand...
Click to collapse
You're welcome and thank you!
It's what I've used to put TWRP on, with 4.4.2 loaded, and make backups and restores.
roirraW "edor" ehT said:
You're welcome and thank you!
It's what I've used to put TWRP on, with 4.4.2 loaded, and make backups and restores.
Click to expand...
Click to collapse
Thanks again. I haven't tried this yet but I will soon.
I can confirm that the trick worked as noted in the VIET website. Thanks again.
joeminati said:
I can confirm that the trick worked as noted in the VIET website. Thanks again.
Click to expand...
Click to collapse
You're welcome!
I must be the only person who cannot understand the Vietnamese website....even when translated. I've attached images of what I get from Google, once translated. Yes, it's English, but it makes no sense. Any help would be appreciated.
ddodge68 said:
I must be the only person who cannot understand the Vietnamese website....even when translated. I've attached images of what I get from Google, once translated. Yes, it's English, but it makes no sense. Any help would be appreciated.
Click to expand...
Click to collapse
You can have the phone already in Download mode and attached when you start the LG Mobile 2014 tool. Personally (if the Android system is working), I leave the phone fully on and plug it into the PC. After all drivers load, I make sure the USB connection is set to MTP, or on 10B set it to Internet.
When you start the flash process in the tool, it'll reboot the phone into Download mode itself. Saves me some finger-wrangling plus coming from the Samsung Galaxy S2 & S3, I like to keep my presses of the power button to a minimum (because they would go bad on the Galaxy S2 & S3).
Leave all the settings exactly as pictured. CSE flash is what you want almost all the time. It's a complete wipe. Normal is like a dirty flash. If you're ever downgrading from a newer version to older version, you DEFINITELY want CSE, but you almost always want CSE anyway. Make a copy of the KDZ file and put it in the folder you extracted LG Mobile 2014 into. Use the button to the right on the first dialog to direct it to the KDZ file you just put in there.
On the screen with the language. Don't believe any instructions that say to leave it to Korean and that it'll still come out English. It doesn't. That doesn't affect actually flashing the phone but it's nice to understand the status messages, so change them appropriately. The rest is just as pictured.
If you have any specific questions beyond that, please ask.
VK810.4G altev Verizon LG G Pad 8.3 Stock 4.4.2 24A (4/5/2015) KDZ file
Added news that the build 24A KDZ file is available at my AFH link for posterity or at one of the two sources I downloaded it from, listed in the OP.
Thanks for always posting about the VK810. I feel like it gets no love!
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!
Hi all,
Just thought i share a little something i came across from playing about with the phone, I found you can flash any of the ROMs that the HiSilicon Kirin 650 chip set uses. Currently only two phones (5c and P9 lite)
First off you'll need the huawei update extractor http://forum.xda-developers.com/showthread.php?t=2433454 and the ROM from the model of phone you want to flash.
Use the update extractor to extract the boot.img and system.img file from the update.app file, then just flash the files on you phone (fastboot flash boot boot.img and fastboot flash system system.img)
Currently im using a stripped down P9 lite VNS L31 B130 ROM with GAPPS on a honor 5c nem-ul10 chinese phone. Working pretty good, seems fast and smooth. Battery life is not better or worse. Everything seems to be working fine.
Post any questions and i'll try to answer
Cheers
Paul
Liffeyman said:
Hi all,
Just thought i share a little something i came across from playing about with the phone, I found you can flash any of the ROMs that the HiSilicon Kirin 650 chip set uses. Currently only two phones (5c and P9 lite)
First off you'll need the huawei update extractor http://forum.xda-developers.com/showthread.php?t=2433454 and the ROM from the model of phone you want to flash.
Use the update extractor to extract the boot.img and system.img file from the update.app file, then just flash the files on you phone (fastboot flash boot boot.img and fastboot flash system system.img)
Currently im using a stripped down P9 lite VNS L31 B130 ROM with GAPPS on a honor 5c nem-ul10 chinese phone. Working pretty good, seems fast and smooth. Battery life is not better or worse. Everything seems to be working fine.
Post any questions and i'll try to answer
Cheers
Paul
Click to expand...
Click to collapse
Could you post the rom here..and does it support the fingerprint
How did you do that
PalakMi said:
How did you do that
Click to expand...
Click to collapse
First off you need fastboot tools installed and the Huawei Update Extractor downloaded http://forum.xda-developers.com/showthread.php?t=2433454
Download b131 p9 lite rom http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v53991/f1/full/update.zip. There is a later ROM for the p9 lite (b151) but the finger print sensor doesn't work with this ROM
Use the extractor to extract the boot.img and system.img files.
Use trwp to complete backup of phone to the micro SD card. Use trwp and select advanced wipe, wipe everything except the micro SD
Reboot to bootloader
Open command prompt from the folder you have extracted the boot and system images, type the following commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
If you have the 5c chinese phone this rom is great, much more stock feel.
If like me you are having issues with the POB trwp, use the trwp made for the p9 lite
Any question let us know
Great, no questions now so far
Can I port a P9 Lite Rom to an european Honor 5c (without finger print sensor and NFC) ??
minisaurio said:
Can I port a P9 Lite Rom to an european Honor 5c (without finger print sensor and NFC) ??
Click to expand...
Click to collapse
Not sure, don't have the european phone. Once you have a complete backup to revert to, you can't really do much harm testing
has anyone figured out, if this works for european copies of the phone as well?
and if yes, is there a chance to run the CM ROM from Meticulus?
i'd really love to see CM on my phone
Thx nice work
johdost said:
has anyone figured out, if this works for european copies of the phone as well?
and if yes, is there a chance to run the CM ROM from Meticulus?
i'd really love to see CM on my phone
Click to expand...
Click to collapse
Yes, I've got the beta build of CM running on my european 5C - you need to follow the install instructions carefully, and there's a couple of extra steps for the 5C - you need to change the install script as described in this post to get it to install (this goes for the TWRP install too):
http://forum.xda-developers.com/showpost.php?p=69989870&postcount=225
Once you've booted up, to get the camera to work you need to follow the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I've added the camera fix to a boot script so that I don't need to do it after every reboot. Once you've done that the ROM is working brilliantly (though with the same small issues the P9-lite users are having).
Malcolm52 said:
Yes, I've got the beta build of CM running on my european 5C - you need to follow the install instructions carefully, and there's a couple of extra steps for the 5C - you need to change the install script as described in this post to get it to install (this goes for the TWRP install too):
http://forum.xda-developers.com/showpost.php?p=69989870&postcount=225
Once you've booted up, to get the camera to work you need to follow the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I've added the camera fix to a boot script so that I don't need to do it after every reboot. Once you've done that the ROM is working brilliantly (though with the same small issues the P9-lite users are having).
Click to expand...
Click to collapse
Have tried the following from an adb shell, but the camera still doesn't work. It doesn't give the error about not been able to connect, it just hangs and displays nothing.
How did you go about adding the fix to the boot script?
Thanks
Paul
Here's the script I used, there may have been a typo in Meticulous' original:
#!/system/bin/sh
stop HwCamCfgSvr
HwCamCfgSvr hi6250 NEMO &
restart media
If you put those 4 lines in a file called:
/system/etc/init.d/99camerafix
Then make sure it's executable (chmod +x /system/etc/init.d/99camerafix) it should run on startup.
Malcolm52 said:
Here's the script I used, there may have been a typo in Meticulous' original:
#!/system/bin/sh
stop HwCamCfgSvr
HwCamCfgSvr hi6250 NEMO &
restart media
If you put those 4 lines in a file called:
/system/etc/init.d/99camerafix
Then make sure it's executable (chmod +x /system/etc/init.d/99camerafix) it should run on startup.
Click to expand...
Click to collapse
Should i name the file 99camerafix.sh or just 99camerafix?
Thanks again
Paul
Liffeyman said:
Should i name the file 99camerafix.sh or just 99camerafix?
Thanks again
Paul
Click to expand...
Click to collapse
Not sure it matters, but I created it without the .sh
Malcolm52 said:
Not sure it matters, but I created it without the .sh
Click to expand...
Click to collapse
Cool, im using the app solid explorer to give the file permissions. I gave it 777, were i think it should be 775. Let me try again.
Just out of curiosity, did you dirty flash the CM over an earlier version? Just reading some of the posts over on the p9 forms. Users are reporting a smoother rom when dirty flashing
Thanks
Paul
Liffeyman said:
Cool, im using the app solid explorer to give the file permissions. I gave it 777, were i think it should be 775. Let me try again.
Just out of curiosity, did you dirty flash the CM over an earlier version? Just reading some of the posts over on the p9 forms. Users are reporting a smoother rom when dirty flashing
Thanks
Paul
Click to expand...
Click to collapse
No, beta was the first build I tried. Nice and smooth for me, except when night mode is on or occasionally when balanced battery mode is selected - but performance battery mode seems to have reasonable battery life so I'm using that for now.
solved problem already, had some troubles packing the zip together again (mac issues...)
it works fine on my phone now (including camera) thanks a lot for the help!
With a little help.... http://forum.xda-developers.com/honor-5c/help/dev-info-support-honor-5c-cm-13-builds-t3517159
Thanks @Liffeyman.
Gonna try installing ur twrp backup of the p9-lite rom (stripped down of bloat + xtra app goodies). My model is the honor 5c Nem-l51. It's the uk 2gb ram/16gb storage without fingerprint sensor. I realize yours was the Chinese model so I'll let u know how I get on and hopefully it works just as well . Like u says, as long u perform a backup, there should be nothing to worry about :fingers-crossed:
If all goes well with that....I might download the B151 rom and extract the boot&system images and flash them as per your instructions previously. Hopefully that build will be even more stable/fast and the fact that the fingerprint sensor does not work is no problem for me as the uk model has no such sensor ?
Will post the outcome of my efforts in the next few days....
iantechie1979 said:
Thanks @Liffeyman.
Gonna try installing ur twrp backup of the p9-lite rom (stripped down of bloat + xtra app goodies). My model is the honor 5c Nem-l51. It's the uk 2gb ram/16gb storage without fingerprint sensor. I realize yours was the Chinese model so I'll let u know how I get on and hopefully it works just as well . Like u says, as long u perform a backup, there should be nothing to worry about :fingers-crossed:
If all goes well with that....I might download the B151 rom and extract the boot&system images and flash them as per your instructions previously. Hopefully that build will be even more stable/fast and the fact that the fingerprint sensor does not work is no problem for me as the uk model has no such sensor
Will post the outcome of my efforts in the next few days....
Click to expand...
Click to collapse
Just noticed with this, you will need to disable the Wi-Fi privacy police or it'll keep disbaling you wifi. I'll try upload a newer version of this shortly