Related
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
9000RPM said:
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
Click to expand...
Click to collapse
Screen Shots Please....
I just updated last night. Everything running smoothly. I had the phone rooted previously but the one click root app got removed in the update process. If anyone has success rooting after the upgrade, I'd love to know about it.
I upgraded this morning and I've been having lots of issues with my installed apps, like Facebook, Messenger, Whatsapp and more, and of course I lost Root which was previously accomplished by KingRoot which doesn't work anymore.
Also I noticed that during the update process, particularly while flashing the firmware, it was flashed using my TWRP recovery and afterwards it got removed.
I'm sure that if I start fresh by performing a factory reset, all will be fluid and in working order, minus TWRP and Root of course, at least for the time being.
All in all, the update to Mashmellow seems to be awesome, some new features.
Cheers!
I'm having issues with the update. It downloads just fine and when I go ahead and try to install...it just spins around on "unzipping" and then proceeds to restart..or turn off for that matter. The phone turned off...I didn't do anything to it just let it sit there for a while and then I saw the charge icon show up (the one you see when the phone is off and charging) at which point I started the phone up. The phone did not update and I can basically repeat the process. There is 4.30 GB of space free and no SD card. What do I do?
EDIT:
So I tried again, kept at it and it eventually worked. Updated just fine but now there are doubles of all folders in the phone. When I plug it into my computer, all the folders (Music, Download etc etc) are showing up twice with the same contents in the each of them...
What...is...going...on?
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
disChapo said:
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
Click to expand...
Click to collapse
Yeah, mine is working flawlessly after a factory reset! Much improvement compared to Lollypop!
Anyone found a Root for Marshmellow yet?
Unless Blu changed something other than the interface I'd guess TWRP won't be working on MM anytime soon. It's a problem seen in the Gionee phone and I would expect the same to happen to the Blu. As for root and a custom recovery (although not a great one) you could try following these instructions: https://forum.hovatek.com/thread-15270.html
I've played a bit with the Gionee Marshmallow firmware on my Vivo XL during the past month or so, and one thing that really bugs me is that it seems to be shipping with a kernel that is way older than it should be on an MM release. And the OTA service that is known for leaking info also seemed to still be present in the updated firmware.
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me. And, if you guys manage to get root, check if AdupOTA is still lurking in there.
batoussai said:
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me.
Click to expand...
Click to collapse
Kernel Version: 3.18.19
Build Number: MRA58k
Custom build version: BLU_V0030UU_V07_GENERICM14-11-2016
Does anybody with TWPR/root upgraded to official 6.0 successfully? What's exact procedure/steps?
I have my Blu Vivo XL with TWRP now, in last (small) OTA update a few months ago, I tried flashing back to original recovery and rom, but still failed OTA.
Here's an attempted TLR of what has happened
Tried installing LineageOS. Got Error 7. Tried a bunch of things to make it work like editing the updater-script and things like that but it didn't work.
Then I simply wanted my phone to work again. Installed Clean Stock ROM + Stock Recovery straight out of OnePlus webpage. Now I have permanent dm-verity error (tried going back to 4.0.2, disabling dm-verity via fastboot commands and restoring 4.0.3) and still appears.
So yeah, basically that.
I messed up like a month ago too, bricked the OP3T and managed to revive it with a chinese program.
Any ideas on why I can never manage to install LineageOS?
EDIT: After the last factory reset, the phone wouldn't find any wifi network. After an hour or so, it found my wifi and got a 92mb update that fixed the dm-verity error
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
sakumaxp said:
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
Click to expand...
Click to collapse
I just received the 4.1.0, going to try again tonight. Hope it works
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. A direct link to kernel sources can be found here. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
https://wiki.lineageos.org/devices/sake/install
Download:
https://download.lineageos.org/sake
Reporting Bugs:
DO NOT report bugs if you're running a custom kernel or you installed Xposed.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless.)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thank you for that!!
Pre install of stock android 12 needed?
thanks pro
NisseGurra said:
Pre install of stock android 12 needed?
Click to expand...
Click to collapse
Yes, I'll update description to clarify that. If you try and boot into the LOS 19 recovery with Android 11 firmware it will crashdump.
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
eVen123 said:
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
Click to expand...
Click to collapse
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Adaoh said:
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Click to expand...
Click to collapse
Nothing was ever uploaded to it. I haven't made a build without GMS yet.
eVen123 said:
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Click to expand...
Click to collapse
Updated OP to specify the exact version you need to be on [31.1004.0404.81 (or .71)]. Basically just a public release, not a beta.
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
eVen123 said:
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
Click to expand...
Click to collapse
SELinux isn't enforcing because it's one of the first builds right after a bringup.
Put up a new build with some things resolved, notably SELinux is now Enforcing.
I also switched from stock's prebuilt NXP NFC stack to the open source stack. Anyone who is able to make payments with Google Pay or something like that, let me know if it works.
Added a vendor_dlkm partition to hold vendor kernel modules so you can flash a different vendor regardless of the kernel situation as the modules are no longer held there.
Enabled automatic brightness by default.
Fixed night light by correct PIxelworks device detection.
Switched from QTI BT to AOSP BT until it gets merged.
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Uploaded a build without GMS for people who don't like using GMS.
Tap to wake functional?, installed "no gms", runs nicely
ZVNexus said:
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Click to expand...
Click to collapse
Working great so far. I am having one issue where once I unlock the phone (and the screen gets really bright to read the fingerprint), it stays bright. If I tap the brightness slider, it doesn't move but it adjusts the brightness to what it should be according the slider.
This is the case with and without Adaptive Brightness enabled.
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
No, Tap to Wake does not work.
Mecallie said:
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Click to expand...
Click to collapse
Same happenning here, booting to Android12 ramdumps me... I was able to update before but now it does not work... Also the flash script gives me an error that it did not give me before.
Code:
Project ZS590KS matching success!
Start erase misc
Erasing 'misc' FAILED (remote: 'Erase of misc is not allowed in snapshotted state')
fastboot: error: Command failed
misc flash failed!
Press any key to exit the script.
. I guess I will be staying on Android 11 then...
EDIT: Ran fastboot snapshot-update cancel like you did, and now the raw image file script works to reset the phone. Very weird. Also thank you so much, without your post, I would have never figured a way to make the script work again I am so glad you posted this
EDIT 2: After running the script (And everything working and passing) and getting everything back to normal, I was able to install Android 12 like I normally would without ramdumps
I have a pixel 5. I've only ever been on the stock image, and have never unlocked/rooted. After the June security update it became really unstable - every time it rebooted a different app or part of the OS would start crashing. Then suddenly I got a message on boot that the device is corrupt & cannot be trusted.
I'm assuming something important got corrupted during the security update, so I downloaded the June 2022 OTA image, and sideloaded it through ADB. This took 3 goes - the first time it said that ZIP signature verification failed, then it said that kDownloadOperationHashMismatch, then finally it worked fine. I did exactly the same thing each time, with the same image, so this again seemed to be just random errors.
Either way, the sideload finally worked, and fingers crossed it's seemed more stable again now. However I still have the 'Device is Corrupt and cannot be trusted' at boot. Any ideas if I can fix that easily, or do I need to unlock, reflash, and start from scratch again? Is it an error I need to worry about, or do I just live with it?
Spoke too soon, apps have started crashing again. I'm worried that the random nature of the crashes indicates some failing storage or memory, but I'll try unlocking and doing a full reflash to see if that fixes things, unless anyone has any better suggestions.
Download the OTA from Google in a browser on a computer and verify the hash, then extract it and do a flash that way. Inside the ota is an update and a flash-all.bat/sh file that you should use to install that way.
Report back after this.