Related
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Can you boot to erecovery?
adriansticoid said:
Can you boot to erecovery?
Click to expand...
Click to collapse
I can but it just puts out the message "Getting package info failed"
Filo83 said:
I can but it just puts out the message "Getting package info failed"
Click to expand...
Click to collapse
Please try another version of firmware.
adriansticoid said:
Please try another version of firmware.
Click to expand...
Click to collapse
That is my problem not to know which version to use because three dowloaded EU-versions weren't successful to install. It resulted in an error at 5 % of the 3-buttons-install mechanism.
Filo83 said:
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Click to expand...
Click to collapse
you download the nocheck recoveries from my rebranding guide, download the corresponding firmware by morph (important!), flash both recovery images just like stated in the guide, boot into recovery mode like you would do to boot into twrp, do a factory reset, reboot and insert the microsd with the dload folder from extracted downloaded firmware and boot into force dload mode (vol+ and vol- and power) - the installation should start now and reset everything back to full stock.
Regards
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Filo83 said:
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Click to expand...
Click to collapse
OTA packages cannot be installed via twrp at the moment
you should use stock recovery for that!
Best regards
Grüße zurrück aus Berlin nach Berlin
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Filo83 said:
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Click to expand...
Click to collapse
soooo, if you flashed one of @-=MoRpH=- 's firmwares, your device is back to stock and the recoveries have been overwritten again! I don't recommend flashing OTA updates or other things through the NoCheck version as it is only intended for worst-case cenarios.
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Filo83 said:
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Click to expand...
Click to collapse
extract the firmware and flash manualy using fastboot
thilak devraj said:
extract the firmware and flash manualy using fastboot
Click to expand...
Click to collapse
That is just needed to be done as last resort. Better stick with dload.
adriansticoid said:
That is just needed to be done as last resort. Better stick with dload.
Click to expand...
Click to collapse
he said he got some errors doing dload, so this method works too
thilak devraj said:
he said he got some errors doing dload, so this method works too
Click to expand...
Click to collapse
He must find the right firmware first.
adriansticoid said:
He must find the right firmware first.
Click to expand...
Click to collapse
finding a firmware for huawei devices is a pain in the ass, you know
thilak devraj said:
finding a firmware for huawei devices is a pain in the ass, you know
Click to expand...
Click to collapse
That's why we have Firmware Finder.
adriansticoid said:
That's why we have Firmware Finder.
Click to expand...
Click to collapse
even in firmware finder, it will be difficult sometimes for sone devices
thilak devraj said:
even in firmware finder, it will be difficult sometimes for sone devices
Click to expand...
Click to collapse
Maybe. But they are constantly improving.
adriansticoid said:
Maybe. But they are constantly improving.
Click to expand...
Click to collapse
i appreciate the firmware finder, but sometimes, its just inappropriate
It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo
kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!
Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/
I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.
Well here we go
This is the First Update for the XT2 in a flashable rom
This is for those who unlocked their bootloader and installed TWRP and can not take OTA update on their phones
As most here know ower version of TWRP is not complete and cannot decrypt the /data partition
so unfortunately you'll have to wipe your phone to install this update (sorry)
Note This also Removes TWRP and restores Stock Recovery
Flashing instructions
download and copy the Stock_B130_ XT2_H1711.zip to your ex_sdcard
copy Magisk-v16.0.zip to your ex_sdcard (just in case you need to patch the boot.img)
Boot into TWRP swipe to allow system access
Go to Settings check Use rm -fr instead of formatting
next choose Wipe / Format Data / Type "yes" to confirm
Now choose Home / Install /Select storage Micro sd /Stock_B130_ XT2_H1711.zip and Flash it (watch the flash for any Red Errors)
choose wipe cache and then reboot.
If everything went well you should be on B130 and ready to setup your phone
Huge thanks go to @m0000 for sharing his updated files
If you have any problems you'll need to reflash TWRP and Try patching the boot.img with Magisk or restore your last backup or simply flash my B120 stock rom
XT2 B130 CleanRom
Now that you have a Stock updated phone you may want to remove all the AT&T Bloat
Here's my CleanRom that removes around 350mb of useless junk from the phone.
First you'll need to flash TWRP back to your phone from fastboot
download recoveryV3_Fixed.zip > https://androidfilehost.com/?fid=673956719939832036
and extract it to your fastboot folder
Shutdown the phone
reboot to the bootloader (power + volume down + plugged in to the PC)
and flash it from command prompt with
fastboot flash recovery recoveryV3_Fixed.img
next reboot to TWRP (power + volume up )
Now you can Download the CleanRom and copy it to your ext_sdcard from your pc.
Flashing instructions are the same as above, but you can do a dirty flash by not formatting data like above if you want to keep your current apps
Here's the list of whats removed
Apps deleted from System:
Amazon shopping
App select
Call Protect
Protect Plus
Device Help
Setup & Transfer
CricketWiFiManager
Facebook
Facebook App Installer
Facebook app manager
Gmail
Google Duo
Google Chrome
Google Drive
Google Maps
Google Play Photos
Google Play Video
Google Play Music
Google Text to Speach Engine
Ignite
Lookout
myCricket
Apps deleted from /Data/hwinit/: (If you dirty flashed these will still be on your phone)
Google Editor Slides
Google Editor Sheets
Google Editor Docs
Firefox
Apps deleted from Cust:
AT&T Remote Support
myAT&T
AT&T Hot Spots
Google Talkback
everything in the H1711z folder
The rom includes the patched boot.img from magisk v16 (it's rooted)
This will probably be the only rom I release for this phone because I don't own one.
Awesome. Thank you! So if I flash magisk after I should be able to keep my root then?
clsA said:
Huge thanks go to @m0000 for sharing his updated files
Click to expand...
Click to collapse
No thanks needed. You did all the work I only followed clear directions
freedomwarrior said:
Awesome. Thank you! So if I flash magisk after I should be able to keep my root then?
Click to expand...
Click to collapse
Yes will need to start over ( TWRP & Magisk )
Your phone will be bone stock after flashing the rom
Sent from my LG-H910 using Tapatalk
Alright. I just want to confirm that the update was successful
Out of curiosity I wanted to see if I could relock the bootloader and that finally worked too. (see screenshot) I was never able to do that before on the B120 stock rom so this is great news if I ever decide to sell the phone or just wanna get SafetyNet working correctly.
I went ahead and unlocked my bootloader again and I flashed TWRP through fastboot, Booted into TWRP and flashed magisk v16 in the OP, rebooted and I am enjoying root again with an updated phone.
Thanks again guys!
freedomwarrior said:
Alright. I just want to confirm that the update was successful
Click to expand...
Click to collapse
thanks for the update! All we need now is a @clsA CleanRom for this version
So does anybody know how hard it would be to compile lineage os 14.1 for the elate/ xt2?
903tex said:
So does anybody know how hard it would be to compile lineage os 14.1 for the elate/ xt2?
Click to expand...
Click to collapse
I have no idea but that sure would be awesome! I am guessing it would be a real pain due to the fact Huawei has not released the source code for this phone.
freedomwarrior said:
I have no idea but that sure would be awesome! I am guessing it would be a real pain due to the fact Huawei has not released the source code for this phone.
Click to expand...
Click to collapse
What about the h1611?
MaxxTwo said:
What about the h1611?
Click to expand...
Click to collapse
I am not sure. I don't own that phone.
First post updated
clsA said:
This will probably be the only rom I release for this phone because I don't own one.
Click to expand...
Click to collapse
If you need a guinea pig for future testing let me know. I have one with your CleanRom and a stock unlocked one for any and all future updates.
Thanks!
I really liked this phone, i was actually impressed. I had money to spend on a new budget phone and I was between a ZTE blade spark and this huawei.
ZTE was ok for me because a couple of years ago i bought one of their big phones but their camera sucked a lot of blur and never had focus. sometimes i even had to touch the screen again and again to make it focus, while capturing video. So i gave a shot to this Huawei, went to walmart, they wanted 89 for the phone, told them to check online because it was 69 online and they lowered me the price right away.
then used the huawei for about an hour and damn, the camera is awesome, and the LCD screen is beautiful.
I have to research on how to unlock the bootloader and pay the 5bucks to make that happen.
One thing i noticed is that altho the phone has a 16gb capacity, i was looking at the storage area and you actually end up having something like 7.3gigs free. Is that normal? most of the space is taken by the rom. Your clean rom would help a lot at least to get more space, but how come it only frees 300megs.
and thank you very much for the update. i do know how damn hard it is to update at&t gophones because those assholes only let you update the phone if you have an att simcard inserted that is also activated and you have to be with an IP that is inside USA, and have celular data ON, and sometimes even having all that.. it doesnt even update
ZeldaWW said:
I really liked this phone, i was actually impressed. I had money to spend on a new budget phone and I was between a ZTE blade spark and this huawei.
ZTE was ok for me because a couple of years ago i bought one of their big phones but their camera sucked a lot of blur and never had focus. sometimes i even had to touch the screen again and again to make it focus, while capturing video. So i gave a shot to this Huawei, went to walmart, they wanted 89 for the phone, told them to check online because it was 69 online and they lowered me the price right away.
then used the huawei for about an hour and damn, the camera is awesome, and the LCD screen is beautiful.
I have to research on how to unlock the bootloader and pay the 5bucks to make that happen.
One thing i noticed is that altho the phone has a 16gb capacity, i was looking at the storage area and you actually end up having something like 7.3gigs free. Is that normal? most of the space is taken by the rom. Your clean rom would help a lot at least to get more space, but how come it only frees 300megs.
and thank you very much for the update. i do know how damn hard it is to update at&t gophones because those assholes only let you update the phone if you have an att simcard inserted that is also activated and you have to be with an IP that is inside USA, and have celular data ON, and sometimes even having all that.. it doesnt even update
Click to expand...
Click to collapse
Instructions for DC Unlocker are here
https://r.tapatalk.com/shareLink?ur...share_tid=3780903&share_fid=3793&share_type=t
Sent from my LG-H910 using Tapatalk
@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?
freedomwarrior said:
@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?
Click to expand...
Click to collapse
Looks like b173
You would need to return to stock b130
To attempt the update
Sent from my LG-H910 using Tapatalk
freedomwarrior said:
@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?
Click to expand...
Click to collapse
clsA said:
Looks like b173
You would need to return to stock b130
To attempt the update
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
B130_B173_ATT is the files i sent to clsA for his b130 rom. i've not received any notification on a newer update yet.
@freedomwarrior nice dark theme btw. what are you using?
Thanks
m0000 said:
B130_B173_ATT is the files i sent to clsA for his b130 rom. i've not received any notification on a newer update yet.
@freedomwarrior nice dark theme btw. what are you using?
Thanks
Click to expand...
Click to collapse
Awe ok. That would just be att update being stupid then.
I am using Pure Dark 5.0. So far it is the best dark theme I have come across.
https://play.google.com/store/apps/details?id=sk.hanni.emuithemes.puredark
freedomwarrior said:
Awe ok. That would just be att update being stupid then.
I am using Pure Dark 5.0. So far it is the best dark theme I have come across.
https://play.google.com/store/apps/details?id=sk.hanni.emuithemes.puredark
Click to expand...
Click to collapse
Awesome, i'll check it out. Are the ads annoying? or can disable with a proper ad blocker?
Thanks
m0000 said:
Awesome, i'll check it out. Are the ads annoying? or can disable with a proper ad blocker?
Thanks
Click to expand...
Click to collapse
No ads so far that I have noticed.
My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?
Yes
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?
old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?
old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.
Do I need to root my phone before manually updating using the OTA file?
speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No
Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal
From Orange France is 036, from Google store is 037
Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine