Related
Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.
I would also like to know this as well as I am currently on 4.4.2 unrooted, but really feel feel like I want to start and get my Moto G rooted and up and running with all the goody's available on the community, but feel like I should wait for the 4.4.3 rollout before I start going through the whole bootloader unlocking, rooting etc.
So I will check back on this post, and thank you to the thread starter as this saves me starting a similar topic.
Rooted 4.4.2 over here as well. Unfortunately I've had no such luck finding a way to update to 4.4.3 while being rooted. I've been through a plethora of guides and suggestions but nothing seems to be working. I'll end up getting an error no matter what I do.
Don't mean to try and hijack your thread, but I've been trying to flash the .zip for the update with both CWM and TWRP but I get an error every time. Anyone have any ideas why? Do I need to configure root-requiring apps beforehand or something?
ugh...same here! Please someone figure this out!
@Kwala Baerr I was hoping for a quick 1,2,3 Guide! I miss posted the question in the General section, then moved it here. I subsequently find a few similar posts in this section. But your message suggests that you may have already tried them which worries me! Anyway I will have a go tomorrow and post here if I get success.
Sent from my Nexus 7 using Tapatalk
@grahamgo oh yea sorry. Well I've tried just about everything. I think I've narrowed down my problem to SoftKeyz messing up my SystemUI.apk so you might still have a chance. Let me know how it goes though!
grahamgo said:
Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.
Click to expand...
Click to collapse
Put on your phone Us firmware http://forum.xda-developers.com/showthread.php?t=2542219 setup the phone via wifi. Update is about 163mb. After that use Mototool to root the phone and fix the white screen http://forum.xda-developers.com/showthread.php?t=2635706
mabey you can do a beckup of sms https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore and https://play.google.com/store/apps/details?id=com.riteshsahu.CallLogBackupRestore
regards
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
What recovery were you on?
Kwala Baerr said:
What recovery were you on?
Click to expand...
Click to collapse
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.
tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.
tarotsujimoto said:
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.
Click to expand...
Click to collapse
I have just wasted a lot of time...... I tried Philz Touch 6.43.8, no go, then an earlier version, still no go. Then I found a thread saying that there were bugs in later versions, they recommended the use of 6.26.6
I tried it and it works great. However I wasted almost 2 hours finding this out.
castuis said:
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.
Click to expand...
Click to collapse
I appreciate @tarotsujimoto post and I see the logic of this approach. But I too was thinking that it might be less troublesome (but maybe take longer) to go back to factory, update it to 4.4.3 and then re-install Xposed and apps + data, etc using Titanium.
@castuis I am intrigued by your mention of using a custom recovery. Could you please expand on what you backed up and if possible more details on how you did it etc.
I have wasted too much time today getting a working Philz Touch going, (maybe I should have stayed with TWRP!). But I do like the look of Philz 6.26.6 now its working. But will have to put my 4.4.3 update attempt off for a day or so.
Thanks!
Since none of the methods mentioned works for me, I have tried to extract the system.img from the original ROM archive. But how do I mount that system.img_sparsechunk files on Linux? They can not be converted by simg2img or unyaffs either ...
I had no success with any of the "short cut" methods either. I was hoping that @castuis promise of a 10 minute method would come true, but he hasn't been back to expand on his method. I myself reverted the phone to factory, let it upgrade. Then re-rooted, installed xposed and then let Google play reinstall my apps. It's definitely not a quick method. But at least it gave me a clean install. Significant frustration, caused by using Philz touch, but switched to TWRP. Finally did a system backup with Titanium. I thought that was it. Now it looks like there will be a 4.4.4 soon. I'm thinking to ignore it and wait for the next upgrade. @nodh I would wait for 4.4.4 !
Sent from my Nexus 7 using Tapatalk
I've solved my upgrade problem: I've flashed the 176.44.1 (retail Germany, 4.4.3) stock ROM, as described here. Altough I didn't flash the recovery (to restore root with the ClockWorkMod recovey) and didn't erase userdata. Now I've got the upgrade, with all my settings preserved and even rooted again.
So I noticed there's no official thread for this tablet. I went ahead a decided to try and get a thread going for this tablet only. I am strongly considering porting a Rom and possibly a recovery pending requests from users on xda for the device.
To ROOT the Alcatel OneTouch Pop 7 p310a
1. Make sure Unknown sources is checked in Settings > Security > Device administration > Unknown Sources
2. You head over to alephzain's ROOT thread and download the framaroot 1.9.3 apk
LINK To Thread: http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
3. Follow the directions on alephzain's thread. Move the apk to the SD card and install the apk.
4. The apk will then run after clicking "install"
If successful, your OneTouch Pop 7 p310a will now be rooted after a reboot.
To test, after reboot you should see superuser in the list of installed applications.
Also you can download 'root checker' from Google play to verify.
---------
Clock Work Mod Recovery for Alcatel P310a.
DO NOT FLASH THIS RECOVERY ON ANY OTHER DEVICE OTHER THAN A P310A. THIS MAY BRICK YOUR DEVICE.
WORKING RECOVERY PORTED/TESTED BY Shawnj0
DOWNLOAD LINK ==> https://drive.google.com/file/d/0B4Bp38aW17GiOXpKNEdXQXBSbjA/view?usp=sharing
Any questions, comments, suggestions all should be directed to this thread.
Reserved.
Sent from my ALCATEL ONE TOUCH P310A using XDA Free mobile app
Reserved
Sent from my ALCATEL ONE TOUCH P310A using XDA Free mobile app
UPDATE 1/24/2015: CWM NON-Touch Now Available as a flashable img. You can use Flashify or Rashr (both can be downloaded through Google Play once you are ROOT.
Thank you for this. How many tablets has this been tested on ?
It works !!!! Now we need some lollipop on it !
memory swap mod
shawnj0 said:
UPDATE 1/24/2015: CWM NON-Touch Now Available as a flashable img. You can use Flashify or Rashr (both can be downloaded through Google Play once you are ROOT.
Click to expand...
Click to collapse
Hi, thanks for this.
Will a memory swap mod, to make the tablet see the external SD Memory as the internal storage, work with the P310A?
Searched and found this for another Alcatel device:http://forum.xda-developers.com/showthread.php?t=2284347&page=39
Is something like this already available for the tablet?
Will be a big improvement if this can be ported to the P310A, and then have a 32Gb or even a 64 Gb memory card be seen as the internal storage.
Thanks.
I have one of these little tablets from T-Mobile (gotta love free) and love it. Last night I got an update warning but have not installed it yet. Unfortunately there is very little information for them like custom ROMs or custom recovery. I would even like to find the software and files needed to return the device back to stock if there was ever a problem and it needed to be reflashed back to out of the box state. Let me know if I can help as I would love to see more for this awesome little device.
Btw, interesting fact about T-Mobile 4G on these tablets. The base is 10 USD for 1gb of 4G a month. All T-Mobile tablets also come with free 200mb 4G a month one top of that. If you have the highest plan at T-Mobile (80 USD a month, unlimited everything including 4g, no drop back to 3g at all) then the tablet actually gets 5gb a month of 4G for the 10 USD instead of 1gb.
..
Just installed the latest update from T-Mobile for the p310a and framaroot 1.93 no longer roots it. Damn.
Try this :wwwDOTmgyunDOTcom/m/en
It rooted my tablet and 2 others. It will install a "kinguser" superuser app. Download clockworks superuser from the play store.
Then disable kinguser and allow clockworks superuser to do its job.
TheEditor said:
Just installed the latest update from T-Mobile for the p310a and framaroot 1.93 no longer roots it. Damn.
Click to expand...
Click to collapse
Can you please share what is on the update?
Find out the update is still on 4.2.
According to the Tmo support site is to improve battery, camera flicker and freezing.
That is about all I see in the update. The version is still the same and I have not seen any real difference personally. Kind of wish I hadn't updated.
Btw, thanks for the recommendation. I am rooted again, woohoo.
---------- Post added at 02:46 AM ---------- Previous post was at 02:00 AM ----------
Well, I am rooted but the only SU that will work is the installed KingUser, no others will work for me.
I have the same tablet, but the P310X, not the P310A variant. Is it safe to flash the CWM recovery? I tried booting into this recovery without flashing by the fastboot flash command, but nothing happens after the transfer, the device won't boot into the new recovery.
After a little searching, it seems to me the two varians only differ in the supported cellular networks and frequencies.
Ok so I rooted this device with kingo at first. I kept have su binary issues. I installed cwm and tried to update su binary through there. I tried booting into recovery using quick boot. My tablet is stuck on tmo screen. Hard reseting takes me back to cwm but I have no backup yet , had no time to even make one. Does anyone have one by chance or a way for me to boot back up through cwm?
Recovery flashed successfully and looks great but, no partitions will mount and I cannot flash any .zips. Anyone else having issues?
I flashed the recovery but when I backed up my data and started getting "unfortunately settings has stopped" error
I did all alternatives and was forced to wipe it clean. But when I tried to restore it kept saying MS5 is not found.
So I am screwed now cause although it did clean it, the settings issue is still there and it will not let me open the wifi /buletooth settings/
keeps crashing and sometimes reboots. So I just want to revert back to the original factory firmware.
Does anyone have the original firmware??
Possible lollipop rom?
shawnj0 said:
So I noticed there's no official thread for this tablet. I went ahead a decided to try and get a thread going for this tablet only. I am strongly considering porting a Rom and possibly a recovery pending requests from users on xda for the device.
To ROOT the Alcatel OneTouch Pop 7 p310a
1. Make sure Unknown sources is checked in Settings > Security > Device administration > Unknown Sources
2. You head over to alephzain's ROOT thread and download the framaroot 1.9.3 apk
LINK To Thread: http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
3. Follow the directions on alephzain's thread. Move the apk to the SD card and install the apk.
4. The apk will then run after clicking "install"
If successful, your OneTouch Pop 7 p310a will now be rooted after a reboot.
To test, after reboot you should see superuser in the list of installed applications.
Also you can download 'root checker' from Google play to verify.
---------
Clock Work Mod Recovery for Alcatel P310a.
DO NOT FLASH THIS RECOVERY ON ANY OTHER DEVICE OTHER THAN A P310A. THIS MAY BRICK YOUR DEVICE.
WORKING RECOVERY PORTED/TESTED BY Shawnj0
DOWNLOAD LINK ==> https://drive.google.com/file/d/0B4Bp38aW17GiOXpKNEdXQXBSbjA/view?usp=sharing
Any questions, comments, suggestions all should be directed to this thread.
Click to expand...
Click to collapse
i have this device and i have searched pretty much everywhere for a mod. can you show me how i could get a lollipop mod ( if there is one available). its a pretty nifty device and it i'm hoping to get the lollipop experience on it. Thanks.
Crying on the inside
SO, i did the absolute unthinkable of unthinkable actions. i attempted to flash what was purported to be a POP 7 MIUI port, and the damn thing crashed on me. To make matters worse, the backup with CWM failed when attempting to back up /system. Anyone manage to get it to work?
Sir Webb said:
I flashed the recovery but when I backed up my data and started getting "unfortunately settings has stopped" error
I did all alternatives and was forced to wipe it clean. But when I tried to restore it kept saying MS5 is not found.
So I am screwed now cause although it did clean it, the settings issue is still there and it will not let me open the wifi /buletooth settings/
keeps crashing and sometimes reboots. So I just want to revert back to the original factory firmware.
Does anyone have the original firmware??
Click to expand...
Click to collapse
I have it
SuperUser666 said:
SO, i did the absolute unthinkable of unthinkable actions. i attempted to flash what was purported to be a POP 7 MIUI port, and the damn thing crashed on me. To make matters worse, the backup with CWM failed when attempting to back up /system. Anyone manage to get it to work?
Click to expand...
Click to collapse
Did you ever get this working? I have this tablet rooted, but no recovery...
I don't mind giving either of you my backups from titanium
Hello all, I am relatively new to the android rooting scene. I have looked into it before but always became discouraged by the amount of different informaton from different sources. I am a little bit familiar with flashing processes as I used to install CFW onto Sony PSP and PS3 devices. However there's a lot of new terms that I am soaking in and trying to figure out what it all means when it comes to phone rooting. I am currently using a Sprint Galaxy S5 Sport running Lollipop 5.0, with build number, "LRX21T.PVPU2BOH1" and Kernel "3.4.0-4445742 August 6, 2015". I've been looking around and every time I think I find a reliable source for rooting I see a disclaimer saying only works with certain build numbers, and mine doesn't seem to be any of the builds I have seen. A Google search of my build brings a total of 5 searches wit no information regarding it. Anyways I am looking to successfully root my device, install a working recovery mode, and if possible, install a ROM. I have searched through threads and scrounge up some information about the SM-G860P but not enough for me to go through with the process with 100% certainty of success. I also hope that this thread can be useful to other SM-G860P users and a one stop shop for all the files needed to safely root, backup, and restore files. Basically, I know it can be rooted using Odin and CFAR on Lollipop 5.0. But the steps after that I am unsure. Do I install TWRP, CRM, what ROMS can I install, what kernel do I need. Thanks in advance to any developers or members who can provide all the proper links to attain my goal.
I have a very similar build. I have successfully put on root, and CWM recovery, but, any attempts at custom roms have failed (assuming due to kernel), and I am unable to get tethering working, despite having root.
Followed http://forum.xda-developers.com/sprint-galaxy-s5/development/recovery-cwm-s5-sport-sm-g680p-t2907945 for recovery.
I rooted following something like: http://www.android.gs/root-sprint-galaxy-s5-on-android-5-0-lollipop-os/. The key was using the auto root, then flashing the update via CWM. Had to make sure CWM was installed, as flashing using stock recovery caused issues.
Tried to flash CM12 from:
http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-adulterated-cm12-5-0-2-t2987665
But ended up in a boot loop.
I'm also scared to put xposed framework on, since most saying need to use a custom rom or else phone will bootloop.
Using most of the methods to tether, (like adb settings global or sqlite), tether_dun_required keeps resetting back to 1 after turning on tethering, so, I still haven't found a solution to that. I'd love to hear from anyone who's got tethering working on SM-G860P with lollipop.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
Hi Everyone,
Honor View 10 is going to be launched soon in my country (this end of month). I have considered it as my next phone upgrade. Before, I have looked upon N*k** 8, but that subforum is dead already (no UBL, no root, nothing to see). I am currently waiting for X***mi RN5P which still have no news about the official launch here (probably another 3 months). But they decided to do some twist, by disabling the UBL ability for the phones they launched officially here. Kinda ironic.
To make sure I can live with the phone as it, I have to confirm several things first :
1. Does the phone has native VoLTE that works out of box without installing any additional app? I read from several thread here, it has support Dual VoLTE, but still doubt. I have checked some other phone who said they support VoLTE but in reality doesn't work. My main carrier used to be CDMA carrier, which has completely moved to 4G (only). So we can only call/sms thru VoLTE. If someone can post the screenshot of the VoLTE call setting, or "Enhanced HD" setting or similar, it will be a great confirmation. (I don't need the video call, only voice call/sms).
2. I am using Automagic (tasker alternative). I am quite active in that forum for several months. From there, I read a lot of incompatibility or something won't work, mostly from Huawei Devices. It seem the aggressive battery saving from the ROM has been disrupting Automagic from running properly. Is there anyone here who use Automagic/Tasker or similar automation app and found problem specific for Huawei devices, specificly for this View 10? (using stock ROM). I mean something like wifi scanning or location which work in Phone A or Phone B using the same android oreo 8.0; but doesn't work in View 10. If only minor problem, I can accept it.
3. Is there anyone having problem with the UBL process? X***mi just pull it tricks by kinda banning all user from my country to unlock the Bootloader. (error 86023:hardwareID) I am afraid of the same, as I need root. But I don't need to change the ROM.
Best case
If all the problems are solved and I have bought the device; I am going to root and install TWRP as usual. But I will stay on Stock ROM, most custom ROM still have problem with VoLTE. I might use LineAge or AOSP-ish ROM if there is any and has solved most bug. This is the step that I am going to do after I bought the phone.
1. Unlock the bootloader. https://forum.xda-developers.com/honor-view-10/how-to/honor-view-10-bootloader-unlock-t3749426 Result : Bootloader Unlocked
2. Install Magisk (latest is 16.2) via fastboot https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280 Result : Root achieved, Magisk Installed
3. Then proceed on to backup the original recovery https://forum.xda-developers.com/showpost.php?p=75630973&postcount=3 Result : Original recovery backed up. I am thinking to do additional backup by using partition backups, but don't know if it works.
4. Flash Official TWRP https://forum.xda-developers.com/ho...recovery-twrp-3-2-1-0-touch-recovery-t3752397 Result : recovery changed to TWRP.
5. Backup all available partition. Result : all partition backed up, except /data. Since FBE still won't work
After the ritual, the phone will be rooted, Magisk installed, TWRP, and have full backup of all backup-able partition from TWRP and the original recovery. Xposed still won't work, so need to find alternative in Xposed. I mostly use Gravity box and App Settings Modules. Maybe there are alternatives available in Magisk. (haven't research much about it). To backup app's data, the only choice is Titanium Backup then, since /data partition can't be backed up in TWRP. We don't have stock firmware yet available, so need to be careful with the modification.
Do I miss something in my steps above?
Thanks for the answer in advance. And sorry for the long post.
Regards,
Desmanto