Related
I am happy with what I have since the new update from Viewsonic.
If I only want to add Google Experience, marketplace, do I still need to go through the process of rooting, installing clockwork and a new UI?
Is there just a simple way to add GE to the Classic UI?
Gapps install
http://forum.xda-developers.com/showthread.php?t=842590
Everyone,
I have had zip luck with this method of installing zapps. Not a dev, but I've been doing this long enough.....
I moved the Recovery file to to /sdcard. Checked for command and command line inside that file All ok to my eye.
Downloaded the gapps file which my WinRAR pronounces a WinRAR/Zip file. So I tried renamein the original update.zip and didn't get any install. So I extracted using winRAR. Still no install.
I tried the permutations as well. Extracted using G-Tablet extract. Still no results.
There must be something I am missing here -- too much holiday cheer or too many crowds or whatever.
Suggestions?!
Rev
butchconner said:
Everyone,
I have had zip luck with this method of installing zapps. Not a dev, but I've been doing this long enough.....
I moved the Recovery file to to /sdcard. Checked for command and command line inside that file All ok to my eye.
Downloaded the gapps file which my WinRAR pronounces a WinRAR/Zip file. So I tried renamein the original update.zip and didn't get any install. So I extracted using winRAR. Still no install.
I tried the permutations as well. Extracted using G-Tablet extract. Still no results.
There must be something I am missing here -- too much holiday cheer or too many crowds or whatever.
Suggestions?!
Rev
Click to expand...
Click to collapse
I HAD to resort to putting on Clockwork Mod 0.8 to get GApps on my G Tablet.
Putting the update.zip on the internal and sd card storage did not work for me either with the newest update installed.
Clockwork Mod is a super easy install - just follow the instructions on how to install G Apps...basically: put CWM on your SD card in it's root (meaning NOT in any directories) and rename it update.zip, put the corresponding recovery directory on the SD as well. I use Winrar as well, I drag the recovery directory right from the file itself and to the SD Card.
Will look like:
Drive: update.zip
Drive: /recovery/command
basically.
Flash it the normal stock way (power and volume +). I press Power and Volume + without even powering off the device, because if the device is powered down and then you start it and miss that first start up, the device WILL delete the recovery/command file and the update won't flash.
GL
I don't officially get to play with my GTab until after package opening tomorrow so I can't do anything today, but I'm trying to line up my to do list. I have never rooted, flashed, or modded anything but am not afraid to play around as long as I don't brick the tablet.
What do you mean when you say "put the corresponding recovery directory on the SD as well. I use Winrar as well"? What is the corresponding recovery directory? What do you use Winrar for? I Googled "winrar" and found " WinRAR is a shareware file archiver and data compression utility developed by Eugene Roshal, and first released in the fall of 1993.[1] It is one of the few applications that is able to create RAR archives natively, because the encoding method is held to be proprietary. " I cannot figure out why it would be needed to load the standard Android market.
MSU_Sparty,
When you do updates (or installs) that have to be flashed onto the internal sdcard, they usually com in pairs of files. You will have an update.zip file that has the update in it (DUH!) -- and accompanying it will be a "Recovery" directory that has a command file in it (The command file has only one line that "calls" the update.zip file.
WinRAR "Zip" utility enters the picture because most of the devs here use WinRAR to package updates. The when they tell you to decompress it, you use WiinRAR and are left with a .zip file to install.
That's the question I had about this update. The Gapp file show to be a RAR package, but when I un-RAR it I come up with no .zip file -- only regular files.
Hope this helps you understand.
Rev
P. S. -- If you are new to this business, take it slow and easy and read ahead on this site and make sure you understand what you are doing. I try to do that, but even with years of IT experience I still mess things up once in a while.
Neoprimal,
Thanks for the tip about CWM. I have two tablets and the other has CWM on it and is fairly modded.
But this tablet I am trying to keep basically stock so I can get updates, etc. and see what the "state of product" is.
As mentioned in my previous answer, I am stumped because I am not getting what looks to be an update.zip file from the Gapp download. When I use WinRAR to decompress the Gapp file, I don't get a .zip file -- only a couple of directories. On the other hand, when I rename the Gapp file update.zip and try to flash it it doesn't work.
Again, thanks for the reply.
Anyone else with suggestions!!!????
Rev
Thanks. What you've written really does clarify the previous post. I appreciate it.
But let me ask another naive question. Why don't the developers create their update programs so they can be installed by just downloading them OTA like most applications? That would sure make it easier for neophytes. I'm guessing that the reason is because we aren't really adding an application but replacing the OS.
I greatly appreciate your guidance and that of all of the folks who use this forum.
Happy Holidays!
For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
when the system reboots, vibrates twice, I see a text rolls a few lines and stops at
usb_function_register. can somebody help.
attached photo showing screen
thanks
I changed the .nbh file to "polaimg-panel3-240x320-2.6.32-froyo-02-09-10_16"
and now it stops at a different line.see attached photo
Come on guys if someone can help i would really apriciate.
NBH file is use when on the three colored screen.
Seems you doesn't have blank screen, that is work, but you need to flash your radio first, or else the installation will not continue, refer to the guide:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
I did exactly what the guide says. I have installed hard spl and the last radio, but nothing different with the results
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
SeanPHTRPW said:
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
Click to expand...
Click to collapse
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
ante0 said:
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
Click to expand...
Click to collapse
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
SeanPHTRPW said:
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
Click to expand...
Click to collapse
It would probably fix it yes, but no boot image or hw/public exist for B110 so I'm guessing it shipped with that build.
You'd have to update, using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't think you can use Firmware Finder as you're probably missing the System Update feature.
Either that one I linked or FunkyHuawei, but Funky cost money to use.
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
SeanPHTRPW said:
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
Click to expand...
Click to collapse
Yes, download base, os and MHA. Extract all to the same folder. You should only have one folder named HWOTA and the files/folders in that. If it extracts to a folder with the same name as the zips, enter the folders and copy hwota folder then go back one folder and paste/merge so you end up with one folder named HWOTA. Easiest way is putting it directly in C:\hwota\, if your windows version allows it. Else place it on desktop. (long file paths or a path containing spaces might make hwota not function correctly).
You need to download all 3 files (fullota update.zip, hw zip and Public zip), easiest way is using firmware finder to download. Either mobile or the pc version. For pc go to the common base tab and search for your model and then download the build you want including public and HW zips.
You only need to download the fullota update, hw and Public zip of the build you're updating to. If you're on b110 and going to update to B172 you only need to download B172.
Rename the files according to the guide (update.zip, update_all_hw.zip and update_data_public.zip), place them in either hwota/update folder or make a HWOTA folder on your sdcard and put the renamed files there.
When running hwota, select script update folder or sdcard update folder depending on where you put the files. Select same model update.
One last question:
Does it have to be FULLOTA, not just OTA?
I am sharing with you here my version of HuRUpdater 0.4 customized for the Mediapad M5. I am not taking any credit here for HuRUpdater, the original work can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279. Please follow the instructions there on how to install it to an SD card. Also unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the as card where you have the other zips. Finally run it from custom recovery.
Your boot loader needs to be unlocked.
HuRUpdater can be used to:
Recover the tablet from a soft brick or bootloop. As long as you can install and access TWRP, it should be good to go.
Restore the tablet back to stock after installing a custom ROM.
Install full OTA updates after unlocking the bootloader, since it appears you cannot install OTAs anymore once the bootloader is unlocked.
Revert back to an older version of the ROM (watch out for XLOADER versions though, make sure that match https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241)
When I was trying to install an OTA after unlocking my bootloader and installing a custom ROM, I found out that HuRUpdater doesn't work out of the box for the Mediapad M5, so I made some minor customizations:
HuRUpdater looks for the volume keys when it starts up in order to read user inputs, and if it doesn't find it, it bails out. I removed that check for the volume keys, so the script will now run without requiring any user input.
HuRUPdater brings its own busybox binary, but it uses unzip trying to install it, which doesn't seem to be available on the M5. I changed it to copy it to the destination instead from the same folder as the other zips.
HuRUpdater checks whether the update will lock your bootloader, and then require you to press a volume key to confirm. Since volume keys are not working and this locking is probably undesired, the script will now bail out if it finds that your booloader may become locked.
NOTE: After successful flash you have to factory reset! And this must be done using the stock recovery, not TWRP!
I have only used it successfully on the Mediapad M5, but but there should be no reason why it wouldn't work on other devices on which HuRUpdate fails when looking for volume keys.
First big thanks for your post! I have a blank Mediapad here without anything any system flashed on it. When I flash HuRU it states an error with the following lines in recovery.log:
Code:
mkdir: 'utils': File exists
cp: bad '/external_sd/CMR-W09C432/hurupdate-binary': No such file or directory
chmod: utils/hurupdate-binary: No such file or directory
cp: bad '/external_sd/CMR-W09C432/busybox': No such file or directory
chmod: utils/busybox: No such file or directory
/tmp/updater[261]: unzip: not found
/tmp/updater[261]: /tmp/utils/busybox: not found
Error with update.zip file. See recovery.log for more details
Updater process ended with ERROR: 1
Any idea on how to fix this?
valko8877 said:
First big thanks for your post! I have a blank Mediapad here without anything any system flashed on it. When I flash HuRU it states an error with the following lines in recovery.log:
Code:
mkdir: 'utils': File exists
cp: bad '/external_sd/CMR-W09C432/hurupdate-binary': No such file or directory
chmod: utils/hurupdate-binary: No such file or directory
cp: bad '/external_sd/CMR-W09C432/busybox': No such file or directory
chmod: utils/busybox: No such file or directory
/tmp/updater[261]: unzip: not found
/tmp/updater[261]: /tmp/utils/busybox: not found
Error with update.zip file. See recovery.log for more details
Updater process ended with ERROR: 1
Any idea on how to fix this?
Click to expand...
Click to collapse
Oh, sorry, think you found a bug and I need to update the instructions. Please unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the sd card where you have the zips and try again.
konradsa said:
Please unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the sd card where you have the zips and try again.
Click to expand...
Click to collapse
Thanks a lot! That worked. It got way too late for me, to come to this idea by my own. Spent several hours to revert to stock firmware and now your version of HuRU seems to to do its work. Currently its flashing Huawei's ZIP files.
valko8877 said:
Thanks a lot! That worked. It got way too late for me, to come to this idea by my own. Spent several hours to revert to stock firmware and now your version of HuRU seems to to do its work. Currently its flashing Huawei's ZIP files.
Click to expand...
Click to collapse
Great, glad it worked for you, I updated the instructions in the first post. The reason I ended up with variant of hurupdater is just like you I found out nothing else works, I was trying to install an OTA.l after unlocking boot loader. When I have some time I will think about how to make this a little more seamless. Let me know if you see any other problems.
konradsa said:
Let me know if you see any other problems.
Click to expand...
Click to collapse
Yeah, so far so good, tablet is now on stock firmware. The flash was successful, after extracting both binaries from your HuRU ZIP to same folder as the other ZIP's including HuRU, flashing the HuRU ZIP itself again and letting it do it's magic. That tool saved me a lot of more hours of working out on how to revert to Stock, while every Huawei way to go and also the Androids way to go have failed. Thanks again! I can also confirm, that the "vanilla" version of HuRU does not work on Mediapad because of the mentioned error of not finding the user input device. Using the specialized Mediapad one instead did it's thing. Thumbs up!
You really saved me!!!! I tried everything before this post... I was about to give up.
Wanted to install multi user function (which has been deleted in the lite version), gone through a series of steps and post including unlocking, rooting, flashing custom bootloader, installing a mask, etc... throughout the way something happened and I got stuck at the TWRP bootloader, nothing worked, everything I tried yielded an error of some kind. This was my salvation! I'll be forever in debt! Tanks a lot!!!!
Hi Guys,
Someone please guide me to flash Android Pie on my G8142. I have already downloaded G8142_Customized VN_1309-2181_47.2.A.0.306_R3C firmware via XperiFirm.
Note -
Locked BL
Currently on 47.1.A.16.20
Thanks in advanced.
Hi, frankly speaking, as your BL is blocked you should/can wait only some few days, it should come over the air very soon
Hi, I also have a locked bootloader, and its still locked after flashing the update using newflasher
all I did was download the VN firmware from xpericheck app that is integrated in flashtool application.
then I downloaded newflasher and it was a zip file, I extracted it, copied all files in it and pasted them in the same folder where the firmware files at, then ran newflasher, and thats it
I have Pie.
Did you delete any of the .TA files prior to flashing?
Hi @madshark2009,
can you provide me any guidelines to do it. I'm new to Sony.
@kw0n2k
No,all I did was simply flash using newflasher
@werty733
here is how i did it:
download xperifirm application:
https://softfamous.com/xperifirm-tool/
when you launch it, select Xperia XZ Premium (the dual one)
then you will get a bunch of fimrwares for different regions, simply select the VN region and it should show on the far right "latest update available" with a number of 47.2.A.0.306
download that to an empty folder of your choice
after download completed, download newflasher from here
https://forum.xda-developers.com/crossdevice-dev/sony/progress-newflasher-xperia-command-line-t3619426
download v13, you will get a ZIP file, copy all files in the file to the same folder where you downloaded the firmware files.
then simply run newflasher from that folder, press n for the first option, and another n for the second option, then it should start doing the magic, after its done, youre set. hope that helped
@madshark2009 thanks, will try your method and update.
@madshark2009 sorry I meant, the new firmware files that you downloaded with xpirifirm, the .TA files in that. correct me if im wrong, but i thought you had to delete them prior to flashing as it might over ride your DRM keys.
@kw0n2k
I dont think so, because i checked my keys stats and they are all ok, no one answered me that officially so i cant give you a concrete answer but i dont think flashing an update resets your drm, we all have been doing it before, i have done it before on oreo and nougat so yah, but get a more officially approved answer from a dev here better for you not to do anything that could harm your device on my word alone
Cheers mate
@madshark2009 Yeah, I converted my G8142 to G8141 cause I couldnt get VolTE in Australia. From what i read, i was under the assumption that .TA files had to be deleted on the new firmware prior to flashing as to not lose your DRM keys. But if you've done it and everything's fine, happy days! I'll just flash normally without deleting any files from now on.
the good @munjeni have exclu .ta in the script no problem for flash with any problem
@madshark2009, it worked perfectly without any issues. but I'm very disappointed there is no Gestures.