Related
Hi everyone!
Got this Miphone A3 yesterday, and I been searching like a fool after information about this damn phone but it ain't a easy thing to find.
But hey, what do you expect from a cloned iphone
So here's my question:
Anyone sitting on a Miphone and have you done anything with it, most imporant for everything, ROOTED?
Phone info on the phone:
Model number:
A8
Where I bought it, it said A3 on the site (mobino1), same on the battery.
But instead of the iPhone Ui it has the Android Ui pretty sweet that it didnt have the iPhone Ui.
Firmware:
1.5
Don't have Android Market app, but everything looks like Android, also works to install . apk apps tried to install apps from 1.6+ but doesn't work.
Kernel:
2.6.25
Build number:
Linkworld Project .0002_A.1_01r_100129
Been looking for that build number for a while now, don't have any info at all on that one.
Hope some1 here has some info, would be a blessing for me!
EDIT:
I found my way into what i think is the recovery mode, came up a where is said enter flash mode put in usb cable, with red background. Then when i did that, the screen turn blue saying "Enter Flash mode, Begin to flash image..."
Been reading a lot, and i never came up with that kind of "bootloader" just saying that
hope some1 could give me some tips
hi, one of the stores provided firmware from A3, I do not know how fresh. ussd queries are unsuccessful, after ussd calls to hang up. In flash mode turns pressing the upper side volume buttons and switch.
depositfilescom/files/0po3pwcu6 - miphone A3 rom
thanks for that one!
flashed my phone, worked! but it wasnt the same version. this one was with the iphone ui (using ahome)
Model number:
A3
Build number: A3 Project.0001_18r_100411
Seems like my 3G connection does not work with this version. ussd, unsuccessful on this version too, same with previous version.
I was wondering, tried to open the one.bin (flash image) but cannot extract it. Any way to extract the image and try to reconfigure the build?
the phone using "tavor platform" flashing software, anyone know anything about tavor platform?
still trying 2 modify the rom I have, no luck so far.
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
xift said:
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
Click to expand...
Click to collapse
I been trying to extract the .bin file MagicIso can read the file using it "missing files" but can't read the files when extracted. Trying to find a program that could read the rom file, have you done anything to update the phone? Do you have a rom file, if so could you upload it pls?
tried to get the firmware from mobino1 but they just ignore mig those bastards.
Ernest25
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
Click to expand...
Click to collapse
Do you want to flash your phone with the .bin file you already have or do you want to know how to update the phone to android 1.6+?
To flash your phone with tavor flashing software, you need to run the flash program in XP and press "volume up" and "power" on the phone to get to flash mode, then plug in the usb with the flash program open, and it automatically flash the phone.
About updating the phone to a newer version of android I have not a solution.
I been trying to, get info on the hardware so I could try to cook a own rom with at least android 2.0
Cheers
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
xift said:
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
Click to expand...
Click to collapse
Ernest25 said:
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
Click to expand...
Click to collapse
If they just told me straight up, we just sell the phone, we don't have any contact what so ever with the manufacture or developers I would accept it. But this just pissed me off.
I've been asking around on other sites that sells the phone, waiting on answers from them. Hopefully they are more friendly.
Don't downgrade, that was a mistake for me (the rom file azat182 nicely posted).
I tried something yesterday, made a own .bin file with android 2.1 but the flash program wouldn't start with it (parse ini error) so I tricked the flash program that it would flash the one.bin (azat182) rom file.
After it opened I replaced the .bin file with mine. Everything seems to work fine, did every step it should like, root system etc finished 100% when I tried to turn the phone on I couldn't, maybe it didn't know were the power "button" source came from.
The android source was made for an other phone, so I wasn't surprised.
Plugged the usb back in, and luckily the phone connected somehow with the computer so I flash it with the (azat182) rom and I'm back at square -1
but now I think, if I could find out the hardware/drivers on this damn phone it would work to cook a own rom using that method.
Cheers
Oh hey, someone else with one of these phones. I've been messing with mine for a while, started out with the A8 rom (from fastcardtech), and have flashed the A3 rom to the device. I've noticed that the gps works a lot better in the A3 rom than the A8, so it's not much of a downgrade, imo. Recently I've made some headway with an android 2.1 port to the device.
Anyway, this device isn't hard to root. If you adb into it, you can get root from the device by remounting /system as RW and pushing a fixed su binary to /system/bin, or wherever it goes, it's been a while
The MTD partitioning in the Miphone's rom is a big giant mess. The rom is split into 25 partitions, the kernel isn't in boot.img like it's supposed to be, neither are the kernel parameters.
The bootloader is dumb, it doesn't check for signed images. The A3 image and A8 image are both engineering builds.
wow you seem to know a lot about it...
does 3g work for you in the a3 rom? also gps doesn't work for me in a8... so a3 could be a possibility if 3g worked.
how did you adb your phone? I could not connect... the driver just didn't show a phone. although I changed the vendor ids etc...
could you write a short tutorial of some sort? would be nice!
if you are root, couldn't you make a backup of your firmware?
is there a downloadable a8 rom at fastcardtech?
regards, xift
I haven't been able to get 3g working, just edge. I don't think the 3g will work in the US, as none of the carriers will work with just wcdma2100, but I'm no expert on the subject. I've had reasonably good luck with the gps with an app called Maverick, but I don't have a data plan currently, so no agps. With gps alone, it takes about a minute or so in an open area to acquire a lock.
For ADB, there's a driver in the android sdk, but don't bother with it. Instead, the phone's going to show up as a rndis/ethernet gadget. For windows, drivers for this can be found at webos-internals.org/wiki/USBnet_networking_setup, just the .inf is all you'll need; MacOS and Linux will just see the ethernet gadget. Once that's installed, the phone will show up on the PC side as a network interface that will need an IP address; I've been using 169.254.231.10 and subnet 255.255.255.0. Once your network interface is configured, you should be able to run adb connect 169.254.231.168:5555, assuming you've got your android sdk tool set up already. From there, you can adb shell in and poke around. Once you get an adb shell, you'll have a root prompt, but to get 'rooted' so that other android apps can make use of it, you'll want to run adb remount to remount /system as RW, then copy a working version of su over to the phone. I think superuser whitelist comes with one.
I don't usually go to that much trouble, as I end up cycling between the A3 firmware and my Eclair build a lot, and the A3 rom is jacked up to where it's a pain to get a terminal emulator running on it. Adb from my desktop seems to get the most mileage.
Fastcardtech didn't have any useful information about recovery firmware that they had, a release date for an android 2.1 rom, information on the manufacturer, anything.
Wow thanks a lot... I tried with the sdk driver.
port 5555 seemed blocked there although it was obviously responding (took much longer than other ports). Thanks for your help - I'll try that one.
Could you upload your eclaire build?
I don't have much time at the moment because of my bachelor's thesis. But I'd like to see that and maybe I could help a bit. Although I do not have any experience with mobile devices etc.
You may need to mess with the usb debugging option. After flashing to the a3 rom, it's enabled. I remember it being the same between the a8 and a3 roms.
At some point, yeah, I'll my eclair build up. I'd like to at least get bluetooth, gsm and wifi going again before I do. I don't have a rom that you'd be able to flash currently; more like a big pile of build scripts, and install scripts for the android system and ramdisk.
yeah I understand that. You could open a google code project or something.
nice to know that there is somebody working on this.
usb debugging is enabled by default. I'll just have to try again.
thanks for your help so far.
file inf
I not have disk only cd and dvd when I will install the drive without the disk says no drive found I save the file as usbnet-pre.inf
if anyone can help me pls
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
xift said:
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
Click to expand...
Click to collapse
linux complicated for me but thank you I hope good news from you about how root this bastard mobile
I have the A3 if you're interested I can pass to you
Hey Guys -
After recently messing up the root on my A9, I re-flashed it completely this weekend. Although it's unlocked, has s-off, and has been converted to a DEV phone (originally AT&T), the process is tedious for me since I use Internal Storage. Instead of just applying a ROM, flashing recovery (twrp-3.0.2-0-hiae), then installing SuperSU; I must apply the RUU to the phone normally, do the steps above, backup the boot.img from the rooted phone, inject my verity key and another setting from the extracted RUU, then re-flash the boot image - the whole process takes a couple of hours but it's the only way I can format my SD as Internal Storage without issue.
It took me a lot of trial & error to figure out all steps required, but if anyone's interested, I have the process documented...
This time around, I went to a slightly newer build from Dev 1.57.617.52 to Dev 1.57.617.60. The only difference this time than past rebuilds is that I used the phone / installed apps for a while with internal storage on prior to rooting and when I rooted, I used the latest SuperSU - 2.78-SR1.
The Issue
The root succeeded as well as reflashing the modified boot image. Once the phone was booted, I was able to launch SuperSU and in Settings saw all looked good. The only change to settings I made was the usual changing of "Prompt" to "Grant." Root Checker Pro verified it to all be good to go, too. However - in most of the apps I try which require root, they say that my phone is not rooted. When selecting an app in Lucky Patcher, I only have the option to create a modified APK. I also downloaded a Build Prop editor which required root that said my phone wasn't rooted. I had to try two additional / different Build Prop editors before I found one that would work. I've never had this issue before!
My best guess is that this issue is due to one of the below things...
- That I used a newer version of SuperSU than in the past
- When starting the rebuild, I applied the RUU for 1.57.617.52 then went to 1.57.617.60 via OTA when prompted. When rebuilding my boot.img after rooting, I did get the extracted boot.img from a 1.57.617.60 RUU I later downloaded, though.
- That I formatted my SD as Internal Storage and installed many apps prior to actually rooting the phone (Even though I get the error in apps that were installed prior to root as well as ones installed afterwards)
- When creating my modded boot image, I copied over the verity key file but instead of copying & overwriting fstab.qcom, I just directly edited it and added ",verify" (It was at end of 1st un-commented line - I think after "wait"")
- That I used a newer RUU version (doubt it - not a huge jump by any means)
Anyone seen this behavior before? Any suggestions would be helpful. I'd obviously prefer a fix where I didn't have to invest time rebuilding from scratch again if possible. I do still have the originally rooted boot.img I backed up from TWRP prior to modding if it makes a difference. Thanks!
Phone Specs:
- HTC One A9
- Originally AT&T - Now Converted to DEV (Still use on AT&T network)
- TWRP 3.0.2-0 hiae
- SuperSU 2.78-SR1
- s-off / Unlocked
Try uninstalling superSU and re-installing it, and maybe try different versions. I also have a question for you, I see that you still use AT&Ts network, I do too. My question is while on the sense based roms do you experience slow data, and if so do you know how to fix it?
Hi all.
Complete noob here - just wanted to document my journey for resurrecting my daughter's Samsung Galaxy Tab 10.1 tablet to make it usable again.
It had stock rom on it (android 4.0.4) ICS and would not update. Consequently, none of the apps were working and basically it was ready for the trash.
Yes, it's 7 years old, but hey, why throw it in the trash - I thought I'd have a go at rooting and updating. It took me a couple of days but now it's done, it's updated to 7.1 Nougat and working flawlessly.
So here is my Journey - I hope it will help someone. Big thanks to all the Devs out there who have put countless hours into keeping this tablet alive (especially decatf who appears to be very nice person
This assumes no prior knowledge - but be warned - I am not responsible for any damage you cause to your device or if you "brick it". If that worries you do not proceed! By following the below guide, you will be wiping all data from your device so proceed with caution!!
The following worked for me to install Android Nougat on my device - mine is a GT-P7510 but I used the files for the GT-P7500 because when I tried the specific files for the P7510, they didn't work). You might have to get creative here and there to get yours to work!
1) Create folder on your PC / Mac computer desktop to put the required files in;
2) Download the files from here:
- Odin3-v1.85.zip - or do a search for it (this will be for "flashing" twerp onto your device)
- twrp311-20171009-p4.zip
- aosp-7.1-p4-20171005.zip
- P7500-open_gapps-arm-7.1-pico-20170416.zip
- GalaxyTabHacks.com_SuperUser.zip
- USB drivers if you need them are here: http://gizmoword.com/Files/2017/09/24/samsung-usb-drivers/
3. Instal Twerp / Custom Recovery
Before you can install custom software (Nougat etc) you will need to root the tablet. Before you root the tablet, you need to install TWERP which will allow you access to things like backup and recovery etc.
To install TWERP follow this guide and ensure you make backup before proceeding to step 4 - that way you can always go back to your stock image if there are any problems.
https://theunlockr.com/2012/05/11/h...od-recovery-on-the-wifi-only-galaxy-tab-10-1/
NOTE: in the above, it mentions ClockWorkMod (CWM) - However CWM did not work for me, so after installing CWM - I then installed TWERP (they basically do the same thing). I am not sure if you can simply install TWERP instead of CWM - but I installed TWERP over the top of CWM after I had followed the above guide.
4. Root the tablet: The following guide was very helpful to me;
https://theunlockr.com/2012/05/18/how-to-root-the-wifi-only-galaxy-tab-10-1/
and / or this one:
https://forum.xda-developers.com/showthread.php?t=2361571
5. Now you should be ready to install the custom ROM (Nougat)
Follow these guides:
https://www.droidword.com/2017/11/2...10-1-gt-p7510-to-android-7-1-nougat-aosp-rom/
and here is the source code and infos;
https://forum.xda-developers.com/galaxy-tab-10-1/development/rom-android-7-0-nougat-t3471350
6. After following the above, I installed Gapps Pico (very small google basic apps needed for tablet boot e.g. playstore etc)
7. Reboot device and enjoy the setup. Congrats - if all went well you should now be on 7.1 Nougat and can download all your favourite apps.
You can also download and install other software e.g. Chrome browser optimised for your old tablet
https://forum.xda-developers.com/ga...t/app-chromium-m56-optimized-tegra-2-t3550210
Best of luck! Note - I am not developer of any of the above. Kudos to all the devs.
I followed your directions and now play store does not work. Can you help me??
I had to experiment with this because some of the files gave me problems. Aside from the aosp-7.1-p4-20171005.zip which does work some the files don't. I ended up using TWRP version 2.8.7.0. (there is no official TWRP for the GT-P7510. Closest one is called "Picaso" you can search specifically for that one). Whichever GAPPS you decide to use must be an "open" Gapps such as, open_gapps-arm-7.1-full-20181106.zip.
After flashing there were difficulties. Google Play apps won't download or install. Google Chrome or any other Google related apps do not function. There are no developer settings. I even tried to download some Developer Setting apks of which none work. The ROM in itself looks and works good except for those bugs. Camera and flash actually work properly.
X L ENT.
clappertrap said:
Hi all.
For a " Nooby " you have achieved an exellent result. I know a lot about PC's, But the Android OS is new for me. I followed your instructions to the letter. The end result is amazing, what a transformation. This article is very detailed and clear, also very well written. My compliments on a job well done. Thank you.
Click to expand...
Click to collapse
Android 8 or 9?
Great post. I'm also a noob but am going to give it a try since you've laid everything out so nicely. One question I have before getting started is do you think this will also work with the latest versions of Android (8 or 9) rather than Android 7? Thanks much for any advice before I take the plunge!
Peter711 said:
Great post. I'm also a noob but am going to give it a try since you've laid everything out so nicely. One question I have before getting started is do you think this will also work with the latest versions of Android (8 or 9) rather than Android 7? Thanks much for any advice before I take the plunge!
Click to expand...
Click to collapse
My curent opinion is that the Android 7 version works better overall.
thread: Complete Guide to Root and Update Samsung Galaxy Tab 10.1
ok so most of the roms i have tested are overcome v2.3, nougat AOSP 7.1.2 , cwm clean rom v2 and others on the GT-P7510MA and i must say they are awesome builds to try and ressurect the tablet giving life to it but these Roms seem to dont give it the core functionality of playing games or even being able to handle the YouTube app version came in the pico packages or downloaded from the play store, can you developers from GitHub please work on this tablet.It gives constant crashes on playing games downloaded from the app store or opening certain apps other from that you guys would make my day and i would generously donate cause you guys deserve every penny!!! please fix this and we are ok worked for me but everything except games and the YouTube app. People remember most of these developers don't have the tablets, time or cash so we have to test on our tablets, donate so there cup of coffee doesn't runs out and report to them effectively right before there coffee runs out!
I'm still using mine. There were some similar issues I had and if I remember correctly Google play was the main issue with other Google apps. I think and this is going on memory. You would install the ROM then the GAPPS, but not flash both at the same time. Or Google apps would lock up for some reason and give you some issue. So for it to work correctly you flash the ROM. Turned it on and let it load up. Then you would turn it off so you could start up the TWRP recovery, then you would flash the GAPPS.
But Channel 48 put out a video on this if you get confused. This is the easiest way.
https://www.youtube.com/watch?v=rN1Xwskjjfw&t=914s
And the update to 8.1 is also an option.
https://www.youtube.com/watch?v=R_bsR1Az3Sw&t=312s
Thanks @Casper Young I will take a look at the 8.1
It seems Channel48 has a lot of helpful videos. You can search for your exact model on his search page: for example, I am checking on P5110 here:
https://www.youtube.com/c/channel48/search?query=p5110
Hi, there, everyone
I've been trying to download the files needed, but most of the links no longer work. Where can I find the programs needed?
First attempt at making a guide for this, so please feel free to make suggestions on how to clean it up (I feel like it doesn't lend itself well to step-by-step but you're welcome to try).
Great news everyone! (well, all three of us with T-Mobile/MetroPCS in the USA...)
I got VoWiFi to work last night on a couple custom ROMs and successfully made wifi calls. It doesn't require many pieces, but it can be complicated (not just a step-by-step) to get the required pieces into the right places.
- You need a copy of /system/priv-app/CNEService/CNEService.apk from a stock OOS install (I did it with the one from 9.0.3).
To get that, you might be looking at booting into TWRP with the other slot active or temporarily using something like @mauronofrio's fastboot install ROM from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and just flashing the system image to one slot to grab the file before restoring back to the one you had. Anyway, use caution, be sure of which slot you're on and what you're flashing to, and copy the apk from /system/system/priv-app (the path when you're booted from TWRP instead of inside the active system slot). You'll probably have to use ADB commands to push/pull the file directly to/from a computer if you already have a custom rom installed on one slot with screen lock set up, since /data will likely be encrypted and unavailable when you're booted up in TWRP with the other stock slot active.
- You need to be able to install a rando apk as a privileged system app to get this apk back into /system/priv-app/ correctly on your custom ROM.
There are ways to do this manually that involve lots of permissions and editing XML files for privileged app permissions in a couple places, but realistically you're using a custom ROM so you probably have Magisk (otherwise what the hell are you doing with custom ROMs?) so you should just use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 and pick option 3 to install it. You'll need Magisk, a terminal emulator, and some ability to type a file path to use this module.
- You'll need to make sure that your /system/build.prop file contains the line "persist.vendor.cne.feature=1" (AEX doesn't at first, XenonHD does, not sure about others).
We've got the requisite stuff in /vendor already, this just enables the ability to use it. You'll need to have root access and a file manager/text editor (Amaze is FOSS and available through F-Droid, MixPlorer through XDA Labs is also nice, or use TWRP and a text editor that knows unix line endings on your computer to copy things back & forth via MTP and remember to set permissions after, I think it's chmod 644).
Reboot, unlock, and try to make a test call. Successfully got it to work on AEX & XenonHD last night, I suspect it works for Omni and others as well.
Try some more ROMs out and report back below if it works for you too!
Now if only you could fix the Android Auto bug.
I'm totally kidding. This is awesome. Thank you!
Tested Omni and it works too; just needed the APK added/systemized, already has the correct entry in build.prop.
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Any chance someone could upload and share the CNEService.apk? Would make life a lot easier...
brmbjn said:
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Click to expand...
Click to collapse
If it's not working in OOS, I don't know what to tell you. Might just be that the connection isn't reliable enough for it to decide to enable... but I never used OB10; I switched back to stable 9.0.3 after OB9.
Great work!
Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
MarSOnEarth said:
Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
Click to expand...
Click to collapse
First, TWRP doesn't work well with latest stock ROM (QQ1A.200105.032), if you'd like to use TWRP, you should use one level down (QQ1A.200105.007)
Second, there's no more upgrade for this ROM, Essential stopped support it, and Feb update was the last one.
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
Click to expand...
Click to collapse
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
chanh2018 said:
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
Click to expand...
Click to collapse
Ah, yes! My interest in 4.4.166-stock-twrp-mgk181 image is because, a) I failed to get root with Magisk, and b) this is a `fastboot` image that's already rooted (notice the mgk181 part of the name), BUT because it was made in January of 2019, I think (if it does, and I know too little to know that) it contains older version of Android, hence the question about whether I will be able to update from it.
Thanks
MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?).
Thanks
Click to expand...
Click to collapse
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
MarSOnEarth said:
I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
Click to expand...
Click to collapse
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
IronRoo said:
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
Click to expand...
Click to collapse
True. Eventually, a proper custom recovery, like TWRP, might be essential (har, har) years down the road (although I only now am coming down from a Moto X (first gen, 2013) that between AFWall and XPrivacy I managed to keep on stock firmware all along), but now I need to get this phone prepped up for daily use, and that means getting root first of all (and from kt-Froggy's note I shall... I see now where I goofed).
I appreciate your input. Thanks!
kt-Froggy said:
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
Click to expand...
Click to collapse
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
MarSOnEarth said:
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
Click to expand...
Click to collapse
That was my suspicion from how I read your post... ? Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
kt-Froggy said:
That was my suspicion from how I read your post... Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
Click to expand...
Click to collapse
OK, that worked splendidly. Thanks!